Currently taking 1 fractional CRO engagement from July 2026
navbar.siteName

Term

Annual Recurring Revenue (ARR)

MAY 27, 2026 · 9 MIN

Introduction & Core Definition

Annual Recurring Revenue (ARR) is the annualized run-rate of active subscription revenue at a single snapshot date. It is not what you billed last year and not what you booked this quarter. It is the value of contracts that are live right now, expressed as if they ran for a full twelve months at today's price. If a customer is paying $4,000 per month under an active subscription on March 31, that customer contributes $48,000 of ARR on that date.

ARR matters because subscription businesses are valued on the durability and growth of recurring streams, not on the lumpy timing of cash collection or revenue recognition. Investors, boards, and acquirers use ARR as the cleanest single proxy for the health of a SaaS franchise. The catch: only ARR that would survive an audit is worth anything. Most early-stage ARR numbers I see in board decks include LOIs, paused contracts, pilots without auto-renew, and multi-year deals counted at full value. Those are aspirational numbers, not board-quality numbers, and the distinction has cost founders real money in down rounds and broken term sheets.

ARR vs MRR vs Bookings vs Revenue

Four numbers get confused constantly. They are not interchangeable.

  • ARR (Annual Recurring Revenue): annualized run-rate of active subscriptions at a snapshot date. Forward-looking. If your subscription book is $400,000 of MRR on June 30, ARR on June 30 is $4.8M.
  • MRR (Monthly Recurring Revenue): the same idea, measured monthly. ARR is simply MRR multiplied by twelve. Companies that bill monthly or have lots of small accounts tend to talk in MRR; companies with annual contracts and larger ACVs talk in ARR.
  • Bookings: the total contract value signed in a period, including multi-year commitments and one-time fees. A three-year, $300,000 deal is $300,000 of bookings the day it is signed, but only $100,000 of new ARR.
  • Revenue (GAAP): what you have actually earned and recognized over a specific period under accounting rules. Revenue is backward-looking and recognized ratably as the service is delivered. A $120,000 annual contract signed July 1 contributes $60,000 of revenue in the current calendar year and $60,000 the next.

The quickest sanity check: ARR is a stock measured at a point in time, revenue is a flow measured over a period, and bookings is a flow that mixes recurring and non-recurring components. If a founder uses these words interchangeably on a board call, the rest of the meeting tends to go badly.

What Counts in ARR and What Does Not

The rule I use with portfolio companies and fractional CRO clients: ARR is the recurring, contractually committed, currently active subscription revenue, annualized. Everything else lives in a separate line.

Included in ARR:

  • Active monthly and annual SaaS subscriptions at current contract price.
  • Recurring platform fees that auto-renew unless cancelled.
  • Recurring usage minimums that the customer is contractually obligated to pay regardless of consumption.
  • Recurring support and maintenance contracts that auto-renew.

Excluded from ARR (no exceptions):

  • One-time implementation, setup, onboarding, and integration fees. These are bookings, not ARR.
  • Professional services and custom development, even if recurring on a project basis. Services revenue belongs on its own line.
  • Pilots and trials without a signed auto-renew clause. A 60-day paid pilot is a pilot, not ARR.
  • Letters of intent, verbal commitments, and signed-but-not-started contracts (those belong in CARR; see below).
  • Variable usage-based revenue above contractual minimums. Treat the floor as ARR and the overage as usage upside; do not annualize a peak month.
  • Multi-year contracts at full multi-year value. A three-year deal at $100k/year contributes $100k of ARR, not $300k.
  • Paused or non-paying customers, even if the contract is technically open. If they have stopped paying for more than a billing cycle, the ARR is impaired.

This last bullet is the one founders fight me on most often. If a customer has stopped paying for two months and you are still counting their ARR, you are flattering the number. Recognize the contraction the moment the cash stops, not when legal finishes the cancellation paperwork.

CARR: Contracted vs Live ARR

CARR (Committed or Contracted ARR) is the number you reach for when you have signed deals that have not yet started generating revenue. It equals live ARR plus signed-but-not-yet-live subscriptions.

A typical example: on March 31, you have $4.8M of live ARR and three signed contracts worth a combined $600k of new ARR that go live in April. CARR on March 31 is $5.4M, ARR on March 31 is $4.8M. Both are legitimate numbers; they answer different questions. ARR answers "what is currently earning?" and CARR answers "what have we already won?"

When to use which:

  • Use ARR for board reporting, valuation discussions, and any external benchmark. It is the conservative, auditable number.
  • Use CARR internally to forecast the next quarter's starting ARR and to credit the sales team for closed-won work that has not yet kicked in.
  • Never quote CARR to an investor without explicitly labeling it as CARR. Mixing the two is the fastest way to lose trust in due diligence.

