The taxonomy

The taxonomy

Where revenue leaks

Revenue leakage is demand a business has already paid to create, which then fails to convert for reasons that have nothing to do with the buyer losing interest.

It does not happen inside the stages of a go-to-market system. It happens at the joins between them — which is exactly where no single team owns the number.

  1. More volume was never the fix. Demand you already paid for is leaking back out of the system.
  2. Every handoff has to answer four questions - context, decision, action, feedback. Miss one and revenue exits there.
  3. Lead capture, the action question: someone raises their hand, and the business answers hours later.
  4. Lead qualification, the context question: leads exist, and nobody follows up.
  5. Not every handoff is on this map. Amoris marks three and the loop; the MQL-to-SQL handoff it does not claim.
  6. Opportunity to close, the action question: the proposal takes days, and reads like the last one.
  7. And nothing tells the front of the system what worked. The loop back from revenue to demand never closes.

The map

The same spine, showing where revenue leaks: slow response between demand and leads, forgotten demand between leads and intent, opportunity friction between opportunity and revenue, and decision blindness, which is the feedback loop back from revenue that was never closed.DEMANDLEADSINTENTOPPORTUNITYREVENUE02SLOWRESPONSE01FORGOTTENDEMAND03OPPORTUNITYFRICTION04DECISION BLINDNESS — NOTHING COMES BACKThe same spine, showing where revenue leaks: slow response between demand and leads, forgotten demand between leads and intent, opportunity friction between opportunity and revenue, and decision blindness, which is the feedback loop back from revenue that was never closed.DEMANDLEADSINTENTOPPORTUNITYREVENUE02010304

Three leaks sit on a handoff. The fourth does not: decision blindness is a feedback loop that was never closed, so it is drawn as the return path that never arrives.

Why the joins and not the stages?

Because a stage has an owner and a join does not. At every meaningful transition there are four questions, and a leak is one of them going unanswered:

  1. 1 — What context should move forward?
  2. 2 — What decision needs to happen?
  3. 3 — What action should follow?
  4. 4 — What feedback should return?

Six leaks, and which have a fix

Of the six below, 4 have an Amoris intervention designed and 1 is available today. Two have neither, and are listed anyway — a taxonomy where every problem happens to be one this agency solves would be a sales sheet.

01

Context stripped at capture

Acquisition → Leads

Context did not move forward

What it looks like. Sales opens a record with a name, an email and nothing else. The first call starts by asking questions the visitor already answered.

What is actually wrong. The form captured the identity and discarded the situation - the page they were on, the question they asked, what they compared you against.

No Amoris intervention

02

Slow response

Demand → Leads

No action followed

What it looks like. Someone raises their hand at 9am and hears back the next afternoon, by which point they have spoken to two competitors.

What is actually wrong. Routing depends on a person noticing a queue. Nothing is wrong with the system; nobody is watching it at 9am.

Lead Response EngineIn design

03

Forgotten demand

Leads → Intent

Context did not move forward

What it looks like. A database of leads that were interested once, went quiet, and have not been contacted since. Everyone knows it is there. Nobody wants to open it.

What is actually wrong. The reason each one stalled was recorded by sales, and the thing that would resolve it shipped in product or marketing. Nobody joins those two records, so a company ships exactly the thing that lost it forty deals and never tells those forty people.

Dormant Lead Revenue RecoveryAvailable now

04

Intent present, not detected

Intent → Qualification

Context did not move forward

What it looks like. A prospect visits pricing three times in a week and nobody knows. The signal exists in a product, a support ticket or a review site.

What is actually wrong. The signal lives in a system nobody has joined to the CRM. It is a plumbing failure that presents as a demand problem.

No Amoris intervention

05

Opportunity friction

Opportunity → Revenue

No action followed

What it looks like. A qualified prospect waits days for a proposal, and the document that arrives reads like the last one because it is the last one.

What is actually wrong. Producing the artefact is manual, so it queues behind everything else - and the objection that eventually kills the deal is never written down.

Proposal-to-CloseIn design

06

Decision blindness

Revenue → Market

No feedback returned

What it looks like. Everyone can report what closed. Nobody can say which change caused it, so next quarter funds the same assumptions.

What is actually wrong. The loop that should carry the outcome back to positioning was never closed. This is not a broken handoff - it is a handoff that does not exist.

Revenue IntelligenceIn design

Why does it persist?

It is nobody's number

Every leak sits between two teams, and both of them are hitting their own targets. Marketing delivered the leads. Sales worked the ones that were routed. The gap between them is not on either dashboard.

It looks like a demand problem

The visible symptom is always the same - not enough pipeline. So the response is always the same: buy more traffic. That treats the one input that is expensive and leaves the one that is already paid for untouched.

Fixing it is unglamorous

Nobody gets promoted for joining a loss-reason field to a product changelog. It is smaller and less interesting than a new channel, and worth more than one.

How would you find yours?

Not by estimating it. Every leak above leaves a trace in data a business already has — a timestamp gap between enquiry and first touch, a closed-lost field, a cohort with no activity since a given date.

The Opportunity Scan is that read, on one export, written up and yours to keep whether or not anything follows. It can also conclude there is nothing here worth doing, and that is written into how it is scoped.

What it will not do is put a number on what you would recover before the work is scoped. A figure invented to fill that gap would be worth less than the honest absence of one.