Pipeline Coverage Calculator

Measure whether qualified open pipeline is sufficient to support the revenue target, then translate any shortfall into pipeline, opportunities, meetings and weekly sourcing pace.

Use qualified opportunities with a realistic close date inside this period.
Coverage status

Enter your assumptions

The calculator compares current qualified pipeline with the coverage implied by your win rate.
Waiting
Remaining gap
-
Target minus closed won
Total-target coverage
-
Open pipeline / target
Gap coverage
-
Open pipeline / remaining gap
Required coverage
-
1 / win rate
Required pipeline
-
To statistically support the gap
Additional pipeline
-
Pipeline still to create
Expected revenue
-
Closed won + pipeline x win rate
Expected attainment
-
Directional expected value
Expected shortfall
-
Target minus expected revenue

Pipeline creation requirement

Deals still needed
-
New opportunities to create
-
Meetings / SQLs needed
-
New opportunities / week
-

Win-rate sensitivity

Win rateRequired coverageRequired pipelineExpected revenue from current pipeline

Why pipeline coverage matters for RevOps and revenue

Pipeline coverage is a forward-looking capacity check. It tells a revenue team whether the qualified opportunity value scheduled for a selling period is large enough to support the target after normal deal losses.

The metric matters because revenue targets are deterministic while sales outcomes are probabilistic. If a team closes 25 percent of qualified opportunities, $1 of remaining quota cannot normally be supported by only $1 of pipeline. The simple starting requirement is about 4x coverage because the inverse of a 25 percent win rate is 4.

That is why a generic 3x or 4x benchmark should not be treated as a universal rule. Clari recommends calibrating coverage to actual win rate, sales cycle, deal quality and pipeline mix. Gong describes 3x to 4x as a rule of thumb, while Salesforce Revenue Insights uses a different denominator and calculates open pipeline against the remaining gap to quota.

Two pipeline coverage definitions RevOps should not mix

Total-target coverage = Qualified open pipeline / Revenue target Gap coverage = Qualified open pipeline / (Revenue target - Closed won)

If no revenue has closed yet, the two figures are the same. Once the period is underway, gap coverage becomes higher because the denominator falls as closed-won revenue accumulates. Use one definition consistently in dashboards and operating reviews.

Required coverage should start with win rate

Required coverage = 1 / Qualified opportunity win rate Required pipeline = Remaining revenue gap / Win rate

A 20 percent win rate implies 5x coverage. A 25 percent win rate implies 4x. A 33 percent win rate implies roughly 3x. This is a planning baseline, not a guarantee. A pipeline concentrated in one large deal, filled with stale opportunities or loaded into the end of the quarter can still miss even when the headline multiple looks healthy.

Coverage is not the forecast

Coverage asks whether enough pipeline exists. Forecasting asks what revenue is likely to close. Revenue systems have long separated total pipeline from probability-adjusted expected revenue. Patent US8065178B2, for example, describes opportunity revenue, close probability, total pipeline and expected revenue adjusted by opportunity probabilities. Patent US7797182B2 describes pipeline assessment against predefined targets and a percent pipeline coverage view by sales stage.

The calculator uses a simple expected-value model, current qualified pipeline multiplied by historical win rate, to make the difference visible. RevOps should still use deal inspection, stage conversion, close-date quality, slippage and forecast categories for a production forecast.

How to use the output in a RevOps operating cadence

  1. Check the remaining gap. Confirm the target and closed-won amount are from the same period.
  2. Compare current gap coverage with required coverage. Use your own qualified opportunity win rate.
  3. Inspect additional pipeline needed. This is the dollar value that demand generation and sales need to create if the current pipeline is insufficient.
  4. Translate the gap upstream. Average deal size estimates opportunity count. Meeting-to-opportunity conversion estimates the qualified meetings needed.
  5. Check timing. The weekly pace only helps the current target if new opportunities can mature inside the remaining sales-cycle window.
  6. Segment the analysis. Calculate coverage separately by region, segment, product or team when win rates and deal sizes differ materially.

What this calculator does not model

This is a directional planning model. It assumes the supplied win rate applies to the open pipeline and that opportunities can close in the selected period. It does not model stage-specific probabilities, pipeline aging, slippage, deal concentration, expansion versus new business, seasonality or future pipeline that has not yet been created.

Pipeline coverage FAQ

