ORM has been using AI for years. Before the hype we did not call it AI, because people did not trust it. Now, if you do not position as an AI-native company you are losing in the market.
The label changed faster than the underlying capability did, and the gap between what these systems can do and what teams can safely rely on is where most of the practical difficulty sits.
AI is broader than the chat window
The current conversation collapses AI into LLMs, which understates the field in a way that matters for forecasting.
AI is more than the LLMs people use today. Machine learning and optimization are separate techniques, and both are core to how forecasting actually works. The model that groups opportunities and predicts a close curve for each group is machine learning, not a language model, and no amount of prompting produces it. See how long deals take to close by group.
That distinction is worth holding onto when evaluating vendors, because a product that added a chat interface to an existing report is making a very different claim from one whose predictions are model-driven.
Where LLMs genuinely help
Three areas benefit: forecasting, data hygiene, and ad hoc analysis.
The biggest value from LLMs specifically is ad hoc analysis. The reason is economic rather than technical. Most analytical questions in a revenue organization never get asked, because asking means writing a ticket, waiting for an analyst, and justifying why the question matters. When the cost of asking collapses, the questions that were not worth a queue slot suddenly get answered, and some of them turn out to matter.
Data hygiene is the second. Identifying inconsistent entries, spotting deals that do not match the pattern of their stage, and flagging fields that changed meaning over time are all tasks where a language model does useful work against messy inputs.
The constraint is trust
Here is the failure mode that keeps these systems out of the decisions that matter.
If you are building a board deck and you ask an LLM to build your slides, how do you know your numbers are correct? Validating them is as time consuming as building the deck yourself.
That is not a complaint about accuracy. It is a structural problem. An answer you cannot trace is an answer you cannot defend, and the moments where these numbers matter most are exactly the moments where you will be asked to defend them. A board member asking why net retention moved two points does not accept a number whose provenance is a prompt.
| Task | LLM value | Blocked by traceability? |
|---|---|---|
| Ad hoc exploratory question | High | No, you can check the answer |
| Flagging data inconsistencies | High | No, output is a list to review |
| Producing a board number | High if trusted | Yes, and this is the blocker |
| Predicting close probability | Not the right tool | Machine learning task |
What that looks like in practice
Traceability requires a layer between raw data and the language model that carries meaning. Raw tables do not define what revenue means in your business, which is why an LLM pointed at a warehouse produces confident answers to questions it has misunderstood.
ORM launched Radar, ORM's MCP and in-app AI. It holds the semantic and analytics layer that raw data lacks, and it is queryable from whichever LLM you connect, including Claude, OpenAI and Copilot, as well as directly in the Radar interface.
The architectural point generalizes beyond any one product. The semantic layer is what makes an answer checkable, because it fixes the definition of every metric before the model is asked anything. Without it, two questions phrased slightly differently return two different numbers and both look authoritative.
Evaluating this in a vendor
Two questions separate products that have addressed this from products that have added a chat box. Both are covered in what to ask an AI forecasting vendor, and the second one is the sharper of the two: do the results pull from our internal data systems, and is there traceability back to the raw data?
If the answer is no, the tool will be used for exploration and abandoned for anything that reaches a board. That is not a disaster, exploration has real value, but it should be bought knowingly rather than discovered later.
Frequently Asked Questions
What is the biggest gap in AI for revenue forecasting?
Trust and traceability. If you ask an LLM to build a board deck, you have no way to confirm the numbers are correct, and validating them takes as long as building the deck yourself. AI output needs to point back to the point of truth that produced each number.
Where does an LLM add the most value in revenue operations?
Ad hoc analysis. The questions that would otherwise sit in a queue waiting for an analyst are the ones an LLM answers well, because the cost of asking drops to near zero and the answer can be checked against a known source.
Is AI in forecasting only about large language models?
No. AI is more than the LLMs people use today. Machine learning and optimization are distinct techniques and both are core to how forecasting models actually work, including deal grouping and close-curve prediction.
Is AI in forecasting the same as adding a chat interface?
No. A conversational layer over existing reports is a genuinely useful feature and a completely different product from one whose predictions are model-driven. Machine learning and optimization do the forecasting work, and neither is a language model.
Why does a semantic layer matter?
Because raw tables do not define what revenue means in your business. Without a layer that fixes each metric definition before the model is asked anything, two questions phrased slightly differently return two different numbers and both look authoritative.
Where do LLMs help most today?
Ad hoc analysis. The cost of asking a question collapses, so the analytical questions that were never worth a ticket and an analyst's queue slot finally get answered, and some of them turn out to matter.
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