Diagnose before you automate.
The expensive mistake is not failing to automate. It is automating the step that felt slowest and discovering a quarter later that the total did not move. One week inside the real operation, five documents, and an order to do things in — including the row that says not yet.
- Price
- $2,000
- Takes
- One week
- Credited
- In full
- Documents
- Five
Pick the stepyou would automate.
Six steps of a real journey, each with the time it takes to do and the time it spends waiting. Choose one, and watch what happens to the total. Most people choose the same one.
Nine areas.One week.
Not a checklist — an order of operations. Each area is read against the ones around it, because a bottleneck is only a bottleneck relative to what feeds it and what it feeds.
Acquisition
Where demand actually comes from, versus where you believe it comes from. These are different in most operations, and the gap is usually the finding.
Qualification
What decides whether an enquiry is worth a slot, who applies it, and whether it is applied the same way twice.
Booking
Whose domain it happens on, what availability it reads, and how many messages it takes to agree a time.
Continuity
The window between booking and arrival: confirmation, preparation, reminders, reschedule. Usually the cheapest thing to fix and rarely the first thing anybody fixes.
Recovery
What happens to abandons, missed calls and no-shows. In most audits the honest answer to this one is nothing.
Attribution
Whether a paid client can be traced to the channel that produced it. Not a leak by itself — it is what stops you finding the other eight.
Data
What is recorded, where it lives, who can read it, how long it is kept, and which spreadsheet is quietly load-bearing.
Governance
Consent, access, retention, and the list of things that must never be automated with the named human each one escalates to.
Operating risk
What breaks if one person is away, one credential expires, or one integration changes its API. The audit finds these; it does not wait for them.
Nine areas is not nine deliverables. They collapse into five documents, because the value is in how they relate — a slow booking step means something different depending on whether qualification is happening upstream of it.
Five documents.Not a slide deck.
Here they are, drawn with sample figures. Four of them describe what is happening. The fifth orders it, and the fifth is the one people keep — including the row that says what not to build this quarter.
Five days.Published protocol.
-
D01
Observe
The real workflow, not the one on the org chart. What enters, where it waits, who decides, what data exists, and where the manual work is hiding.
-
D02
Separate
Symptom from bottleneck. Most of what hurts is downstream of one thing that does not hurt at all, and telling them apart is the whole reason this takes a week and not an afternoon.
-
D03
Register
Every leak written down with its impact, its effort and the evidence label it was found under — OBSERVED, ESTIMATED or MODELED. Nothing goes in the register unlabelled.
-
D04
Sequence
Dependencies mapped, so the order comes out of the work rather than out of what is easiest to sell. Some rows depend on two others being done first.
-
D05
Hand over
The five documents, a walkthrough, and a straight answer about what to build, in what order, and what to leave alone — with the reason attached to each.
What the auditactually costs you.
The fee comes off a build in full, so on most paths this is free in net terms. On one path it is not, and that path is on this page at the same size as the others.
- A journey and signal map: every path a customer can take, and what the business records at each point.
- A leak register with impact, effort and an evidence label on every row.
- A system and integration map: what talks to what today, and where a person is moving data by hand.
- A risk and escalation map: what must never be automated, and who it goes to instead.
- A build sequence with dependencies — and an explicit list of what not to build this quarter.
- The full $2,000 credited against Booking OS, Revenue OS Core or Revenue OS Growth.
What this isn’t
- Not a slide deck with AI recommendations in it.
- Not a workshop. Two conversations and read access, not six people in a room for two days.
- Not a sales process wearing a diagnostic’s clothes — the sequence is allowed to end in nothing.
- Not a commitment to build with us. The documents name what, not who.
$2,000, one week.Credited in full.
No scope creep clause, because the scope is a week and the deliverable is a list. The full fee comes off Booking OS, Revenue OS Core or Revenue OS Growth if you build.
Request the auditThe Revenue Leak Check is six questions and two minutes, and it exists to tell you whether this week is worth $2,000 to you. Run it first — we would rather you did.
Run the free checkWhere it sits in the ladder
- Revenue Leak CheckSix questions · directional · can say don’t buyFree
- Revenue Systems AuditOne week · credited in full against a build$2,000
- Booking OSThe wedge · the door, done properly$2,500
- Revenue OS CoreThe full loop, signal to outcome$7,500
- Revenue OS GrowthEvery channel, control and evidence layer$12,000
The audit is the only step on this ladder whose job is to talk you out of the steps above it when they are not the right size yet.
The questions thatactually stop the deal.
Why would I pay for a diagnostic when the other one is free?
Is the fee really credited in full?
What if you find nothing?
How much of my team’s time does this take?
Do I have to build with you afterwards?
Can you audit a business in Spanish, or in Latin America?
Find the constraintbefore you fund the fix.
Twenty minutes to see whether a week is the right size for your operation. If the free check would tell you the same thing, we will say that instead of selling you the audit.
No deck, no pitch. If it does not fit, we say so on the call.