Why sales forecasts are inaccurate (and how to fix yours)

Picture of PragmaCRM Team

PragmaCRM Team

6 min read

Every quarter it plays out the same way. The pipeline says one thing in week four and the closed number says something else in week thirteen. Someone asks what happened. The answer is usually a story about one deal that slipped and another that came in smaller than expected, and everyone agrees to keep a closer eye on it next time.

Next time it happens again.

The problem is almost never the forecasting method. Weighted pipeline is sound arithmetic and has been for decades. The problem is that the arithmetic is being performed on numbers that were never accurate to begin with, and no amount of scrutiny at the end of the quarter can fix what went wrong at the point of entry.

Here are the three places it usually breaks.

Cause one: deal value is a free text field

In most CRMs, the value of a deal is a box a sales rep types a number into.

That number gets entered early, when the scope is still a conversation rather than a quote. It reflects a genuine estimate at the time. Then the scope changes twice, one line item comes out, a discount goes in, and the number in the box stays exactly where it was. Nobody is being careless. There is simply no moment in the process where updating it is the obvious thing to do.

Multiply that across forty open deals and the pipeline total becomes a collection of guesses of varying ages. It is not wrong on purpose. It is just no longer describing anything real.

The fix: calculate the value, do not capture it.

Build a catalogue of what you actually sell, with your prices. When a rep builds a deal, they select from that catalogue rather than typing a figure. The deal value becomes the sum of the line items, which means three things follow automatically.

Every number can be traced back to something specific that was quoted. Change the scope and the value recalculates itself rather than going stale. And nobody can inflate a deal to make their pipeline look healthier, because there is nowhere to type an inflated number.

This one change does more for forecast accuracy than any amount of pipeline review.

Cause two: stage probabilities are decorative

Most pipelines have probabilities attached to each stage. Qualified is twenty per cent, Proposal Sent is fifty, Negotiation is seventy-five. These numbers are usually inherited from whatever the CRM shipped with, or picked in an afternoon when the pipeline was first set up, and then never examined again.

The deeper issue is that stages themselves are often defined by what the seller has done rather than by what the buyer has done. “Proposal Sent” describes an action your rep took. It says nothing about whether the buyer has a budget, a timeline, or the authority to sign. A deal can sit at fifty per cent for months on the strength of an email that was never opened.

The fix: define stages by buyer evidence, then check the numbers.

Rewrite each stage so that moving into it requires something the buyer did. Not “proposal sent” but “proposal acknowledged and a review meeting booked”. Not “negotiation” but “terms under review by their legal team”. The stage now describes a real position rather than an activity log.

Then check your probabilities against your own history. Take the deals that reached each stage over the last year and calculate what proportion actually closed. If the deals that hit your seventy-five per cent stage close forty per cent of the time, your forecast is not slightly optimistic, it is systematically wrong by nearly half. That is a fifteen-minute exercise that most teams have never done.

Cause three: renewals and new business share one forecast

If your business has recurring revenue, some of your pipeline is new customers and some is existing ones renewing or expanding. These behave nothing alike.

Renewals close at much higher rates and over much shorter cycles. New business is slower and less certain. When both sit in the same pipeline with the same stages and the same probabilities, two things go wrong at once. Renewals drag the apparent win rate upward, which makes new business look healthier than it is. And new business drags renewal forecasting downward, which hides the fact that an account you already won is about to lapse.

The blended number is wrong in both directions simultaneously, which is the hardest kind of wrong to notice.

The fix: run them as separate pipelines.

Give renewals and upsells their own stages, their own probabilities and their own reporting. Your acquisition win rate then measures acquisition. Your renewal rate measures retention. Neither is quietly propping up the other.

This also surfaces a number most small B2B businesses never see: how much revenue is up for renewal in the next ninety days, and how much of it is actually being worked.

What a trustworthy forecast looks like

If you fix all three, the forecast changes character. It stops being a number someone assembles at the end of the month and becomes something that is simply true at any moment, because it is built from data that arrived as a by-product of doing the work.

You should be able to click any figure and see the line items behind it. You should be able to explain why a stage carries the probability it does, with reference to your own closed deals. And you should be able to answer “how much of this is new business” without exporting anything.

That is a higher standard than most teams hold their pipeline to. It is also much less effort than the alternative, which is rebuilding the numbers in a spreadsheet every time somebody senior asks a question.

The honest summary

Forecast accuracy is a data capture problem wearing the costume of an analysis problem. You cannot review your way out of it, and adding required fields makes it worse rather than better, because every field you demand is a reason for a rep to work around the system.

The way through is to design the process so that entering good data is the path of least resistance. Calculate values instead of asking for them. Define stages by what the buyer has done. Keep the two revenue motions apart.

Do that and the forecast becomes something you can put in front of a board without a caveat.


PragmaCRM was built around these three ideas. Deal values are calculated from your product and service catalogue and locked. Stages carry probabilities you set. Acquisition and Growth run as separate pipelines with separate reporting. Try it free for 14 days, no credit card required.

Share this post