← All articles

GTM Operations

3x Pipeline Coverage Is a Number That Lies to You

Required coverage is 1 divided by your win rate. At the 19% win rate B2B posted in 2025 you need 5.3x, not 3x. Here is the truth stack that replaces the ratio, with the queries to build it this week.

· 12 min read

Close 19% of your pipeline and 3x coverage means you miss the quarter by roughly 40%. That is the number the ratio hides. For years pipeline health had one answer, chanted in every review from SMB to enterprise: keep 3x in the pipe and you are covered. A rep shows $3M of open pipeline against a $1M quarter, the room nods, and everyone moves on. Then the quarter closes at $780K and the same room asks how a covered number missed.

It missed because 3x was never a real number. It was a ratio pasted over a win rate nobody put on the same slide. Required coverage is one divided by your win rate. B2B win rates fell to 19% in 2025, down from about 29% the year before (Ebsta and Pavilion, 2025 B2B benchmarks). At 19% the coverage you need is 5.3x. Teams still quoting 3x are running at barely half the pipeline they think they have, and 76% of reps missed quota in the first half of 2025 (Ebsta and Pavilion). The ratio did not break because reps got worse. It broke because the win rate that produced it walked out the door and the number stayed.

19%
B2B win rate in 2025, down from 29% (Ebsta/Pavilion)
5.3x
Coverage a 19% win rate requires, not 3x
$265K
Hidden miss in the worked example below

Here is what I build in place of the ratio. Four honest layers stacked on top of a weighting table, each one correcting a different lie the raw number tells. This is the framework. Scroll it, then I will show you the math and the queries under every rung.

Build it bottom to topThe coverage truth stack
  1. L5Report three numbers3 numbers

    Every pipeline review shows raw coverage, weighted coverage, and stripped-and-weighted coverage side by side. The gap between the first and the last is the action item.

  2. L4Strip the zombies0.52x

    Exclude any open deal with no activity in 21 days before you weight it. Show it as its own line so reps see how much of their coverage is already dead.

  3. L3Weight the pipeline by stage$735K

    Multiply each open dollar by its stage weight and sum. This weighted total is what you compare to quota, per rep and per stage, never blended.

  4. L2Set required coverage from win rate1 / win rate

    Replace the flat 3x with 1 divided by win rate, computed per segment. SMB and enterprise do not share a win rate, so they do not share a required-coverage number.

  5. L1Build the weighting table365 days

    Compute per-stage entered-to-won close rate from the last 365 days of closed opportunities. Store it once so every dashboard reads one source, not a hardcoded guess in ten places.

Locate yourself on that ladder. Most teams live on the bottom rung, quoting a raw ratio and calling it a forecast. Every rung above it subtracts a specific illusion. By the top rung the number you carry into the review is one you can defend, because you can show your work at each step.

The math the ratio hides

Coverage is only meaningful against the rate at which pipeline converts to revenue. Required coverage is one divided by your win rate (Clari, 2026 coverage framework). Close 50% of your pipeline dollars and you need 2x. Close 25% and you need 4x. Close 19% and you need 5.3x. So a rep sitting at 3x coverage with a 19% win rate is not covered. That rep is carrying $3M against a $1M quota and needs $5.3M. The 3x looked safe against a rule of thumb and hid a $2.3M gap.

That inverse relationship is the whole game, and it is worth seeing rather than reading.

The relationship Required coverage is the inverse of win rate
Win rateCoverage needed19% needs 5.3x25% needs 4x33% needs 3x50% needs 2x
The lower your win rate, the more pipeline every dollar of quota demands. 3x is only correct at a 33% win rate.

Put your own win rate in and watch the required number move. This is the calculation nobody runs in the meeting.

Coverage you have vs coverage you need

coverage

Try

Below ~3x you are almost certainly going to miss unless win rates are unusually high. Above ~5x the number is either sandbagged pipeline or wishful staging. The healthy band is 3 to 4x.

coverage: 3.6x

Where 3x came from and why it stuck

Somewhere a sales leader with a 33% win rate said “keep 3x in the pipe,” and it was correct for that team in that year. Then it detached from the win rate that produced it and became scripture. Now teams that close 18% and teams that close 45% both chant 3x, and only one of them is telling the truth. The ratio survived because it is easy to say in a meeting and impossible to argue with when nobody has the win rate on the same slide.

Here is the honest version of the rule across win rates. Print it and tape it to the pipeline review.

Win rateRequired coverageWhat 3x buys at this rate
50%2.0xOver-covered, likely sandbagging
40%2.5xComfortable
33%3.0xExactly covered (where the rule was born)
25%4.0x75% of what you need
19%5.3x57% of what you need
15%6.7x45% of what you need

The row that should scare you is the 19% row, because that is the market. RepVue put average quota attainment at 42.7% for Q2 2025, with 57.3% of reps missing (RepVue, Q2 2025). A team quoting a 3x rule calibrated for a win rate it no longer has is running at 57% of the coverage it believes, and the attainment numbers show exactly that shortfall landing on the board.

Coverage is also not one number for the whole company. Enterprise teams running 15% to 25% win rates on 120-day-plus cycles need 4x to 7x on a rolling two-quarter basis (Clari). A blended company coverage number averages a high-velocity SMB motion against a consensus-buying enterprise motion and describes neither. Compute it per segment or do not compute it.

Stage-weighted coverage is the honest version

Raw coverage treats a Stage 1 discovery call and a Stage 5 verbal commit as the same dollar. A dollar in a stage that historically closes 12% of the time is worth twelve cents of forecast. A dollar in a stage that closes 70% is worth seventy. Stage-weighted coverage multiplies each open dollar by that stage’s historical conversion-to-close, sums it, and compares the weighted total to quota. That number survives contact with a quarter-end.

