Run Rate

Run rate takes one slice of revenue and pretends it lasts twelve months. A company does $2M in a quarter, multiplies by four, and reports an $8M run rate — a projection, not a result. The number is useful because it lets a two-year-old company describe itself in annual terms before it has an annual track record. It is dangerous for exactly the same reason: it converts a snapshot into a forecast and hopes nobody checks the shutter speed.

How Run Rate Is Calculated

Run rate annualizes a base period by multiplying it to a full year:

• Monthly base: current month × 12
• Quarterly base: current quarter × 4

So a $750K month implies a $9M annual run rate. A $2.4M quarter implies a $9.6M run rate. The math is trivial, which is the problem — it carries no information about whether the base period was normal, seasonal, or a one-time spike. Revenue run rate uses recognized revenue; bookings run rate uses signed contracts; ARR run rate annualizes only the recurring subscription portion and strips out one-time fees. Conflating those three is the most common honest mistake.

Worked Example

Two companies both report a $12M run rate. They are not the same company.

Alpha's real recurring base, averaged across the year, is closer to $700K/month — a $8.4M run rate, not $12M. The label survived. The substance did not.

When Sales Teams Use Run Rate

Founders and CFOs use run rate in board decks and fundraising because it makes growth legible before a full fiscal year closes. RevOps uses it for capacity planning — if the current bookings run rate is $20M and quota-carrying capacity supports $16M, hiring is behind. Finance uses MRR-based run rate as the cleanest version because monthly recurring revenue is already normalized and excludes the one-time noise that distorts bookings. Investors treat run rate as a starting point for diligence, not an answer — the first question in any data room is "which month, and why that one."

Common Run Rate Gaming Patterns

The exploit is base-period selection. A company picks its strongest month, multiplies by twelve, and reports the result with a straight face — December annualized looks 40% better than a trailing-twelve-month average if Q4 carried a seasonal renewal cliff. Pulling deals forward into the base month inflates it further, then the following month craters and gets quietly excluded from the next deck.

The second pattern is mixing non-recurring revenue into a "recurring" run rate. Professional services, implementation fees, and one-time licenses get annualized as if they repeat — they do not. A clean ARR figure would catch this; a blended revenue run rate hides it.

Run rate also says nothing about retention. It annualizes gross revenue and ignores the churn that will erode the base before the year ends. A $12M run rate with 25% annual churn is not a $12M company. The number that survives diligence is the one cross-checked against bookings linearity and forecast accuracy — if a company's months are smooth and its forecasts land, its run rate means something. If December does all the work, it does not.