Forecast versus actual analysis compares predicted revenue to what closed. Run it at fixed snapshots through the quarter, day 1, 30, 60 and 90, rather than only at close. A model accurate only in the final snapshot is describing the quarter rather than forecasting it.
Most revenue teams make hiring plans, budget calls and board commitments on a forecast they will miss. Across ORM's customers, forecast accuracy on new and expansion revenue usually reaches about 90%, and only through heavy manual effort. The forecast vs actual gap is not a reporting problem. It is an operational problem that compounds every quarter.
The good news: forecast variance is diagnosable. Every miss has a root cause, and root causes cluster into a small number of patterns. After building custom forecast models for B2B SaaS companies for twenty years, I can tell you that most companies miss for the same five reasons. The companies that close the gap are the ones that stop treating the forecast as a number and start treating it as a system.
This is the guide to measuring the gap, diagnosing the cause, and building the system that prevents the next miss.
How Do You Compare Forecast vs Actual?
| Metric | Formula | What It Tells You | Target | ||
|---|---|---|---|---|---|
| Forecast accuracy | 1 - (\ | Actual - Forecast\ | / Actual) x 100 | Overall prediction quality | Suggested: 90% or better |
| Forecast bias | (Forecast - Actual) / Actual x 100 | Direction of the miss (over or under) | Within +/- 5% | ||
| Variance by segment | Segment forecast vs segment actual | Where the miss originates | No segment > 15% variance | ||
| Deal slippage rate | Deals that pushed / Total forecasted deals | Pipeline movement discipline | Under 10% | ||
| Coverage-to-close ratio | Beginning pipeline / Closed revenue | How much pipeline you need per dollar closed | Track quarterly to establish baseline | ||
| Stage conversion variance | Actual stage conversion vs modeled conversion | Whether conversion assumptions hold | Within 5% of model |
Why Do Forecasts Miss?
1. Deal Slippage
Deal slippage is the most common cause of forecast misses. Deals that were forecasted to close this quarter push to next quarter. They do not die. They slide.The aggregate impact is brutal. If 15% of the pipeline you counted on slips out of the quarter, and you started at 3x pipeline coverage assuming about a third converts, you lose about 15% of the target. Slippage creates a compounding problem because the slipped deals also inflate next quarter's pipeline, creating false confidence.
How to detect it: Track the "vintage" of pipeline. Deals that entered this quarter versus deals carried over from last quarter. If a large share of your committed pipeline is carryover from previous quarters, your forecast leans on deals that have already slipped once, and a deal that moves from one quarter to the next is less likely to close, even in commit. How to fix it: Implement strict commit criteria tied to buyer actions, not rep judgment. A deal is "committed" when the economic buyer has verbally confirmed timing and budget, not when the rep believes it will close. ORM's models assign probability based on buyer behavior data, not CRM stage alone.2. Conversion Rate Drops
Your forecast model assumes certain conversion rates at each pipeline stage. When those rates decline without detection, the forecast inherits the error.
A 5% drop in Stage 2 to Stage 3 conversion does not sound dramatic. But if you have $20M in Stage 2, that 5% drop means $1M less pipeline reaching Stage 3, which means $300-400K less closed revenue after applying downstream conversion rates.
How to detect it: Monitor stage conversion rates weekly, not quarterly. Plot them as a rolling 90-day average. Any downward trend beyond one standard deviation from the trailing four-quarter mean warrants investigation. How to fix it: Decompose the drop by segment and rep. Conversion rate drops are rarely uniform. They concentrate in specific segments (maybe enterprise is flat but mid-market dropped) or specific reps (new hires ramping slower than modeled). Fix the specific problem, not the average.3. Pipeline Quality Degradation
Total pipeline value looks healthy. Coverage is 3.5x. But the composition has shifted. More early-stage deals, fewer late-stage deals. More small deals, fewer large ones. More competitive deals, fewer uncontested ones.
The aggregate number hides the quality decline. A $40M pipeline with a healthy stage distribution produces a very different outcome than a $40M pipeline front-loaded with Stage 1 opportunities.
How to detect it: Weight pipeline by stage and deal quality indicators. Compare the weighted pipeline to the unweighted number. If the gap is growing, quality is declining. Also track "pipeline created this quarter that closed this quarter" as a leading indicator of pipeline freshness. How to fix it: Separate pipeline quantity targets from pipeline quality metrics. Measure your demand gen team on pipeline that converts as well as pipeline created. ORM's prescriptive models flag pipeline quality issues before they hit the forecast.4. Rep Sandbagging and Happy Ears
Human bias is baked into any forecast that relies on rep input. Reps who have been burned by missed commits in the past will sandbag. Reps chasing accelerators will over-commit. Both distortions hit the forecast.
Sandbagging creates the illusion of overperformance ("we beat forecast!") while masking the real pipeline health. Happy ears create the opposite problem: inflated commitments that evaporate in the final weeks of the quarter.
How to detect it: Compare each rep's forecast accuracy over trailing four quarters. Reps who beat their forecast by a wide margin quarter after quarter are likely sandbagging. Reps who miss by a wide margin every quarter likely have happy ears. Both patterns are addressable. How to fix it: Reduce reliance on subjective rep input. ORM's models generate forecasts from pipeline data (stage, age, engagement signals, historical conversion) rather than asking reps what they think will close. The model does not have emotions.5. Coverage Gaps
Sometimes the forecast misses because there simply was not enough pipeline to hit the target at any reasonable conversion rate. This is the most avoidable cause because it is detectable months in advance.
If your historical pipeline-to-revenue conversion rate is 25% and you need $10M in closed revenue, you need $40M in pipeline at the start of the quarter. If you enter the quarter with $30M, the math says you will close $7.5M. No amount of deal acceleration changes that arithmetic.
How to detect it: Track pipeline coverage by segment at the start of each quarter. Compare to the coverage ratio required to hit target based on your historical conversion rate (not the industry average). How to fix it: Build pipeline coverage requirements into planning as well as monitoring. Set coverage targets by segment and track them as a leading indicator 90 days before the quarter starts. ORM's models calculate the exact coverage needed per segment based on your specific conversion rates.Budget vs Forecast vs Actual: What Each One Is
The three get used interchangeably in conversation and mean different things on a report. Getting them straight is what makes a variance number interpretable.
| Term | What it is | When it is set | Changes during the period |
|---|---|---|---|
| Budget | The committed plan for the period | Before the period starts | No, it is the fixed reference |
| Forecast | The current expectation of where you land | Continuously | Yes, every time conditions move |
| Actual | What was recorded once the period closed | After the fact | No |
A team can hit budget while missing forecast badly, which means the plan was right and the process is blind. The reverse, forecasting accurately into a miss, means the process works and the plan was wrong. Those call for opposite responses, and reporting only one variance hides which situation you are in.
What Drives the Gap in 2026
Most forecast variance traces to conditions moving under a model that did not move with them.
The clearest example is timing. The median B2B SaaS sales cycle runs 84 days and has lengthened 22 percent since 2022 across 939 companies. A model carrying a 2022 cycle length expects revenue earlier than it arrives, then reads the shortfall as a pipeline problem rather than a timing one.
The measurable counter is cadence. Companies tracking pipeline velocity weekly reach 87 percent forecast accuracy against 52 percent for irregular tracking, with revenue growth of 34 percent against 11 percent. That 35-point gap comes from measurement rhythm rather than modeling technique, which makes it the cheapest improvement available to most teams.
Why Can the Forecast Miss When the Pipeline Was There?
Because the forecast assumed an execution pace that did not happen. One ORM customer had a quarter where the forecast fell apart even though the pipeline was mostly there. Coverage was tight but sufficient. The problem was that deals did not move through the quarter the way the forecast assumed. More of them slipped, and the team did not win or lose as many as expected. Too much stayed stuck in the middle.It was Q1, the organization was not as focused early in the quarter as it needed to be, and by the time that was obvious there was little room to recover. The tell everyone missed was velocity. The opportunities were there. They were not progressing, closing or being disqualified at the expected rate.
Add three questions to every forecast vs actual review:
| Question | What a "no" means |
|---|---|
| Are deals moving? | Stage progress has stalled, so timing assumptions are off |
| Are close dates holding? | Slippage is building, and commit is less reliable than it looks |
| Are we winning and losing at the expected rate? | Pipeline is aging in the middle, which inflates coverage |
What Should You Do When You Fall Behind Mid-Quarter?
At week six, the answer is better focus, and more activity rarely helps.
1. Find the gap. Is it deal size, win rate, pipeline, time to close, or a mix? 2. Decide what can still be sold this quarter. Focus on open deals with a credible path to close. Stop spending time on the rest. Deals you can pull forward without heavy discounting are on the table too. 3. Put executive support where it moves the most. Remove a blocker, reach the right decision-maker, reinforce value or create urgency on the deals that matter.
How Do You Build a Forecast vs Actual System?
A one-time variance analysis is useful. A recurring system is transformational. Here is the structure.
Weekly: Pipeline health check. Compare current pipeline stage distribution to the distribution required to hit target. Flag any stage where volume dropped 10%+ week over week. Monitor conversion rates by stage. Monthly: Variance decomposition. Compare month-to-date actuals to the monthly pace required by the forecast. Decompose any variance by segment, rep, and deal type. Identify whether the issue is pipeline quantity, quality, or conversion. Quarterly: Full forecast vs actual review. The comprehensive analysis. Compare the forecast to the actual by every dimension: segment, stage, rep, deal size, deal type, new vs expansion. Identify the top three root causes. Update the model assumptions for next quarter. Annually: Model recalibration. Review trailing four quarters of forecast vs actual data. Identify systematic biases. Recalibrate conversion rate assumptions, coverage requirements, and seasonal adjustments.How ORM Closes the Gap
ORM builds custom forecast models that eliminate the most common sources of forecast error. Our approach works in three layers.
Layer 1: Data-driven forecasting. We generate the forecast from your pipeline data using mathematical models calibrated to your specific conversion rates, sales cycle length, and deal dynamics. This eliminates the subjective bias from rep input. Layer 2: Variance decomposition. When the forecast and actual diverge, our models automatically decompose the variance by segment, stage, and rep. You do not have to hunt for the root cause. It surfaces automatically. Layer 3: Prescriptive analytics. The model tells you where the gap is and what to do about it. Which deals to prioritize. Where to add pipeline. How to reallocate resources. The gap between forecast and actual becomes a specific action plan, not a number on a slide.We target 95% accuracy on new and expansion revenue. Getting there comes from better modeling (more accurate predictions) and better execution (prescriptive actions that close the gaps the model identifies).
The Bottom Line
Every forecast will be wrong. The question is whether it is wrong by 2% or 20%, and whether you have a system to diagnose and correct the error in real time.
Forecast vs actual analysis is not a post-mortem exercise. It is an operating system. The companies that run it rigorously, decomposing variance weekly, identifying root causes monthly, and recalibrating models quarterly, are the ones that achieve the forecast accuracy their boards expect.
The gap between 75% accuracy and 95% accuracy is not a tooling gap. It is a discipline gap. Build the system. Run the system. The accuracy follows.
Related reading: - Best RevOps Tools - Sales Forecasting: Complete Guide - Forecast Accuracy - Pipeline Coverage Ratio - Deal Slippage - Revenue Variance - Stage Conversion RateFrequently Asked Questions
What is forecast vs actual analysis?
It compares the revenue you predicted with what you closed, then breaks the gap down by segment, stage, rep and deal type. The point is to find the cause, so the next forecast does not repeat it.
What is an acceptable forecast accuracy for B2B SaaS?
Accuracy on new and expansion revenue, excluding renewals, usually reaches about 90% today, mostly through heavy manual work. ORM targets 95% without manual adjustment, from day one to day 90. Measure your own first.
How do you calculate forecast accuracy?
Forecast accuracy = 1 - (|actual - forecast| / actual), shown as a percentage. If you forecast $10 million and close $9 million, accuracy is 90%. Break it down by segment, deal type and rep to find the real story.
Why do sales forecasts miss?
Five common causes: deals slip to the next quarter, stage conversion drops, pipeline quality falls, reps sandbag or have happy ears, and there is not enough pipeline. Underneath most of them, the market moved and the model did not.
When should forecast versus actual analysis be run?
At fixed points through the quarter as well as at the end. Snapshot at days 1, 30, 60 and 90, and compare each with the final actual.
What does a large positive variance indicate?
Often revenue pulled forward rather than a great quarter. Early deals are usually discounted, and they drain a future quarter whose pipeline was built six to 12 months earlier. Tag pulled deals when they close.
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