Sign in

Blog · Forecast and pipeline

Pipeline coverage vs weighted pipeline: what is the difference, and when each one lies

Pipeline coverage and weighted pipeline are two ways of asking whether there is enough pipeline to make the number. Coverage divides unweighted in-period pipeline by the target and compares the multiple to one over the win rate. Weighted pipeline multiplies each deal by a stage probability and compares the sum to the target directly. This page sets out both, computes them on the same ten deals, shows that they agree when the stage probabilities are the team's own measured rates and disagree when they are defaults, and says which to use for what.

The short answerPipeline coverage is in-period open pipeline divided by target, read against a required multiple of one over the win rate. Weighted pipeline is the sum of each open deal's value times the probability assigned to its stage, read directly against the target. They are the same idea at different resolution: coverage applies one win rate to everything, weighted pipeline applies a rate per stage. When the stage probabilities are the team's own measured stage-to-won rates, the two agree. When the probabilities are CRM defaults, which is usual, weighted pipeline is a precise-looking number built on untested assumptions, and coverage against a measured win rate is the safer check. Both lie when aged deals and out-of-period close dates are left in.

Two checks on the same question: is there enough pipeline. They differ in how finely they apply the win rate.

The definitions

Pipeline coverage Weighted pipeline
Formula In-period open pipeline ÷ target Σ deal value × stage probability
Compared with Required multiple = 1 ÷ win rate The target itself
Win rate used One, for all counted pipeline One per stage
Needs A measured win rate Measured stage probabilities
Fails when Win rate borrowed; aged deals included Probabilities are defaults; few large deals

Both on the same ten deals

Target: $500,000. All close dates inside the quarter. Team's measured win rate from qualified, by value: 25 percent.

Deal Value Stage CRM default probability Measured stage-to-won
1 $200,000 Qualified 25% 12%
2 $150,000 Qualified 25% 12%
3 $300,000 Discovery 40% 20%
4 $100,000 Discovery 40% 20%
5 $250,000 Proposal 60% 35%
6 $180,000 Proposal 60% 35%
7 $120,000 Proposal 60% 35%
8 $220,000 Negotiation 80% 60%
9 $90,000 Negotiation 80% 60%
10 $140,000 Verbal 90% 85%
Total $1,750,000

Coverage.

$1,750,000 ÷ $500,000 = 3.5x, against a required 1 ÷ 0.25 = 4.0x. Short.

Weighted, CRM defaults.

Stage Value Probability Weighted
Qualified $350,000 25% $87,500
Discovery $400,000 40% $160,000
Proposal $550,000 60% $330,000
Negotiation $310,000 80% $248,000
Verbal $140,000 90% $126,000
Total $951,500

Nearly twice the target. Comfortable.

Weighted, measured probabilities.

Stage Value Probability Weighted
Qualified $350,000 12% $42,000
Discovery $400,000 20% $80,000
Proposal $550,000 35% $192,500
Negotiation $310,000 60% $186,000
Verbal $140,000 85% $119,000
Total $619,500

Above target, with little margin.

Three answers from the same deals: short, comfortable, and marginal. The default-weighted figure is the outlier, and it is the one most CRM dashboards show. Coverage says short because it applies the from-qualified rate to a pipeline that is more advanced than average; the measured weighted figure credits the late-stage mix and is the best of the three here. It is also the only one that needed work to produce.

When they agree

If the stage mix of today's pipeline matches the historical mix, measured weighted pipeline over target equals coverage over required coverage. They are the same calculation. Divergence between them is information: weighted above coverage means the pipeline is later-stage than usual; weighted below means it is early, and belongs to next quarter, not this one.

When each lies

Coverage lies when the win rate is borrowed, the 3x rule; when deals dated next quarter are counted; when aged deals are left in. The pipeline coverage benchmark covers each.

Weighted pipeline lies when probabilities are defaults; when reps advance stages to raise their weighted number, which costs nothing and is rarely audited; and when the deal count is small. Deals 3 and 5 alone are $550,000 of this pipeline. Their measured weighted contribution is $147,500, a figure neither can produce.

Both lie about time. A deal at proposal for 120 days against a norm of 40 carries the proposal probability in both methods and should carry close to none. Remove deals past twice the stage's normal age before either calculation; the pipeline coverage worked example does it by hand.

Which to use

Situation Use
Early quarter: do we need more pipeline? Coverage against 1 ÷ measured win rate
Mid to late quarter: will the stage mix deliver? Weighted with measured probabilities
Team with under about thirty open deals Neither as a number; read the deal list
Board reporting Coverage, with the win rate stated beside it
CRM dashboard with default weights Replace the weights or hide the tile

Measuring the stage probabilities

For each stage, over the trailing four quarters:

Stage-to-won = deals that reached the stage and were won ÷ deals that reached the stage and were decided, with stalled deals counted as lost

By value as well as count. Recompute quarterly. It is one pivot table on a deal export that carries stage history, and it replaces five numbers somebody typed into a settings page years ago. The win rate, close rate and conversion rate comparison covers the denominators.

The short version

Coverage applies one win rate; weighted pipeline applies one per stage. With measured rates they agree, and the difference between them tells you whether the pipeline is early or late. With default probabilities, weighted pipeline is the more dangerous of the two because it looks more exact. Covirage computes both from the opportunity export, with the stage probabilities measured from the team's own closed deals and aged deals removed.

Questions people ask

Where do stage probabilities come from?

In most CRMs, from the default configuration: 10, 25, 50, 75, 90 percent. Nobody measured them. The measured version is, for each stage, deals that reached that stage and were won over deals that reached it and were decided, over the trailing four quarters. It is a pivot table, and the result usually differs from the defaults by twenty points or more at the late stages.

Which should I use on a forecast call?

Neither as the forecast. Both are sufficiency checks: is there enough. The forecast is a deal-by-deal judgement, tested afterwards for bias. Use coverage early in the quarter, when the question is whether to build more pipeline, and measured weighted pipeline later, when stage mix matters more than volume.

Why does weighted pipeline fail on a small team?

Because it treats a 500,000 deal at 50 percent as 250,000, and that deal will close at 500,000 or at zero. With two hundred deals the law of averages makes the weighted sum meaningful. With eight, the outcome is dominated by two large deals, and a weighted figure describes a result that cannot occur.