Forecast Deals Whose Final Value Is Still Uncertain
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
The buyer has named a decision-maker, scheduled an evaluation, and explained the approval process. The quantity is still unresolved. Yet the forecast carries the largest amount mentioned in a discovery call, multiplied by the opportunity’s standard probability.
That calculation answers the wrong question. A credible path to winning does not establish how much the buyer will purchase. To forecast an opportunity whose deal size is uncertain, separate the probability of winning within the forecast period from the value if it wins. Then choose a minimum, a supported range, or a conditional scenario calculation according to the evidence available.
The practical test is simple: can another reviewer reconstruct the amount without relying on the seller’s optimism? The worksheet below makes the assumptions visible, including when a precise weighted amount would overstate what is known.
1. Separate the two uncertainties before changing the amount
A single opportunity amount often hides two different judgments:
- Win uncertainty: Will this buyer complete the purchase within the forecast period?
- Amount uncertainty: If the purchase completes within that period, what scope will it include?
A strong buying process can support the first judgment while leaving the second unresolved. Conversely, a buyer may have settled the quantity while the purchase itself remains uncertain.
Use a consistent value basis before doing any arithmetic. Decide whether the forecast measures annual contract value, total contract value, or another defined bookings measure. Do not mix those measures across scenarios. Also decide what counts as a win in the period. A later expansion is not part of this period’s opportunity value merely because it involves the same customer.
For a conditional calculation, the relationship is:
Expected contribution = probability of winning in the period × expected value conditional on winning in the period
This does not require assuming that scope and timing are independent. The conditional value must already reflect which scopes could close in the period. If the larger scope changes the approval path or closing date, that difference belongs in the scenarios rather than being ignored.
2. Sort scope by evidence, not by enthusiasm
Before assigning probabilities, divide the amount discussion into three evidence categories.
Confirmed minimum scope is the smallest coherent purchase the buyer has explicitly identified as acceptable. It is not a guaranteed booking. The buyer can still delay, choose another supplier, or make no purchase. The point is that the scope has support if the deal proceeds as currently understood.
Plausible expansion has a named business need, an identifiable decision owner, and a known unresolved condition. It is more than a seller’s suggestion, but it has not cleared the condition necessary for inclusion.
Unsupported maximum scope is a ceiling discussed without enough evidence of purchase intent or feasibility. It might reflect every possible team, location, or use case. Preserve it as discovery context, not as the forecast amount.
For each category, record what the buyer actually confirmed, who confirmed it, and what remains open. “They liked the bigger option” is not equivalent to “the budget owner confirmed that the additional group can be included this period.”
If no minimum scope has been established, say so. Do not relabel the smallest number in a presentation as a confirmed minimum.
3. Filled hypothetical amount worksheet
Fictional worked example: All company details, amounts, probabilities, dates relative to review, and calculations in this example are hypothetical. They illustrate a forecasting method, not customer results or recommended probability defaults.
A fictional buyer, Northbridge Services, is evaluating a subscription for an initial operating group. A second group may join the same purchase. A company-wide rollout has also been mentioned, but no one has established its requirements or approval path.
Forecast frame
- Measure: Annual contract value in dollars, using the same valuation basis for every scenario.
- Period: The current quarter.
- Win event: A completed purchase counted in the current quarter under the team’s forecasting rules.
- Hypothetical probability of that event: 60%, based on the assumed buying-process assessment—not on the maximum amount discussed.
- Current forecast treatment: $160,000 opportunity amount multiplied by 60%, producing $96,000.
A. Confirmed minimum scope
- Scope: The initial operating group only.
- Value if won at this scope: $60,000.
- Evidence recorded: The buyer’s project owner confirmed this group is the initial purchase scope and can proceed without the second group.
- Remaining uncertainty: Final purchase approval is still outstanding.
- Forecast role: Supported base scope, not a guaranteed revenue floor.
B. Plausible expansion
- Scope: Initial group plus the second group in the same purchase.
- Incremental value: $40,000.
- Total value if included: $100,000.
- Evidence recorded: The second group’s owner has confirmed a need and is assessing participation.
- Unresolved condition: That owner must confirm funding and inclusion before the current purchase is finalised.
- Forecast role: Supported upside scenario, conditional on a specific decision.
C. Unsupported maximum scope
- Scope: Company-wide rollout.
- Total discussed value: $160,000.
- Evidence recorded: A broader rollout was raised as a possible future direction.
- Missing evidence: No confirmed participating groups, scope owner, funding decision, or current-quarter approval route.
- Forecast role: Excluded from the current calculation. Reconsider only when new evidence supports it.
Conditional scenario assumptions
For illustration, the reviewer assigns a 65% chance to the $60,000 outcome and a 35% chance to the $100,000 outcome, conditional on a win this quarter. These are mutually exclusive total-value outcomes. They sum to 100% within the assumed win case.
Those percentages are explicit judgment calls for this fictional exercise. The worksheet exposes them for challenge; it does not make them objectively measured facts. If the reviewer cannot defend them, the range treatment in the next section is preferable.
4. Calculate the alternatives without mixing their meanings
The hypothetical worksheet supports three distinct views. Each is useful for a different forecasting convention.
Supported-base treatment
$60,000 × 60% = $36,000
This uses only the confirmed minimum scope. It is straightforward and avoids counting unresolved expansion as settled. Its trade-off is that it does not represent plausible upside in the point estimate, so the expansion should remain visible separately.
Conditional expected-value treatment
Expected value if won = ($60,000 × 65%) + ($100,000 × 35%) = $74,000
Expected contribution = $74,000 × 60% = $44,400
The same calculation can be checked through joint outcomes:
- No current-quarter win: 40% probability, $0 contribution.
- Base-scope win: 60% × 65% = 39% probability, at $60,000.
- Expanded-scope win: 60% × 35% = 21% probability, at $100,000.
The probabilities total 100%. The expected contribution is $0 + $23,400 + $21,000 = $44,400. Do not apply the 60% win probability again after using these joint probabilities.
Supported-range treatment
The supported value range if won this quarter is $60,000–$100,000. At a fixed hypothetical 60% win probability, applying the same weight to the endpoints gives $36,000–$60,000.
That second range is a sensitivity range for weighted forecast contribution, not a range of actual possible bookings. Actual current-quarter outcomes in this simplified example are $0, $60,000, or $100,000.
The old $96,000 calculation treated the unsupported $160,000 ceiling as certain conditional on winning. Replacing it with $44,400 reduces the hypothetical weighted forecast by $51,600. That is an assumption correction, not evidence that the buying process deteriorated.
5. Use a range when probabilities would be invented precision
A range is more honest than a precise weighted amount when the endpoints have evidence but the distribution between them does not.
In the hypothetical example, the reviewer may reasonably accept the base and expanded scopes while rejecting the 65%/35% split. Perhaps the second group has not yet assessed its funding. There may be no defensible basis for distinguishing a 35% inclusion chance from a substantially different estimate.
In that case, report the conditional value range, identify the unresolved decision, and use the team’s documented rule for any required single amount. A supported-base amount can work as that operational choice, provided it is labelled as a base treatment rather than an expected value.
Do not silently use the midpoint of a range. A midpoint assumes something about where outcomes sit within the range; it is not automatically more neutral than using the lower endpoint.
Conditional expected values become more useful when scenario judgments can be explained consistently and later reviewed against outcomes. Even then, keep the underlying scenarios visible. A number such as $74,000 is an analytical average, not necessarily a scope the buyer could purchase.
6. Keep amount, timing, and expansion from being counted twice
The simple worksheet fails if expanded scope changes the purchase process. Suppose, in another hypothetical variation, the second group’s inclusion requires an additional approval that could move the entire purchase into the next quarter. Keeping a fixed win probability while merely increasing the amount would miss that dependency.
Replace the simple calculation with joint scenarios: base scope closes this quarter, expanded scope closes this quarter, and no close this quarter. Give each scenario an amount and a probability, with all probabilities summing to 100%. Do not assign the expanded scenario the base scenario’s timing confidence without checking the approval path.
Also distinguish an expansion included in the initial purchase from one expected after it. If the second group will decide only after the first group starts, its value should not automatically sit in the current opportunity’s amount.
Choose one place to represent each potential purchase. Otherwise the same expansion can appear in both the original deal’s upside and a separate expansion opportunity. During review, ask: “Where else is this scope counted?”
7. Repair an inflated amount without hiding the correction
When the largest discussed value is already in the forecast, avoid quietly overwriting it. Leave a short explanation that separates changed evidence from changed treatment.
For the fictional worksheet, an appropriate note would be:
Amount treatment corrected from company-wide discussion ceiling to supported scope scenarios. Current-quarter win assessment remains 60%. Supported value if won is $60,000–$100,000. Conditional expected value is $74,000 using an illustrative 65% base / 35% expanded split. Company-wide scope is excluded pending buyer evidence.
If the scenario split cannot be defended, replace that part of the note with the chosen base-and-range treatment. The recovery should make the forecast easier to inspect, not merely produce a smaller number.
Assign the unresolved expansion decision to a named owner and set the next review around an observable event, such as the second group’s funding decision. At that review, promote the expansion, remove it from the period, or retain the range with an explicit reason. A missed internal date alone does not establish which scope the buyer will purchase.
8. Make the next forecast review measurable
At the next review, select a small batch of opportunities whose quantity or scope remains open. For each one, complete these fields:
- Forecast period and consistent value measure.
- Smallest buyer-supported purchase scope and its value.
- Expansion scope, incremental value, and unresolved condition.
- Unsupported ceiling excluded from the calculation.
- Win-in-period assessment, kept separate from amount assumptions.
- Chosen treatment: supported base, conditional range, or conditional expected value.
- Evidence owner and next observable decision.
Count how many reviewed opportunities have all seven fields, how many still use an unsupported maximum, and the total change in weighted contribution caused specifically by amount corrections. Keep that change separate from changes caused by win probability or timing.
After decisions arrive, compare the eventual scope with the recorded scenarios. Repeated outcomes outside the supported range suggest the worksheet is missing a scope driver. Repeatedly unused expansion suggests the upside assumptions need closer scrutiny. The immediate goal is not a more impressive point estimate; it is a forecast whose value assumptions another person can trace, challenge, and update.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications