Sales forecasting methods — and when each one lies
Weighted pipeline, rep commit, historical run-rate and stage-velocity forecasting compared: how each is calculated, what it systematically gets wrong, and how to combine them.
A forecast is a decision tool, not a prediction
The purpose of a forecast is to let someone commit resources — hire, spend, extend runway — with a known level of confidence. That reframing matters, because it means a forecast that is consistently wrong in a known direction is more useful than one that is randomly right.
Which is the main argument for measuring your forecast against what actually closed, every period, and keeping the record. The bias is the signal.
Weighted pipeline
How it works: every open deal's value is multiplied by a probability attached to its stage, and the results are summed.
Where it is right: at portfolio scale with a lot of deals, stage probabilities derived from your own history behave reasonably. It is also the cheapest method — most CRMs calculate it automatically.
Where it lies: stage probability is an average, and your specific deals are not average. A single large deal at fifty percent contributes a number that will never occur — the deal closes or it does not. With a small number of large deals, weighted pipeline produces a figure that is wrong in every possible outcome.
It also inherits whatever stage discipline you have. If deals advance because time passed rather than because the buyer committed, the probabilities are attached to nothing.
Use it when: you have many deals of similar size, and stage probabilities come from your own closed history rather than the CRM's defaults.
Rep commit
How it works: each rep says which deals will close this period. You add them up.
Where it is right: reps know things the data does not — that the champion is leaving, that procurement has gone cold, that the buyer said one thing on the call and something else afterwards. No model captures that.
Where it lies: it is a human estimate with incentives attached, and the bias is usually consistent per person rather than random. Some reps sandbag reliably, others are reliably optimistic. That is workable once you know each rep's historical accuracy — and useless until you do.
The other failure is the alignment trap: if commit drives compensation or pressure, it stops being an estimate and becomes a negotiation.
Use it when: deal counts are low and values are high. Track per-rep accuracy over at least four periods before trusting any of it.
Historical run-rate
How it works: you closed a certain amount in each of the last several periods; project forward, adjusted for seasonality and growth.
Where it is right: as a sanity check it is excellent, and it is the fastest way to notice that a bottoms-up forecast has drifted into fantasy. If your pipeline forecast is triple your best-ever quarter, the pipeline is wrong.
Where it lies: it assumes next period resembles the last ones. It cannot see a new competitor, a changed motion, a market shift or the fact that you doubled the sales team. It is a trailing indicator being used as a leading one.
Use it when: as the sanity check on every other method, never as the primary one during change.
Stage velocity
How it works: measure the historical conversion rate between each pair of stages and the average time spent in each. Push current deals through those rates and durations to project when and how much will close.
Where it is right: it is the only common method that forecasts *timing* as well as amount, and it surfaces where deals actually die. If discovery-to-proposal converts at seventy percent and proposal-to-close at fifteen, you have located your problem.
Where it lies: it needs volume. With thirty deals a quarter your stage conversion rates have wide error bars and will swing on noise. It also assumes deals move forwards, and quietly mishandles the ones that skip stages or go backwards.
Use it when: you have enough deal flow for the rates to be stable, and you want diagnosis rather than just a number.
The combination that works
No single method is sufficient. A practical approach:
- Calculate weighted pipeline as the mechanical baseline.
- Collect rep commit separately, without showing them the weighted number first — anchoring destroys the independent signal.
- Sanity-check both against run-rate. If either is far outside your historical range, find out why before reporting it.
- Record all three and what actually closed. After four periods you will know each method's bias for your business, which is worth more than any of the individual numbers.
- Report a range, not a point. Committed, best case and worst case. A single number implies a precision you do not have and encourages decisions that assume it.
The data problem underneath all of it
Every method above depends on the pipeline being current. A forecast built on deals whose stage was last updated three weeks ago is arithmetic performed on fiction, and no methodology fixes that.
Which makes pipeline hygiene the highest-leverage forecasting work available:
- Every open deal has a next step with a date. A deal without one is not a deal, it is a hope.
- Age-in-stage is visible and reviewed. Deals that sit are the ones that inflate forecasts.
- Closed-lost happens promptly. The reluctance to mark a deal lost is the single largest source of forecast inflation, and it is emotional rather than analytical.
- Activity captures itself. If updating the CRM is a separate chore from doing the work, the data will lag the reality by exactly as long as reps can get away with. Autocloz writes every email, call, LinkedIn message, SMS and WhatsApp to the deal automatically for this reason — the forecast is only as good as the freshness underneath it.
What to report
Report the range, the assumptions and the accuracy history. Something like: committed, best case, worst case, with the note that your weighted number has run about a certain percentage high for the last four quarters.
That last clause is what turns a forecast into a decision tool. A number with a known bias can be used. A number presented as certain and then missed twice teaches everyone to discount it by an unknown amount, which is the worst of both worlds.
More on the underlying discipline in sales pipeline stages explained and the tooling in best sales pipeline management software.
Frequently asked
Which sales forecasting method is most accurate?
None on its own. Calculate weighted pipeline as a mechanical baseline, collect rep commit separately without showing them that number first, sanity-check both against historical run-rate, and record all three against what actually closed. After four periods each method's bias is worth more than any single number.
Why is my sales forecast always too high?
Most often because closed-lost happens late. The reluctance to mark a deal lost is the single largest source of forecast inflation, and it is emotional rather than analytical — those deals stay open and keep contributing weighted value.