Sales forecasting is an automation that builds and updates your forecast from the real deals in your CRM. It weighs each deal on stage, age, activity, and your own historical close rates, rolls up an honest number with a range, and flags the deals most likely to slip or sandbag. A person still owns the number they commit to. Most teams are live in two to three weeks.
The problem
Most forecasts start life as a spreadsheet that someone rebuilds every Monday. A manager pulls the open deals out of the CRM, pings reps for updates, and marks each one likely or not on a feel for how the last call went. The trouble is that the inputs are soft. A rep leaves a deal at "proposal" because moving it back looks bad. A close date slides a week at a time and nobody resets it. Two deals worth the same on paper are nothing alike in reality. So the forecast comes out looking precise, a single number to the dollar, when underneath it is a pile of guesses.
That is why so few leaders trust the number. Gartner's State of Sales Operations Survey found that only 45% of sales leaders and sellers have high confidence in their organization's forecasting accuracy (Gartner, February 2020), and Gartner points to poor CRM data quality as a main cause. The time cost is real too. Figure a sales manager spends 3 to 5 hours a week pulling deals, chasing updates, and rebuilding the roll-up by hand. Over a quarter that is 40 to 60 hours on a number half of them still would not stand behind. (Those hours are a modeled estimate for a manager doing the forecast manually, not a client figure.)
The hours are not the real damage. The real damage is the decision made off a confident wrong number. A discount gets approved to save a quarter that was never going to land. Headcount or spend gets committed against revenue that slips into next quarter. A deal everyone counted on falls out in the last week and nobody had flagged it as shaky. None of that shows on a timesheet, and all of it traces back to a forecast that looked more certain than it was.
How the automation works
It reads the live deals in your CRM.
Every open opportunity comes in with its stage, amount, age, close date, owner, and recent activity, straight from the system your reps already work in. Nothing gets re-keyed into a separate spreadsheet.
It weighs each deal on real signals.
Instead of a flat percentage per stage, each deal is scored on the signals that actually predict a close for your business: how long it has sat, whether activity is still happening, the deal's characteristics, and your own historical close rates by stage. Every weighting shows the reasons behind it.
It rolls up an honest forecast with a range, and flags the risk.
You get a committed-to-best-case range rather than one false-precise figure, plus a shortlist of the deals most likely to slip (stalled, past their close date) or sandbag (heavy activity sitting at a low stage). It updates as the pipeline moves.
The pieces are proven: reading deals from the CRM, weighting them against close-rate history, rolling them up, and flagging outliers. The real work is the wiring. A forecast is a projection, not a promise, and it is only as good as the CRM data feeding it. Reps' stage and close-date hygiene is always messy, so the model has to account for that and present a range with its reasoning instead of a single number that looks more certain than it is. A confident wrong forecast is worse than an honest fuzzy one, because people bet real money on it, so a human always owns the number they commit. Tuning the model against your real deal history, and deciding how to surface the risk, are what get set up, tested, and handed over during implementation.
What this looks like in practice
Around 80 open deals in the pipeline at any time, forecast rebuilt by hand every week.
- The manager rebuilds the forecast in a spreadsheet every Monday, roughly 4 hours pulling deals and chasing reps for updates.
- The number goes up as a single figure with no range, and it lands within 10% of actual maybe half the quarters.
- Deals that quietly stalled still sit in the quarter at full value, so the commit runs optimistic and nobody knows which deals are the real risk until they fall out.
- The forecast rebuilds itself from live CRM data, and the manager reviews it in under 30 minutes instead of building it from scratch.
- The number comes as a range with the reasoning attached, and the deals most likely to slip or sandbag are flagged before the commit goes up.
- The manager commits a number they can defend, and spends the reclaimed time coaching the flagged at-risk deals instead of reconstructing a spreadsheet.
Typical impact
Typical ranges for this pattern, not client claims. Your numbers get modeled in the audit.
Systems it connects
Plus most tools with an API. The audit maps your exact stack.
Who this fits
- A forecast built by hand each week or month, off gut feel and an optimistic spreadsheet
- 10 or more employees, with enough deal volume that a roll-up actually matters
- Deals tracked in a CRM with stages and close dates, even if the hygiene is not perfect
- A sales leader who will own the committed number and act on the flagged risk