How this works
Let's find what isworth fixing first.
Most businesses have two or three jobs quietly eating a day a week between them. I go looking for those, work out which one is worth the most to you, and build the thing that takes it off your team's hands.
How I help
Three steps, and you can stop after any of them.
- 01
We find where your time is going
A week spent watching how work really moves through your business — not how the process document says it does.
You end up with a short, ranked list of what is costing you, and roughly what each one is worth fixing. Most people are surprised by what comes top.
- 02
We fix the one that matters most
Not everything at once. The single change with the best payback, built properly and tested against your real data.
You get the hours back straight away, and you can see it working before we talk about anything else.
- 03
You get your week back
It runs on your own systems, quietly, with a nudge to someone if it ever stops.
That is the point of all of it: fewer hours in front of a screen doing admin, and more spent with the people who pay you.
What gets better
What it looks like a few months later.
- Your team stops doing the same thing twice
- The hours that went into copying things between screens go back into actual work.
- Things stop slipping through the cracks
- Jobs happen because the system starts them, not because someone remembered.
- You hear about problems before customers do
- Something stops, you know that morning, not next week.
- The result stops depending on who is in
- Holidays and staff changes stop changing how the work turns out.
What it costs
I price each job for what it actually involves rather than off a menu, because the same piece of work in two businesses is rarely the same amount of work. Connecting two tidy systems and untangling nine messy ones look alike on paper and are not.
So you get a number for your situation, in writing, before anything starts — and it does not move once we have agreed it. The opening week is fixed too, and it comes off the price if you carry on into a build.
What changes the number is mostly practical: how many systems are involved, how well they are documented, how clean the data is, and whether things have to keep running while they change. The opening week has a guarantee on it, which is the bit most people ask about.
What I build
Most people start with the first and carry on into whichever of the others turns out to matter. You do not have to decide up front.
Getting a price
It starts with a conversation, not a form.
- 01
Tell me what is eating your week
A paragraph is plenty. What your team does by hand, and roughly what it feels like it is costing.
- 02
We talk it through
Usually a short call and a look at the systems involved, so I understand the job before I price it.
- 03
You get a scope and a price
In writing — what I would build, what it costs, and how long it takes. Then you decide.