Stop Reporting Pipeline Coverage to Your Board

No, 3x pipeline coverage is not a reliable forecast, and the reason is simple: when the ratio becomes the target, your team manages the ratio. Report two numbers instead, pipeline created inside the period and days in stage against the deals you actually won, both pulled from stage history you already have.

Coverage survives in board decks because it is easy to calculate and comfortable to present. One division, one number, a green cell. It also happens to be the only revenue metric that improves when your team does the wrong thing.

Why your coverage ratio always lands near 3x

Coverage is open pipeline divided by quota. The denominator is quota, which is fixed. The numerator is a sum of amounts and close dates that your reps type in. When the standing instruction is "we need 3x," reps supply 3x. They add marginal deals, they nudge close dates into the quarter, they round amounts up. The number self-corrects to the target regardless of what the quarter actually holds.

This is not a theory about rep behaviour, it is built into the arithmetic. The numerator is editable and the target is known, so the numerator moves to meet the target.

The arithmetic gets worse when you strip the dead weight. A reported 4x that contains 30% dead deals is really 2.8x. Teams overstate coverage three ways: stale deals left open, blended win rates across segments that convert at very different rates, and measuring at a point in the quarter that flatters the result.

And the mechanism that makes coverage structurally blind: a deal that has sat in Proposal for sixty days occupies exactly the same slot in the coverage calculation as a deal that entered Proposal yesterday. Coverage counts dollars. It does not count time, and time is where the forecast lives.

The mirror case is the one nobody puts on a slide. A company can walk into a quarter thin on coverage and still beat the number, because a strong create-and-close motion generated pipeline inside the period that coverage never counted on day one. Coverage punishes that company and rewards the one carrying a warehouse of aging deals.

Coverage is among the most reported numbers in B2B revenue, and forecast accuracy remains a standing complaint in most revenue organisations. Those two things belong in the same sentence.

The two numbers that actually predict the quarter

One: pipeline created in period. How much new qualified pipeline did you create this quarter, and what share of the quarter's expected revenue will come from deals created and closed inside it? This is the number that separates a business with a working demand engine from one living off inventory. Carry-over pipeline tells you what you did last quarter. In-period creation tells you what you are doing now.

Two: days in stage, measured against deals that eventually closed won. Take your won deals from the last twelve months, pull the stage-change timestamps, and compute the median days each winner spent in each stage. That curve is the shape of a deal that closes at your company. Now compare every open deal against it. A deal running past the median for its stage is not neutral. It is drifting.

Age is a sharp predictor, and it is one you can verify inside your own account rather than borrowing. Compute win rate for deals that closed inside your median cycle against those that ran past it. In most pipelines the gap is wide enough to settle the argument on the spot.

How to compute both this week, without a data team

Your CRM already stores every stage change with a timestamp. That is the whole dataset.

1. Export won deals, last twelve months. For each, calculate days spent in every stage and the total days from creation to close. Take the median, not the mean. One eighteen month enterprise deal will wreck an average.
2. Build your winner curve. For example: Discovery 9 days, Demo 11, Proposal 12, Negotiation 7, total median win cycle 39 days. Do this per segment. SMB and enterprise are different businesses sharing a logo.
3. Score your open pipeline against the curve. For every open deal, days in current stage divided by the winner median for that stage. Anything above 1.0 is slow. Anything above 1.5 is a problem.
4. Measure in-period creation. Sum qualified pipeline created since the quarter started, and separately sum deals created and closed won inside the same quarter. The second figure is your create-and-close rate, and it is the number that tells you whether you can still influence this quarter.

Healthy ranges depend entirely on cycle length. On a 30 to 45 day cycle, a large share of the quarter's revenue should come from in-period created pipeline, and a deal 20 days past its stage median is close to dead. On a 90 to 120 day cycle, almost nothing you create this quarter closes this quarter, so in-period creation is a forecast for next quarter, and your stage medians are measured in weeks, not days. Stage duration differences are real: early-stage movement that takes a few days in SMB routinely takes two to three weeks in enterprise, and closing stages stretch further still. Do not import anyone else's benchmark. Your own won deals are the only honest reference.

