Most teams forecast the pipeline they can see and miss the revenue motion they cannot see yet. That is the structural flaw in nearly every quarterly forecast, and it is why a healthy looking coverage ratio and a missed quarter show up together so often. The fix is to stop forecasting the pipeline and start forecasting the quarter.
Where does a quarter's revenue actually come from?
Three sources, and only one of them is visible on day one.| Source | Visible on day one | How to model it |
|---|---|---|
| Carry over | Yes, sitting in the CRM | Timing curves applied to existing opportunities |
| In quarter created and closed | No, does not exist yet | Historical creation and same quarter conversion rates by segment |
| Pull forward from future periods | Partially, records exist with later dates | Acceleration rate by segment, priced with the discount cost |
How much of the quarter does day one pipeline really deliver?
Roughly 20 percent of it, measured across ORM's customer base.Across ORM's customer base, of the pipeline carrying close dates inside the quarter on day one, about 20 percent actually closes in that quarter. That means 80 percent of the value sitting in the quarter on day one is not realized in it. Read that number twice, because it changes what a coverage ratio means.
If four fifths of the visible in quarter pipeline is not going to convert this period, then the ratio between total pipeline and target is answering a question nobody asked. The useful question is which specific portion converts, and what fills the space the rest leaves behind.
How do you model revenue from deals that do not exist yet?
From the historical rate at which your segments create and close deals inside the same period.The pattern is measurable even though the records are not. Look back across eight quarters and calculate, per segment, the value of opportunities created after day one that closed before day ninety. That rate is far more stable than most RevOps teams expect, because it is driven by structural things like deal size, buying process length, and demand generation rhythm rather than by individual deal drama.
Timing is what makes this modelable. At ORM each opportunity is grouped by a machine learning model, and each group carries a predicted curve for how long it takes to close. Those curves run from 1 to 80 weeks, with most of the expectation before week 12. Groups whose curves peak inside a few weeks are the ones capable of producing in quarter revenue from scratch. Groups that peak at week thirty cannot, no matter how much of them gets created in month one.
That gives you a direct planning input. If your enterprise segment closes on a twenty week curve, an enterprise pipeline generation push in week two contributes to next quarter, and pretending otherwise is how a plan turns into a miss.
How do you price a pull forward?
By the discount given and the hole left in the next quarter.Pulling deals forward is a legitimate move and it is rarely accounted for honestly. The acceleration usually costs discount, which lowers realized deal size, and it removes revenue from a period that still carries its own target. A team that pulls $800,000 forward to save the current quarter starts the next one $800,000 short with a thinner pipeline behind it.
Model it as a policy rather than a scramble. Set an acceleration budget per quarter, track how much you actually used, and report the next quarter impact alongside the current quarter save. The number that gets reported gets managed.
Why does coverage fail as a substitute?
Because it hides composition.Most teams still work from a 3x to 5x pipeline to goal rule. Across ORM customers, coverage ranges from 1.4x to 5x with most sitting around 3.5x. In stable conditions the rule is directionally predictive, and it is dangerously incomplete, because a company can hold 4x and still miss badly when the pipeline is low quality, concentrated in the wrong stage, dependent on a handful of large deals, inflated by stale opportunities, or built on close dates that sellers keep pushing forward.
The reverse also holds. A company can open a quarter with thin pipeline and outperform if it has a strong in quarter motion, which is exactly the component coverage ignores. The deeper argument sits in the 3x pipeline coverage rule is wrong, and the mechanics of the ratio itself in pipeline coverage.
What breaks the model mid quarter?
A change in the business or the market that the forecast was not built to absorb.The most common reason a forecast fails is that something changed and the forecast rested on old assumptions. A new competitor creates pricing pressure and average deal size falls. Buyer uncertainty stretches the qualified to closed cycle, which pushes in quarter creation out of the quarter entirely. A territory redesign leaves coverage intact while execution suffers.
The in quarter component is the most sensitive to all of this, because it depends on speed. Carry over deals have momentum. Deals that must be created and closed in ninety days have none, and any friction added to the buying process removes them from the period first.
Seasonality deserves the same attention. Q2 and Q4 usually run stronger than Q1 and Q3, and the third month of a quarter usually runs stronger than the first two. A model that ignores that shape will read a normal slow start as a crisis.
What does a good forecast tell you?
How the quarter is going to happen, before it happens.It says what will close from existing pipeline, what must be created and closed in period, what might be pulled forward, and what risk attaches to each path. That is a different document from a coverage report, and it is the one that leaves room to act.
Getting the forecast right in the last week of the quarter does not help anyone, because by then the quarter has already happened. The value is knowing the likely shape of it on day one, early enough to do something about it. For the underlying build, see how to forecast revenue.
Frequently Asked Questions
How do you forecast revenue from deals that do not exist yet?
Model it from history rather than from records. Every segment produces a measurable rate of deals created and closed inside the same quarter, and that rate is stable enough to forecast against once you have enough closed history to fit it. The prediction comes from the creation and conversion pattern, not from opportunities in the CRM.
How much of a quarter comes from pipeline visible on day one?
Less than most teams assume. Across ORM's customer base, of the pipeline carrying close dates inside the quarter on day one, roughly 20 percent actually closes in that quarter. That means 80 percent of the value sitting in the quarter on day one is not realized in it, and the gap has to be filled from somewhere else.
What are the three sources of quarterly revenue?
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 quarter, and pull forward deals from future periods that close early, usually with discounting or a cost to the next quarter.
Why is pipeline coverage a poor substitute for this?
Coverage measures the visible pipeline against a target and says nothing about composition. A company can hold 4x coverage and miss badly when the pipeline is concentrated in the wrong stage, dependent on a few large deals, or inflated by stale records. Coverage is a useful input and it should never be the conclusion.
What does pulling deals forward actually cost?
Discount given away to accelerate the close, plus the revenue removed from a future quarter that still carries a target. Teams routinely understate both. Pulling forward saves the current number and creates the same problem one quarter later with less pipeline to solve it.
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