What Is the Difference Between Scenario Forecasting and a Single-Number Forecast?
A single-number forecast tells you what you expect, and scenario forecasting tells you what would have to be true for that expectation to hold. The first is a commitment. The second is an explanation of the risk sitting underneath it.Most companies produce the single number and stop. A rep roll-up becomes a manager roll-up, a leader applies a haircut, and one figure goes to finance. That figure carries no information about how fragile it is. A number built on five deals each carrying a fifth of the target is treated the same as a number built on 200 deals in a stable segment.
Scenario forecasting adds that missing layer. It does not replace the commit number. It surrounds it with the conditions that would move it.
Why Does a Single Number Hide the Risk in a Quarter?
Because two identical forecast totals can sit on completely different quarters, and the total shows none of the composition. This is the same trap that makes pipeline coverage misleading. A company can hold 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 sellers keep pushing forward.The composition question is the real forecasting question. Not whether you have enough pipeline, but whether you understand how the quarter is going to happen before it begins. That means naming the sources of revenue rather than the total: carry-over deals already in pipeline on day one, in-quarter deals that do not exist yet but will be created and closed inside the period, and pull-forward deals from future quarters that may close early at a discount and leave a hole behind them.
A single number collapses all three into one figure and loses every distinction that would let you act.
What Makes a Scenario Useful Instead of Theater?
Every scenario must name a mechanism and trigger a decision. A downside case labeled "minus 15 percent" is decoration. It gives nobody anything to do, and everybody knows it.The most common reason forecasts miss is that something in the business or the market changed and the forecast was still built on old assumptions. That is where scenarios earn their place, because those changes are nameable in advance:
- A new competitor enters and creates pricing pressure, so average deal size falls. - Interest rates rise, private equity slows capital deployment, portfolio companies cut cost instead of buying, and win rates decline. - Broad market uncertainty makes buyers stop deciding, which stretches the time from qualified to closed. - Territories get redrawn and sellers are distracted, so coverage looks healthy while execution slips.
Each of those has a different early indicator and a different response. Pricing pressure shows up in average closed-won value before it shows up in the forecast, and the response is a discount authority review. A stretching cycle shows up in stage duration, and the response is pipeline generation, not deal coaching.
| Dimension | Single-number forecast | Scenario forecast |
|---|---|---|
| Output | One figure | Three figures with named causes |
| Answers | What do we expect | What would change what we expect |
| Board use | The commitment | The risk explanation behind it |
| Effort | Low | Moderate, mostly one-time setup |
| Drives a decision | Only if it misses target | Yes, each scenario has a trigger |
| Accountability | Clear | Clear only if one case is the commit |
| Failure mode | Hides composition risk | Becomes theater without mechanisms |
How Do You Build Three Scenarios Without Guessing?
Anchor each case to a measurable driver and change one driver at a time. Guessing percentages produces numbers nobody believes. Moving a single driver produces a number somebody can argue with, which is the point.Use four drivers and hold the rest constant: average deal size, win rate, sales cycle length, and pipeline created in period. For the downside, compress average deal size to the level you would see under real pricing pressure and leave the rest alone. For the upside, raise in-quarter pipeline creation to the best rate you have actually achieved rather than an invented one.
Two calibration inputs keep the range honest. First, seasonality, since Q2 and Q4 typically run stronger than Q1 and Q3 and the third month of a quarter runs stronger than the first two, so a flat monthly scenario is wrong before you start. Second, the in-quarter close rate. Across ORM customers, only about 20 percent of the pipeline carrying in-quarter close dates on day one of the quarter actually closes in that quarter, meaning 80 percent of the value sitting in the period does not land in it. A downside scenario built on the assumption that most dated pipeline converts is not a downside scenario.
What Should You Actually Present to the Board?
Lead with the commit number, then show two mechanisms that would move it and what you will do about each. Presenting a range first reads as an unwillingness to commit, and it invites the board to pick a number from your range rather than accept yours.The structure that works runs three slides. The commit number with its composition split across carry-over, in-quarter creation and pull-forward. The two most credible mechanisms that would break it, each with its early indicator and the threshold that triggers a response. Then the current reading on those indicators.
That last slide is what separates a forecast from a report. Saying that average closed-won deal size has moved from 80,000 dollars in pipeline to 40,000 dollars at close is a fact a board can act on. Saying revenue might come in lower is not.
Does Scenario Forecasting Weaken Accountability?
Only if you refuse to designate a commit case. The legitimate objection is that a team presenting a range will later claim any outcome inside it counts as a hit, which turns forecasting into insurance.Close that gap with two rules. Score forecast accuracy against the base case alone and never against the range. And record the probability you assigned to each scenario at the start of the period, so at quarter end you can assess the quality of the risk read as well as the quality of the number. A team that called the downside mechanism correctly and still missed learned something. A team that missed for a reason it never listed did not.
Run this alongside the standard discipline in sales forecasting best practices, and remember what the scenarios are for. Getting the forecast right in the final week of the quarter helps nobody. The value is knowing the likely shape of the quarter on day one, early enough to change it.
Frequently Asked Questions
What is the difference between scenario forecasting and a single-number forecast?
A single-number forecast produces one figure the company plans against. Scenario forecasting produces several outcomes, each tied to a specific set of conditions, so you can see how much the number depends on things that have not been decided yet. The single number is what you commit to. The scenarios explain what would have to be true for that commitment to hold or break.
Should you present scenarios or one number to the board?
Present one number as the commitment and use scenarios to explain the risk behind it. A board needs a figure to plan cash and hiring against, so leading with a range reads as an unwillingness to commit. Leading with the commit number and then showing the two or three mechanisms that would move it demonstrates that you understand the quarter rather than that you are hedging.
How many scenarios should a revenue forecast have?
Three. Any fewer and you have a point estimate with decoration, any more and nobody reads them. The useful structure is a downside driven by one named mechanism, a base case that matches your commit, and an upside driven by a different named mechanism. Each scenario should differ by a cause you can point to, not by a percentage someone picked.
What makes a scenario useful instead of theater?
Each scenario has to name a mechanism and a decision. A downside case that says revenue drops 15 percent teaches nothing. A downside case that says average deal size compresses because a competitor entered with aggressive pricing, and that this triggers a discount authority review, gives someone something to do. If a scenario does not change a decision, delete it.
Does scenario forecasting reduce forecast accuracy accountability?
Not if you designate one scenario as the commit. The risk is real when teams present a range and later claim any outcome inside it counts as a hit. Avoid that by scoring accuracy against the base case only and reporting the scenario weights you assigned at the start of the period, so the quality of your risk assessment is auditable alongside the number itself.
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