In this piece · 5 sections
Why SaaS gets a revenue multiple at all
Most online businesses are valued on what they earn. A content site or a store is priced on a multiple of its profit, because the cash it threw off last year is the cleanest read on what a buyer inherits. SaaS is the odd one out: it is routinely priced on a multiple of its recurring revenue instead — its MRR or ARR — even when the profit line is thin or negative.
The reason is the shape of the cash flow. When customers pay every month and most of them renew, next month's revenue is largely knowable today. A buyer is not purchasing a snapshot they have to recreate — they are purchasing a stream that keeps arriving. That predictability is what justifies pricing the revenue directly rather than waiting for it to show up as profit.
This is the narrow mechanic this post is about. For the bigger question of when a SaaS should be valued on revenue versus on owner earnings — the SDE-versus-revenue lens choice that governs small versus large software — read the full SaaS valuation guide. Here we assume the revenue-multiple lens already applies and dig into how the multiple itself is set.
MRR multiple vs ARR multiple — the same thing, scaled
The first confusion to clear up is that an MRR multiple and an ARR multiple are not two different methods. Annual Recurring Revenue is just Monthly Recurring Revenue times twelve, so the two multiples are the same valuation expressed at different scales. An MRR multiple is roughly the matching ARR multiple divided by twelve.
Worked the easy way: if a SaaS would trade at a 4x ARR multiple, that is the same as roughly a 48x MRR multiple — because a year of revenue is twelve months of it. Neither number is more correct; they are the same price wearing different labels.
Smaller, owner-run SaaS deals are often quoted as an MRR multiple because operators think in monthly run-rate. Larger and venture-scale deals are quoted as an ARR multiple because that is the language of growth-stage software. The danger is mixing them: a "4x" quoted as ARR and a "4x" assumed to be MRR are off by a factor of twelve. Always confirm which one a number refers to before you compare two listings.
Because they are interchangeable, the rest of this post talks in terms of "the multiple" without picking a side. Everything that pushes an ARR multiple up pushes the equivalent MRR multiple up by the same proportion. What actually matters is what moves it — which is the next section.
What drives the multiple up or down
Two SaaS businesses with identical MRR can carry very different multiples. The headline run-rate tells a buyer how big the stream is; a handful of operating metrics tell them how durable and how fast-growing it is — and durability plus growth is what they actually pay the premium for.
Churn and net revenue retention (NRR) are the first lever, and usually the biggest. Low churn means the stream you sell is the stream the buyer keeps. NRR above 100% — where existing customers expand faster than others cancel — means the business grows even with zero new sales, and that earns the steepest multiples. High churn does the reverse: it forces constant re-acquisition just to stand still, and buyers discount hard for it.
Growth rate is the second. A SaaS adding MRR quickly hands the buyer momentum they did not have to build, so it commands a higher multiple than a flat one at the same run-rate. Gross margin is the third — software margins should be high, and a product dragging heavy hosting, support, or third-party API costs through its cost of revenue is structurally weaker than a near-80–90%-margin peer.
Two quieter levers round it out. ARPU (average revenue per user) and the mix behind it tell a buyer whether the MRR rests on a few fragile whales or a broad base — a book of many small accounts is more durable than the same revenue from two. CAC payback — how many months of subscription it takes to earn back the cost of acquiring a customer — tests whether growth is even profitable. Fast payback supports the multiple; growth bought at a loss erodes it.
How a SaaS profile pulls the MRR multiple
Treat that chart as direction, not arithmetic. The point is the ordering: a clean, low-churn, growing SaaS sits at the top of its category's range, and a high-churn, slow, thin-margin one sits at the bottom — sometimes at a fraction of the multiple, on the very same MRR.
Two ways operators accidentally misread their own multiple
Before you apply a multiple to your MRR, two habits quietly distort the answer. Both are easy to fix, and both move the band more than most owners expect.
Both fixes point the same way: the multiple is only as trustworthy as the MRR and retention figures underneath it. Tighten those before you reach for a number, and the resulting band is one you can actually defend in a negotiation. For the cash-vs-profit definitions that sit alongside this, the SDE versus EBITDA explainer covers which earnings figure matters once a SaaS is large enough to be priced on profit too.
How to read the band you get back
Once the MRR is clean and the levers are scored, the output is not a single multiple — it is a range. That is deliberate. No automated estimate can know your private renewal contracts, a strategic buyer's premium, or how your churn cohort will age. The honest answer is a band, wider when the inputs are thin and tighter when they are verified.
Read the width as information, not noise. A SaaS with verified MRR, an exported retention curve, and documented operations earns a tighter, higher band. One with self-reported revenue, unknown churn, and a single-developer dependency earns a wide, low-confidence band — and that width tells you exactly which evidence to gather before you take it to market.
Real Site Worth builds the band this way on purpose. The qualitative signals are scored into deterministic inputs; the recurring-revenue, growth, margin, and retention figures feed a model that computes the range in code. The AI narrates which inputs are doing the heavy lifting — it never invents the figure. A number you cannot trace is a number a buyer discounts on sight.
For where real multiples actually sit by asset type and size in the current market, anchor against the website valuation multiples for 2026 rather than any single rule of thumb. And if your software is small and owner-run rather than revenue-led, the MRR multiple may not even be the right lens — the micro-SaaS valuation guide covers when SDE governs instead.
