Pipeline coverage by stage splits a single coverage ratio into one ratio per stage, each measured against the conversion rate that stage historically produces. Total coverage answers whether enough dollars exist. Stage coverage answers whether those dollars sit close enough to a decision to land inside the period.
The calculation
Required pipeline at any stage equals the remaining target divided by the cumulative conversion rate from that stage to closed won. Deeper stages convert at higher rates, so they need fewer turns.
Illustrative rates on a $2M target. Use your own trailing four-quarter rates by segment.
| Stage | Converts to won | Required coverage | Open pipeline on a $2M target |
|---|---|---|---|
| Qualified | 15% | 6.7x | $13.3M needed |
| Solution fit | 30% | 3.3x | $6.7M needed |
| Proposal | 60% | 1.7x | $3.3M needed |
Why the total ratio hides the risk
Total coverage treats a first-call opportunity and a signed-off proposal as equivalent dollars. They are not. ORM customer data shows that of the pipeline value carrying in-quarter close dates on the first day of a quarter, roughly 20% actually closes in that quarter. The other 80% either slips, shrinks, or dies. A book weighted toward early stages sits further from a decision, so its headline ratio implies more in-quarter revenue than the stage mix supports.
Stage coverage also exposes bottlenecks. When one stage holds a disproportionate share of the book quarter after quarter, the problem is an exit criterion nobody enforces rather than a generation shortfall. Related reading on discounting pipeline by probability sits in weighted pipeline, and the base metric is covered at pipeline coverage.
Build it on real exit criteria
Stage coverage is only as good as stage definitions. If reps advance deals on optimism, conversion rates drift and the requirement moves with them. Two guardrails hold the model together. Write exit criteria that a manager can verify from the record itself, and recompute conversion rates every quarter rather than freezing them at the start of the year.
Teams that maintain this discipline can act early. A late stage gap identified in week two is a coverable problem. The same gap identified in week eleven is a miss that has already happened. Tracking forecast accuracy against stage coverage over several quarters shows which stage carries the most predictive signal for your business.
Frequently Asked Questions
How do you calculate coverage for a single stage?
Take the cumulative conversion rate from that stage to closed won, then divide the remaining target by it to get the pipeline required at that stage. Compare the requirement against the dollars actually sitting there. A stage converting at 60% needs about 1.7x, while a stage converting at 15% needs closer to 6.7x.
Which conversion rates should you use?
Trailing four quarters, calculated separately by segment. A blended rate across SMB and enterprise describes neither, and stage coverage built on a blended rate produces requirements that are wrong in both directions.
Does stage coverage replace weighted pipeline?
No. Weighted pipeline discounts each deal to a single expected value. Stage coverage keeps the stages separate so you can see where the shortfall sits. Teams use both, since a weighted number that looks adequate can still hide an empty late stage.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like pipeline coverage by stage into prescriptive action for your team.
Schedule a Demo