# Why is my sales forecast always wrong?

https://salesintelligenceexperts.com/answers/why-is-my-sales-forecast-wrong

## Short answer

Usually because the CRM records intentions rather than facts. Deals sit in stages nobody moves, verbal agreements get marked closed-won, and reps update records to reflect hope. The forecast is not wrong so much as it is faithfully reporting bad inputs, which is why most teams keep a second number in a spreadsheet.

## What this is based on

- RevOps practitioners describe maintaining a 'true' number in a separate spreadsheet that they trust more than the CRM, described as commonplace rather than exceptional. ([Our analysis of 1,157 Reddit posts, August 2026](/research/what-sales-teams-actually-say))
- A widely-upvoted account describes Salesforce reporting $6.1M while leadership had already stated $6.8M. The gap traced to a verbal agreement marked closed-won and deals rotting in untouched stages. (r/revops, captured in our corpus, August 2026)
- Spreadsheets out-rank every paid sales tool except HubSpot in tool mentions across the corpus. (Our analysis of 1,157 Reddit posts, August 2026)

## What we don't know

- We have no data on forecast accuracy rates by company size or methodology. This describes causes we observed practitioners reporting, not a measured error distribution.
- Whether stricter stage definitions actually improve accuracy, or just move the optimism somewhere else, is not something we can answer from this data.

## The tell: everyone has a second number

The clearest signal that a forecast is not trusted is that someone maintains a
parallel one. In practitioner discussion this comes up constantly, and it is described
as normal rather than as a scandal:

> *"There appears to be a commonality where they always maintain a 'true' number in
> another spreadsheet that they trust more than what is coming from the CRM."*

If that describes your organisation, the forecasting problem is not a modelling
problem. It is a data problem, and everyone already knows.

## What actually goes wrong

One account in our corpus is worth quoting because it is so specific. Salesforce
reported $6.1M for the quarter. The VP had already told the CEO $6.8M. Two hours of
reconciliation found:

- a $400k deal marked closed-won that was actually a verbal "we're in"
- several deals rotting in a stage nobody had moved them out of since August, because
  the rep who owned them had stopped updating anything

Neither of those is a forecasting failure. Both are recording failures that the
forecast then faithfully reported.

## The three inputs that break

**Stage means different things to different people.** If "proposal sent" means
"emailed a PDF" to one rep and "verbally agreed, paperwork pending" to another, stage
weighting is arithmetic on noise.

**Nothing expires.** A deal untouched for 90 days is almost never still live, but
almost no CRM removes it from the forecast automatically. Stage rot inflates every
number quietly.

**Closed-won is applied optimistically.** Sometimes for commission timing, sometimes
for genuine ambiguity about when a deal is done. Either way it front-loads revenue.

## What we would check first

1. How many open deals have had no activity in 30 days? 60? 90?
2. How many closed-won deals have no contract or payment date attached?
3. What proportion of the forecast sits with a single contact at the customer?
4. Does anyone maintain a spreadsheet version? Ask them why. The answer is the audit.

That fourth question is the fastest diagnostic available, and it costs nothing.

## The uncomfortable part

Tightening stage definitions is the standard advice and it is not wrong, but it
usually redistributes optimism rather than removing it. The underlying issue is that
reps are asked to be simultaneously accurate and confident, and those pull in
different directions. Systems that separate "what I believe" from "what has actually
happened", signed and dated and paid, tend to survive contact with a board meeting better.

Free tool for this: [CRM Health Score](https://salesintelligenceexperts.com/tools/crm-health-score)