How to value a SaaS business (what your software or app is really worth)

Why SaaS is valued differently from a content or store

A content site is valued on traffic that converts to ad or affiliate income. An ecommerce store is valued on product margin and order volume. A SaaS business is valued on something more durable: recurring revenue that renews month after month with little extra effort. That recurring base is why software commands different — and usually higher — multiples than a comparable amount of one-off income, and it is why the valuation method itself changes.

The core distinction is predictability. When a customer pays every month, next month's revenue is mostly knowable today. A buyer is purchasing a stream they can forecast, not a snapshot they have to recreate from scratch. That predictability lowers perceived risk, and lower risk is exactly what pushes a multiple up.

Think about what a buyer is actually underwriting. For a content site, they inherit a search-ranking position that an algorithm update can erase overnight. For a store, they inherit inventory, suppliers, and ad accounts that need active steering.

For SaaS, they inherit a base of customers who have already decided to pay — and who, in a healthy business, keep paying without being re-sold every month. That signed-in, billed-monthly base is the closest thing the online-business world has to an annuity.

If you want the full cross-model picture first, start with our complete guide to website valuation, then come back here for the software-specific mechanics. The short version: every model is priced on the durability of its cash flow, and SaaS happens to score well on durability when its retention is strong.

ARR multiple or SDE multiple — pick the right lens

There are two dominant ways to value SaaS, and the right one depends on the business. Larger, growth-oriented SaaS is usually valued on a revenue multiple — a multiple applied to Annual Recurring Revenue (ARR) or its monthly cousin, Monthly Recurring Revenue (MRR). Small, owner-operated, and micro-SaaS businesses are usually valued on an SDE multiple, where Seller's Discretionary Earnings (the owner's true take-home profit) is multiplied by a market factor.

This split is not a Real Site Worth invention — it is how the brokers who actually close software deals operate. FE International, which advises on technology M&A, values most SaaS under roughly $5M on an SDE multiple and switches to earnings or revenue multiples for larger, faster-growing companies.

The threshold moves with the market, but the logic holds: small profitable tools are priced on the cash they throw off, big growth machines on the revenue they command.

The reason the lens changes is earnings. A venture-scale SaaS may reinvest everything into growth and show little or no profit, so an earnings multiple would understate it — the market prices its expansion instead, via a revenue multiple.

A profitable micro-SaaS, by contrast, throws off cash the owner actually keeps, so an earnings multiple captures its value cleanly. If you are unsure which profit figure applies to you, our SDE versus EBITDA explainer walks through the difference for small online businesses.

These lenses are not rivals so much as a continuum. As a SaaS grows from a one-person side project into a staffed company, the natural method shifts from SDE to EBITDA to a revenue multiple.

The crossover point is about whether earnings are clean and transferable, not a hard revenue threshold — which is why the next sections focus on the underlying signals rather than the headline number. Get the lens wrong and your estimate can be off by a factor of two, even before you touch a single growth or churn figure.

The metrics that actually move the multiple

Within either lens, the multiple itself is not fixed. A 2x ARR business and a 6x ARR business can sit in the same category — the gap is explained by a handful of operating metrics that buyers scrutinize. These are the levers that decide where in the range a given SaaS lands, and they matter far more than the raw revenue figure.

Growth rate is the first lever. A SaaS growing 60% year over year earns a steeper multiple than a flat one, because the buyer inherits momentum they did not have to build. Net revenue retention (NRR) and churn are the second. If existing customers expand faster than others cancel, NRR exceeds 100% and the business grows even without a single new sale. High churn does the opposite — it forces constant acquisition just to stand still, and buyers discount heavily for it.

Gross margin matters because software margins should be high. A SaaS dragging large hosting, support, or third-party API costs through its cost of revenue is structurally weaker than one running near 80–90% gross margin. CAC payback and the LTV:CAC ratio test whether growth is even profitable. If it costs more to acquire a customer than that customer is ever worth, scale destroys value rather than creating it — and a sharp buyer will spot that in the unit economics within minutes.

Those healthy zones are directional, not promises. They describe where a buyer relaxes versus where they start negotiating the price down. The numbers in your own business are what matter, and the further any one of them sits from its healthy zone, the more it drags on the multiple.

Two more levers round out the picture. The Rule of 40 says a healthy SaaS should have its growth rate plus its profit margin sum to at least 40 — a quick test of whether a business balances expansion against efficiency rather than buying growth it cannot afford.

SaaS Capital's research on the Rule of 40 for private SaaS companies found that businesses clearing the bar command higher revenue multiples than those that miss it.

Bessemer, which popularized the rule, has since refined it into a weighted version they call the Rule of X — the idea that for cloud companies, a point of growth is worth more than a point of margin, so the two should not be added one-for-one. For a small SaaS you do not need that precision, but the principle travels down-market: a buyer rewards growth and efficiency together, and punishes growth that is bought with cash you do not have.

The last lever is the quietest. Customer concentration is a silent killer: if one client accounts for most of the revenue, that revenue is not really recurring — it is one cancellation away from collapse, and buyers price that risk aggressively. A book of two hundred small customers is worth more than the same revenue from two large ones, because no single decision can sink it.

