What is pipeline coverage?
Pipeline coverage is the ratio of open pipeline value to a revenue target. If you need to close $500,000 this quarter and you are carrying $2,000,000 in open opportunities, your coverage ratio is 4x. It exists because not every opportunity closes: the ratio backs out how much pipeline has to exist today so that, after normal win-rate attrition, the revenue target still gets hit.
Coverage is a planning number, not a performance number. A healthy ratio tells you the funnel is sized correctly; it says nothing about whether the deals inside it are real, current, or likely to close on schedule, which is why coverage alone is not enough to run a forecast on.
How this calculator works
Coverage ratio needed = 1 ÷ win rate Required pipeline = revenue target ÷ win rate Deals needed to win = revenue target ÷ average deal size Total opportunities = deals needed to win ÷ win rate New opportunities/week = total opportunities ÷ (period days ÷ 7) Open deals at any time = (total opportunities ÷ period days) × sales cycle days
The last line is an application of a simple queuing idea: if new opportunities enter the pipeline at a steady rate and each one takes your average sales cycle to resolve, the number sitting open at any given moment equals that rate multiplied by the cycle length. A longer sales cycle means more deals in flight at once for the same coverage target, which is why cycle length belongs in a pipeline calculation, not just win rate and deal size.
What's a healthy pipeline coverage ratio?
| Win rate | Coverage ratio needed | Typical of |
|---|---|---|
| 50% | 2.0x | High-velocity, transactional or inbound-led motions |
| 33% | 3.0x | Common mid-market SaaS benchmark |
| 25% | 4.0x | Common enterprise or complex-sale benchmark |
| 20% | 5.0x | Long-cycle, multi-stakeholder deals |
The 3x to 4x range gets cited constantly in sales-ops writing, but it is math, not a mandate: it falls straight out of 1 divided by a 25 to 33% win rate, which happens to be a common range for B2B SaaS. Run your own historical win rate through the formula instead of borrowing someone else's ratio, since a team closing at 40% needs meaningfully less coverage than one closing at 20%.
Common pipeline coverage mistakes to avoid
Counting Stale Deals That Will Never Close
An opportunity that has sat in the same stage for three months past your average cycle length is not really open pipeline, it is a number inflating your coverage ratio while contributing nothing to the forecast. Teams that never purge stale deals end up with a coverage ratio that looks healthy on a dashboard and produces a revenue miss anyway, because the win rate calculated against that bloated pipeline was never real. Set an age threshold tied to your average sales cycle, flag anything past it for a status review, and either re-qualify or close it out before it distorts the ratio.
Using One Blended Win Rate Across Very Different Deal Sizes
- Enterprise and SMB deals rarely close at the same rate. Blending them into one win rate understates the pipeline needed for your harder, larger deals and overstates it for your easier, smaller ones.
- Segment win rate by deal band before running coverage math. Calculate coverage separately for SMB, mid-market and enterprise segments if they behave differently, then sum the required pipeline values.
- Recheck the split whenever your mix shifts. A quarter that leans more enterprise than usual needs a fresh blended calculation, not last quarter's ratio applied to a different deal mix.
Confusing Pipeline Coverage with Pipeline Health
A 4x coverage ratio built from ten deals is a much riskier bet than the same ratio spread across forty, since losing any single large deal in a concentrated pipeline can blow the whole quarter. Coverage answers "is there enough," not "is it diversified, current, and likely." Layer in a look at deal concentration, stage distribution and average deal age alongside the raw ratio before treating a quarter as safely covered.
Ignoring Sales Cycle Length When Setting Weekly Targets
Two teams with identical coverage ratios can be in very different weekly positions if one closes deals in 30 days and the other in 90. The team with the longer cycle needs its full quarter's worth of opportunities open much earlier, since deals started in the final month of the quarter cannot possibly close inside it. Convert your total opportunity requirement into a weekly new-opportunity target using your actual cycle length, and treat a slow start to the quarter as a real gap, not something later weeks can fully absorb.
Frequently asked questions
How do you calculate sales pipeline coverage?
Pipeline coverage ratio equals 1 divided by your win rate. At a 25% win rate you need 4x your revenue target sitting in pipeline; at 33% you need roughly 3x. Multiply your revenue target by that ratio to get the pipeline value you need to be carrying right now.
What is a good pipeline coverage ratio?
A ratio in the 3x to 4x range is the figure most commonly cited across sales-ops literature, though it is a derived heuristic from the 1-divided-by-win-rate math rather than a single official benchmark. The right ratio for your team is whatever 1 divided by your actual historical win rate produces, adjusted upward if your pipeline includes stale or unqualified deals that inflate the win rate's accuracy.
How much pipeline do I need to hit my sales target?
Divide your revenue target by your win rate to get required pipeline value, and divide your revenue target by average deal size to get the number of deals you need to win. A $500,000 target at a 25% win rate and $10,000 average deal size needs $2,000,000 in pipeline, or 200 total opportunities.
What's the difference between pipeline coverage and pipeline velocity?
Pipeline coverage is a snapshot ratio: how much open pipeline you're carrying relative to a revenue target. Pipeline velocity is a rate: how fast pipeline turns into revenue, calculated from opportunities, win rate, deal size and sales cycle length. Coverage tells you if you have enough in the funnel; velocity tells you how fast that funnel is moving.