Level 01
Observe
It reads, interprets and shows you. Dashboards, status boards, reports, alerts. It tells a person; the person decides.
If it is wrong: you see a wrong number and I fix it.
What I Build
These are not products off a shelf. Each capability below is built into the way your organisation already works — then combined into the smallest system that solves your actual problem.
01 — Dashboards
Most dashboards fail because they show what the tool could measure rather than what you actually decide on. I start from the questions you ask every Monday morning and build backwards from there.
Every widget is configurable, every view is scoped to a role, and the whole layout is yours to rearrange as the business changes — without calling a developer.
02 — Live Tracking
The expensive problems are rarely the ones you can see. They are the order that quietly failed to sync at 2am and surfaced as an angry phone call three days later.
Status ops closes that gap. Every job, order, asset and integration reports its own state continuously — and when something drifts, the system tells the right person before the customer finds out.
03 — Marketing Operations
Most small teams market in bursts — a push when someone has a spare afternoon, then months of silence. The reason is never the idea. It is the labour: the segmenting, the writing, the scheduling, and the checking of what actually worked.
So the system does the labour. Overnight it watches behaviour, builds the segments, drafts the copy in your voice and queues the campaign. In the morning you look at what it prepared and decide what goes out. Nothing reaches a customer that a person has not released.
Want it to send and move spend on its own? That is Level 4 — available, with a soak period, spend ceilings and a kill switch, and priced accordingly.
04 — Communication
A shared inbox is a single point of failure wearing a friendly name. The message that matters most is usually the one that arrived while the person who checks it was on holiday.
I put every inbound channel through one policy-driven pipeline: understood, classified, routed to the right person, and escalated when it is urgent — with a reply already drafted and waiting, and the whole thread recorded against the customer.
05 — Data Pipelines
When two reports disagree, everything above them stops being trustworthy — and someone starts keeping a private spreadsheet. That spreadsheet is where good decisions go to die.
Pipelines move your data on a schedule and on events, validate it before it lands, reconcile the disagreements, and leave a trail from any figure back to the record it came from.
How much it does on its own
“AI-powered” covers everything from a chart that updates itself to software emailing your customers unsupervised. Those are very different risks, so I price and build them differently, and I tell you which one you are buying.
Level 01
It reads, interprets and shows you. Dashboards, status boards, reports, alerts. It tells a person; the person decides.
If it is wrong: you see a wrong number and I fix it.
Level 02
It collects information correctly the first time. Job capture on a phone, validated intake forms, documents read into a record you confirm.
If it is wrong: the person entering it sees it before it saves.
Level 03
It does the work and puts it in front of a person to release. The invoice is already typed and waiting. The reply is drafted. You glance and click. This is where most people stop.
If it is wrong: somebody deletes a bad draft. Nothing left the building.
Level 04
It sends, spends and posts on its own. Gated — built with a soak period, provider-level spend ceilings, a full audit trail and a kill switch anyone in your office can use.
If it is wrong: a customer sees it. That is why this one is priced and controlled differently.
Most of the pain in a business is labour, not clicking. The office manager re-typing forty jobs a week into the accounting system does not need invoices issued automatically — they need the invoice already sitting there, filled in correctly, waiting for a glance and a click.
That is Level 3, and it is where almost all of the hours come back for almost none of the risk. I will build Level 4 when you genuinely need it, but it runs in draft mode first so we both see its real error rate before anything is let loose — and plenty of people get to the end of that and decide Level 3 already did the job.
Finding the right fit
Described in your words, not in software terms. “Our techs waste an hour a day on paperwork” is a better brief than “we need a workflow engine” — because it tells me what success actually looks like.
A real number, even a rough one. It is not a negotiating position — it is the constraint that decides whether we build the whole system now or the highest-value slice of it first.
Physical networking and IT work is billed separately. On-site cabling, hardware, network installation and similar physical IT functions are an additional charge, and may involve third-party vendors. Any such costs are quoted and agreed with you first, then reflected on the bill — nothing appears as a surprise.
That is the normal starting point, and working it out is free. Tell me what is slowing you down and roughly what you can invest — I will tell you which of these actually helps.