Annual Recurring Revenue (ARR) and MRR Explained
Lightbridge defines annual recurring revenue (ARR) as the normalized value of a SaaS company's recurring subscription revenue expressed over a twelve-month period. ARR equals monthly recurring revenue (MRR) times twelve. It counts committed, repeatable subscription revenue only, and it excludes one-time setup, implementation, and professional-services fees that do not recur.
ARR is a SaaS run-rate that annualizes recurring subscription revenue.
Annual recurring revenue (ARR) measures the recurring portion of a subscription business, expressed over a year. The formula is simple: ARR equals MRR times twelve. Because MRR is already normalized to a monthly figure, ARR is a snapshot of the recurring run-rate at a point in time. It is not a trailing total of revenue booked over the prior twelve months, and that distinction matters when a company is growing fast.
ARR and MRR exist to answer one question that a single GAAP revenue line cannot: how much recurring revenue is committed and repeatable right now. Investors, boards, and operators use ARR to compare scale and growth across subscription companies. Lightbridge is the umbrella brand across an independent group of practices, and growth-finance metrics are part of its cross-entity thought leadership for SaaS founders, CFOs, and RevOps leaders.
One caution before any formula: ARR is a SaaS-finance convention, not a GAAP or FASB requirement. There is no single authoritative definition, which is precisely why discipline matters. The figures here are general information, not financial, accounting, or investment advice. Define your metric, write it down, apply it consistently, and reconcile it to audited revenue.
ARR counts committed recurring revenue and excludes one-time fees.
The accuracy of ARR depends entirely on what you include. The boundary is whether revenue is committed and repeatable. Get this wrong and the run-rate is fiction. These four rules separate recurring revenue from everything else.
Counts: subscription fees
Recurring license or subscription charges that a customer is contractually committed to pay on a repeating cycle. This is the core of ARR and MRR: revenue you expect to see again next period without a new sale.
Counts: contractual minimums
Committed usage floors and contractual minimum commitments count, because they are recurring and predictable. Do not assume all usage revenue is excluded: the test is whether the revenue is committed and repeatable, not whether it is labeled usage.
Excludes: one-time fees
Setup fees, implementation charges, onboarding, training, and professional-services revenue are excluded. They are real revenue, but they do not recur, so folding them into ARR overstates the recurring base.
Excludes: non-contractual usage
Variable, non-contractual overage and pay-as-you-go usage above any committed minimum is excluded from ARR, because it is not guaranteed to repeat. Many teams track it separately as variable or consumption revenue.
How you bill a customer is a separate question from what counts as recurring. For the mechanics of subscription pricing and invoicing, see Lightbridge ERP on subscription billing models.
Calculating ARR means normalizing MRR first, then multiplying by twelve.
ARR is built from MRR, and MRR is built from normalization. Work it in that order. The three pieces below are the whole calculation, and the normalization step is the one teams most often skip.
MRR
MRR is the sum of all normalized monthly recurring revenue across active subscriptions in a given month. Annual and multi-year contracts are normalized to a monthly figure (annual contract value divided by twelve) so every customer is measured on the same monthly basis.
ARR = MRR x 12
ARR is MRR multiplied by twelve. Because MRR is already normalized, ARR is a point-in-time snapshot of the recurring run-rate, not a trailing sum of revenue actually booked over the past year. It answers a forward question: what is the annualized recurring base right now.
Normalization
Normalization is the discipline that makes ARR and MRR comparable. A 24-month deal and a monthly deal both reduce to a per-month figure first, then roll up. Without normalization, contract length distorts the metric and two companies cannot be compared.
A worked example makes it concrete. Suppose a company has 400 active customers paying an average normalized 500 dollars per month. MRR is 400 times 500, which is 200,000 dollars. ARR is 200,000 times twelve, which is 2.4 million dollars. If one of those customers also paid a one-time 10,000 dollar implementation fee, that fee stays out of both numbers, because it does not recur. The run-rate stays 2.4 million dollars.
ARR and MRR measure the same recurring revenue on different time scales.
ARR versus MRR is not a question of which is correct, because ARR equals MRR times twelve by construction. They differ in use. MRR is the operating metric: teams break it into new, expansion, contraction, and churned MRR to see exactly where the recurring base moved this month. ARR is the headline metric: it is what boards, investors, and annual plans speak in, because a single annualized number is easier to compare across companies.
As a rule of thumb, month-to-month and earlier-stage businesses tend to lead with MRR, while annual-contract and later-stage businesses tend to lead with ARR. The important discipline is to keep the two reconciled: ARR should always be exactly twelve times the MRR you report, computed on the same normalized base. If they drift, someone changed a definition.
ARR is the base for the wider family of SaaS growth metrics.
Once ARR and MRR are defined, the rest of the SaaS metric stack builds on them, and every one is a convention with variable definitions, not a GAAP rule. Net revenue retention (NRR, also called net dollar retention) is (starting MRR plus expansion minus contraction minus churn) divided by starting MRR, and because it includes expansion it can exceed 100 percent. Gross revenue retention (GRR) is (starting MRR minus contraction minus churn) divided by starting MRR, excludes expansion, and is therefore capped at 100 percent. Churn rate is measured two ways: revenue churn (lost MRR over starting MRR for the period) and logo churn (lost customers over starting customers for the period).
The efficiency metrics sit on the same base. The Rule of 40 says growth rate percent plus profitability margin percent should be at least 40; the profitability term is variable, and this guide uses EBITDA margin as the default (free-cash-flow margin is common for mature companies, operating margin less so). The Rule of 40 traces to Brad Feld in 2015 and the SaaS investors of that era. The SaaS magic number is net new ARR in a period divided by sales-and-marketing spend in the prior period; state whether the numerator is a net-new-ARR delta or a GAAP-subscription-revenue delta, since both are used and give different results, and roughly 0.75 or higher is a common efficiency heuristic. The burn multiple (Bessemer and David Sacks) is net cash burned divided by net new ARR, where lower is better.
Unit economics round out the set. CAC is sales-and-marketing cost to acquire a customer in a period divided by new customers in that period. Lifetime value (LTV) is commonly (ARPA times gross-margin percent) divided by churn rate, and the often-cited LTV:CAC of 3:1 is a non-GAAP heuristic, not a standard, that depends entirely on those assumptions. CAC payback in months is CAC divided by (ARPA times gross-margin percent). The SaaS quick ratio is (new MRR plus expansion MRR) divided by (churned MRR plus contraction MRR). Each is a management convention to define explicitly and apply consistently, not a financial-reporting requirement.
SaaS growth metrics are conventions, not GAAP requirements.
Every metric on this page (ARR, MRR, NRR, GRR, churn, Rule of 40, magic number, burn multiple, CAC, LTV) is a SaaS-finance convention with a variable definition. None is mandated by GAAP, IFRS, or FASB. That is why two companies reporting the same headline ARR can have computed it on different rules. Recognized revenue under GAAP follows ASC 606 and answers a different question: revenue earned as performance obligations are satisfied over time.
The practical implication is reconciliation. A management metric like ARR should be defined in writing, applied consistently across periods, and tied back to audited GAAP revenue so investors and auditors can see the relationship. Lightbridge ERP covers the accounting side in depth, including ASC 606 revenue recognition and deferred revenue, which is where the billing schedule, recognized revenue, and recurring run-rate are kept distinct and reconciled.
This guide is general information, not financial, accounting, tax, or investment advice. Definitions and benchmarks vary across the industry and change over time. Confirm any metric you report with your own finance, accounting, and audit advisors before relying on it.
Annual recurring revenue: frequently asked questions
- What is annual recurring revenue (ARR)?
- Annual recurring revenue (ARR) is the normalized value of a SaaS company's recurring subscription revenue expressed over twelve months. ARR equals MRR times twelve. It is a point-in-time run-rate, not a trailing sum of revenue booked over the past year. ARR counts committed, repeatable subscription revenue and excludes one-time setup, implementation, and professional-services fees. ARR is a SaaS-finance convention used to communicate scale and growth, not a figure defined by GAAP or FASB. Lightbridge treats ARR as a management metric that should be reconciled to audited GAAP revenue, never as a substitute for it.
- How do you calculate ARR?
- Calculate ARR in two steps. First compute MRR: normalize every active subscription to a monthly figure (an annual contract is divided by twelve, a multi-year contract by its number of months), then sum those monthly figures across all customers. Second, multiply MRR by twelve. The result is your annualized recurring run-rate at that point in time. Exclude one-time fees and non-contractual usage from both steps. For example, 400 customers at an average normalized 500 dollars per month is 200,000 dollars MRR, which is 2.4 million dollars ARR.
- What is the difference between ARR and MRR?
- ARR and MRR measure the same thing on different time scales. MRR is monthly recurring revenue, the normalized recurring revenue in a single month. ARR is annual recurring revenue, equal to MRR times twelve. They are mathematically linked, so neither is more accurate than the other. Teams use MRR for granular, month-over-month movement (new, expansion, contraction, churned) and use ARR for board-level scale, valuation conversations, and annual planning. Smaller and month-to-month businesses tend to lead with MRR; larger and annual-contract businesses tend to lead with ARR.
- What counts toward ARR and what does not?
- ARR counts recurring, committed subscription revenue: subscription fees and contractual minimum commitments that repeat on a predictable cycle. ARR excludes one-time setup, implementation, onboarding, training, and professional-services fees, because those do not recur. ARR also excludes non-contractual, variable usage above any committed minimum, because it is not guaranteed to repeat. A common error is excluding all usage revenue: committed or contractual usage minimums can be included, while only the variable, non-committed portion is excluded. The test is whether the revenue is committed and repeatable.
- Is ARR a GAAP metric?
- No. ARR is a SaaS-finance convention, not a measure defined by GAAP, IFRS, or FASB. There is no single authoritative definition of ARR, which is why two companies can compute it differently. Recognized revenue under GAAP follows ASC 606 and reflects revenue earned over time as performance obligations are satisfied, which is a different question from the forward-looking recurring run-rate that ARR describes. Lightbridge recommends defining ARR explicitly in writing, applying it consistently, and reconciling it to audited GAAP revenue so investors and auditors can see how the management metric and the financial statements relate.
- Does usage-based or consumption revenue count toward ARR?
- It depends on whether the usage is committed. Contractual minimum commitments and committed consumption count toward ARR, because they are recurring and predictable. Non-contractual, variable usage above any committed floor does not count, because it is not guaranteed to repeat. Usage-based businesses often report a committed-ARR figure alongside a separate variable or consumption-revenue line so the recurring base stays clean. The rule is consistency: decide the boundary, document it, and apply it every period. Lightbridge helps teams set that boundary so usage revenue is neither double-counted nor silently inflating the recurring base.
- How does ARR relate to revenue recognition and billing?
- ARR is a forward-looking run-rate, while revenue recognition is the accounting record of revenue earned. A customer can be billed annually in advance, recognized monthly over the contract under ASC 606, and contribute a flat amount to ARR the whole time. These three views (billing schedule, recognized revenue, and recurring run-rate) move on different clocks and answer different questions. Lightbridge ERP owns the revenue-recognition and billing topics in depth. Confusing the three is one of the most common sources of board-deck errors, so the disciplined practice is to define each explicitly and reconcile them.
- How does Lightbridge help teams measure ARR and SaaS growth metrics?
- Lightbridge is the umbrella brand across an independent group of practices. On growth-finance metrics, the work is to define ARR, MRR, NRR, churn, and the efficiency ratios precisely, apply them consistently, and reconcile the management metrics to audited GAAP revenue. Lightbridge ERP handles the underlying billing and revenue-recognition systems, and Lightbridge Labs handles AI for forecasting and analysis. The throughline is rigor: a SaaS metric is only useful when its definition is written down, agreed, and held stable period over period so the trend is real and not an artifact of changing the formula.
From a clean ARR number to a metric you can defend.
When the question shifts from what ARR is to whether your number holds up in a board deck or a diligence room, Lightbridge helps you define it precisely and reconcile it to audited revenue.