Companies rarely go looking for a new forecasting tool because they want a prettier forecast. They go looking because they have lost confidence in the one they have. They want earlier warning, a more independent view and a better way to run the business.
In my experience, one of two triggers usually starts the search. The company misses a quarter, or the Sales Ops team runs out of room to keep doing the work by hand. The six signs below are how those triggers show up in practice.
1. You missed a quarter and nobody saw it coming
A missed quarter on its own is rarely the whole problem. The damage comes from the lack of warning. By the time leadership realizes the forecast is off, it is too late to change anything, and that is what breaks trust.
It gets worse when Sales committed to a number and then missed it. Once that happens a few times, leadership wants a view that does not come from the sales team alone.
2. Sales Ops is buried in spreadsheets
Sales Ops can end up maintaining 37 spreadsheets with 12 tabs in each, reconciling every input to keep them current. Then they are asked to run the forecast call too, in place of the sales leaders.
At that point the team spends more time assembling the forecast than analyzing the business. They usually need the most help, and they are often the least likely to say so out loud.
3. You turn the forecast off near quarter end
The feedback ORM hears most often from teams using a roll-up tool is some version of this: "We had to turn off the forecast in the last four weeks because it was way off." A clean interface for reps and managers to roll up their numbers does not make the underlying forecast accurate.
A forecast worth paying for holds from day one to day 90. If yours becomes trustworthy only after the quarter has mostly happened, it is describing the quarter rather than forecasting it.
4. The model did not notice the market change
The most common reason a forecast misses is that something in the business or the market changed and the model kept running on old assumptions. A new competitor pushes deal sizes down. Rising interest rates slow private-equity investment and buyers cut spending. Uncertainty stretches sales cycles.
Early 2026 was a clear example. Across ORM customers, pipeline coverage looked fine on paper while fewer deals were being decided at all. Days in stage crept up and days to close rose. A tool built on a fixed coverage ratio or fixed stage weights reported a healthy quarter the whole way through.
5. The board interrogates every number
Boards trust a forecast that is consistent, traceable and honest about its range. That means the same number on every slide unless there is a clear reason it moved, a roll-up that works the same way from region to total, the ability to drill down to the deals underneath, and a low, on-target and upper case.
If every board meeting turns into a debate about where a number came from, the forecast is not doing that job.
6. Nobody can explain how a number was built
This one sits under the other five. If the forecast comes out of a system nobody can trace, every miss becomes an argument. Two questions are worth asking of any tool you use: does the result come from your own systems, with a trace back to the raw data, and is your data secure?
Who makes the call?
Often the CEO or CFO rather than the CRO. The CRO is focused on selling. The CEO and CFO usually hold the discretionary budget, and they want confidence: will the company hit the number, and if it will not, will they know early enough to do something about it?
| Trigger | What it looks like | Who usually acts |
|---|---|---|
| A missed quarter | No early warning, broken commitments | CEO or CFO, wanting an independent view |
| Sales Ops overload | Dozens of spreadsheets and Ops running the forecast call | CFO, often before Sales Ops asks |
| A forecast nobody trusts | Turned off in the final weeks, debated at every board meeting | CEO |
Replace, or add?
Replacing is not the only option. In some companies ORM and Clari run side by side: ORM carries the statistical forecast, and Clari handles the rep and manager roll-up as an independent view. Leadership then sees two perspectives, what the field believes will happen and what the data says is likely to happen. When they disagree, that gap is worth a conversation.
Whichever way you go, start with one question for every vendor: "How will this work for my business?" If they cannot explain how the tool adapts to your stage definitions, your definition of qualified pipeline, the difference between expansion and renewal, and who owns the forecast, keep looking. If they say the forecast will be running in 15 minutes, walk away. A forecast you can trust takes weeks, and most of that time goes into understanding the business. See rolling out forecasting software and sales forecasting software compared.
---
Pete Furseth is COO of ORM Technologies, which builds custom revenue forecast models on a company's own CRM data.Frequently Asked Questions
What makes a company look for new forecasting software?
Usually one of two things. They miss a quarter without an early warning, or Sales Ops is overwhelmed and cannot keep producing the forecast by hand. Underneath both is lost confidence in the process.
Who usually decides to replace a forecasting tool?
Often the CEO or CFO rather than the CRO. They usually hold the discretionary budget, and they want to know early whether the company will hit the number. The CRO is focused on selling.
Why do teams turn off their forecast late in the quarter?
Because it stopped being right. The feedback ORM hears most often is some version of: we had to turn off the forecast in the last four weeks because it was way off. A tool that is only trusted early in the quarter is not doing its job.
Can you keep your current tool and add a forecasting model?
Yes. In some companies ORM and Clari run side by side. ORM carries the statistical forecast and Clari manages the rep and manager roll-up, so leadership sees what the field believes and what the data says.
What should you ask a replacement vendor?
How will this work for my business? A good answer covers your stage definitions, what counts as qualified pipeline, how expansion differs from renewal, and who owns the forecast. A promise of a working forecast in 15 minutes is a red flag.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo