Total Recurring Revenue

What it measures

The revenue you actually recognize this period from contracts that repeat — software subscriptions, recurring services retainers, and product subscriptions. Each contract is recognized pro-rata: its total contract value divided by the days in the full term, times the days in the reporting period, summed across every active recurring contract. It excludes one-time fees (implementation, setup, perpetual licenses) and usage spikes. Unlike ARR, which annualizes a run-rate, Total Recurring Revenue is the hard revenue earned in the actual month, quarter, or year.

Why it matters

Total Recurring Revenue tells you how much of your business is built to repeat. You track it to separate durable, contracted income from lumpy one-time deals. Investors weight it heavily because recurring revenue is forecastable and commands a far higher valuation multiple than project or services revenue — so a company with growing recurring revenue is fundable and resilient, while one with shrinking recurring revenue is signaling that its value proposition is eroding. Your board reads it to answer three questions: is the model repeatable or deal-dependent, are new wins and upsells outrunning churn, and how sticky is the revenue.

How to read it

Read recurring revenue as a period total, never a snapshot — always compare this month or quarter to the prior one and to plan. Rising recurring revenue means new customers, upsells, and retention are outpacing churn and downgrades; flat or falling recurring revenue means the leaks are winning. Track it as a share of Total Revenue: if that share is falling, the business is drifting toward one-time services, which is usually a bad sign. And check the breadth of the base — recurring revenue that climbs on a handful of mega-deals is lumpy and at-risk, while recurring revenue growing across many customers is durable.

What good looks like

Watch-outs

• Reporting annualized run-rate as recurring revenue. This metric is the revenue earned in the actual month or quarter, not the annualized projection. A team that calls a single month's number 'recurring revenue of $100K' is almost always stating ARR. State the time window, and use ARR terminology when you mean the run-rate.
• Letting non-recurring revenue leak in. One-time setup, implementation, and perpetual licenses inflate recurring revenue and hide the true repeatable run-rate. If a deal closes with $50K upfront and $10K annual subscription, only the $10K (its in-period pro-rata) counts.
• Double-counting multi-year or renewal contracts. When a two-year deal renews, do not re-recognize the full value; recognize only the portion earned this period. A $24K two-year renewal adds roughly $1K/month, not a $24K spike.
• Lumping every stream into one number. Combining software, services, and hardware into a single figure hides which streams are growing and which are at risk. Break it down by product line, segment, or contract type so you can see where to focus retention.

Worked example