£leak
01
Money
Margin disappears in extra work, missed leads, and messy handoffs.
Find the leak. Ship the fix.
Bring one messy workflow. I find where time and money leak out, then build the fix your team can actually run.
copyingchasingwaitingguessingfixed
Where leaks show up
Money, time, leads, founder attention.
Most fixes start in one of these places. We pick the messy one, price the leak, then build only what is worth building.
02
Time
People keep rebuilding the same report, chase, or setup.
inroutebook
03
Leads
Good enquiries wait too long before the right person sees them.
Waiting on founder
Needs approval
Can run alone
04
Founder
Too many small decisions still come back to you.
Example scenarios
Four common leaks, mapped like a build ledger.
Not case studies and not promises. These are the kind of workflows I diagnose, quote, and build when the numbers make sense.
Founder quick read
01 / 04
01
Candidate screening
inqueuereview
Which queue goes stale fastest?
Leak
Good candidates sit too long.
Fix
First pass sorted for review.
Worth checking
Which queue goes stale fastest?
Engagement model
Small first. Build if it adds up.
Start with one messy workflow. The diagnosis gives you the map, quote, and go/no-go before anyone commits to a bigger build.
Project route
call → diagnosis → build
0120 minutes
Free fit call
We pick one expensive workflow and decide whether it is worth diagnosing.
02£950
Diagnosis
I trace the work, quantify the leak, and give you a plain plan for the fix. The fee comes off the build if we continue.
03Fixed fee
Build
I ship the workflow in code, wire it into your tools, and hand it over with clear operating notes.
Stop gate
If the leak is not worth building around, we stop at the diagnosis.
What I build
Messy work in. Useful system out.
The output is not a strategy deck. It is the workflow picture, the tool picture, the fix plan, and the working system your team can use.
Build console
messy input → working system
messy inputs
forms
inbox
sheets
CRM
rules
code
checkwireship
01
Workflow picture
See the stuck steps
02
Tool picture
Know what connects
03
Fix plan
Choose the fix
04
Working system
Use it Monday
CRMemailsheetsreportsSlackdatabase
Proof
Product judgment plus engineering delivery.
I have shipped software for product teams and built my own AI products in public. The useful part for you: I can choose the right workflow, then actually build it.
Questions
Short answers.
How long does it take?
The free call is 20 minutes. The diagnosis is usually a focused short piece of work. Build timing depends on the workflow, tools, and access needed.
What if it does not work?
That is why diagnosis comes first. If the workflow is not worth building, I will say that before a bigger project starts.
Do we need technical knowledge?
No. Bring the messy workflow and the tools involved. I will handle the technical shape and explain the trade-offs plainly.
Who owns the result?
You do. It runs in your tools and accounts. I am not renting you a black box.
Which tools can you work with?
CRMs, spreadsheets, reporting tools, forms, email, Slack, databases, and custom apps. The diagnosis decides what should connect and what should stay manual.
What does it cost?
The diagnosis is £950. If we continue into a build, that fee comes off the build. The build itself is quoted after the diagnosis.
What happens after launch?
You get the working system, access, and handover notes. If you want support after that, we can agree a simple support path.
Start here
Bring one messy workflow.
In 20 minutes we will work out whether it is worth diagnosing, what data we would need, and what a useful first build could be.
Book the free callFree fit call
20 minOne workflow. One decision.
bring the messy bit
find the real leak
decide the next step
bring the messy bit
01
show the workflow
02
check the leak
03
yes / no
No prep deck. No full audit. Just enough to know whether there is a useful diagnosis hiding in the mess.