Operating businesses
How to Sell a SaaS Business
The short answer
Smaller, profitable SaaS businesses are typically priced on a multiple of seller's discretionary earnings (SDE) or EBITDA, often somewhere between roughly 3.5 and 9 times depending on size, growth and how dependent the product is on the founder. Larger, faster-growing subscription businesses reinvesting most of their cash into growth are instead priced on a multiple of annual recurring revenue (ARR), and that multiple varies far more widely. Which basis applies, and where you land, comes down to a short list of metrics: net revenue retention, gross margin, growth rate, customer concentration and key-person risk.
Your numbers
The numbers
Step 1 of 3
Loading your calculator…
Prefer the dedicated tool? SaaS Business Valuation Calculator
ARR multiple or SDE multiple: which applies to you
Software businesses get valued one of two ways, and mixing them up leads to wildly wrong expectations. If your company is small, already profitable and growing steadily, buyers value it like most owner-run businesses: a multiple of SDE — profit with your own salary and personal expenses added back — or EBITDA once it is large enough to be run by someone else. That is the common path for bootstrapped, cash-flow-focused SaaS under a few million in revenue.
If your company is growing quickly, spending heavily on sales, marketing or product to fuel that growth, and therefore showing thin profit or a loss while revenue climbs, buyers price it on annual recurring revenue instead. ARR is simply subscription revenue restated on an annualised basis, used precisely because profit is not a meaningful number for a company deliberately trading earnings for growth.
There is no hard revenue line where one method switches to the other. A slow-growing $2M ARR business with healthy margins might be priced on SDE, while a $2M ARR business growing 100% a year will almost always be priced on ARR. The honest test is whether profit or growth is the point of the business today. Buyers price whichever one you are actually optimising for.
Knowing which applies before you talk to anyone matters, because the two are not comparable. A '6x' offer means something entirely different at 6x SDE of $200,000 versus 6x ARR of $2M, and owners anchored on the wrong reference point are often confused by early offers.
Net revenue retention and churn
Net revenue retention (NRR) measures how your existing customer base's revenue changes over a year — upgrades, downgrades and cancellations — excluding new customers. NRR above 100% means existing customers alone grow your revenue before you sell a single new subscription, which is among the strongest signals a buyer looks for, because growth does not depend entirely on refilling the funnel.
Churn is the flip side: the share of customers or revenue lost each month or year. A small business with low churn and steady expansion revenue can command a stronger multiple than a larger one growing only through expensive acquisition while quietly leaking customers out the back.
Buyers will ask for a cohort analysis — how customers who signed up in a given month behave over the following months and years. That tells them far more than a blended churn number, because it shows whether retention is improving, stable or deteriorating as the product matures.
If churn is elevated, understand why before going to market. Churn caused by a fixable issue, like a rough onboarding flow or a pricing tier that fits no one, is a very different conversation than churn that reflects a product that simply is not sticky.
Gross margin, CAC payback and growth rate
Gross margin is revenue minus the direct cost of delivering the software — mainly hosting, infrastructure and the support tied to serving customers. Healthy SaaS businesses run well above what you would see in a services business, and buyers treat a lower-than-expected margin as a flag worth investigating, since it can mean the product is expensive to run or that support costs are masking product problems.
CAC payback measures how many months of subscription revenue it takes to recover what you spent acquiring a customer. A shorter payback means you recycle marketing and sales spend faster, which reduces the cash needed to fund growth and lowers risk for a buyer financing that growth after closing.
Growth rate is the most visible number, but it is rarely judged alone. A business growing 40% a year while burning cash and losing customers is a riskier story than one growing 20% profitably with strong retention, even though it looks faster on paper.
Together these three show how efficiently the business converts spending into durable revenue, which predicts what it will be worth to a buyer far better than growth alone.
The Rule of 40, explained plainly
The Rule of 40 is a rule of thumb used mostly for ARR-priced businesses: add your annual growth rate to your profit margin, and if the total is 40 or more, the business is considered in healthy balance between growth and profitability. A company growing 30% with a 10% margin passes at exactly 40, as does one growing 50% while losing 10%, or one growing 5% at a 35% margin.
The point is not that 40 is magic, but that it stops buyers judging growth and profit in isolation. Burning cash to grow fast can be attractive if the growth is real and efficient, while a business barely growing needs strong profitability to be equally attractive. Falling well short on both — slow growth and losses — is the combination that worries buyers most.
For smaller SDE-priced software businesses the framework matters less directly, since they are judged on actual profit. Even there, showing a credible if modest growth rate alongside profit supports a stronger multiple than flat or declining revenue.
Customer concentration, contract length and billing
Concentration is how much revenue comes from your largest customers. If one represents 20% or more, most buyers will flag it, because losing that account after closing could badly damage the business and a new owner has little influence over a relationship they did not build. Reducing concentration, or at least documenting the strength and length of those relationships, is worth doing well before going to market.
Contract length and billing cadence matter more than owners expect. Customers on annual contracts paid upfront give a buyer far more revenue visibility and cash predictability than month-to-month billing that can be cancelled with little notice. Annual prepaid contracts are generally viewed as lower risk and can support a stronger multiple, all else equal.
If you have a mix, show the split clearly along with how renewal rates differ between the groups. A pattern where annual customers renew reliably while monthly customers churn quickly tells a buyer something useful about where to focus after the sale.
Code quality, technical debt and IP
Before closing, most buyers of any size run technical due diligence, where an outside engineer assesses the codebase for maintainability, security and how much unresolved technical debt exists. A codebase that is hard to work in, or built on outdated and unsupported technology, lowers confidence in what it will cost to keep the product competitive after the sale.
Intellectual property assignment is a related and often overlooked issue: every contractor, freelance developer or early co-founder who touched the code needs to have assigned their rights to the company in writing. A gap for even one contributor creates real doubt about what the company owns, and it is far harder to fix after a buyer finds it in diligence.
Open-source licensing deserves a specific look. Some licences require software built with them to be made available or licensed on particular terms, which can be a serious problem for a company selling proprietary software. An inventory of open-source components and their licence terms is a standard diligence request and is much better prepared in advance.
None of this means the codebase must be flawless. Buyers expect some technical debt in any real product. What they are assessing is whether it is understood, documented and manageable, rather than a surprise that could force a costly rebuild.
Key-person risk, contractors and deal structure
If you are the sole developer, the only person who understands the infrastructure, or the main face of sales and support, that concentration of knowledge is key-person risk — one of the most common reasons buyers reduce an offer or ask for a longer transition. Documenting processes, cross-training team members, and bringing on someone who can independently maintain the product all reduce it meaningfully.
If your team is mostly contractors, buyers want to know how likely they are to stay after a change of ownership and whether their agreements include IP assignment and confidentiality terms. Long-tenured, well-documented contractors are viewed as manageable; loosely arranged freelancers with no written agreements are a risk to be priced in.
On structure, cash at closing is rarely the whole story. An earnout, where part of the price is paid later contingent on hitting revenue or retention targets, is common when growth is central to the story, since it lets a buyer share the risk that growth continues. An escrow, where part of the price is held by a neutral third party for a period after closing, is common to cover breaches of the seller's representations, such as an undisclosed contract issue or an IP gap. Expect some combination on any deal above the smallest size, and know your walk-away price on the cash-at-closing portion alone before negotiating the rest.
A hypothetical example
Say a bootstrapped project-management tool has grown steadily to $900,000 of ARR with $340,000 of SDE, mostly monthly-billed customers, low concentration, and one solo founder-developer maintaining the codebase. Given modest growth and heavy reliance on that founder, it might attract roughly 3.5 to 4.5 times SDE — about $1.19M to $1.53M — with a buyer likely asking for a meaningful transition period. Now take a different company with $6M of ARR growing 55% year over year, net revenue retention of 118%, mostly annual prepaid contracts and a small engineering team beyond the founders. Because it is clearly priced for growth rather than current profit, buyers might value it at roughly 5 to 8 times ARR — about $30M to $48M — likely with an earnout tied to sustaining that growth. This example is illustrative only and is not a prediction for any specific business.
Multiple ranges reviewed September 2026. They are a guide, not a quote or a formal appraisal — see how the process works.
Common questions
Is a SaaS business valued on revenue or profit?
It depends. Smaller, profitable, slower-growing companies are valued on a multiple of SDE or EBITDA. Larger, fast-growing companies reinvesting in growth are valued on a multiple of ARR, since profit is not the point of the business yet.
What is a typical SaaS multiple?
Smaller profitable SaaS businesses commonly sell for roughly 3.5 to 9 times SDE or EBITDA depending on size, growth and founder dependence. ARR-priced companies see a much wider range driven by growth, retention and margin.
What is net revenue retention and why does it matter?
It measures how existing customers' revenue changes over a year, including upgrades and cancellations but excluding new customers. Above 100% means existing customers alone grow revenue, a strong sign the business does not depend on constant new acquisition.
What is the Rule of 40?
A rule of thumb where growth rate plus profit margin should total roughly 40 or more for a software business to be in healthy balance. It is used mainly for ARR-priced companies rather than smaller SDE-priced ones.
Does customer concentration hurt the price?
Yes. If one customer is a large share of revenue, buyers see real risk in losing an account they did not build. Reducing concentration before selling generally supports a stronger price.
Why do buyers care about open-source licences and IP assignment?
Some open-source licences require software built with them to be licensed on particular terms, which conflicts with selling proprietary software. Separately, every developer who worked on the code must have assigned rights to the company, or it may not fully own what it is selling.
What is an earnout, and will I have to accept one?
It is part of the price paid later, contingent on hitting agreed revenue or retention targets after closing. It is common in SaaS deals where growth is central to the valuation, since it shares the risk that growth continues.
How much does it matter if I'm the only developer?
A lot. Being the only person who understands the codebase is key-person risk, usually priced in through a lower offer or a longer transition. Documenting processes and involving others before selling reduces the concern.