Forecasting

Why sales forecasts fail before the first deal closes

6 min read·Nicole van Zanten·Listen here (coming soon)

Most forecast reviews start in the wrong place.

A sales leader pulls up the pipeline, walks through each deal's stage, and asks the rep the same question: “Is this still closing this quarter?” The rep, wanting to seem on top of things, says yes. The number goes in the forecast. Three weeks later, it doesn't close, and everyone acts surprised.

It shouldn't be a surprise. The forecast was never wrong at the end — it was wrong at the beginning. By the time a deal is being reviewed in a forecast call, most of the damage is already done.

The forecast isn't a sales problem. It's a definitions problem.

Ask five sales reps what “commit” means, and you'll get five different answers. One rep commits when a verbal agreement exists. Another commits once legal has the contract. A third commits whenever their manager is asking too many questions and they want the conversation to end.

None of these are wrong, exactly. But if a company doesn't have one shared, specific definition of what qualifies a deal to be forecast at each stage — with criteria, not vibes — the forecast isn't measuring the business. It's measuring how optimistic each rep happens to feel that week.

This is the first thing I look at in a revenue diagnostic, and it's rarely written down anywhere. It lives in people's heads, and it's different in every head.

Forecasts fail earliest at the top of the funnel, not the bottom

The instinct is to scrutinize the deals closest to closing — they're the ones with a number attached, so they feel like the highest stakes. But the deals that blow up a quarter almost never fail in the last two weeks. They fail because they were never qualified properly in the first four.

A deal that enters the pipeline without a real budget, a real timeline, or a real decision-maker engaged doesn't become a bad forecast entry later. It starts as one. It just doesn't announce itself as a problem until the quarter is almost over and there's no time left to find a replacement.

This is why forecast accuracy is really a top-of-funnel discipline wearing a bottom-of-funnel costume. Fix what enters the pipeline, and the forecast mostly takes care of itself. Try to fix it only at the review stage, and you're just getting better at predicting problems you created weeks earlier.

The incentive is almost always working against the truth

Here's the uncomfortable part: in most organizations, there's no real cost to a rep forecasting optimistically, and a real, immediate cost to forecasting conservatively. An optimistic number buys time and avoids an uncomfortable conversation today. A conservative number invites scrutiny today, for a problem that might not even materialize.

So people do what the incentives reward. It's not a discipline problem or a character problem — it's a design problem. If the system punishes honesty and rewards hope, you'll get hope, every time, regardless of who's on the team.

Fixing this isn't about tightening the screws on reps. It's about removing the penalty for accurate forecasting and building a review cadence where “this is likely to slip, here's why” is treated as useful information, not a red flag on someone's performance.

What a reliable forecast actually requires

None of this is about a better spreadsheet or a fancier CRM field. A forecast leadership can actually trust needs three things in place, in this order:

Shared stage definitions with real criteria. Not “we're in late stages,” but “the champion has confirmed budget, we've had a technical validation call, and procurement is engaged.” Specific enough that two different reps would categorize the same deal the same way.

A qualification bar at the top of the funnel, enforced consistently. Deals that don't meet it don't enter the forecast-eligible pipeline at all, regardless of how good they feel.

A review culture where flagging risk early is rewarded, not punished. The rep who says “this is at risk” in week two of the quarter should look better in six months than the rep who said everything was fine until week eleven.

Get those three right, and the forecast becomes something rare in most companies: a number leadership can actually plan around, instead of a number everyone has quietly agreed to distrust.

This is the kind of gap a revenue diagnostic surfaces in the first two weeks — not because reps are bad at their jobs, but because nobody ever wrote the rules down. If your forecast has stopped being something you trust, let's talk.