We price the leak before anyone builds anything.
Days inside your real inbox and workflow, ending in written findings with the loss priced in your own numbers. It is paid work with a deliverable: the findings are yours to keep and act on, whoever you build with — including if you build with no one.
Findings you keep, whoever builds it.
01
What you get
A document you can act on, and a number you can defend.
Everything below is handed over in writing at the end of the engagement.
A map of the leak
Where enquiries enter, where they stall, and where they die. Traced through the real messages rather than described from memory in a workshop.
The leak, priced
A monthly figure built from your own records and your own currency, with the assumptions written down so you can challenge them.
Response-time baseline
How long a serious enquiry currently waits, measured rather than estimated. This becomes the line any future build is judged against.
The recommended workflow
The single path we would build first, end to end, and why that one before the others. Scoped tightly enough to finish in weeks.
Risks and dead ends
What will break, what your current tools cannot do, and where automation would make things worse. Including the case for building nothing.
A build proposal
Fixed scope, fixed price, and the instrumentation we would wire in. You are free to take it to anyone, or to no one.
02
The shape
Days, not weeks. Inside the work, not around it.
Exact duration is agreed on the introductory call, against how much of the workflow needs reading.
- Before01
Access and consent
Read access to the inbox and the systems the enquiry touches, plus a short list of who does what. We agree in writing what we may see and how it is handled.
- Day one02
Read the real traffic
We go through actual enquiries end to end. No sample data, no idealised journey. We are looking for the gap between what should happen and what does.
- Middle days03
Watch the handoffs
Short sessions with the people doing the work. Where they re-key data, where they chase, where they guess. This is where most of the number comes from.
- Last day04
Count and cost
We turn observations into a monthly figure with stated assumptions, and settle on the one workflow worth building first.
- After05
Findings and a decision
A written document and a call to walk you through it. You then decide: build with us, build elsewhere, or do nothing. All three are acceptable answers.
How price is set
Scoped on the call, fixed in writing, before anything starts.
We do not publish figures, because a price without your workflow attached would be a guess. The diagnostic is scoped on the introductory call, once we know how much of the business the enquiry touches, and the price is fixed in writing before work begins. No hourly drift, no discovery invoices.
The diagnostic is paid work with a named deliverable — that is what makes the findings yours to keep and the attention senior.
Its cost is driven by how many systems and people the enquiry passes through, not by your revenue.
The build is quoted as one fixed figure for one workflow, after the diagnostic — never before.
Anything outside the agreed scope becomes a written change, priced and approved separately.
No retainers to start. No licence fees to us. No mark-up on tools you buy directly.
If the findings show the loss is too small to justify a build, the document says so, and everything stops there.
03
Request a diagnostic
Tell us where the money goes.
A few lines is enough: what the workflow is and roughly what it costs you each month. We reply within one working day.
04
The terms, up front
What the diagnostic commits us to.
Stated here so there is nothing to negotiate later.
Days
Inside the real workflow, not around it.
Written
Findings you keep, whoever builds it.
Fixed
Diagnostic price agreed before it starts.
1 day
To reply to your enquiry.
30 min
The introductory call that scopes it.
0
Demos delivered instead of findings.