Pipeline Coverage Is Not the Forecast
Pipeline coverage is the most trusted number in revenue that tells you the least. A CRO can walk into a board meeting with 4x coverage, feel completely covered, and still miss the quarter by a mile. Coverage is an input. It was never the forecast, and treating it like one is the single most expensive habit in B2B SaaS revenue planning.I have built forecast models for SaaS companies, and the pattern repeats everywhere. Teams forecast the pipeline they can see and miss the revenue motion they cannot see yet. The 3x to 5x pipeline coverage rule feels like rigor. It is actually a way of avoiding the real question.
This post is the case against the rule, and the model I use instead.
Why the 3x Coverage Rule Hides the Quarter
Most teams still run on a 3x to 5x pipeline-to-goal ratio. Across ORM customers the pipeline coverage ratio has a median around 3.5x, with a real spread. I have customers at 1.4x and customers at 5x. In stable conditions the rule is directionally predictive, and that is exactly what makes it dangerous. It is right often enough that people stop looking underneath it.
Here is what a single coverage number cannot see. A company can carry 4x coverage and still miss badly if the pipeline is low quality, concentrated in the wrong stage, dependent on a few large deals, inflated by stale opportunities, or built on close dates that sellers keep pushing forward. The reverse is also true. A team can start thin and outperform if it has a strong in-quarter creation motion. The ratio treats every dollar of pipeline as equal. They are not equal.
Three specifics from ORM data make this concrete.
First, quality decays inside the number. Typically 10 percent or more of a pipeline is stale, meaning no meaningful activity in 12 months. We define meaningful activity as a change in stage, close date, or amount. Stale deals still count toward coverage. They contribute almost nothing to revenue. Your ratio looks fat while the usable pipeline is thinner than it reads. This is a pipeline hygiene problem masquerading as a coverage strength.
Second, the value is inflated. It is common to see an average pipeline deal size of 80,000 dollars against an average closed-won deal size of 40,000 dollars. Deals get logged at aspiration and close at reality. If your coverage math uses face value, you are overstating coverage by the size of that gap before a single deal slips.
Third, and most damning, the timing rarely holds. On the first day of the quarter, only about 20 percent of the pipeline with close dates inside that quarter actually closes in that quarter. That means 80 percent of the value dated to land this quarter does not. A coverage ratio built on those close dates is built on sand, because deal slippage is the norm, not the exception.
So the metric that makes executives feel informed is the same metric that masks the actual risk. Total coverage without context is noise dressed as insight.
The Better Question, and the Carry-Create-Pull Model
The real forecasting question is not "do we have enough pipeline?" The better question is "do we understand how the quarter is going to happen before it begins?"
Answering it means decomposing the quarter into its actual sources of revenue. I call this the Carry-Create-Pull model, and it is the frame I use for every revenue forecasting conversation.
Every dollar you close in a quarter comes from one of three places:
| Source | What it is | Where teams go wrong |
|---|---|---|
| Carry-over | Deals already in pipeline on day one, expected to close this quarter | Over-trusted; slippage and value decay ignored |
| In-quarter created | Deals not visible yet that will be created, qualified, and closed inside the quarter | Under-modeled; treated as zero because it is invisible |
| Pull-forward | Future-period deals closed early, often with discounting | Cost of pulling forward is understated |
Coverage answers none of these. It blends all three sources into one ratio and calls it a plan. Carry-Create-Pull forces you to forecast each source on its own terms, with its own risks. That is what a forecast is supposed to do.
A Worked Example (illustrative, not a benchmark)
Take a company I will call Cedarline. Numbers below are illustrative, meant to show the mechanics, not benchmarks to copy.
Cedarline opens the quarter with a 2M target and 7M of open pipeline. That is 3.5x coverage. On the rule, they are covered. The VP of Sales tells the board they are in good shape.
Then Cedarline runs Carry-Create-Pull. Of the 7M, 1.5M is stale under the 12-month rule and should be discounted to near zero. The remaining carry-over is logged at an average deal size well above what these deals historically close for, so the realistic carry-over contribution is closer to 900K, not the 7M headline. In-quarter creation, which they never modeled, historically delivers another 700K. Pull-forward could add 300K, but only by discounting deals that were tracking to close next quarter at full price.
The 3.5x number said covered. The decomposition says Cedarline is looking at roughly 1.6M against a 2M target, with a 400K gap they have to close by manufacturing in-quarter pipeline or accepting margin-eroding pull-forward. Same pipeline. Completely different quarter. The difference is whether you looked at a ratio or at the composition.
What Coverage Is Actually Good For
I am not telling you to throw coverage out. I am telling you to demote it. Coverage is a useful input and a terrible conclusion. Use it as a first-glance sanity check, then immediately go underneath it.
That means pairing coverage with real pipeline inspection: stage distribution, deal concentration, age, source channel, and close-date stability. The best early signal of a soft quarter is not a low ratio. It is a rep changing a close date, and the earliest signal of all is the absence of any signal, no activity, no notes, no movement on a deal that is supposed to be live. A ratio will never show you that. Inspection will.
The prize here is timing. Getting the forecast right in the last week of the quarter helps no one, because by then the quarter has already happened. The value is knowing the likely shape of the quarter on day one, early enough to build pipeline, reassign coverage, or reset the number with the board while you still can. Coverage gives you a feeling of readiness in week one. Carry-Create-Pull gives you a plan.
The "best practice" I quietly ignore is treating pipeline coverage as an answer. It is a starting point, not a conclusion, and the teams that beat their number are the ones that decompose the quarter instead of trusting the ratio. That decomposition, carry, create, and pull, each forecast on its own risk, is exactly the model ORM builds into your forecast so you see the true shape of the quarter on day one.
Frequently Asked Questions
What is pipeline coverage?
Pipeline coverage is the ratio of open qualified pipeline to your revenue target for a period. A 3x coverage ratio means you have three dollars of open pipeline for every dollar of quota. The standard range in B2B SaaS is 3x to 5x, and across ORM customers the median sits around 3.5x, with a spread from roughly 1.4x to 5x.
Is pipeline coverage the same as a forecast?
No. Coverage is a single input that tells you how much pipeline exists relative to your goal. A forecast explains how the quarter will actually happen: what closes from existing pipeline, what gets created and closed inside the quarter, and what might be pulled forward. Coverage can look healthy while the forecast is failing, because a ratio hides the composition and quality of the pipeline underneath it.
Why is the 3x pipeline coverage rule unreliable?
The rule assumes every dollar of pipeline is equal, and it is not. A company can hold 4x coverage and still miss if the pipeline is concentrated in a few large deals, aged and stale, sitting in the wrong stage, or built on close dates sellers keep pushing. In ORM data, only about 20 percent of the pipeline dated to close in the quarter on day one actually closes in that quarter, so a raw coverage number tells you very little about the outcome.
How should you decompose a quarterly forecast?
Split the quarter into three revenue sources: carry-over deals already in pipeline on day one and expected to close, in-quarter deals that are not visible yet but will be created and closed inside the period, and pull-forward deals from future quarters that may close early. Forecasting each source separately exposes risk that a blended coverage ratio hides, and it lets you act on day one instead of the last week.
What makes pipeline stale, and why does it matter?
Pipeline is stale when an opportunity has had no meaningful activity, meaning no change in stage, close date, or amount, over a long window. ORM uses a 12-month rule for most customers, and typically 10 percent or more of a pipeline is stale and untouched for a year. Stale opportunities inflate your coverage ratio while contributing almost nothing to the forecast, which is exactly how a healthy-looking number masks a thin quarter.
Why is average deal size in pipeline higher than closed-won?
Deals are frequently logged at aspirational values and get negotiated down before they close. In ORM data it is common to see an average pipeline deal size of 80,000 dollars against an average closed-won deal size of 40,000 dollars. If your coverage math uses pipeline value at face, you are overstating coverage by the full size of that gap, which is one reason coverage alone should never be treated as the forecast.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo