Quick answer
Annual run rate is a short period's revenue extrapolated to a full year, such as last month × 12 or last quarter × 4. It is a straight-line projection, so it overstates after peak seasons or one-off deals, and it is not the same as annual recurring revenue (ARR).
Formula: Annual run rate = revenue in period × periods per year (month × 12, quarter × 4)
What is annual run rate?
In finance and SaaS reporting, annual run rate (also revenue run rate or annualized run rate) is a short period's revenue extrapolated to a full year: last month × 12, last quarter × 4. It answers "if the business kept performing exactly like this for twelve months, how much would it bring in?"
The calculation is trivial; the judgement is not. Run rate is a straight-line projection, so it inherits everything unusual about the period you start from. The two biggest traps are extrapolating a peak season (December for a retailer, March for a tax tool) and extrapolating a single large deal or one-off fee. Run rate is also not the same thing as annual recurring revenue (ARR), which counts only contracted subscription revenue, even though both are sometimes abbreviated "ARR".
Run rate formula
Annual run rate = revenue in period × (number of such periods in a year)
| Starting period | Formula | Example |
|---|---|---|
| One month | Monthly revenue × 12 | $85,000 × 12 = $1,020,000 |
| One quarter | Quarterly revenue × 4 | $240,000 × 4 = $960,000 |
| One week | Weekly revenue × 52 | $18,000 × 52 = $936,000 |
| One day | Daily revenue × 365 | $2,600 × 365 = $949,000 |
The shorter the starting period, the more noise you multiply. A single day × 365 magnifies one good or bad day into a six-figure swing. Official statistics publish many figures at annual rates for comparability, and statistical agencies remove seasonal patterns with tools such as the Census Bureau's X-13ARIMA-SEATS; most business run rates skip that step.
Run rate vs ARR vs forecast
| Annual run rate | Annual recurring revenue (ARR) | Revenue forecast | |
|---|---|---|---|
| What goes in | All revenue in the period: subscriptions, one-off fees, usage, services | Only recurring contracted subscription revenue, annualized | Expected future revenue by month, with assumptions |
| Formula | Period revenue × periods per year | Monthly recurring revenue × 12, or sum of annual contract values | Model: trend, seasonality, pipeline, churn |
| Handles seasonality | No | Not needed (contracts are flat) | Yes, if modelled |
| Handles one-offs | No, it multiplies them | Excludes them | Yes, as separate lines |
| Good for | Quick size of a young or steady business | SaaS health, valuation, investor reporting | Budgets, hiring, cash planning |
| Main risk | Overstates after a peak, understates after a slump | Ignores non-recurring revenue the business really earns | Assumptions can be wrong |
To calculate MRR and ARR from your plan mix, use the MRR and ARR calculator; for a seasonal projection, the revenue forecast calculator.
Worked example: December × 12 vs the actual year
Sample data: an online store's monthly revenue for one year, in thousands of dollars.
| Month | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Revenue ($k) | 80 | 72 | 85 | 88 | 92 | 90 | 94 | 98 | 96 | 105 | 150 | 210 |
The twelve months add up to $1,260k, an average of 1,260 ÷ 12 = $105k a month. Three run rates from different starting points:
- December × 12 = 210 × 12 = $2,520k, which is 2,520 ÷ 1,260 − 1 = 100% above what the year actually produced.
- Q4 × 4 = (105 + 150 + 210) × 4 = 465 × 4 = $1,860k, 1,860 ÷ 1,260 − 1 = 47.6% above.
- June × 12 = 90 × 12 = $1,080k, 1,080 ÷ 1,260 − 1 = 14.3% below.
The same business looks like a $1.08M or a $2.52M company depending on the month you pick. Now a simple seasonality adjustment: last year, December brought in $183k of a $1,100k year, so December's share of annual revenue was 183 ÷ 1,100 = 16.6% (a seasonal index of 183 ÷ (1,100 ÷ 12) = 2.0).
- Seasonally adjusted run rate = December revenue ÷ December's share = 210 ÷ (183 ÷ 1,100) = $1,262k, within 0.2% of the actual $1,260k.
The adjustment works here because the seasonal pattern repeated. If you have a year of history, the trailing twelve months (here exactly $1,260k) is the simpler, honest number; run rate is for when you do not.
The one-off deal problem
Sample data: a B2B SaaS company has $50k of monthly recurring revenue. In March it also books a $40k one-off implementation fee.
- March revenue = 50 + 40 = $90k, so the March run rate = 90 × 12 = $1,080k.
- ARR = 50 × 12 = $600k, because the fee does not recur.
The run rate is 80% higher than ARR (1,080 ÷ 600 − 1), purely because one invoice landed in the month used for the calculation. If a deck says "$1M+ ARR" from that March, it is reporting a run rate under the wrong name. The fix is to strip non-recurring items before annualizing, or to report ARR and other revenue on separate lines.
When run rate is useful and when it is not
- If revenue is steady month to month (low seasonality, many small customers, no big one-offs), then a 3-month average × 12 is a reasonable quick size.
- If the business is very young and growing fast, then run rate from the latest month is a fair "current scale" number, but say which month and keep it separate from forecasts; see revenue growth rate for describing the trend itself.
- If the starting month is a known peak or trough, then either adjust by last year's share of revenue for that month or use the trailing twelve months.
- If revenue includes setup fees, hardware or one-time projects, then remove them before annualizing, or report ARR instead.
- If you are planning budgets or hiring, then use a month-by-month forecast with seasonality, not a run rate. For digging into which products and periods drive revenue, see sales analysis.
Common mistakes
- Annualizing the best month. The holiday month, launch month or a viral week makes the most flattering and least reliable run rate.
- Calling run rate "ARR". Annual recurring revenue excludes one-off and usage revenue; annual run rate includes them.
- Mixing gross and net. Decide whether refunds and discounts come off before you multiply, and say so.
- Using days or weeks. Multiplying a short period by 365 or 52 turns noise into big numbers.
- Comparing run rates from different months. January's run rate vs December's run rate mostly measures seasonality, not growth.
Run rate inputs in TapCub
Here is the store example worked through in TapCub. TapCub does not do subscription billing, so contracted MRR and ARR come from your billing system; TapCub works with the purchase events you send.
- Get the period revenue. All-platform analytics › Business › Commerce & revenue reads purchases from the order ledger: choose December and read revenue and orders. Amounts are converted to the site's base currency at the day's rate. Refunds in the same period are reported separately and are not subtracted, so decide whether your run rate is gross or net before multiplying.
- See the monthly pattern. In All-platform analytics › Behavior › Event analysis, measure the
purchaseevent with the property sum ofrevenue, set granularity to month and compare with the same period last year. That gives the twelve monthly figures and last year's December share used in the seasonal adjustment above. - Save the metric once. In All-platform analytics › Behavior › Metrics & SQL, define revenue as the property sum of
revenueonpurchase(currency format), so every chart and dashboard uses the same definition of the number you annualize. - Track against the year, not the month. In All-platform analytics › Business › AARRR growth, you can set an annual revenue target; progress is year-to-date revenue divided by the target, which avoids multiplying one month at all.
Sources
- U.S. Bureau of Economic Analysis, Why does BEA publish estimates at annual rates?
- U.S. Census Bureau, X-13ARIMA-SEATS Seasonal Adjustment Program.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Data Analyst
Explores traffic sources, conversion funnels, and retention, using clear metric definitions and concrete examples to explain what the numbers mean.