Three times coverage is probably the most repeated number in B2B sales. It is also one of the least examined, and for early-stage SaaS teams it routinely produces false confidence right up to the last two weeks of a quarter.
What coverage actually measures
Pipeline coverage is a simple division: open pipeline expected to close in the period, divided by the target for that period.
coverage = open pipeline closing this period ÷ period target
$3M of qualifying open pipeline against a $1M quarterly target is 3x coverage. The intent is to answer one question: do we have enough in flight to hit the number, given that most of it will not close?
Where 3x comes from
The 3x default comes from somewhere specific: it is the inverse of a 33% win rate. If one deal in three closes, you need three times your target in the pipe to land on it.
Which means 3x is only correct if you close roughly a third of your qualified pipeline. Adopt the benchmark without checking that assumption and you have imported someone else's win rate into your own forecast.
| Your win rate | Coverage you actually need |
|---|---|
| 20% | 5.0x |
| 25% | 4.0x |
| 33% | 3.0x |
| 40% | 2.5x |
| 50% | 2.0x |
This is the first and easiest correction. Calculate your own win rate on qualified opportunities over the last four quarters, take the inverse, and use that as your target.
The three ways it lies
1. Stale pipeline inflates the numerator
The most common failure by a distance. Deals sit in Proposal for five months with a close date that has been pushed four times. They are still counted. Coverage looks like 3.6x, and a third of it has no realistic chance of closing.
The signature of this problem is high coverage alongside a missed quarter, repeatedly. If that has happened twice, you have a hygiene problem rather than a volume one.
2. Stage definitions are not shared
Coverage assumes all the deals in the numerator are comparably real. If one rep marks a deal Qualified after a good first call and another only after a budget conversation, you are adding together two different things and dividing by a target.
This is why coverage is downstream of stage definitions with exit criteria. Without those, coverage measures data entry habits.
3. Small numbers move violently
At ten open deals, one $200k opportunity slipping changes coverage by a whole turn. Early-stage teams read it as a trend line when the sample is far too small to trend. Below about twenty deals in the period, read it as a rough sufficiency check and nothing more.
High coverage and a missed quarter, twice in a row, is not a pipeline problem. It is a hygiene problem.
Two adjustments that fix it
Adjustment one: only count deals that pass a staleness test
Before calculating, exclude any deal that meets either condition:
- Close date has been pushed more than twice
- No buyer-side activity in more than 1.5× the median time in that stage
Run this once and expect the number to drop hard, often by 20–40%. That figure is the first honest coverage number you have had, and the gap it reveals is one you still have time to act on.
Adjustment two: segment before you divide
Blended coverage hides the problem. A 3.2x blended number can be 1.4x in new business and 6x in expansion, which are completely different situations requiring completely different responses. Calculate coverage separately for each motion you run.
How to actually use it
Coverage is a sufficiency check rather than a forecast. It answers whether there is enough in flight, not what will close. Treat it accordingly:
- Check it in week two, while there is still time to generate more. Checking in week eleven is archaeology.
- Pair it with stage hygiene. Coverage tells you volume; hygiene tells you whether the volume is real. Read them together.
- Watch the trend, not the value. Coverage falling from 4x to 2.8x over three weeks is a far more actionable signal than any single reading.
Context worth holding: Gartner found fewer than half of sales leaders and sellers have high confidence in their organisation's forecasting accuracy. Coverage is one of the few inputs you can clean up quickly — and cleaning it is mostly a definitions exercise, not a data science one.
If you want someone to run the staleness test against your live pipeline and tell you what the honest number is, that is part of the free GTM teardown.
Source: Gartner, State of Sales Operations Survey.
Frequently asked questions
How do you calculate pipeline coverage ratio?
What is a good pipeline coverage ratio for B2B SaaS?
Why is my coverage ratio high but I still miss quota?
Should coverage include deals with close dates outside the quarter?
Zachary works with founder-led B2B SaaS companies between seed and Series B, as a fractional VP of Sales and Marketing and through the team that builds their revenue operation on Throughline.
Get a free GTM teardown