ARR sounds simple until three people in the same company give you three different numbers.
In SaaS, ARR is annual recurring revenue. It’s the yearly value of the revenue you expect to repeat. The trouble starts when founders use it loosely, as if it means total sales, booked contract value, or “roughly what we’re on now”.
You don’t need more jargon. You need a few clear ARR definitions that fit the moment. Investors, boards and finance teams often ask different questions. If your ARR number can’t survive those conversations, it isn’t doing its job.
What ARR actually means for a SaaS business
At its simplest, ARR is the annual value of your recurring subscription base. If a customer pays you £1,000 a month for software, that’s £12,000 of ARR. If ten customers do the same, that’s £120,000.
Think of ARR as the repeatable engine in the business. It tells you how much predictable revenue your product is producing, before one-off bits muddy the picture. That’s why SaaS founders track it so closely.
The simplest way to define ARR
Here’s the version a founder can use in a pitch, board meeting, or team update:
ARR is the yearly value of contracted recurring software revenue.
Short. Clear. No fluff. It says what matters, and it leaves out what doesn’t.
What should and should not be included
Include subscription fees, renewals, recurring add-ons, and upgrades that increase ongoing spend. If the customer is paying for software access on a repeat basis, it probably belongs in ARR.
Leave out setup fees, consultancy, project work, onboarding charges, hardware, and any non-recurring service line. Those sales may be useful, but they are not ARR. A founder who mixes them in usually ends up overstating growth.
This is where mistakes creep in. A £15,000 onboarding project can make the month look strong, but it doesn’t make next year safer. ARR is about what repeats, not what happened once.
The ARR definitions founders should use in different situations
This is the part most founders miss. ARR is one idea, but the number you present should match the question being asked.
If your sales report, board pack and investor update all show different ARR, trust disappears fast.
ARR for day-to-day management
For internal management, ARR should help you run the company. That means using a consistent month-end figure based on live recurring revenue. You want to see momentum, slippage, and trend without changing the rules every time the story gets uncomfortable.
This version of ARR is useful because it links to what operators can control. New customers lift it. Expansion lifts it. Churn and downgrades pull it down. Track it the same way every month and you start to see the business clearly, not emotionally.
ARR for investors and fundraising
Fundraising ARR needs to be clean. Investors don’t want padded numbers. They want recurring software revenue that is real, durable, and easy to diligence. Pilots, one-off service bundles, and soft verbal renewals do not belong here.
A good investor number also needs context. How fast is it growing? How much came from expansion versus new logo wins? What does churn look like? That’s why a proper investor-grade SaaS financial model matters. It ties ARR back to the drivers underneath it, instead of treating it like a headline pulled from thin air.
ARR for board packs and reporting
Board reporting needs more than a single closing number. Boards need movement. What was opening ARR? How much came from new business, expansion, contraction, churn, and reactivation? What changed, and why?
That is where a simple ARR bridge helps. A clean board pack should show the story behind growth, not only the total. If you want a sharper view of MRR and ARR movements, build the habit of reporting the components every month. It makes board conversations calmer and far more useful.
How ARR differs from MRR, bookings, and revenue
Founders often say ARR when they mean something else. That’s not a small wording issue. It creates confusion in forecasts, fundraising decks, and board updates.
ARR versus MRR
MRR is monthly recurring revenue. ARR is the annualised version of that recurring base. In many SaaS companies, ARR is simply MRR multiplied by 12.
But it isn’t always that neat. Annual contracts, discount periods, usage changes, and mid-month upgrades can distort the picture. So yes, MRR x 12 is a good shortcut, but only if your underlying MRR is defined properly in the first place.
ARR versus bookings and recognised revenue
Bookings are the value of signed contracts. Recognised revenue is what lands in the accounts over time under accounting rules. ARR is neither of those.
Take a £24,000 annual contract paid upfront. Bookings may show £24,000 on the day it is signed. Cash may also arrive upfront. Recognised revenue usually lands monthly across the year. ARR still reflects the recurring annual value of that subscription, assuming it fits your inclusion rules. Three different numbers, three different jobs.
A clean ARR policy that keeps everyone on the same page
The best SaaS businesses don’t argue about ARR every month. They write down the rules once, then stick to them.
Decide your inclusion rules once
Set the policy in plain English. Say what counts. Say what doesn’t. Decide how you handle upgrades, downgrades, discounts, churn, paused contracts, and annual prepayments.
Keep it simple enough that finance, sales, and leadership all calculate the same number. If two people can produce different ARR figures from the same data, the policy isn’t clear enough.
Use the same definition in every report
Your dashboard, investor update, board pack, and sales reporting should all use the same ARR logic. The presentation can change, but the underlying definition shouldn’t.
Once founders start changing the maths for different audiences, confidence drops. People may not say it out loud, but they notice. Consistency is part of credibility.
Check ARR against cash and churn
ARR is useful, but it isn’t the whole picture. A business can grow ARR and still have cash pressure. It can report a solid headline number whilst retention quietly worsens.
So compare ARR movement with cash collected, gross churn, net retention, and renewal performance. That is how you stop a good-looking metric from hiding a bad underlying trend.
Conclusion
A SaaS founder doesn’t need a clever ARR definition. They need a clear one that holds up in management meetings, investor conversations, and board packs.
When ARR is defined properly, decisions get better. Forecasts tighten up. Reporting becomes easier to trust. And growth looks like what it is, not what you hope it is.
Good SaaS finance is never about dressing numbers up. It’s about numbers you can stand behind.
Over 12 years across Big Four audit, investment banking and corporate advisory. Kishen works with UK SaaS and AI companies on financial strategy, fundraising and board-level CFO support. ICAEW regulated. Big Four trained. Based in London.