What run rate measures and what it does not
Revenue run rate is a current-pace projection, not a forecast. It answers the question: if nothing changes from this point forward, what would we expect to generate in a full year? It does not account for anticipated new bookings, known churn events, or seasonal patterns. That constraint is what makes it quick to calculate and unreliable in anything but a steady state.Run rate is most useful early in a company's life when there is no full year of history, or at a point in the year when only a portion of the annual period has elapsed. It gives a quick, comparable number that can be used in investor updates, internal planning discussions, or board materials without waiting for a full twelve-month period to close.
The core formula and its variants
| Approach | Formula | Use case |
|---|---|---|
| Monthly annualization | Most recent month x 12 | Fast-growth companies; captures latest momentum |
| Quarterly annualization | Most recent quarter x 4 | Smooths single-month noise; common in reporting |
| Trailing twelve months | Sum of last 12 months | Eliminates seasonality; not technically "run rate" |
Where run rate creates distortions
In a growing SaaS business, monthly annualization produces an optimistic number. If a company generated $100K in January and $200K in December after consistent growth across the year, annualizing the December figure suggests a much higher trajectory than the company actually achieved over the year. This is directionally useful but should not be confused with a realistic full-year projection.
Run rate is also unreliable when revenue includes meaningful non-recurring components. Professional services fees, one-time implementation charges, or large enterprise contracts with irregular payment schedules will inflate a single-period run rate without representing the repeatable business.
Run rate in the context of ARR and forecasting
For subscription businesses, annual recurring revenue is almost always the preferred metric over run rate because it is grounded in actual contracts rather than a projection from recognized revenue. When the two diverge significantly, it usually signals a timing difference between billings and recognition, or a meaningful gap between contracted and realized revenue.
Use run rate as a quick conversational shorthand, but anchor planning and performance review in ARR and formal revenue forecasting models. The distinction between these metrics is covered in detail in ARR vs MRR.
Frequently Asked Questions
How do you calculate revenue run rate?
The most common approach is to take the most recent month's revenue and multiply by twelve, or take the most recent quarter's revenue and multiply by four. The result is a projection of what the business would generate over a full year if its current pace held constant. The formula is straightforward; the challenge is deciding which period is representative.
What is the difference between run rate and ARR?
ARR is a contractual metric derived from the value of active subscription contracts. Run rate is a projection derived from actual recognized revenue in a recent period. For a mature, stable SaaS business, the two should converge. For a company with high growth, seasonal patterns, or significant one-time revenue, they can diverge substantially.
When is run rate misleading?
Run rate assumes the recent period is representative and that growth or decline will not continue. In a high-growth company, annualizing a recent month overstates the likely full-year outcome because earlier months were lower. In a business with significant one-time fees, services revenue, or seasonal spikes, run rate inflates the projected annual figure relative to the recurring base.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like revenue run rate into prescriptive action for your team.
Schedule a Demo