The pipeline coverage ratio is one of the most quoted, least useful numbers in B2B sales operations.

The benchmarks are well-established. Enterprise SaaS teams typically need 4x to 5x coverage of their quota, and some segments require 5x to 7x — see Outreach’s analysis of pipeline coverage and the supporting research on average B2B win rates around 21 percent. The math is simple. If you close one in five, you need five times your quota in pipeline to hit. Three times is the floor; four to five is the working target.

The problem is that the ratio is a snapshot of a thing whose value comes from motion. A 4x pipeline made up of stale deals is worse than a 3x pipeline made up of fresh ones. The number is the same. The reality is not.

“Pipeline coverage answers the wrong question. The right question is whether the buyer moved this week.” — Mark Southgate

The reason most pipeline reviews feel performative is that they are inspecting the wrong property of the pipeline. Coverage is necessary but not sufficient. Freshness — the rate at which buyers are actually doing things — is the thing that determines whether the coverage will close.

The 4x pipeline that does not close

Imagine two AEs, both with $1M quotas. Both have $4M in pipeline at the start of the quarter. Both have a 4x coverage ratio. The first AE’s pipeline has been steady for nine months — same accounts, same stages, same close dates rolling forward. The second AE’s pipeline is largely new in the last 90 days, with deals in earlier stages but visible buyer activity in each.

Coverage says they are equivalent. The forecast treats them as equivalent. The end of quarter will not.

The first AE’s pipeline is going to slip almost in its entirety. The deals have been in pipeline that long because the buyers were never moving. The seller has been mistaking the absence of “no” for the presence of “yes.” When the quarter ends, the deals will roll into the next one. The coverage looked fine. The realised revenue will not.

The second AE’s pipeline will convert at roughly the win rate of the company’s actual sales motion. Some deals will close, some will not, but the ratio will hold because the buyers are engaged.

This is why coverage as a ratio misleads. It cannot distinguish between pipeline that is moving and pipeline that is static. The pipeline review that only inspects coverage will miss the difference. The forecast that uses coverage as a forward indicator will be wrong, in one direction, predictably.

The four properties of a pipeline that will actually close

If coverage is necessary but not sufficient, what is the rest of it?

Property 1: freshness. A pipeline that is freshening — new opportunities created at a rate that matches or exceeds the rate of opportunities aging out — is structurally healthier than a pipeline of the same size that is static. Watch the creation rate by week. If it falls below the conversion rate, the pipeline is hollowing out even if the headline number looks steady.

Property 2: distribution by stage. A pipeline that is heavily concentrated in late stages looks good for the current quarter and disastrous for the next one. Healthy pipelines have weighted distribution that matches the cycle length of the segment. If 70 percent of your enterprise pipeline is in late stage and you have a 9-month cycle, you have built a cliff into next quarter.

Property 3: movement velocity. Deals that are moving stage-to-stage on a normal cadence are healthier than deals that have been parked at the same stage for two months. Measure stage age, not just deal age. Deals that have been at “proposal” for 60 days are not in proposal stage. They are in slip stage, with the wrong label.

Property 4: buyer-activity recency. This is the property the forecast call rarely inspects. When was the last meaningful buyer-side activity on each deal? Not seller activity — the rep sent an email — but buyer activity: a meeting, a response, a stakeholder added, a document downloaded. Deals where the buyer has been quiet for three weeks have a slippage probability several multiples higher than deals where the buyer was engaged in the last seven days.

A pipeline review that inspects all four — freshness, distribution, velocity, buyer-activity recency — produces a forecast that holds. A pipeline review that only inspects coverage produces a forecast that surprises.

Why the ratio is still useful, when used differently

Pipeline coverage is not useless. It is just a lagging summary of a story whose detail matters more.

Used well, the ratio is a threshold, not a target. Below 3x, you are mathematically unlikely to hit. Below 2x, the rest of the conversation is not really about forecasting — it is about pipeline generation. Above 4x, the conversation can move to quality and motion, because the quantity is at least nominally in place.

The mistake is treating the ratio as the conversation rather than the prerequisite for it.

As Mark Southgate puts it: “Coverage is the entry fee to a useful pipeline conversation. Most teams collect the entry fee and skip the conversation.”

The pipeline review that produces a different result

The shape of a pipeline review that uses coverage as a prerequisite rather than a destination:

  1. First five minutes: coverage check. Confirm the ratio is above the threshold. If not, the rest of the review is about pipeline generation, not deal management. This is a real conversation, but a different one.
  2. Next ten minutes: pipeline composition. What share of the pipeline is in late stage versus early? What is the average age of pipeline by stage versus the segment benchmark? Where is freshness coming from and where is it not?
  3. Next twenty minutes: the deals that matter. The top deals by ACV or strategic importance, inspected for buyer-activity recency, mutual plan status, and named risk. This is where the deal review forum overlaps with the pipeline review. The two should be designed together as part of the deal review operating system.
  4. Last ten minutes: pipeline generation forward look. What is the team doing this fortnight to refresh the pipeline? Who has a generation gap that the next quarter will pay for?

Most pipeline reviews skip steps 2 and 4 entirely and turn step 3 into deal narration. The result is a 60-minute meeting that produces no decisions.

“A pipeline review that only inspects the ratio is the cheapest meeting you can run. It is also the one that produces the worst forecast accuracy. The two things are connected.” — Mark Southgate

The forecast implication

A pipeline that has been inspected for all four properties — coverage, freshness, distribution, motion, buyer-activity — produces forecast categories that mean something. Commit pipeline has actually been pressure-tested for buyer movement, not just labeled by stage. Best case pipeline has been distinguished from the optimistic guess.

The forecast accuracy lift from this is not small. Teams that move from coverage-as-target to coverage-as-prerequisite, combined with the other three properties of pipeline inspection, regularly see forecast variance halve within two quarters. The mechanism is not better forecasting. It is better pipeline diagnosis upstream.

The diagnostic

Pick the largest 30 deals in your current pipeline. For each, answer in 15 seconds:

  1. When was the last buyer-initiated action on this deal?
  2. What stage has the deal been in for the longest, and for how long?
  3. Is the close date a buyer date or a seller date?

If more than one-third of the deals have buyer-quiet windows of 21 days or longer, stage ages above the segment benchmark, or close dates the buyer has not confirmed, your coverage ratio is overstating the pipeline by 20 to 30 percent.

That is not a forecasting problem. That is the difference between coverage as a story and coverage as a number. The number can be hit and missed in the same week. The story takes longer to tell, costs more to inspect, and is what makes the forecast hold.

The teams that take the story seriously stop being surprised by Q3. The teams that rely on the ratio keep finding themselves in the same conversation, every quarter, about why a perfectly fine 4x pipeline produced a missed number.