Build a Revenue Leakage Map
A revenue leakage map shows where an opportunity can enter the business, lose ownership or context, stall, and leave without a clear next action.
The problem
Revenue leaks can be small handoff gaps: a missed call that never creates a lead, a form that reaches an inbox with no owner, a quote with no scheduled follow-up, a booked job whose source is lost, or an automation that keeps running after the customer has already converted.
The principle
Map the handoffs before choosing the fix. A leak is actionable when you can name the entry point, the expected next state, the owner, the evidence that the handoff occurred, and what should happen when it does not.
The framework
Demand exists but never becomes an owned opportunity.
Implementation: List every entry point and prove that each creates or updates a durable record.
Watch for: Missed calls remain only in a call log; Form submissions sit in a shared inbox; Referral leads are tracked in memory
Evidence: Uncaptured or duplicate inquiries found during a sample review.
Next action: Review the last ten inquiries from each major entry point.
The opportunity exists, but the next action is late, generic, or missing.
Implementation: Assign a next action and owner for every active opportunity and define follow-up stop conditions.
Watch for: No scheduled next action; The same message is sent regardless of context; No explicit close-lost reason
Evidence: Active opportunities without a next action.
Next action: Filter the pipeline for records with no future action.
Intent is present but the path to booking, purchase, or a human decision is harder than necessary.
Implementation: Observe the actual path from qualified intent to commitment on desktop and mobile.
Watch for: Repeated data entry; Dead-end CTAs; Unclear ownership between sales and operations
Evidence: Qualified opportunities that fail before the intended commitment event.
Next action: Complete the primary conversion path as a customer would and record every unnecessary step.
The business gets an outcome but cannot connect it back to source or preceding actions.
Implementation: Join source, identity, progression events, and outcome around a durable customer/opportunity record.
Watch for: Lead counts and revenue live in separate reports; Source is overwritten; Closed outcomes have no origin
Evidence: Closed outcomes without reconstructable source and progression history.
Next action: Audit five recent wins and five losses for complete source-to-outcome history.
Automation adds activity without reducing ambiguity or manual exception work.
Implementation: Give each automation explicit inputs, outputs, stop rules, retry behavior, and escalation ownership.
Watch for: Retries are invisible; Messages continue after conversion; Exceptions require manual detective work
Evidence: Automation exceptions without a visible queue or owner.
Next action: List active automations and document the stop condition for each one.
Example
A missed call may look like a phone problem, but the leak can happen later. The caller might receive a text, yet no durable opportunity is created. A staff member may respond, but the source may be lost. The customer may book, but the booking may never update the original lead. The useful map follows the opportunity across those handoffs instead of treating each tool as a separate project.
Put it to work
- Choose one high-value customer journey and write the expected states from first inquiry to closed outcome.
- For every transition, name the current owner, system of record, and evidence that the handoff happened.
- Sample recent real opportunities and mark where the expected state differs from what actually happened.
- Rank leaks by customer impact and repeat frequency, not by how interesting the technology appears.
- Fix one leak, then rerun the same sample before moving to the next one.
System checklist
- Every entry point has a durable destination.
- Every active opportunity has a next action and owner.
- Every conversion path has a clear commitment event.
- Every closed outcome keeps its source and progression history.
- Every automation has stop conditions and an exception path.
Quick worksheet
Create a table with columns for Stage, Entry state, Expected next state, Owner, System of record, Evidence, Failure path, and Fix. Fill it with one real journey before adding more journeys.
Common failure modes
- Mapping software instead of mapping the customer and opportunity states.
- Declaring a leak fixed because a message was sent rather than because the next state became reliable.
- Prioritizing rare edge cases while common handoff failures remain unresolved.
- Changing several stages at once and losing the ability to tell which change helped.
What to measure
- Inquiries without a durable opportunity record
- Active opportunities without a next action
- Qualified opportunities that stop before commitment
- Closed outcomes without source history
- Automation exceptions without an owner
Next action
Map one real journey and circle the first handoff where the expected next state cannot be proven.