Multiply every deal by its stage probability, sum the result, and you have a forecast that is wrong in a predictable direction: too high, because stages encode hope.
- ›Why weighted pipeline systematically overstates
- ›What an evidence-based forecast uses instead
- ›Reading a forecast with its reasoning
- ›The habits that make forecasts accurate
Why weighted pipeline overstates
Two compounding errors.
Stage probabilities are nominal. The 60% attached to your negotiation stage was chosen once, by someone, and probably never validated against your actual conversion rate from that stage.
Deals sit in stages they have not earned. A deal advances when a rep moves it, and reps move deals for reasons including optimism, pressure, and pipeline-coverage targets. The arithmetic is fine; the inputs are not.
The result is a forecast that is directionally useful and consistently high, which teams learn to discount by a factor they have inferred from experience. That discount is doing the real forecasting.
What evidence-based forecasting uses
Your actual conversion rates, computed from your history per stage, per segment, per deal size. Not the nominal percentages.
Evidence per deal. Does this deal have the characteristics that deals which closed from this stage had? Multiple stakeholders engaged, recent activity, a defined next step, a timeline the buyer articulated.
Stage-evidence mismatch. The most valuable output. Deals sitting in a late stage without late-stage evidence, flagged individually. This is where a forecast becomes actionable rather than merely accurate.
Velocity patterns. How long deals of this shape usually take from here, which is what tells you whether an in-quarter close is realistic.
Reading a forecast
A useful forecast comes as three numbers plus a list:
- ›Commit: deals with strong evidence, high confidence.
- ›Likely: deals that fit the pattern but have gaps.
- ›Upside: possible, not plannable.
- ›The list of mismatches: deals whose stage and evidence disagree, which is your pipeline meeting agenda.
Run this as a deep analysis before a board meeting or a quarterly plan (about 10 credits in Brainis). Run the mismatch list weekly.
Important: When the AI's forecast persistently disagrees with your stages, the stages are usually the problem. Fixing stage definitions improves forecast accuracy more than any model change. See sales pipeline management.
The habits that make forecasts accurate
Beyond the sales number
Forecasting improves further when it can see beyond sales. A deal contingent on delivery capacity you do not have is not a forecast risk a CRM can see, but a connected system can. This is the argument for revenue forecasting inside a shared data layer rather than a standalone CRM.
FAQ
How much history is needed?
Two to three quarters of closed outcomes gives usable patterns. Less than that and you are forecasting from stage definitions, which is where you started.
Should reps see the AI forecast?
Yes, along with its per-deal reasoning. Hidden forecasts breed suspicion; visible reasoning invites correction, which is how it improves.
What accuracy is realistic?
Within 10-15% at a quarter boundary is a good outcome for most teams. Claims of much better usually indicate a pipeline being managed to the forecast.
Brainis produces evidence-based forecasts with reasoning you can challenge, across Revenue, delivery, and finance data. See Revenue OS.
Sharing insights on business operations, AI, and modern team management.
Run your company on Brainis
All 11 Operating Systems on every plan, from $29 a month. No per-seat pricing — you pay for AI capacity, not headcount.
See pricing