Open preview

How business size changes the method

Size is the single biggest reason two SaaS valuations use different math. At the small end — indie apps, solo-founder tools, a niche developer-tools or documentation-software app earning a few thousand dollars a month — the business is really the owner's labor plus a codebase. Its value tracks Seller's Discretionary Earnings, because what a buyer gets is the cash the owner currently takes home, adjusted for how dependent that cash is on the founder personally.

Take that developer-tools example concretely. A documentation-software micro-SaaS earning, say, a modest monthly profit (illustrative, not a broker quote) is bought for its loyal user base and its working code, not its growth story. The buyer wants to know two things: how much the founder really keeps after honest expenses, and how hard it would be to run the product without them. Everything else is secondary at that size.

Micro-SaaS in particular trades close to SDE multiples seen on marketplaces like Acquire.com, with the multiple bent up or down by churn, growth, and how transferable the operation is.

We go deep on that segment in the micro-SaaS valuation guide, and on the specific case of mobile and web apps in how much is my app worth. Both are part of this silo because the SDE lens dominates there in a way it never does for venture-scale software.

As revenue and team grow, the method climbs the ladder. Once a business has staff, documented processes, and earnings that no longer hinge on the founder's daily work, EBITDA becomes the cleaner lens.

And once growth is the headline story and profit is deliberately reinvested, the market stops pricing earnings altogether and prices the ARR stream directly. The same company can legitimately be valued three different ways across its life — the trick is matching the method to where it actually is today, not where you hope it will be next year.

Tech and team risk: the discount nobody lists on the P&L

Financial metrics describe the revenue. They say nothing about whether that revenue will survive a change of ownership — and that is where a surprising amount of value is won or lost. A SaaS can have flawless retention and still sell at a discount because the buyer cannot safely operate it after the founder leaves. This is the risk a calculator that only reads revenue will always miss.

Single-developer dependence is the classic example. If one person wrote, hosts, deploys, and supports the entire product, the codebase is effectively undocumented tribal knowledge. A buyer either pays the founder to stay or accepts the risk of a system they cannot maintain — both lower the price. The fix is mundane and valuable: written documentation, a clean deploy process, and a second pair of hands who understands the stack before the listing goes live.

Tech debt and transferability are the other half. A product built on abandoned frameworks, hard-coded credentials, or accounts tied to the founder's personal email is harder to hand over and riskier to run. Buyers do not just discount for what is broken — they discount for what is fragile. Clean, transferable infrastructure is a real, if invisible, line item in the valuation, and it is one of the few you can fix in the months before a sale rather than over years.

There is a simple test for all of this. Picture handing the buyer the keys on a Friday and going dark for a month. What breaks? If the answer is "nothing the docs do not cover," your transferability is strong and your multiple holds. If the answer is "the founder is the only person who can restart the server," expect that gap to show up as a real number in the offer.

Turning all of this into a range, not a guess

The problem with SaaS valuation is that every lever above interacts. A high growth rate offsets some churn; strong margins offset modest concentration; founder dependence claws back what clean financials add. Holding all of that in your head produces a gut number, and a gut number is the one thing a buyer will not pay for. The job is to turn each signal into a defined input and let the math combine them consistently.

That is exactly how Real Site Worth approaches it. The qualitative signals — category, transferability, founder dependence, brand strength — are scored into deterministic inputs.

The recurring-revenue figures, growth, margin, and retention feed a model that picks the right lens (SDE or revenue multiple) for the size and earnings profile, then bands the result. You can sanity-check any output against real sold comparables for web and software assets to see how the band sits against the market.

We are deliberate about one thing here: the AI never invents the number. The dollar range is computed in code from your inputs; the written explanation is the part that gets narrated. That order matters, because the failure mode of most "AI valuation" tools is a confident figure with no arithmetic behind it. A number you cannot trace is a number a buyer will discount on sight.

Confidence is part of the output for a reason. A SaaS with verified financials, clean retention data, and documented operations earns a tighter, higher-confidence band. One with self-reported revenue, unknown churn, and a single-developer dependency earns a wide, low-confidence band — and that width is itself useful information, because it tells you exactly which evidence to gather before you take the business to market.

Where to go from here

If your software is small and owner-run, the SDE lens governs — read the micro-SaaS and app guides and gather your true owner earnings. If it is growing and revenue-led, the ARR multiple governs — focus on growth, retention, and margin, because those are the levers that move it. Either way, the next step is the same: assemble the evidence, then read the range against real comparables rather than a single headline figure.

Be honest with yourself about which figures you can actually back up. "Roughly 4% monthly churn" from memory is worth far less in a negotiation than a churn cohort you can export. The work of tightening your own numbers before a sale usually pays for itself twice — once in a higher multiple, and again in a faster, cleaner due-diligence process that does not stall on questions you cannot answer.

Real Site Worth exists to make that first orientation fast and honest. It will not hand you a number to repeat to a broker — it will hand you a defensible range, a confidence score, and a clear view of which metrics are helping and which are holding you back. That is the difference between guessing what your software is worth and understanding it.