A discipline that pays off: report ARR and CARR side by side every month, with the delta explicitly broken into "contracts signed, awaiting kickoff." When the gap stays small, your time-to-go-live is healthy. When the gap widens, your delivery or onboarding is the bottleneck, and your first 90 days of revenue work should focus there.

The Quarterly ARR Walk Boards Want

The format that institutional boards expect is the quarterly ARR walk. It moves you from starting ARR to ending ARR using five components:

Starting ARR + New ARR + Expansion ARR - Churn ARR - Contraction ARR = Ending ARR

Worked example. A B2B SaaS company starts Q1 at $5,000,000 of ARR. During the quarter:

  • Sales closes nine new logos worth $480,000 of new ARR.
  • Existing customers upgrade seats and add modules for $220,000 of expansion ARR.
  • Three customers do not renew, representing $150,000 of churn ARR.
  • Four customers downgrade seat counts or drop a module, removing $70,000 of contraction ARR.

Ending Q1 ARR = $5,000,000 + $480,000 + $220,000 - $150,000 - $70,000 = $5,480,000.

Net new ARR for the quarter is $480,000. Gross new ARR is $700,000 (new plus expansion). Gross churn is $220,000 (churn plus contraction). Net Revenue Retention can be derived from this walk: ($5,000,000 + $220,000 - $150,000 - $70,000) / $5,000,000 = 100.0%. For more on this, see net revenue retention.

A board-quality walk includes three additional disciplines. First, currency: lock the FX rate at the start of the quarter so movement reflects real customer behavior, not exchange-rate noise. Second, dates: timestamp each component to the day, not the quarter, so you can investigate spikes. Third, source of truth: the walk should be reproducible from your billing system, not from a sales operations spreadsheet that nobody can recompute. If your CFO and your VP Sales produce different ARR walks for the same quarter, your data architecture has a problem that no slide will fix.

Common Founder Mistakes With ARR

After cleaning up ARR reports for dozens of founder-led teams, I see the same eight mistakes repeatedly:

  1. Counting LOIs as ARR. A letter of intent is marketing language. Until the master agreement is signed and the subscription is active, it is not even CARR.
  2. Annualizing multi-year contracts at full value. A three-year deal at $100k per year is $100k of ARR, not $300k. If you book it as $300k, you owe the board an awkward conversation when the deal renews.
  3. Including one-time fees. Implementation, setup, training, and onboarding fees are services revenue. They belong on a separate line and they should never inflate ARR.
  4. Counting pilots as ARR. A paid pilot without an auto-renew clause is a pilot, not a subscription. Many of them never convert. Track conversion rate separately.
  5. Ignoring paused customers. If a customer has not paid in two months, recognize the contraction. Hope is not a reporting framework.
  6. Single-year deals with auto-cancellation. If your standard contract auto-terminates rather than auto-renews, your effective ARR is materially weaker than the headline number. Disclose it.
  7. Mixing CARR and ARR. State the definition in the footnote of every dashboard. Switching back and forth between the two without labeling destroys credibility.
  8. Treating usage overages as recurring. The contractual floor is recurring; the overage is upside. Annualizing a peak month creates a number that you will not hit again.

A related symptom: an early-stage CEO claims $2M of ARR, but billings, recognized revenue, and the customer list cannot reconcile to anywhere near that figure. Diligence finds it within an hour. Run a clean ARR reset before the term sheet, not after. A pre-CRO sales audit is the natural place to do that work, alongside fixing pipeline coverage benchmarks and sales cycle reporting.

Key Considerations & Best Practices

  1. Define ARR in writing. Publish a one-page memo that names every included and excluded item. Tie it to your billing system, not to a sales narrative. Update the memo only with board approval.
  2. Run ARR off the billing system. Sales operations dashboards drift; billing systems do not. If your CRM ARR and your billing ARR disagree, billing wins.
  3. Report ARR and CARR side by side. Both numbers are useful; only one is auditable. Always label.
  4. Walk the quarter, every quarter. The five-component walk forces honest accounting of expansion, churn, and contraction. Founders who skip the walk lose feel for the business.
  5. Watch the ratio of services to subscription revenue. If implementation revenue is more than 25 to 30 percent of total revenue, you are running a services company with a software side, not the other way around. That changes valuation math significantly. See SaaS sales process: PLG vs SLG for how this interacts with go-to-market design.
  6. Cross-reference with TAM. A clean ARR number is also the denominator for penetration math against your total addressable market and the numerator in sales velocity calculations.
  7. Audit before fundraising. Run a clean-up two quarters before a planned round. The diligence team will run the walk anyway; better that you find the discrepancies first.

Conclusion