The stale-deal rule and the conversation that follows

The rule: any open deal older than 1.5x your median won cycle for its stage and segment gets reforecast or closed. On a 12 day Proposal median, that puts the stale line at 18 days. Pick a multiple, 1.5x is a defensible starting point, and hold it rather than relitigating it deal by deal.

Much of what you lose is not lost to a competitor. It is lost to no decision, a buyer who never chooses at all. You are not being outsold. You are being out-waited. Check your own closed-lost reasons for the split.

The conversation with the rep. Three questions, no commentary. What changed since the last documented buyer action? Who, by name, is pushing this forward inside their company? What is the specific event that makes them decide, and is it on a calendar? If the first and third answers are vague, the deal moves out of the quarter today. Not next week.

The conversation with the buyer. Do not chase for an update, that produces politeness and silence. Name the indecision instead: "My read is this is not a priority fight you can win this quarter, and that is a legitimate answer. Should we plan around a decision in Q3, or should I close this out and come back when the trigger is real?" Giving a buyer permission to say no surfaces the truth faster than any follow-up sequence, and it costs you nothing you were going to get anyway.

The board slide to use instead, and the spend it quietly kills

Four lines, one chart:

• Pipeline created in period, against the same quarter last year.
• Create-and-close revenue as a share of the quarter.
• Median days in stage for open deals versus the won-deal curve, by segment.
• Dollars sitting past the 1.5x stale line, and what you did with them.

Coverage can stay as a footnote, as context, not as the headline.

Now the part most revenue teams miss. Coverage is a sales artefact, so nobody traces it back to marketing spend, and that is where the money leaks. Once you can see stage velocity by campaign source, the ranking of your channels changes. A source that produces fewer deals that move fast and close inside the period is worth more than a source that produces volume that ages out past your stale line. Cost per lead will tell you the opposite, confidently, every month. This is why the channel your dashboards love is often the one funding your stale pipeline.

That join, stage history on one side and campaign source on the other, is exactly what fragmented stacks cannot do. The deal history is in the CRM, the source is in the ad platform, the behaviour is in analytics, and nobody owns the sentence that connects them. In Payani AI, deals and pipelines hold the stage history, reporting and analytics fuses GA4 with CRM data, website visitor tracking and lead scoring show what the account did before and between stages, and Ask Payani reads all of it in one place. You get the two numbers your board should be asking for, and the spend decision that follows from them.

Frequently asked questions

Is 3x pipeline coverage ever useful?

As context, yes. As a forecast, no. One revenue analytics vendor found median coverage across its customer base near 3.5x with real companies ranging from 1.4x to 5x, which means the single ratio carries almost no predictive signal. Keep it as a footnote on the board slide, not the headline.

What two numbers should I report instead?

Pipeline created inside the period, including the share of the quarter's revenue coming from deals created and closed in the same quarter, and median days in stage for open deals measured against the deals you actually won. Both come straight from CRM stage-change timestamps, so neither needs a data team.

How do I set a stale-deal threshold for my business?

Take your won deals from the last twelve months, compute the median days in each stage per segment, and flag any open deal running past 1.5x that median. Published guidance on pipeline ageing puts the practical stale range at 1.5x to 2.0x, with an example of a 12 day Proposal median going stale at 18 to 24 days.

Why does deal age predict the quarter better than pipeline value?

Because coverage counts dollars and ignores time. A deal sitting in Proposal for sixty days occupies the same slot in the coverage calculation as one that entered yesterday. Benchmark work cited in 2025 sales research found opportunities closing within about 50 days winning roughly 47% of the time, falling to 20% or lower past that mark.

How does this change marketing spend decisions?

Once you can see stage velocity by campaign source, a channel producing fewer deals that move fast and close in period outranks one producing volume that ages past your stale line. Cost per lead will rank them the other way. That requires joining CRM stage history with campaign source in one system rather than comparing exports from several.