Optimized Sales Optimized Marketing Target Accounts For CROs For CFOs For CMOs Blog News Glossary Compare Tools About Schedule a Demo
Pipeline Analytics

How to Calculate Weighted Pipeline Coverage

Pete Furseth 6 min read
pipeline coverageweighted pipelinepipeline analytics
How to Calculate Weighted Pipeline Coverage
Home/ Blog/ How to Calculate Weighted Pipeline Coverage

What is weighted pipeline coverage?

Weighted pipeline coverage divides risk-adjusted pipeline by the revenue target, instead of dividing raw open pipeline by the target. Raw coverage counts every open dollar the same way. A $200,000 opportunity created last week in discovery counts identically to a $200,000 contract sitting in procurement. Those dollars do not convert at the same rate, so treating them as equal produces a ratio that moves for reasons unrelated to whether the quarter lands.

Weighting fixes the numerator. Each open opportunity gets multiplied by the rate at which deals in its position have historically closed, and the sum becomes the pipeline you count. The output is a smaller number and a more honest one. The pipeline coverage definition covers the unweighted version this builds on.

Put this to work on your numbers
Run your own numbers with the free Pipeline Velocity Calculator, then see how ORM builds it into a custom model.

What is the formula for weighted pipeline coverage?

Multiply every open opportunity by the close rate of its stage, sum the results, then divide by the revenue target for the period.

``` Weighted pipeline = Sum of (Open opportunity amount x Close rate for its stage) Weighted coverage = Weighted pipeline / Revenue target for the period ```

Filter to opportunities with close dates inside the period before you weight anything. Future-dated deals inflate the numerator and produce a ratio nobody can act on. Then group the remaining opportunities by current stage, apply the rate for that stage, and total the column.

Where do the stage weights come from?

Your own closed history, calculated as the share of opportunities that reached a stage and went on to win. Take every opportunity that entered a given stage over the last four to eight quarters, count how many closed won, and divide. That single number is the weight.

Do not use the probability field the CRM ships with. Those percentages are configuration values someone set during implementation, and they describe an opinion rather than a result. CRM probability values are frequently set well above the rate a stage actually converts at, which inflates the weighted pipeline.

Rebuild the weights every quarter. The most common reason a forecast misses is that something in the business or the market changed while the model kept running on old assumptions. A new competitor creating pricing pressure or a shift in buying behavior moves stage conversion before it moves any headline metric.

What does the calculation look like on real pipeline?

Weighting collapses a comfortable-looking ratio into a specific dollar gap.
StageOpen pipelineClose rateWeighted value
Discovery$6,000,00012%$720,000
Solution fit$4,200,00022%$924,000
Proposal$3,600,00038%$1,368,000
Negotiation$1,900,00065%$1,235,000
Total$15,700,000$4,247,000
Against a $5,000,000 target, this pipeline reports 3.14x raw coverage. Across ORM customer data, 3x to 5x is the standard raw range and most companies sit near 3.5x, so this team looks normal by that measure. Weighted, the same pipeline covers 0.85x of the target and carries a $753,000 gap. The gap is the number worth managing, and it points directly at the two stages that produced it.

How does weighted coverage differ from raw coverage?

Raw coverage answers whether there is volume. Weighted coverage answers whether there is convertible value. The two ratios are read on completely different scales. Raw coverage needs a multiple because most open deals lose. Weighted coverage targets roughly 1.0x, since the loss rate already sits inside the numerator.

That difference is why a fixed raw multiple makes a poor health check. Two teams reporting identical 3.5x ratios can weight down to 1.2x and 0.7x depending on where the value sits, and only one of them is going to make the number. The problem with treating a multiple as an answer is covered in why the 3x pipeline coverage rule is wrong.

What breaks the weighted calculation?

Stale opportunities and inflated deal amounts, both of which corrupt the numerator before any weight touches it.

Across ORM customers, 10% or more of open pipeline has not been touched in 12 months. Meaningful activity means a change in stage, close date, or amount, so an opportunity with none of those is dead weight that still sits in a stage and still collects a close rate. Filter on last meaningful change before you weight.

Inflated amounts do parallel damage. A pipeline carrying an average deal size of $80,000 while closed-won deals average $40,000 doubles every weighted value. Compare the average open amount per stage against what actually closed from that stage, and discount the gap.

Close-date movement is the third distortion. Deals that keep sliding accumulate in a stage without converting, which holds the ratio steady while the quarter underneath it decays. Track deal slippage separately rather than letting it hide inside the coverage number.

What does weighted coverage still miss?

It prices only the pipeline that exists today, and a quarter is not made entirely of visible pipeline. Across ORM customers, roughly 20% of the pipeline carrying in-quarter close dates on day one of the quarter actually closes in that quarter. The other 80% of that value moves, shrinks, or dies.

A complete read decomposes the period into carry-over deals already in pipeline, business that gets created and closed inside the quarter, and deals pulled forward from future periods. Weighted coverage prices the first bucket well and says nothing about the other two. Treat it as one input to the forecast rather than the forecast itself, a distinction developed further in the guide to weighted pipeline.

How often should you recalculate weighted coverage?

Weekly through the quarter, and always on day one. Day one is when the number changes decisions, because there is still time to create pipeline, reallocate capacity, or move spend toward the stage that is short. A weighted ratio produced in the final week reports history.

Watch the trend rather than the level. Weighted coverage that drifts from 1.1x to 0.9x over four weeks tells you deals are exiting stages as losses or pushes, and that movement shows up well before the submitted forecast admits it.

Frequently Asked Questions

What is the formula for weighted pipeline coverage?

Multiply each open opportunity by the historical close rate of the stage it sits in, add the results together, then divide that total by the revenue target for the period. A pipeline that weights down to $4,247,000 against a $5,000,000 target has 0.85x weighted coverage.

What is a good weighted pipeline coverage ratio?

Around 1.0x, because the weights already price in the risk. Raw coverage needs a multiple of 3x to 5x to absorb losses. Weighted coverage does not, since the loss rate is baked into the numerator. Anything meaningfully below 1.0x is a stated revenue gap.

Should I use the CRM probability field as the weight?

No. The default probability attached to each CRM stage is a configuration value someone entered once and rarely revisits. Calculate your own rates from closed history: count the opportunities that reached each stage over the past four to eight quarters and divide the wins by the total.

How is weighted pipeline coverage different from weighted pipeline?

Weighted pipeline is the risk-adjusted dollar value of open deals. Weighted pipeline coverage is that value expressed as a ratio against the target. The first tells you what the pipeline is worth, the second tells you whether it is enough.

Does weighted coverage account for deals that are not in the CRM yet?

No, and that is its main limitation. It prices visible pipeline only. Business created and closed inside the same quarter never appears in a day-one weighted calculation, so the ratio has to be read alongside a separate expectation for in-quarter creation.

PF
Pete Furseth
ORM Technologies
Pete has built custom revenue forecast models for B2B SaaS companies for over a decade.

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