Forecast sales opportunities that cannot all close together

A probability-weighted sales pipeline can overstate expected cash when probabilities assigned to alternative purchases are inconsistent. A customer considering either a $60,000 implementation or a $90,000 managed project may choose only one. The assigned probabilities must respect that restriction, and the cash plan must distinguish a weighted average from an outcome the customer can actually produce.

Mark opportunities that share a customer budget, procurement decision, delivery slot or financing condition. The relationship may cross account names when several subsidiaries depend on one group approval. Ask the sales owner what could happen together and what cannot. That question is more informative than asking whether every opportunity feels likely.

Expected deal values can be added without statistical independence. Coherent marginal probabilities still produce a valid total expectation when deals are mutually exclusive or correlated. Their relationship affects the possible combined outcomes and cash-shortfall risk, so an average alone is insufficient for those decisions.

Build plausible combined outcomes for the connected opportunities. Preserve the original deal records for selling activity, and use the grouped cases alongside the weighted estimate when deciding how much cash or delivery capacity to commit.

Mutually exclusive opportunities cannot both happen under the defined circumstances. A bid for one of two alternative scopes is an example. Dependent opportunities can happen together, but their chances move together because they rely on a shared event. Three contracts funded by the same customer financing round may all be delayed if that financing slips.

Capacity introduces a third relationship. Your company may win several deals but be unable to deliver them all in the same month. That limitation affects invoicing, collections and the cost of subcontracting. Record which constraint applies instead of attaching a broad warning to the entire pipeline.

Define the time horizon when assessing exclusivity. Two projects may compete for this quarter's budget but both be purchased across a year. A monthly cash model needs the timing restriction even if the annual revenue target could eventually include both. Revisit the grouping when the customer changes its plan.

Give each group a named owner and an explicit explanation in the forecast. A label such as shared approval is insufficient if nobody knows which approval or which customer contact can confirm it. Keep the relevant procurement note, proposed scope or internal capacity decision beside the assumption. This also helps a replacement sales owner understand why finance has not simply added every visible opportunity.

Suppose a hypothetical customer has three outcomes for an upcoming decision: a 40% chance of choosing a $60,000 project, a 30% chance of choosing a $90,000 project and a 30% chance of making no purchase. These outcomes are mutually exclusive and their probabilities total 100%. The weighted contract value is $51,000: $24,000 from the first outcome plus $27,000 from the second.

That $51,000 is an expectation, not a contract the business can invoice. The actual outcome in this simplified model is $60,000, $90,000 or zero. Preserve those possibilities when evaluating a cash shortfall. A company that needs a $40,000 deposit next week cannot spend an expected value that has not become an accepted contract and a collectible invoice.

If the CRM assigns a 70% probability to each of these mutually exclusive alternatives, the probabilities total 140% and cannot describe this decision coherently. The resulting weighted total is $105,000, above the largest available purchase. The error is the incompatible probabilities, not the act of adding expected values. Grouping exposes that problem before it reaches a hiring or spending approval.

Contract value must pass through billing and collection assumptions before it enters a cash forecast. For each outcome, identify the expected signing date, invoicing trigger, payment terms and likely receipt date. A deposit, milestone payment and final acceptance payment belong in different periods, with separate evidence for their timing.

For the illustrative $60,000 project, assume a $20,000 deposit and two later payments of $20,000. The $90,000 alternative might require $30,000 upfront and $60,000 after acceptance. Even if the second contract has a higher expected value, its later concentration of receipts can produce a different short-term funding requirement.

Financial statements distinguish performance over a period from cash moving into and out of a business. Keep that distinction in the forecast: signing an agreement, recognizing revenue, issuing an invoice and collecting payment are different events. The model should state which event every column represents.

When several opportunities depend on one customer approval, create a case where approval happens on time, another where it is delayed and a case where it fails. Adjust the related deals together. Changing one deal to a downside assumption while leaving every linked deal at its optimistic date produces a misleading mixture.

Keep independent opportunities outside the group unless evidence connects them. Over-grouping can make an entire pipeline look as though every customer will act together. The purpose is to represent known dependencies, not to construct a dramatic worst case by assuming all adverse events coincide.

For capacity-constrained cases, state which accepted work gets delivered first and what happens to the rest. If subcontractors provide extra capacity, include their payment timing and delivery risk. If delivery shifts, move the related invoice and receipt dates. Do not retain the original cash dates merely to preserve the sales target.

At each pipeline review, ask sales owners to identify alternatives, shared approvals and changes to purchasing sequence. Finance can then update the grouped outcomes without rewriting every opportunity. Retain the prior assumptions so a later variance can be traced to a specific change in scope, probability or timing.

Report both the weighted estimate and the plausible cash cases to decision-makers. Labeling them clearly prevents a planning average from becoming a spending authorization. Where the downside case would require action, identify the latest date on which hiring, supplier commitments or other discretionary spending can be adjusted.

After the customer's decision, close the rejected alternatives and replace the outcome group with the signed terms. Follow actual billing and collection evidence from that point. An opportunity that has become a receivable should not also remain in the pipeline cash estimate, or the same expected receipt will be counted twice.