ANAlpesh Nakrani
SolutionsBlogBooksPraiseAboutWork with me
Back to the blog
Blog/Sep 24, 2026 · 10 min

Pipeline Coverage Is Not Pipeline Quality

A coverage ratio counts dollars sitting in a CRM stage, not evidence a buyer will actually close, and boards keep confusing the two.

A 4x pipeline coverage ratio tells your board you're going to hit the number. It tells you nothing about whether a single dollar of that pipeline reflects a buyer who is actually going to sign, and confusing those two facts is how a forecast that looked safe in July collapses at the exact board meeting where you needed it to hold.

Corinne Aldous ran revenue as CRO at Kestrel Analytics, a mid-market supply chain visibility company selling to logistics and manufacturing buyers. Her Q3 target was $3M in new bookings. The week before the board meeting, her CRM showed $12.6M in open pipeline: a clean 4.2x coverage ratio against a target that had historically closed with reasonable comfort at 3.5x. The number looked exactly like what a board wants to see.

It wasn't real. Two weeks later, her team ran an evidence audit against every open opportunity. Only $6.4M of that pipeline had anything a buyer had actually confirmed attached to it: a named economic buyer, a document, a dated commitment. The rest was pipeline in the sense that a rep had typed a stage name into a dropdown. Coverage dropped from 4.2x to 2.1x overnight, and nothing about the quarter had changed except how honestly the pipeline was being counted.

Nobody at Kestrel had a pipeline volume problem. They had a stage integrity problem, and the coverage ratio, the single number every board and CRO leans on hardest, was the last place anyone would have found it. Coverage math doesn't ask what evidence sits behind a stage. It only counts the dollars parked there.

Key takeaways

  • Pipeline coverage measures dollars sitting in CRM stages, not evidence that a buyer is going to close. A healthy ratio can sit directly on top of a hollow pipeline, and the math will never tell you.
  • Deals advance stages when a rep updates a dropdown, not when a buyer takes an action that proves the deal is real. A stage should require evidence. Most CRMs only require activity.
  • 55% of sales leaders don't have a high degree of confidence in their own forecast accuracy, according to Gartner research, which means the coverage number most boards trust is already distrusted by the people reporting it.
  • Enforcing evidence-based stage criteria will shrink your reported coverage ratio immediately, sometimes by half, and it usually happens right before a board meeting. That's the uncomfortable, necessary cost of a forecast you can actually defend at close.
  • Between 40% and 60% of deals that look like they're moving toward a decision are lost to the buyer's own indecision, not a competitor, which means a coverage ratio built on "still in motion" deals is measuring the wrong kind of motion.

The business problem: coverage counts dollars, not evidence

Pipeline coverage ratio is simple math: divide total open pipeline value by the revenue target for the period. A 4x ratio against a $3M quota reads as $12M of pipeline, and the whole framework assumes a roughly fixed win rate will convert some share of that into closed revenue. The math itself is fine. The assumption underneath it, that pipeline dollars are of roughly equal quality, is the part almost nobody checks before presenting the number.

Clari's own guidance to revenue teams is blunt about what happens when that assumption fails: "a high pipeline coverage ratio built on stale, unqualified, or single-threaded deals is not an asset. It's a liability." A liability, because a board makes hiring, spend, and guidance decisions off that ratio, and none of those decisions get cheaper to unwind when the number turns out to be fiction three weeks before quarter close.

Stage inflation happens for a boring, structural reason. Reps get measured on pipeline generated and stage velocity, both of which reward moving a deal's stage field forward. Nothing forces that stage change to correspond to something the buyer actually did. A deal can sit in "proposal sent" because a PDF went out over email eleven weeks ago and nobody followed up, and the CRM reports that dollar figure inside your coverage ratio exactly as confidently as a deal where the buyer is redlining a contract this week.

Why the usual fix, more pipeline, makes it worse

When a coverage ratio looks thin against target, the standard response is to generate more pipeline: run another campaign, push reps to log more opportunities, loosen the bar for what counts as a qualified deal so more of it shows up as open. I've written about the layer below this one, where a healthy-looking lead count hid a pipeline problem that had been there the whole time, and the layer above it, where a marketing scoring model rewarded activity it could measure instead of intent it couldn't. Coverage ratio is the third layer, the one boards actually see, and it inherits every distortion baked into the two layers underneath it.

Adding volume to a coverage ratio that already contains hollow deals doesn't dilute the hollow deals. It makes the ratio bigger while the hollow share stays the same or gets worse, because the new pipeline gets logged under the same loose stage criteria that inflated the old pipeline in the first place. A bigger number built on the same broken definition is not progress. It's the same problem with better cover.

There's a second reason the volume fix fails, and it has nothing to do with CRM discipline. Research behind the book The JOLT Effect, drawn from a study of more than 2.5 million recorded sales conversations, found that 40% to 60% of deals that appear to be progressing toward a decision are ultimately lost to the customer's own indecision, not to a competitor. A deal can pass every stage gate you have, look perfectly healthy in the pipeline report, and still die because the buyer never resolves their own internal doubt. Coverage ratio has no mechanism for detecting that risk. It only sees a dollar figure sitting in a stage.

A pipeline coverage ratio answers one question: how many dollars are sitting in the CRM. It was never built to answer the question a board actually needs answered: how many of those dollars represent a buyer who is going to act.

The framework: evidence per stage, not activity per stage

The fix isn't a better ratio. It's a different definition of what earns a deal the right to sit in a given stage. I ask every revenue team I work with, including inside ViitorCloud, to require a specific piece of buyer-confirmed evidence before a deal advances, not a rep's judgment call that the conversation "felt like" progress.

  • Qualified. A named problem with a quantified cost, confirmed in the buyer's own words in an email or meeting notes, not inferred by the rep from a good call.
  • Validated. An economic buyer engaged directly, by name and title, not relayed through a champion who "will loop them in" eventually.
  • Committed. A mutual close plan with dated next steps on both calendars, agreed to by the buyer, not a plan your team proposed and never heard back on.
  • Contracted. Procurement or legal has the paperwork, or the buyer's economic authority has verbally confirmed the deal to their own leadership, not just to your rep.

Two more rules catch what stage evidence alone misses. Any deal open longer than twice your average sales cycle gets discounted out of coverage regardless of its stage; time is itself evidence, and a deal "committed" for five months without closing is telling you something the stage field won't. Any deal with a single point of contact, no second stakeholder ever looped in, gets flagged regardless of stage too, because a single-threaded deal has no way to survive its champion changing jobs or simply losing interest.

What the research says about why this keeps happening

This isn't a Kestrel-specific failure. Gartner research reports that 55% of sales leaders don't have a high degree of confidence in their own sales forecast accuracy, which is a striking admission from the people whose job is to defend that number to a board every quarter. If the people reporting the ratio don't trust it, the ratio was never doing the job it was supposed to do.

Clari's own analysis shows how fast the gap compounds once stale pipeline gets involved: a team reporting 4x coverage with 30% of that pipeline stale can be running real, evidence-backed coverage closer to 2.8x, without anyone changing a single number in the board deck. The reported ratio and the real ratio can differ by nearly half, and the CRM will show no warning that they've diverged.

A disqualification rate above 80% is not sales being difficult, and a coverage ratio that keeps missing the number is not a forecasting problem. Both are the same failure: a model counting activity it can observe instead of evidence it never asked for.

None of this should surprise anyone who has run a forecast. It surprises boards, which is exactly the problem, because the gap between reported coverage and evidence-backed coverage tends to become visible at the worst possible time: the week you miss.

The ViitorCloud perspective: the machine flags the gap, judgment closes it

