Every forecast call ends the same way.
The CRO leans back, stares at the number, and somebody finally asks the thing everyone in the room is already thinking. “So… do we feel good about this?”
Feel. Not know. Feel.
That one word tells you what forecasting really is. Nobody asks whether the coverage math checks out, because it always checks out. Somebody built the model. The model says 3.2x. The question underneath the question is different, and everyone knows it. Do we believe the people who gave us these numbers?
After 15 years sitting next to CROs at Splunk, Databricks, Datadog, and Harness, through a run at Splunk from $160M to north of $2B and at Databricks from $100M to $1B, I can tell you the forecast was never really about the deals. It was about the people calling them.
The forecast is a read on people, not on deals
Watch a good CRO work a forecast call and you will notice they are barely looking at the opportunity record. They are listening to how the deal gets described.
Does this rep follow the process, or do they quietly skip steps? Which steps? Are they a sandbagger who pulls a deal out of thin air on the last Thursday of the quarter, or are they happy ears, calling commit on a deal where nobody has met the economic buyer? Is that frontline manager genuinely in their business, or are they narrating a summary a rep gave them twenty minutes ago?
None of that lives in the CRM. All of it determines whether the number is real.
What the leader is doing is building a correction factor for every human in the chain. Take the raw commit, apply the correction, and you get something closer to the truth. The best leaders I worked with could do this in their heads with startling precision, and almost none of them could explain how.
The forecast is not a calculation. It is a diagnosis.
That is why the calls never stop
If you have ever wondered why a revenue org runs so many meetings, this is the answer.
Pipeline reviews, forecast reviews, deal inspections, one-on-ones, the end-of-month scrub. From the outside it looks like ceremony. But the leaders who run these well are not running meetings. They are taking the temperature.
Every one of those calls collects data on the humans, not the deals. How confident does this rep sound this week compared to last week? Why did they stop mentioning that account? Why does this manager’s team always slip in month three and never in month two?
A hundred small signals, gathered by hand, one conversation at a time.
Then you have to translate it twice
Once leaders have their read, they cannot simply publish it. They have to translate it for a CEO and a board who hear the same number differently.
The CEO is running the operating plan. They need to know whether the miss is a timing problem or the start of a trend, because their decisions have longer lead times than the quarter does. The board is underwriting a thesis. A slight beat built on three pulled-forward deals is worse news than a slight miss caused by lengthening cycles in one segment, and a good board member knows it.
Same number, two different conversations. Get the translation wrong and you lose credibility that takes a year to rebuild.
Most forecasting tools are spreadsheets with a login
Now look at what we handed leaders to do all of this with.
Nearly every forecasting product on the market is a roll-up engine. It collects the commit from the rep, sums it to the manager, sums that to the region, sums that to the number, and renders it in a grid with some history alongside. That is genuinely useful. It is also a spreadsheet with permissions and an audit trail.
Notice what never happens in that process. No intelligence gets added between the bottom and the top. The number that arrives on the CRO’s screen contains exactly the same information the rep typed in, just arranged more neatly. Every bias, every skipped step, every optimistic close date rides all the way up untouched.
That is why sales leaders quietly get so little value from these systems, and why the forecast call still exists as a live meeting. The tool tells you what people said. The meeting is where you find out what’s more likely happening.
Now imagine the same roll-up with actual intelligence harvested underneath it. Call recordings that show the economic buyer has not been on a live conversation in five weeks. Email threads that went one-directional in March. Slack channels where the deal team stopped talking about an account before anyone changed its stage. Progression patterns measured against what winning deals in that segment actually looked like, rather than what the stage definition claims.
That is not a better spreadsheet. That is the first time the forecast has known something the rep didn’t tell it.
More signal does not mean less judgment
The temptation, and I see it in nearly every AI conversation I am in right now, is to point all of that at replacing the judgment. Generate the number, remove the human bias, let the model call the quarter.
That is the wrong ambition, and it misreads what the judgment was ever for.
The leader’s read was never a workaround for bad data. It was the accumulated pattern recognition of someone who has watched a thousand deals and several hundred sellers and knows which combinations end badly. Judgment like that scales badly. One leader can hold accurate correction factors for maybe forty people. Past that, they are trusting somebody else’s read on a read, and the error compounds at every layer.
Real signal does not make that judgment obsolete. It hands leaders the correction factors they used to build by hand over eight quarters of watching, and it makes them teachable, which matters far more.
Then they can spend their time on the part no system will ever do for them, which is deciding what to tell the CEO on Monday.
The best tools were never going to replace the CRO’s read.
They were always going to sharpen it.
