A SaaS company is the rare small business that gets valued less on what it earned last year than on what its revenue base will do next year without you. Buyers underwrite the subscription engine — retention, growth, and margin — before they look at anything else. We buy established Southern California businesses directly, and software founders come to us with the same question owners in every industry ask, but with a different answer: in SaaS, the metrics are the valuation. Here is how acquirers actually price a SaaS or software business, which buyer pays the premium, and what diligence will test.
What a SaaS Business Actually Sells For
There are two valuation regimes in SaaS, and knowing which one you are in changes everything about how you prepare. Smaller, owner-operated software businesses — typically bootstrapped, modest growth, founder doing support and sales — are usually priced like other small businesses: a multiple of SDE (seller’s discretionary earnings, meaning profit plus your compensation and personal add-backs), commonly in the low-to-mid single digits. Once a SaaS company shows meaningful scale, durable retention, and real growth, buyers switch to pricing it as a multiple of ARR (annual recurring revenue), because they are buying the revenue base itself, not just this year’s profit.
Where a given company lands on the ARR-multiple spectrum is driven by a short list of variables: growth rate, net revenue retention, gross margin, and how concentrated the customer base is. In our experience, two software companies with identical revenue can sell for wildly different numbers because one has revenue that compounds on its own and the other has revenue that quietly leaks. Before anyone else frames the number for you, get a grounded first read on your own figures with our business valuation calculator — then pressure-test it against the metrics below, because a SaaS buyer will.
The Metrics Buyers Underwrite Before They Talk Price
Every serious SaaS acquirer works from the same short dashboard, and they will rebuild it from your billing data rather than take your spreadsheet’s word for it.
ARR and MRR, cleanly calculated. Recurring revenue means contracted subscription revenue — not one-time implementation fees, not services, not month-to-month usage spikes annualized at their peak. Buyers strip non-recurring revenue out first, and sellers who blended it in lose credibility along with the revenue.
Net revenue retention (NRR). Of the customers you had a year ago, how much revenue do they generate today, after churn, downgrades, and expansion? NRR above 100% means your existing base grows without new sales — the single most valuable property a software business can have. Gross revenue retention (GRR), which excludes expansion, tells the buyer how leaky the bucket is underneath.
Churn, in logos and in dollars. Losing many small customers and losing one large one are different diseases, and buyers want to see both cuts. They will also look at cohorts: whether customers acquired two years ago retain better or worse than last year’s.
Gross margin and cost to serve. True software margins — after hosting, support, and any human-delivered service tucked into the subscription — separate a real SaaS business from an agency with a login page.
Efficiency of growth. CAC payback and the general shape of the growth-versus-profitability tradeoff (buyers often shorthand this as the Rule of 40: growth rate plus profit margin) tell an acquirer whether growth is bought or earned.
SDE, EBITDA, or ARR: Which Multiple Applies to You
Founders selling their software business often anchor on headline ARR multiples from venture-scale deals, and it costs them months of mispriced conversations. The honest sorting question is: what is the buyer actually buying? If the answer is a profitable, stable product that throws off cash and needs an operator, the deal will price on earnings — SDE for owner-operated companies, adjusted EBITDA once there is a management layer. If the answer is a compounding revenue base a larger company can pour into its own distribution, the deal prices on ARR, and profitability matters less than retention and growth.
For earnings-priced deals, the add-back schedule does heavy lifting. Your salary, one-time development pushes, personal expenses run through the company, and other discretionary items get added back to reconstruct what the business truly earns for its owner — and every line will be challenged in diligence. We walk through how that reconstruction works, and where sellers overreach, in our guide to SDE add-backs. Getting the add-back file documented before buyers arrive is one of the cheapest ways a software seller protects the price.
How Retention Moves the Price: An Illustration
The table below shows three illustrative SaaS companies, each with $2,000,000 in clean ARR, to make the point concrete. These figures illustrate patterns we see in the market; they are not a quote or a promise of value.
| Company A: Leaky | Company B: Stable | Company C: Compounding | |
|---|---|---|---|
| Net revenue retention | ~85% | ~100% | ~115% |
| Annual growth | Flat | ~15% | ~35% |
| Largest customer share of ARR | ~30% | ~12% | ~5% |
| Founder dependence | Founder is lead dev & sales | Small team, founder oversees | Team runs product & pipeline |
| Illustrative multiple | ~1.5–2x ARR | ~3x ARR | ~5x ARR or more |
| Illustrative enterprise value | ~$3–4M | ~$6M | ~$10M+ |
Same revenue, radically different outcomes. The spread between Company A and Company C is not the product — it is retention, growth efficiency, concentration, and founder dependence. All four are improvable in the one to two years before a sale, which is why the most profitable work a SaaS founder can do pre-exit usually happens in the metrics, not the codebase.
Who Buys SaaS Companies: The Strategic, the Financial, and the Micro-Acquirer
The strategic buyer is a larger software or industry company that wants your product, your customer relationships, or your niche — and can sell what you built through a distribution engine you could never afford. Strategics pay the premium when the fit is real, because they are buying acceleration, not just cash flow. The tradeoff: strategic processes run slower, involve more stakeholders, and sometimes end with your product absorbed rather than continued.
The financial buyer — private equity platforms and the growing field of SaaS-focused holdcos — buys the cash flow and the growth math. They care intensely about NRR, margin durability, and whether the business runs without you. Financial buyers are systematic and close reliably, but they price to a model, not to a dream.
The micro-acquirer and individual buyer dominate the smaller end — profitable products under roughly seven figures in ARR — often through direct outreach or marketplaces. These deals move fast but skew toward earnings-based pricing and heavier seller-financing asks.
Which buyer is right depends less on price than on what you want afterward: strategics for maximum value when fit exists, financial buyers for clean exits from durable businesses, and direct sales to a funded principal when speed and confidentiality matter more than running a broad auction.
What Diligence Looks Like When the Asset Is Software
SaaS diligence adds a technical layer on top of the financial one, and the failures are predictable.
IP ownership. Every line of code must be owned by the entity being sold. Contractor work without signed IP assignment agreements — especially early freelance work — is the single most common software deal defect, and it is fixable before a sale and expensive during one.
Open-source hygiene. Buyers scan the codebase for open-source components and check license compatibility. Permissively licensed libraries are routine; copyleft licenses in the wrong place become a negotiation.
Contracts and assignability. Customer agreements get read for assignment and change-of-control clauses, auto-renewal terms, and any bespoke promises sales made along the way. Data processing agreements and your privacy posture get the same treatment, particularly if you touch regulated or personal data.
Key-person and code risk. If one developer — often the founder — is the only person who understands the system, buyers price that as fragility. Documentation, a second engineer with real depth, and a sane deployment process all read as value.
The revenue rebuild. Expect the buyer to reconstruct MRR movements — new, expansion, contraction, churn — directly from billing-system exports and bank deposits. If your dashboard and your Stripe data disagree, the deal reprices to the Stripe data.
Getting Buyer-Ready: The Twelve Months Before You Sell
Most of the price improvement available to a software seller is operational, not technical. Start with metric hygiene: separate recurring from non-recurring revenue, rebuild your MRR history from source billing data, and know your NRR, GRR, and cohort behavior cold. Move month-to-month customers to annual agreements where you can — contracted revenue is worth more than habitual revenue. Reduce concentration by broadening the customer base or at least locking your largest accounts into term.
Then work the transferability file: confirm IP assignments from every contractor who ever touched the code, document the architecture and deployment process, get a second person genuinely capable in the codebase, and pull sales and support off your personal plate wherever possible. Finally, build the add-back schedule with receipts behind every line. A seller who arrives with clean metrics, clean IP, and a documented earnings story keeps control of the process; a seller who arrives with a dashboard and a shrug hands that control to the buyer’s diligence team.
Where to Start
If you are weighing a sale, start with an honest read of which valuation regime you are in and what your metrics say to a buyer who has seen a hundred of these — then decide whether a strategic process, a financial buyer, or a direct sale fits how you want to exit. We give Southern California software and SaaS founders a confidential, no-obligation answer in days, not quarters: bizselldirect.com/sell-your-business.
Frequently Asked Questions
How much can I sell my SaaS business for?
Smaller owner-operated software businesses typically sell on a low-to-mid single-digit multiple of SDE, while SaaS companies with durable retention and real growth price on a multiple of ARR — with net revenue retention, growth rate, gross margin, and customer concentration deciding where in the range you land. Two companies with identical revenue can sell for very different numbers, which is why the metrics file matters more than the headline revenue.
Do SaaS businesses sell on ARR or profit?
Both regimes exist, and the sorting question is what the buyer is buying. Profitable, stable products that need an operator price on earnings — SDE or adjusted EBITDA. Compounding revenue bases that a larger acquirer can accelerate price on ARR, where retention and growth matter more than current profitability. Anchoring on the wrong regime is the most common way software sellers misprice their own company.
What is a good net revenue retention for selling a SaaS company?
NRR at or above 100% means your existing customers generate as much or more revenue each year without any new sales, and buyers treat that as the strongest single signal in the business. NRR meaningfully below 100% does not make a company unsellable, but it shifts the conversation toward earnings-based pricing and shortens the multiple.
Who buys SaaS and software businesses?
Three main groups: strategic acquirers who want the product or customer base and pay premiums when fit is real; financial buyers — private equity and SaaS holdcos — who buy retention and cash flow systematically; and micro-acquirers or individuals at the smaller end, often through marketplaces or direct outreach. Which is right depends on your size, metrics, and what you want after close.
Can I sell my SaaS business if it is not profitable?
Yes, if the revenue base itself is the asset — strong retention, credible growth, and healthy gross margin can support an ARR-based sale even without bottom-line profit. What does not sell well is a business that is both unprofitable and leaking revenue, because neither valuation regime has anything to underwrite.
What will buyers diligence in a software acquisition?
Expect a rebuild of your MRR history from billing data, cohort and churn analysis, IP assignment verification for every contributor to the codebase, an open-source license scan, a read of customer contracts for assignability and change-of-control terms, a look at data privacy posture, and an assessment of how dependent the system is on you or a single engineer. Sellers who prepare these files in advance keep both the timeline and the price intact.
How long does it take to sell a SaaS business?
A brokered or banked process commonly runs nine to eighteen months from engagement to close, and strategic acquirers can add time with internal approvals. A direct sale to a funded principal can move from first conversation to an agreement in roughly 60 to 90 days, with technical diligence running in parallel rather than in sequence.
What happens to my team when I sell my software business?
In most acquisitions the buyer needs your engineers and support staff, because they hold the institutional knowledge that keeps the product running — and buyers frequently ask for retention arrangements for key technical people. Strategic acquirers sometimes consolidate roles over time, which is a fair question to ask any buyer directly before you choose one.