This forecast accuracy calculator scores up to 4 quarters. Enter the forecast you committed at the start of each quarter and the revenue that closed. You get the average accuracy, the bias and the worst quarter. For what the metric means and how to raise it, read the forecast accuracy guide.
Get The Forecast Brief
You just scored your forecast. The Forecast Brief is a short email from Pete Furseth, ORM's COO, built on what ORM sees in its customers' forecasts.
How to read your score
Forecast accuracy is calculated as: 1 - |Forecast - Actual| / Actual, expressed as a percentage. A score of 95% means your forecast was within 5% of actual revenue.
Here is how your accuracy stacks up against published B2B SaaS benchmarks:
| Accuracy Range | Assessment | Context |
|---|---|---|
| 95%+ | Excellent | ORM's target range for client engagements. Top decile. Gartner reports only 7% of sales teams achieve 90%+ forecast accuracy. At this level, your board can trust the number and plan around it. |
| 85-95% | Strong | Top quartile. Forecast is reliable enough for revenue planning but typically lacks the prescriptive layer that turns the gap into action. |
| 75-85% | Average | Typical for B2B SaaS companies using CRM-based forecasting without predictive models. |
| Below 75% | Needs work | Forecast misses at this level create board-level credibility problems and make resource planning unreliable. |
What the bias tells you
Forecast bias is as important as accuracy. Consistent over-forecasting (actuals come in below forecast) usually signals one of three problems: reps inflating their commits, conversion assumptions that are too aggressive, or deals slipping that are not being flagged early enough.
Consistent under-forecasting (actuals beat forecast) is less common but signals conservative assumptions or an acceleration in deal velocity that the model is not capturing.
At ORM, we decompose variance by segment, deal type, rep, and pipeline stage. That granularity reveals whether your accuracy problem is structural (the model is wrong) or behavioral (reps are not updating pipeline accurately). The fix is different in each case.
ORM's take: accuracy is the output, not the goal
Most companies treat forecast accuracy as a metric to improve. We treat it as a diagnostic of the revenue engine. When accuracy is low, the question is not "how do we get the number closer to actual." The question is "what is the underlying pipeline dynamic that the forecast is not capturing."
A custom model built on your data, calibrated to your conversion rates, and adjusted for your specific seasonal patterns will consistently outperform any spreadsheet, CRM roll-up, or generic platform algorithm. That is not because the math is more complex. It is because the model is specific to your business.
Common questions
How does this forecast accuracy calculator work?
For each quarter it takes the gap between forecast and actual, divides it by the actual and subtracts that from 100%. A $1M forecast against $900K closed misses by $100K, which is 11% of what closed, so the quarter scores about 89%. The headline score is the average of the quarters you enter.
What score should the calculator show?
Aim for 90% or better at the quarter level. Only about 7% of companies achieve it. Below 80% the forecast stops being useful for planning, because the error is larger than the decisions it informs. The benchmark table below the calculator shows each band.
What does the bias number mean?
Bias is the average of (forecast - actual) / actual. A positive number means you over-forecast, a negative one means you under-forecast. Accuracy says how far off you were. Bias says which way you lean, which is why the calculator shows both.
Why does the calculator skip a quarter?
A quarter needs both a forecast and an actual above zero. The formula divides by the actual, so an actual of zero has no defined accuracy. A miss larger than the actual scores 0% instead of a negative number.
Should forecast accuracy be measured per rep or per team?
Both. Team accuracy tells you whether the number is safe to commit. Per-rep accuracy tells you where the error comes from, and because individual bias is consistent quarter to quarter it can be subtracted rather than argued about.
Set the target at 95%
ORM builds custom forecast models that deliver board-ready accuracy. You get the number and what to do about it.
Schedule a Demo