What this covers
- What is usually happening
- The four things to check
- How to tell which one it is
- Why this is hard to see in most stacks
What is usually happening
The honest answer depends on a number most teams cannot produce: revenue collected per channel, not leads per channel.
Diagnosis is worth more than technique here. Applying the right fix to the wrong cause is how teams spend a quarter improving something that was not the constraint.
The four things to check
Inbound looks cheaper on cost per lead and often is not on cost per customer
This is the most common cause and the easiest to test.
Outbound is measurable earlier, which makes it easier to fix
Worth checking before you conclude the previous one is the answer.
The right split changes with deal size and cycle length
Less common, but expensive when it is the cause.
Both should be judged on collected revenue, which requires one database
Frequently the real constraint once the obvious ones are ruled out.
How to tell which one it is
Each cause leaves a different fingerprint in the data. Look at stage conversion first — if losses concentrate in one stage, you have a process problem at that stage. If they are spread evenly, the problem is upstream in qualification or targeting.
Then look at time in stage, comparing won deals against lost. Where the two diverge is where intervention pays back.
Why this is hard to see in most stacks
Every diagnosis above needs engagement data and revenue data in the same place. When outreach lives in one tool, deals in another and invoices in a third, the questions become quarterly export exercises that nobody performs.
That is the practical argument for one database — not elegance, but that the diagnostic questions become answerable on a Tuesday afternoon.