Pipeline stages describe where a deal is in the buying process. Forecast categories describe something different: how confident the seller is that the deal will close in this period. A deal can be at the Proposal stage and be a near-certainty, because the customer has budget, a deadline and verbal agreement. Another deal at the same stage can be a long shot, because nobody senior has looked at it. Forecast categories exist to capture that difference.
The usual categories
Names vary between companies and CRM systems, but most use some version of these:
- Closed. Signed and booked. No judgement involved.
- Commit. The seller is confident the deal will close this period and is willing to be held to it. A commonly used definition is that the seller would be surprised and disappointed if it did not close.
- Best case. The deal could close this period if things go well, but there are known risks: an approval not yet granted, a competitor still in contention, a legal review not started.
- Pipeline. A real opportunity, but not expected to close this period, or too early to judge.
- Omitted. Excluded from the forecast entirely, for instance because the deal is lost or stalled.
A rep’s forecast is then usually reported as two numbers: closed plus commit, which is what they are prepared to stand behind, and closed plus commit plus best case, which is their realistic upside.
Commit is a promise, not a mood
The forecast falls apart when categories mean different things to different people. One rep commits anything where the champion is enthusiastic. Another commits only deals where the purchase order number has been issued. Their totals cannot be meaningfully added together.
The fix is to define each category with observable evidence rather than feelings. A commit deal might be required to have all of the following:
- The economic buyer has confirmed the decision and the timing.
- Budget is approved, not merely expected.
- The paper process is known: who signs, which legal and procurement steps remain, and how long they take.
- A dated close plan exists and the customer has agreed to it.
- No unresolved competitive or technical issues.
Best case might need a confirmed need and an engaged buyer, but allow open items. With rules like these, a manager can challenge a category with a factual question (“Has procurement seen the contract yet?”) instead of a debate about optimism.
How the forecast rolls up
In most organisations, the forecast is built from the bottom. Reps categorise their deals. Their front-line manager reviews each committed deal, then submits a team forecast that may differ from the sum of the reps’ numbers. The manager might remove a deal they think is at risk, or add one they believe the rep is underplaying. The next level up does the same with the managers’ submissions, and so on up to the revenue leader, who gives the company forecast to the CEO and CFO.
Each level adds judgement. It is good practice to record both the raw roll-up and the adjusted figure at each level. Over time, this shows which managers consistently over- or under-call, and by how much.
Sandbagging and happy ears
Two biases distort forecast categories in opposite directions.
Happy ears is over-optimism: hearing what you want to hear in a customer meeting and committing deals that are not ready. It is common among newer sellers and in teams where managers react badly to low forecasts.
Sandbagging is deliberate understatement: keeping solid deals in best case or pipeline so that the rep can beat their forecast comfortably. It is common where missing a commit is punished harshly while beating it is celebrated. Sandbagging seems harmless, but it damages the business, because the company plans hiring, spending and cash on numbers that are too low.
Both are, in large part, products of culture. If a team is punished for every missed commit, it will commit less. If it is rewarded for big forecasts early in the quarter, it will commit more. Treating the forecast as a measurement, with accuracy rewarded in both directions, reduces both biases.
Measuring forecast accuracy
Accuracy needs a fixed point of comparison. A forecast submitted in the last week of a quarter is not very informative; most deals are decided by then. Many companies snapshot the commit figure at a set point, perhaps the end of the first month of the quarter, and compare it with the final result.
If a team committed ₹2 crore at that point and closed ₹1.8 crore, it achieved 90% of its commit. Tracking this across quarters, by rep and by manager, reveals patterns that one quarter cannot. A manager whose teams land between 95% and 105% every quarter is forecasting well. One whose teams swing from 70% to 130% is not, even if the average looks fine.
It also helps to look at the composition of the result. If a team hit its commit number but half the committed deals slipped and were replaced by best-case deals that closed unexpectedly, the total was right for the wrong reasons. Deal-level accuracy, the share of committed deals that actually closed in the period, is a sharper measure of judgement than total-level accuracy.
Where categories fit with other methods
Forecast categories reflect human judgement. Weighted pipeline uses stage probabilities. Run-rate methods use historical patterns, such as how much of a quarter’s bookings typically arrive in its final month. Many CRM platforms now also offer machine-learning predictions based on deal activity. None of these is reliable on its own. Mature forecasting processes compare several methods and investigate when they disagree. A large gap between the categorised commit and the statistical estimate is exactly the kind of signal worth a conversation before the quarter ends, not after.
Written by the RP Strativa Team. Figures in the examples are illustrative.
Leave a Reply