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
Tool sprawl is usually a symptom of an attribution gap — each tool was bought to answer a question the others could not.
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
Count how many systems hold a version of the same contact
This is the most common cause and the easiest to test.
Ask which tool answers "which campaign produced revenue" — usually none
Worth checking before you conclude the previous one is the answer.
Consolidation is worth it when it closes the loop, not when it just saves licence cost
Less common, but expensive when it is the cause.
Integrations keep two systems roughly in sync, and "roughly" is where attribution dies
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.