Pull your own stage conversion first

This is a report, not a guess (rung L1). Take the last four closed quarters and for every stage compute what fraction of dollars that entered that stage eventually closed won. The fastest first cut is closed opps grouped by the stage they reached.

SELECT StageName, IsWon, COUNT(Id) cnt, SUM(Amount) amt
FROM Opportunity
WHERE IsClosed = true
  AND CloseDate = LAST_N_DAYS:365
GROUP BY StageName, IsWon

For a truer read of “entered this stage, eventually won,” pull stage transitions from history rather than final stage.

SELECT OpportunityId, StageName, CreatedDate
FROM OpportunityFieldHistory
WHERE Field = 'StageName'
  AND CreatedDate = LAST_N_DAYS:365
ORDER BY OpportunityId, CreatedDate

Roll each opportunity’s transitions up to the set of stages it touched, join to whether it eventually won, and you have entered-to-won conversion per stage. Store the result once as custom metadata or a small object so every report reads the same weights. If ten dashboards each hardcode their own stage probability, you have ten forecasts and no source of truth. That is the difference between the L1 rung holding and quietly rotting.

A worked example

Take a rep with a $1M quarter and $3M of open pipeline. Raw coverage: 3x. Everyone relaxes. Now watch what happens as each rung of the truth stack goes to work on that same $3M. The raw pile dissolves into the sliver that is real.

Same $3M, three honest numbersRaw pipeline dissolves into real coverage
3.0xRaw pipeline$3M against a $1M quota. 3x. The room relaxes and moves on.

Split the $3M by stage and apply the weights this team posts in its own history. The chart is the story: the raw pile on the left, what each stage is worth once you weight it.

Open pipeline vs stage-weighted value
Same $3M of pipeline. Toggle between what the rep reports and what each stage is worth once weighted. Weighted total: $735K against a $1M quota.
View as table
ItemValue
Discovery1,200K
Qualified900K
Proposal600K
Negotiation300K

The stage math in a table, so the weighting is explicit.

StageOpen pipelineHistorical closeWeighted value
Discovery$1.2M10%$120K
Qualified$900K20%$180K
Proposal$600K40%$240K
Negotiation$300K65%$195K
Total$3.0M (3x)$735K (0.74x)

Weighted pipeline: $735K against a $1M quota. The rep with 3x coverage is forecasting a $265K miss, and the raw ratio said they were fine. The gap was hiding in a $1.2M pile of early-stage dollars that convert at ten cents.

Reconcile it back to the required-coverage table and the numbers line up. That $735K of weighted value against $3M of raw pipeline is a blended close rate of 24.5%, so this rep needs roughly 4x coverage (the 25% row), not 3x. At the 19% blended rate the market is posting they would need the full 5.3x. Either way 3x was never enough. The weighting made the shortfall visible before quarter-end instead of after.

Now subtract the zombies

Weighted coverage still assumes every open dollar is a live dollar. Roughly 30% of open pipeline has had no activity, no email, no call, no meeting, in 21 or more days, and a 4x book with 30% stale is an effective 2.8x before you weight anything (Clari). Those deals sit in a stage but they are not moving. Treat a no-activity-21-days deal as dead until proven otherwise, because that is how it behaves.

Find them with the filter that matters, last activity, not last edit.

SELECT Id, Name, StageName, Amount, LastActivityDate
FROM Opportunity
WHERE IsClosed = false
  AND (LastActivityDate = null OR LastActivityDate < LAST_N_DAYS:21)
ORDER BY Amount DESC

Run the subtraction on the worked example to feel it. Strip about 30% of the dollars in each stage for no recent activity, then reweight the survivors, and the $735K weighted number falls to roughly $515K, or 0.52x live coverage. A stalled deal in Negotiation with a 65% stage weight is not worth 65 cents. It is worth close to zero, because it is not in Negotiation anymore. It is in limbo wearing a Negotiation label.

What the review shows What is there once you look
Headline coverage 3.0x, "we are covered" 0.52x live and weighted
Early-stage dollars Counted at full value Worth about 10 cents each
Stalled deals Still in their stage No activity 21+ days, near zero
The conversation "You are fine" "You need $600K of new pipe by week 4"
The distance between these two columns is the size of the forecast lie.

What to report instead

Stop reporting raw coverage on its own (rung L5). In the pipeline review put three numbers on the rep: raw coverage, weighted coverage after stage conversion, and weighted coverage after stripping deals with no activity in 21 days. The distance between the first and the third is the size of the lie you were about to forecast on. When raw says 3x and stripped-and-weighted says 0.52x, the conversation changes from “you’re covered” to “you need $600K of new pipe by the fourth week,” which is a conversation someone can act on.

There is a timing trap here too. Coverage checked in week 10 of a 13-week quarter is an autopsy, not management (Clari). By then the pipeline that could have closed this quarter is already built or already missing. The three-number report earns its keep when you run it in week 1 and week 4, while there is still time to source. Run it at week 10 and you are narrating a result, not changing one.

The 3x rule of thumb costs you one blown forecast per year. The weighting table costs you an afternoon. Two moves compound the fix: build the truth stack once, and pair it with a forecast that names its own assumptions so the coverage number and the commit number tell the same story. For that second move see the forecast you can defend, and for the deals rotting under your coverage number see the zombie deal autopsy. Pull the query above, build the weighting table, and walk into Friday’s review with raw coverage sitting next to the stripped-and-weighted number. Once the room sees the two side by side, the raw ratio loses its authority on its own.

pipeline forecasting coverage

Keep reading

One email. Every week.

One email a week: an operating problem I solved or botched, with the model, the numbers, and what I would change. No roundups, no theory, unsubscribe whenever it stops being useful.

The newsletter opens soon.

Connect a provider in src/config.ts