The AI-Native argument I make about engineering work applies to pipeline the same way it applies to a lead funnel or an MQL score. A model can flag every deal that violates a stage-evidence rule faster and more consistently than a manager working the CRM by hand: the deal open longer than twice the sales cycle, the single-threaded opportunity, the "committed" deal missing a dated next step. What it cannot do is decide whether the qualitative evidence a rep entered is actually real, whether a buyer's verbal commitment is trustworthy, or whether a stalled deal deserves one more push or a clean kill. That call is still a judgment a person makes, and it's the one that decides whether your coverage ratio means anything at all.

As VP of Growth at ViitorCloud, I run our own forecast against these same evidence rules before I'd recommend them to anyone else's revenue team. It's the same discipline behind the work described across ViitorCloud's case studies: an accurate, smaller number beats an optimistic one every time procurement actually gets involved.

We now run this as a working engagement for revenue leaders who suspect their coverage ratio is reporting hope instead of pipeline, informally called a Pipeline Quality Audit: we pull your open pipeline, apply evidence rules stage by stage, and hand back a real coverage number instead of a recommendation to generate more leads. If your board keeps asking why a healthy-looking ratio keeps missing the number, ViitorCloud's technology consulting team runs the Pipeline Quality Audit against your actual CRM data, not a benchmark deck.

Here's the trade-off I'd rather name than hide. Applying evidence-based stage criteria will shrink your reported coverage ratio immediately, possibly by half, and it will usually happen right before a board meeting, because that's when someone finally runs the audit. The honest answer to "why did coverage just drop" is that it was never the number you thought it was. A smaller, evidence-backed ratio is the only one worth presenting, because it's the only one that survives contact with the quarter.

A stage-integrity audit you can run this week

This takes an afternoon against your current open pipeline, not a new tool or a new hire.

  • Pull every open opportunity and check it against the evidence-per-stage criteria above, not the stage label the CRM currently shows.
  • Discount or flag any deal open longer than twice your average sales cycle, regardless of what stage it's sitting in.
  • Ask each rep to name the economic buyer, by name and title, for every deal above your average deal size, and flag anything single-threaded.
  • Recalculate coverage using only opportunities that pass the evidence bar, and compare it to what the CRM currently reports. The gap is your real number, quantified.
  • Report both ratios at your next board meeting: reported coverage and evidence-backed coverage. The size of the gap is itself a useful metric to track quarter over quarter.

For most teams running this for the first time, that gap is large. It's the conversation worth having before your next forecast call, not the one about funding another lead channel.

Frequently asked questions

What is a healthy pipeline coverage ratio?

It depends entirely on your win rate: a common rule of thumb is coverage equal to 1 divided by win rate, so a 25% win rate needs roughly 4x coverage and a 33% win rate needs roughly 3x. That math only holds if the pipeline behind it is evidence-backed. A 4x ratio built on stale or single-threaded deals behaves like a much lower real ratio the moment those deals fail to close.

Why does a high coverage ratio still lead to missed forecasts?

Because coverage ratio counts dollars assigned to a CRM stage, not evidence that a buyer is actually going to act. A deal can sit in an advanced stage for months without a confirmed economic buyer, a dated next step, or any buyer-side commitment, and the coverage math will count it exactly the same as a deal that's genuinely about to close.

How do I know if my pipeline has a stage-quality problem instead of a volume problem?

Run the evidence audit described above against your current open pipeline. If your evidence-backed coverage comes in meaningfully lower than your reported coverage, commonly by a third or more, you have a stage-quality problem. Adding more leads or opportunities on top of that gap will make the reported number look better while the real number stays exactly as broken.

Does fixing pipeline quality mean my team should generate less pipeline?

No. It means the stage a deal sits in should require buyer-confirmed evidence before it counts toward coverage, not just a rep's stage-field update. Fix the evidence bar first, so you can trust what a coverage ratio is actually telling you, and only then decide whether volume needs to go up, down, or stay the same.

Share
Next

Keep reading

View all blogs

Ask AI about Pipeline Coverage Is Not Pipeline Quality