Annualize the recent past
Run-rate forecasting projects revenue by extending recent performance forward, such as multiplying the latest month by twelve, making it the fastest and simplest method available. It answers a quick question: if things continue exactly as they are right now, where does the year land. That simplicity is its appeal and its weakness. The method assumes the recent period represents the whole year, which is convenient for a back-of-envelope estimate and dangerous as a basis for real planning.The assumption that breaks it
Run-rate forecasting is only as good as the representativeness of the period you annualize.
- Annualizing a seasonally strong month overstates the year. - Annualizing a month with a large one-time deal projects a spike that will not repeat. - Annualizing during a growth inflection either overstates or understates depending on direction.
Because it ignores seasonality, trend, and one-off events, run-rate is reliable only when performance is genuinely flat and steady, which is rarely true for a growing business. It is closely tied to the revenue run rate metric, which carries the same caveat: a snapshot annualized is a starting point, not a plan.
Use it as a baseline, not a plan
The right role for run-rate forecasting is a quick sanity check or a baseline to pressure-test a more rigorous forecast against, not the primary number for planning. For a fast estimate in an early conversation, annualizing the run rate is fine. For hiring commitments, board targets, or capacity decisions, a method that accounts for pipeline, seasonality, and trend, weighted or driver-based, is far more trustworthy. The discipline is knowing which job you are doing: run-rate for speed, a real model for accuracy. Treating a run-rate number as a planning forecast is one of the most common ways teams build a plan on a period that was never representative, then miss it and wonder why the forecast accuracy was so poor.
Frequently Asked Questions
What is run-rate forecasting?
It projects annual revenue by taking recent performance and extending it forward, for example multiplying the most recent month by twelve or the latest quarter by four. It is the fastest, simplest forecasting method, useful for a quick estimate, but it assumes the recent period is representative of the whole year.
What are the limits of run-rate forecasting?
It ignores seasonality, growth trends, and one-time events. Annualizing a strong month overstates the year if that month was seasonally high or included a large one-off deal; annualizing a weak month understates it. Run-rate works as a rough baseline but misleads whenever the recent period is not representative, which is often.
When should you use run-rate forecasting?
As a quick sanity check or a baseline, not as a primary forecast for planning. It suits early conversations and back-of-envelope estimates. For decisions that need accuracy, a method that accounts for pipeline, seasonality, and trend, such as driver-based or weighted forecasting, is far more reliable.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like run-rate forecasting into prescriptive action for your team.
Schedule a Demo