Pipeline coverage compares the value of qualified open sales opportunities with the revenue target they need to support. It is usually expressed as a multiple, such as 3x or 4x. The useful question is not whether the CRM contains a large pipeline, but whether enough qualified opportunity value exists to absorb normal losses and still hit the target.

Enter the revenue target for one selling period, revenue already closed, qualified open pipeline expected to close in that period, historical opportunity win rate, average deal size, meeting-to-opportunity conversion rate, sales cycle and weeks remaining. The calculator then shows current coverage, required coverage, pipeline gap, expected attainment and the pipeline creation pace needed to close the gap.

Start with Required Coverage and Current Gap Coverage. Required Coverage is based on your win rate. If current coverage is lower, review Additional Pipeline Needed, Opportunities to Create and Weekly Opportunity Pace. Expected Attainment estimates the revenue implied by your current pipeline at the supplied win rate. Treat it as a planning model, not a forecast commitment.

Total-target coverage divides qualified open pipeline by the full period revenue target. Gap coverage divides qualified open pipeline by the remaining target after subtracting closed-won revenue. Salesforce Revenue Insights uses open pipeline divided by gap to quota. Showing both prevents teams from comparing two differently defined coverage numbers as if they were the same metric.

There is no universal healthy multiple. A common B2B rule of thumb is around 3x to 4x, but the mathematically relevant starting point is the inverse of your qualified opportunity win rate. A 25 percent win rate implies about 4x required coverage, while a 50 percent win rate implies about 2x. Deal quality, stage mix, sales cycle and slippage can require more buffer.

Coverage exists because not every qualified opportunity closes. If one in four qualified opportunities closes, the revenue team needs roughly four dollars of qualified pipeline for each dollar of remaining target, before considering timing, deal concentration or quality risk.

Count opportunities that meet your revenue organization's qualification criteria and have a realistic close window inside the period being measured. Including stale, unqualified or out-of-period opportunities inflates coverage without improving the probability of hitting the revenue target.

Both views answer different questions. Unweighted coverage shows how much qualified opportunity value exists at face value. Weighted pipeline applies stage or deal-level probabilities and is closer to an expected-value view. Do not mix weighted pipeline with an unweighted coverage benchmark without labeling the method.

No. Coverage measures whether enough opportunity value exists to support a target. A forecast estimates what the team expects to close, usually using stage, probability, deal inspection, rep judgment or predictive models. Coverage is an input to revenue planning, not a substitute for forecasting.

A high multiple can still contain stale deals, weak qualification, unrealistic close dates, poor stage distribution, low buyer engagement or concentration in a few large opportunities. Coverage quantity does not guarantee pipeline quality or timing.

Coverage should be reviewed on a cadence that leaves time to create and mature replacement pipeline. Weekly reviews are common during active quarters. Longer sales cycles require teams to inspect next-quarter coverage before the current quarter is close to ending.

Pipeline created late in a period may not have enough time to close. This calculator subtracts the sales-cycle duration from the weeks remaining to estimate the sourcing window. If the sales cycle is longer than the time left, pipeline created now is unlikely to support the current-period target and should be planned against a future period.

Pipeline dollars alone do not tell teams how much upstream activity is required. Average deal size converts a pipeline shortfall into an approximate number of opportunities. Meeting-to-opportunity conversion then estimates how many qualified meetings are needed to create those opportunities.

Pipeline coverage is a leading capacity check for the revenue plan. It connects the target with the amount of opportunity value needed before the quarter or year closes. RevOps can use the gap to set sourcing targets, allocate demand-generation effort, inspect weak segments and escalate risk before a forecast miss becomes unavoidable.

Why this output matters

Pipeline coverage tells RevOps whether the qualified opportunity value in the current selling window is sufficient to support the revenue target. Reading coverage against win rate, remaining quota, deal size and sales cycle helps revenue teams identify pipeline gaps early, set pipeline-generation targets, and separate a full CRM from a pipeline that can realistically support the number.

Related RevOps tools

View RevOps tools
Unit Economics Calculator
Calculate LTV, CAC payback, LTV:CAC, NRR, Magic Number and Burn Multiple.
Founder-Led Sales Ceiling Calculator
Calculate the revenue ceiling created by founder selling hours, deal size and founder dependency, then quantify the handoff required to reach a target.