Will we hit the number? Why forecast accuracy is an operations problem too
Most forecasts look strong right up until someone adds operational context. By then, it’s usually the final fortnight of the quarter.
Every growing business has lived through it. The pipeline review says the quarter is safe. Three weeks before quarter end, finance flags that two big deals can’t be invoiced until delivery completes. Delivery is already stretched. Suddenly the board conversation looks very different.
Nobody did anything wrong. Each team was looking at an accurate picture of its own part of the business. The problem is that the number depends on all of them.
A forecast is more than pipeline
Revenue confidence depends on pipeline quality, but also on:
- Delivery capacity: can we actually start the work we’re about to sign?
- Customer readiness: are customers ready to go live and be invoiced on time?
- Finance terms: when does a closed deal really become recognised revenue?
- Renewal exposure: which existing revenue is quietly at risk this quarter?
When those signals sit in separate systems, the forecast review becomes a debate about whose view is right. When they sit side by side, it becomes a discussion about what to do.
Speed and quality aren’t a trade-off : improving forecast accuracy
It’s tempting to think a better forecast means a slower, more cautious one. The research suggests the opposite. McKinsey found that organisations which make decisions quickly are twice as likely to make high-quality decisions . Yet 61% of respondents said most of the time they spend on decisions is used ineffectively .
In forecasting, that ineffective time is easy to spot. It’s the hours spent exporting pipeline data, matching it to finance terms and chasing delivery leads for a status update. Every hour spent assembling the forecast is an hour not spent improving it.
Week three, not the final fortnight
Commercial risk spotted in week three of a quarter is a decision you can still make. You can pull forward a deal, reallocate delivery capacity or reset expectations with the board early. The same risk spotted in the final fortnight is an explanation, not a decision.
The difference between the two isn’t effort. It’s whether the operational signals that shape the number reach the leadership team in time.
What good looks like : operational maturity in forecasting
- One agreed definition of pipeline, forecast and recognised revenue across sales and finance
- Pipeline, delivery capacity and renewal exposure visible in the same view
- Forecast reviews that start with the risks, not with reconciling the numbers
- Early warnings when a deal’s delivery or invoicing date slips
A practical first step
Take your last two forecast misses and trace them back. When was the risk first visible, and in which system? When did it reach the leadership team? The gap between those two dates is the cost of disconnected data, measured in weeks.
Quick self-check : assess your pipeline visibility and forecast confidence
☐ Do sales and finance agree on the forecast before the review, not during it?
☐ Can you see delivery capacity alongside pipeline without exporting anything?
☐ Did your last forecast miss surface before the final fortnight?
This is the second of five decisions that define operational maturity. Next: “What’s going to miss?”
Download The operations leader’s guide to AI you can trust , our guide for operations leaders in growing businesses. It covers the five decisions that define operational maturity, a 10-question scorecard and a practical 90-day plan.
We think you'll like...

Everyone wants AI. But have we forgotten to fix the foundations? Why AI data readiness matters
November 2, 2026Why credible AI strategies start with trusted data and a measurable business problem. - By...
Blogs

Are we on track? Why the simplest question gets harder as you grow | Operational maturity for growing businesses
October 30, 2026It’s the question every leadership meeting should answer in the first five minutes. In most...
Blogs

Can we deliver what we’ve committed to? Where strategic execution quietly fails
October 30, 2026Most strategies don’t fail in the boardroom. They fail weeks later, in an overloaded team,...
Blogs