What Does It Mean to Use Data in Sales?
Most sales teams do not use data. They count it. Calls logged, emails sent, meetings booked, pipeline added. Those numbers fill a dashboard and feel like rigor, but every one of them describes something that already happened. Using data in sales means reading the signals that tell you what will happen next, on which deal, in time to change the outcome.We build forecast models for B2B SaaS companies, and I have watched the same pattern across dozens of pipelines. The teams that miss their number are rarely short on data. They are stuck on a low rung of a ladder, reporting lagging activity while the leading signals sit untouched in the same CRM. This post lays out that ladder, four rungs from backward-looking counts to a forward view of the quarter, and shows what moves you up each one.
| Rung | What you track | Lagging or leading | The question it answers |
|---|---|---|---|
| 1. Activity | Calls, emails, meetings logged | Lagging | Did the team do the work? |
| 2. Coverage | Pipeline-to-goal ratio | Lagging | Do we have enough pipeline on paper? |
| 3. Deal signals | Close-date moves, silence, deal age | Leading | Which specific deals are alive? |
| 4. Predictive models | Close-time curves, forecast decomposition | Leading | What shape will the quarter take? |
Why Do Activity Reports Fail to Predict Revenue?
Activity reports fail because effort is a lagging indicator, not a prediction. A rep can make eighty calls a week into dead accounts and post a beautiful activity chart. The chart tells you the work got done. It says nothing about whether any of that work will become revenue.Activity counts earn their place at the bottom of the ladder for one reason: they are the easiest thing to measure and the furthest from the outcome. Volume of touches correlates with pipeline creation loosely and with closed revenue barely at all. When activity is the only data a team reads, it manages the input it can see and stays blind to the deals quietly dying inside the pipeline it already built.
Is Pipeline Coverage Enough to Forecast the Quarter?
No. Pipeline coverage is an input, not a forecast, and treating it as the answer is the most expensive mistake in RevOps. The standard rule says carry three to five times your goal in open pipeline. Most teams I work with sit around 3.5x. Some run as low as 1.4x, some as high as 5x. The ratio feels like a forecast because it produces a single confident number, and that confidence is the problem.A company can hold 4x coverage and still miss badly. The pipeline might be concentrated in a handful of large deals, aged past the point of life, sourced from channels that rarely convert, or priced above what actually closes. I see the last one constantly: an average open-deal size of $80,000 against an average closed-won size of $40,000. Coverage counts the $80,000. The quarter pays out at $40,000.
Age exposes the same illusion. On the first day of a quarter, at least 10% of pipeline has sat untouched for twelve months, and only about 20% of the deals dated to close in-quarter actually close in-quarter. That means 80% of the value sitting in your quarter on day one will not be realized in that quarter. Coverage sees the whole pile. It cannot see which fifth of it is real.
Which Deal Signals Actually Predict Whether a Deal Will Close?
The two signals that predict a deal best are a change to its close date and, before that, the absence of any change at all. When a rep pushes a close date, the deal is telling you it is slipping, and a deal that slips from one quarter into the next is less likely to close even when it sits in commit. That is the clearest slippage signal there is.The earlier signal is quieter. It is silence. A deal with no stage change, no amount change, no new notes, and no close-date movement is a deal going cold, and from the seller's side the tell is a buyer who has stopped returning email and calls. This is why I define meaningful activity narrowly: a change in stage, close date, or amount. Everything else is noise dressed as engagement. Reading these deal-slippage signals is the first genuinely leading move on the ladder, because for the first time you are acting on the future of a specific deal instead of the aggregate of a whole board.
How Do Predictive Models Turn Data into a Forward Forecast?
A predictive model turns raw CRM history into a forward forecast by grouping deals with machine learning and predicting a close-time curve for each group. At ORM, every opportunity lands in a group, and each group carries its own curve for how long it takes to close. Those curves run from 1 to 80 weeks, with most of the expectation landing before week 12 and very few groups reaching past a year. That is opportunity aging done by math instead of gut feel.The model also decomposes the quarter into the revenue you can see and the revenue you cannot see yet. Three sources feed the number: carry-over deals already in pipeline on day one, in-quarter deals that do not exist yet but will be created and closed inside the period, and pull-forward deals dragged in early from future quarters, usually at a discount. Most teams over-trust the visible pipeline and never model the invisible motion, which is why their forecasts describe the past.
This is where accuracy comes from. A manual new-and-expansion forecast usually tops out around 90% and goes stale the moment market conditions move. A model trained on four to six weeks of your own historical sales data targets 95% and holds it from day one to day ninety of the quarter, updating as conditions change instead of waiting for a rebuild. Because the model responds to change, it catches the real reason forecasts miss: the assumptions underneath them shifted. A competitor pressured pricing, interest rates moved capital out of the market, a territory got reshuffled, and the old forecast never noticed.
Do You Need to Fix Your Data Before You Can Use It?
No, and the belief that you do is the most common excuse for staying on rung one. Every RevOps leader thinks their data is uniquely bad. It is not. Everyone's data is messy. What matters is not whether the data is clean but whether it is consistent, because a model can learn from consistent mess and still predict accurately. Garbage in does not have to mean garbage out.Waiting for perfect data is how teams justify another year of counting calls. The better move is to start reading the signals you already have and climb: from activity, to coverage, to deal-level signals, to a model that sees the shape of the quarter on day one, early enough to do something about it. That is the whole point of using data in sales. A number you can only read in the rearview mirror arrived too late to change anything.
Frequently Asked Questions
What is the difference between lagging and leading indicators in a sales pipeline?
Lagging indicators describe work that already happened, like calls logged, meetings booked, and current pipeline coverage. Leading indicators point at what will happen next on a specific deal, like a close-date change or a stretch of silence. Lagging data tells you the team was busy. Leading data tells you which deals are actually going to close.
Is pipeline coverage a reliable sales forecast?
No. Pipeline coverage is an input, not a forecast. Most teams carry three to five times their goal and sit around 3.5x, but a company can hold 4x and still miss if the pipeline is stale, concentrated in a few large deals, or priced above what closes. An average open-deal size of $80,000 that closes at $40,000 breaks a coverage-based forecast every time.
What is the best signal that a deal is going to slip?
The clearest signal is the rep changing the close date, and a deal that slips from one quarter into the next is less likely to close even when it sits in commit. The earliest signal is quieter: no stage change, no amount change, and no new notes on the deal. On the seller's side, that shows up as a buyer who has stopped returning email and calls.
How accurate can a SaaS sales forecast be?
A manual new-and-expansion forecast usually reaches about 90%, but it takes heavy effort and goes stale as conditions change. A model trained on four to six weeks of your own historical sales data can target 95% and hold it from day one to day ninety of the quarter, updating as the quarter progresses instead of waiting for a manual rebuild.
Do you need clean data before you can forecast sales?
No. Every RevOps leader believes their data is uniquely bad, and almost none of them are right. What matters is consistency, not cleanliness, because a model can learn from consistent mess and still predict accurately. Garbage in does not have to mean garbage out, so waiting for perfect data mostly delays the work.
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