Every revenue miss gets explained one of two ways in the room. Marketing says the pipeline was there and sales did not close it. Sales says the pipeline was thin and low quality. Both sides argue from the same dashboard because that dashboard does not contain the number that settles it.
The number that settles it is a recomputation, and it takes about an hour to build.
Do I have a pipeline problem or a conversion problem?
Recompute the closed quarter using your historical conversion rates against the pipeline you actually had, then compare that result to plan.Take the pipeline that existed at the start of the period, apply your trailing four-quarter conversion rate by stage and segment, add the revenue your history says gets created and closed inside the period, and see what number falls out.
If that recomputed number clears plan, you had enough pipeline. The revenue was available and the funnel did not deliver it. That is a conversion problem.
If the recomputed number misses plan even when every stage converts at its historical rate, no amount of execution would have saved the quarter. That is a pipeline problem, and it was set months earlier by pipeline creation.
The test works because it removes the argument about effort. It asks a single question: was the raw material sufficient?
What numbers separate the two?
Pipeline problems show up in creation and coverage. Conversion problems show up in stage rates, cycle length, and realized deal value.| Signal | Pipeline problem | Conversion problem |
|---|---|---|
| New opportunity creation vs trailing average | Down | Flat or up |
| Stage conversion rates vs trailing baseline | Flat | Down at one or more stages |
| Average sales cycle length | Flat | Often longer |
| Amount at close vs amount in CRM | Flat | Gap widening |
| Coverage ratio | Falling | Can stay flat or rise |
| Where the miss concentrates | Early in the funnel | At a specific stage or in a specific segment |
Why does pipeline coverage fail to answer this?
Coverage is a volume input, and both problems are quality problems in disguise.Most teams still run a 3x to 5x pipeline-to-goal rule. In stable conditions that rule is directionally useful. It is also dangerously incomplete, because it hides the composition of the quarter.
A company can carry 4x coverage and still miss badly when the pipeline is low quality, concentrated in the wrong stage, dependent on a handful of large deals, inflated by stale opportunities, or built on close dates that sellers keep pushing forward. A company can start the quarter with thin coverage and outperform, if it has a strong in-quarter creation motion.
Across ORM customers, coverage runs from 1.4x to 5x, with most landing near 3.5x. That spread is wide enough that no single ratio functions as an operating rule. We wrote about why the 3x pipeline coverage rule is wrong in more detail, and the short version applies here: coverage is a useful input and it is never the conclusion.
What if the answer is both?
Fix conversion first, because volume added to a leaking funnel costs full price and returns nothing.When both are broken, the sequencing matters more than the diagnosis. Adding pipeline to a funnel with a broken stage means you acquire deals at full cost that exit before revenue. Worse, the larger denominator masks the conversion problem for another quarter or two, so the team keeps solving the wrong thing.
There is a second reason to sequence this way. Conversion fixes are cheaper. Tightening a stage exit criterion costs a process change. Generating 30% more pipeline costs headcount, program spend, or both.
The one exception is when pipeline creation has fallen far enough that no conversion rate closes the gap. In that case, run both, but keep the measurement separate so you can tell which lever moved the result.
How do the fixes actually differ?
A pipeline fix changes what enters the funnel. A conversion fix changes what happens inside it.For a pipeline problem, work the creation math backward from the target. Take the revenue goal, divide by your realized average deal size at close rather than the amount sitting in your CRM, then divide by your historical stage conversion to get the required opportunity count. That count becomes a weekly creation target owned by name.
For a conversion problem, isolate the first stage where the rate falls outside its trailing range and fix the input to that stage. Late-stage conversion problems trace to buyer access and deal economics. Early-stage conversion problems trace to sourcing standards. Weighting your pipeline by stage, as covered in weighted pipeline, makes the difference visible in a single view.
Both fixes need the same guardrail: hold your pipeline coverage definition constant while you work. Teams that change the definition mid-diagnosis lose the ability to tell whether anything improved.
How long before the fix shows up in revenue?
A conversion fix shows up within one cohort. A pipeline fix shows up one full sales cycle out.Deals already past the broken stage carry the old behavior with them, so a conversion fix only becomes visible when a complete cohort has entered and exited the stage under the new standard. Measure by cohort entry date. Calendar weeks will mislead you.
Pipeline fixes are slower and more predictable. Opportunities created this week convert on your median cycle, so a creation push in month one of the quarter pays off next quarter in most B2B SaaS motions and two quarters out in enterprise.
That lag is the argument for diagnosing early. Getting the answer right in the last week of the quarter does not help anyone, because by then the quarter has already happened. The value of the diagnosis comes from knowing the shape of the quarter early enough to change it.
Frequently Asked Questions
What is the fastest test to separate a pipeline problem from a conversion problem?
Recompute the last two quarters using your historical conversion rates against the pipeline you actually had. If the recomputed number hits plan, you had a conversion problem. If it misses plan even at historical conversion, you had a pipeline problem.
Can pipeline coverage tell me which problem I have?
No. Coverage compares pipeline value to a target and tells you nothing about the quality, stage distribution, age, or concentration of that pipeline. A company can carry 4x coverage and still miss badly if the pipeline is stale, held by the wrong reps, or dependent on a few large deals.
What pipeline coverage ratio do most companies actually run?
Across ORM customers the range runs from 1.4x to 5x, and most sit near 3.5x. The spread is wide enough that a single target number is a poor operating rule for any specific business.
Which problem is faster to fix?
Conversion, usually. Pipeline created today converts on your sales cycle, so a pipeline fix pays off one full cycle out. A conversion fix can change outcomes on deals that are already in flight, though it will not save deals that are past the stage where the problem lives.
What if both problems are present at the same time?
Fix conversion first. Adding volume to a funnel that leaks means you pay full acquisition cost for deals that will exit anyway, and it hides the conversion issue behind a larger denominator.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo