I come inside your business and find exactly what to fix.
Most businesses don't need an agency or a platform. They need someone technical to actually look: at the systems, the subscriptions, the double-handling, the decisions that quietly eat the week. So that's the product. I come in, work hands-on alongside the people doing the work, and diagnose what's really going on.
Every decision in the business gets classified: code should make it, AI should make it, or it stays human. The goal is the lowest-friction version of your business for the people actually in it.
You deal with me directly. Nothing is outsourced.
I watch the business run
Inside the business, shadowing the real work, not the org chart. I sit with the people doing it while a real job runs through, and I write down every step, every tool, every subscription, every copy-paste. It ends with the inventory: every system you run, every recurring task, what each costs in time and money.
I map the decisions
The inventory gets traced into workflows: every step, every decision, who makes it and what it needs. Each one classified: code decides, AI decides, or it stays human. We walk the draft together before anything is final, so wrong assumptions die in the room, not in the report. It ends with the decision map.
I design the ideal shape
Your workflows rebuilt on paper into the lowest-friction version for the people in them, and every change itemised. The pattern is the same at every step: the machine fetches, assembles and sends, and the person decides. It ends with the plan: the map, the redesigned flows, and what each build would involve.
A discussion, not a report drop
The plan shows the most automation I can responsibly conceive. Some steps you genuinely won't mind doing manually, so we go through it together and you pick what you care about. No all-in decision, no open meter.
I would not automate a decision about a price or a person in the first ninety days, and probably not ever. Those stay with whoever knows the customer.
The same annoyance, many times a week, to several people.
That is what I am hunting for, because it is where the time actually is. Before I have seen your business these are the shapes I expect to find, and the first week usually changes the list.
- Anything re-typed from one screen into another. Re-keying is where the errors come from as well as the time, so fixing it pays twice.
- Anything assembled by hand from several sources on a deadline. A quote, a report, a pack that goes out to a customer. The pieces are all somewhere already.
- Routine things that arrive as a message. Enquiries most of all, because those can be handled where the message lands without waiting on anyone's integration.
- Work nobody can see the state of. Often the fix is not automation at all. It is one view that tells you where everything is.
- Anything an admin or offshore team does that follows a fixed pattern. That frees them for the work that actually needs a person.
So what have I missed? You almost certainly know one already, and I would rather hear it than guess at it from out here.
One spine, not a drawer of tools.
The risk with a person like me is that you end up with forty clever one-off tools that only one person understands. So everything I build has the same four parts, whether it is a two-line job or the thing your week runs on. That sameness is what makes them add up to one system instead of a drawer, and it is the part I push at constantly.
A form, an email, a document, the clock reaching a time, someone asking for something. Every way in is declared, so nothing can start off the books.
Everything between arriving and acting is decisions. Working out which kind each one is, is most of the job, and it is what I would be doing in your business from the first week.
The message goes, the record updates, the job gets booked. This is the only part that touches anything real, so it is the part that stays switched off until it is deliberately armed.
Every decision belongs to one of three
The rules that never vary. Same situation, same answer, every single time, and you can read the rule for yourself.
The reading-and-judging calls a rule cannot cover. It answers in a fixed shape, and when it genuinely cannot tell, it has to say so rather than guess.
Price, people, risk, anything you would want to sign off. It stops and waits for you, for as long as that takes.
The decisions vary. Everything between them does not.
Code, AI and a person are the only three things allowed to decide anything. How the work actually moves between those decisions is defined in code, and it does not vary: every step writes down what it did at the moment it did it, and none of it is edited afterwards. So any action can be traced back to the thing that decided it, and to the information that thing actually had in front of it at the time, rather than reconstructed later from memory.
It is also where the systems you already pay for get synced in, including the ones that will not open up, so what they know sits with everything else instead of staying locked inside a tool you cannot get at.
The rules I hold to while building it
- Work only moves from a person to a machine once the rule is actually known. That usually means watching a person do it enough times to see the rule, and it is why the first weeks look like shadowing rather than building.
- Failure is loud. A thing that quietly does nothing is the expensive kind, so anything that can die is built to announce it. Nothing that has not been checked is ever recorded as done.
- Fixes go at the cause. If the same kind of failure turns up a second time, the first fix was at the wrong level and I go further up rather than patching it again where it showed.
- Closed platforms sync into the record rather than holding it. That turns the system your data is stuck inside into one more tool you could replace, and a software bill that grew a line at a time becomes small cancellations instead of one risky migration. Nothing gets cancelled until its replacement has run on live work in parallel.
- Everything is written down. Every piece ends with its state on paper, on the assumption that whoever picks it up next knows nothing. That includes you, if you ever want someone else to run it.
Want to learn more? Contact me.
There's no set package here, because no two businesses run the same. Text or call me, tell me what you run, and we'll work out what coming inside your business should look like.
And if you want it to go further: some businesses keep me on after the builds to own their whole tech and AI side long term. That's a conversation we have after the work proves itself, not before.
If you would rather see something than read something: pick one job in your week that shouldn't need a person, and I'll build a rough working version of it this week so you can watch it run. No charge and nothing owed either way. I'd rather be judged on something running than on a document.
You deal with me directly. Nothing is outsourced.