ARR is the single most-quoted SaaS metric, and the one most often abused. The discipline is simple in description and hard in practice: count only the recurring, contractually committed, currently active subscription revenue, annualized; separate CARR; walk the quarter in five components; never mix in bookings, services, pilots, or LOIs. Founders who run their company on board-quality ARR rather than headline ARR raise on better terms, sleep better through diligence, and build a reporting culture that scales. The ARR number that survives a SaaS audit is the only one worth optimizing for.

// Let's build

Back to General glossary

Reference terms not tied to a specific service engagement.

General glossary service

Mathematically they are identical: ARR equals MRR multiplied by twelve. The difference is which number you actually report and reason with. Companies with mostly monthly billing, freemium funnels, or PLG motions usually run on MRR because the cadence of change is monthly and small movements matter. Companies with annual contracts and larger ACVs run on ARR because the granularity matches the business: most movement happens at renewal, and a quarterly walk is the natural reporting unit.

The practical implication is which dashboard the executive team stares at on Monday morning. If churn shows up first in MRR and only later in ARR-equivalent terms, you want MRR up front. If your sales team closes annual contracts and your finance team plans in annual increments, ARR is the cleaner unit. Pick one as your primary metric, label it clearly, and stop translating between the two on every slide.

For investor reporting, ARR is the default at Series A and beyond regardless of how you bill internally. Translate cleanly and consistently. The mistake is reporting MRR in one deck and ARR in another without reconciling the snapshot date.

One year, full stop. ARR is the annualized run-rate at a snapshot date, which means it answers the question, "if this customer's contract continued at today's price for the next twelve months, how much would they pay?" The answer for a $100,000-per-year contract is $100,000, whether the total commitment is one year, three years, or ten.

The multi-year commitment shows up in two other places, not in ARR. First, it shows up in bookings: a three-year, $300,000 deal is $300,000 of bookings on the day it signs. Second, it shows up in your weighted-average contract length, which is a signal of stickiness. Both are valuable; neither is ARR.

Founders sometimes argue that the multi-year commitment is more valuable than a one-year deal and therefore deserves higher ARR. The way to express that is in retention assumptions, churn forecasts, and contract length analytics, not by inflating the headline number. Diligence teams will catch the overstatement immediately, and the cleanup is more painful than the discipline.

Split it into two components. The contractual floor or commitment is ARR; everything above the floor is usage upside, tracked separately. If a customer commits to $5,000 per month minimum with overage charges for additional API calls, the ARR contribution is $60,000 regardless of whether they consume $5,000 or $50,000 last month. The variable component is reported as consumption revenue, ideally with its own walk that tracks attach rates and expansion.

Why not annualize the peak month? Because the peak does not recur reliably. Annualizing a spike turns a one-time event into a structural ARR commitment that the business cannot defend at renewal. The mirror failure is annualizing the trough, which makes a healthy account look like it is contracting.

The cleanest approach for usage-heavy models is to push for higher contractual floors at renewal. That converts variable upside into committed ARR and improves the predictability of the book. It also changes the conversation with the customer from "how much did you use last month?" to "what is your committed capacity?" which is a much healthier framing for a long-term partnership.

The moment they stop paying for a full billing cycle past the grace period defined in your contract. Not when sales stops believing the deal is salvageable, not when customer success closes the renewal note, and not when legal completes the offboarding paperwork. Cash is the truth-teller. If a customer has missed a full billing cycle and shows no operational signal of resuming, the ARR is impaired and should be recognized as contraction or churn in the current period.

The reason this matters: late ARR recognition compounds. If you carry a paused customer for two quarters and then write them off, the write-off lands in a single quarter and distorts the walk. The board sees a sudden churn cliff and asks why. The honest answer is, "we should have recognized this two quarters ago." That answer is worse than the small adjustment you would have made at the time.

A helpful operating rule: define a paused-but-recoverable category that sits between ARR and churn. Move the impaired contract there immediately, take the ARR hit, and then if the customer resumes within ninety days, count it as won-back ARR in the recovery quarter. The accounting is symmetric, and the walk stays honest.

A typical cleanup runs four to six weeks and starts with a full reconciliation between the billing system, the CRM, and the contract repository. We list every customer in the active book, identify the contract terms, the current paid status, and any open disputes. Discrepancies surface immediately: pilots counted as ARR, multi-year deals booked at full value, paused customers still in the active list, one-time fees blended into subscription revenue.

From that reconciliation we produce a restated ARR for the past four quarters and a clean walk for the current quarter. We also produce a one-page definition memo that names every included and excluded item, and we install a monthly close process that reproduces the walk from billing data automatically. The output is a board-ready dashboard that nobody has to defend by hand.

This kind of work shows up in the first thirty days of most of my fractional engagements because almost no early-stage company has it nailed. The work is unglamorous but it is the foundation for every downstream decision: pricing, hiring, fundraising, and territory design. If you want to see how this fits into a broader scope, the fractional CRO first 90 days and the pre-CRO sales audit are the natural entry points.