Best case, worst case, most likely forecasting is one forecast, built on the same rep-confidence inputs, presented three times at three different levels of optimism. The three columns don’t measure anything different about the pipeline. They just give leadership a wider range to be wrong inside, and a worst-case column to point to when the number misses.
This structure, expanded on in Gap Revenue Performance, replaces the three-column hedge with three separately measured slices of the pipeline: Commit, Projected, and Upside, each backed by its own historical close-rate data rather than a rep’s gut. The distinction matters because the two structures produce different behavior at the point where it counts most: what happens when a number is missed.
What the Three-Column Hedge Does
Best case, worst case, most likely persists because it looks like discipline. Three numbers instead of one feels more analytical than a single guess. But the three columns vary only in the degree of optimism applied to them. They draw from the same deals and the same rep-reported data every time, regardless of which column a number lands in.
“It’s not forecasting. It’s hiding.” The worst-case column exists to give leadership permission to miss. When the quarter comes up short, the org points to a number it already flagged as possible, and nobody has to explain why the “most likely” column was wrong. The hedge absorbs the miss instead of explaining it.
That’s the functional problem with the model, independent of how sophisticated the surrounding process looks. An organization can run calibration meetings, weight probabilities by stage, and build a clean-looking dashboard around best case, worst case, most likely, and still be measuring nothing more than how confident the rep felt that week.
Commit, Projected, Upside: What Each Number Measures Against
It’s fair to look at Commit, Projected, and Upside and assume it’s the same three-column hedge with new names. The difference is what each number is measured against.
Commit is backed by buyer validation: all five conditions of the Buyer Confidence Model confirmed by the buyer, not the rep, with a historical close rate of 80% or better. Projected is backed by historical maturation data, real conversion rates for deals at three or four of five conditions verified, pulled from the last several quarters rather than asserted by a rep. Upside is early-stage pipeline, one or two conditions verified, reported as ceiling and never included in the number the organization plans against.
Each of the three is its own slice of the pipeline, measured on its own terms, with no overlap between them. The number a CRO takes to the board is Commit plus Projected. Upside is disclosed separately as potential, visible to the board but never counted as planned revenue. Best case, worst case, most likely runs the opposite way: one pool of deals, three degrees of rep optimism applied to the same numbers. For a closer look at how the underlying buyer data feeds that scoring, see Improving Sales Forecast Accuracy With Buyer Input Data.
The Curve Inside the Quarter Is the Real Signal
Under this model, Commit is a number that should rise steadily across the quarter as deals mature and get buyer-verified. A quarter where Commit is still sitting at roughly a third of target by week eight is a quarter with a real problem, and there’s still time to find out which C is breaking across the pipeline before it becomes a board surprise. A quarter where Commit reaches target by week ten is a fundamentally healthier quarter than one that scrapes across the line in the final days, even if both end at 100%: the first was managed, and the second was rescued.
Best case, worst case, most likely can’t produce that signal, because none of its three numbers is anchored to anything that changes systematically week over week. A “most likely” figure in week two and a “most likely” figure in week eleven are both just a rep’s or manager’s current mood about the pipeline, updated on request.
What Changes at the Point of a Miss
This is where the two models diverge in practice, not just in math. Under best case, worst case, most likely, a missed number is recoverable inside the story the three columns already told. The worst case was always on the table. Nobody has to explain why reality landed where the pessimistic column said it might.
Under Commit and Projected, a miss is a different kind of event. If the organization said a deal had all five conditions of buyer readiness verified and it didn’t close, something in the system broke, and the miss demands a specific answer: which condition was scored as verified when it wasn’t, which manager signed off on a deal that shouldn’t have entered Commit, and what needs to change so it doesn’t happen again. That question doesn’t have anywhere to hide inside a three-column hedge, because a hedge was never designed to answer it.
Gartner’s State of Sales Operations survey found that fewer than half of sales leaders and sellers have high confidence in their own organization’s forecasting accuracy, which is the predictable outcome of a structure built to absorb misses rather than explain them. A forecast nobody trusts stops functioning as a planning tool and starts functioning as a quarterly ritual.
Frequently Asked Questions
Why is best case, worst case, most likely forecasting considered unreliable?
Because all three columns are built from the same underlying inputs, rep confidence and CRM stage, with different levels of optimism applied. None of the three measures anything distinct about the pipeline’s readiness to close. The structure functions as a hedge that gives leadership a wide range to be wrong inside, rather than a measurement that improves with more data.
What replaces best case, worst case, most likely in this model?
Commit, Projected, and Upside: three separately measured categories, each backed by its own historical close-rate data. Commit requires full buyer-verified readiness with an 80%-plus historical close rate. Projected covers deals at three or four of five verified readiness conditions, with close rates pulled from historical maturation patterns. Upside covers early-stage deals and is reported as potential, never as planned revenue.
Is Commit, Projected, Upside just a relabeled version of the same hedge?
No. Best case, worst case, most likely applies three degrees of optimism to one undifferentiated pool of deals. Commit, Projected, and Upside are three distinct slices of the pipeline with no overlap, each measured against its own historical data rather than a rep’s stated confidence. The forecast reported externally is Commit plus Projected only; Upside is disclosed separately and never planned against.
What should a healthy Commit number look like across a quarter?
It should rise steadily as deals mature and get buyer-verified, reaching or exceeding target before the final week of the quarter rather than in it. A Commit number that’s flat for most of the quarter and then jumps in the last two weeks signals that deals are being pulled into Commit under pressure rather than genuinely maturing, which is the same failure mode the three-column hedge was designed to hide.
What happens differently when a Commit-category deal doesn’t close?
Under a validated model, a missed Commit deal triggers a specific investigation: which of the five readiness conditions was marked verified when it wasn’t, and which manager signed off on it. Under best case, worst case, most likely, a missed forecast has no equivalent trigger, because the worst-case column already accounted for the possibility and no one has to explain the specific point of failure.
Does replacing the hedge require new software?
Not necessarily. The structural change is in what gets measured and how deals are scored before they’re allowed into a forecast category, not in which forecasting tool sits on top of the CRM. Most of the work is building the scoring criteria and the discipline to apply it consistently, which existing CRM and forecast tools can usually support once the underlying rubric exists.
Sales leaders who want to see where their own forecast process stands against this model can run ASG’s Quick Pulse Revenue Performance Assessment, a short diagnostic built to flag whether a pipeline is being validated or hedged.
0 Comments