How to Sell a SaaS: What Buyers Actually Pay For
To sell a SaaS, make its earnings believable, transferable, and independent of you before discussing a multiple. Buyers care less about the codebase than…
To sell a SaaS, make its earnings believable, transferable, and independent of you before discussing a multiple. Buyers care less about the codebase than retention, customer concentration, margins, operating workload, and whether revenue survives the handoff. ProvenStartups would refuse to estimate a sale price from MRR alone because the cited cases disclose operating results, not completed transaction prices.
Contents
The straight answer on SaaS valuation
There is no honest “real sale multiple” in the supplied cases because none discloses both a completed sale price and normalized profit. Revenue can establish scale, but it cannot establish what a buyer paid. Treat any multiple derived from these figures as invented, whether the listing appears on Acquire.com, MicroAcquire, or a private spreadsheet.
Wikipedia’s software-as-a-service entry defines the delivery model; it does not make recurring revenue equally valuable. A buyer still has to determine how durable that revenue is and what work is required to keep it.
The full matching cohort contains 229 projects, including 138 solo-run projects. Of 86 that publish a clean monthly figure, the median is $30K/mo across the full matching set, with a range from $6/mo to $2.2M/mo. The cohort’s recorded evidence split is 34 [V], 0 [F], 0 [C], and 0 [U].
That is useful market context, not a valuation formula. ProvenStartups separates the number from its source using its evidence grading method, because a verified operating result and a founder claim should not enter diligence with the same weight.
What buyers inspect before making an offer
Buyers want proof that cash flow will continue after the founder loses access to production. The strongest package connects bank deposits to billing exports, explains churn and acquisition, documents every recurring task, and exposes customer or platform dependencies. Clean code helps, but a transferable revenue engine is the asset being purchased.
Prepare these items first:
- ·Monthly revenue, refunds, fees, infrastructure costs, and owner add-backs tied to source documents.
- ·Customer-level retention, cohort behavior, contract terms, and concentration.
- ·Acquisition channels with spend, conversion, and founder labor separated.
- ·Architecture, deployment, credentials, third-party licenses, and incident history.
- ·A handoff plan showing which tasks remain manual and who can perform them.
Data Fetcher reports $23K/mo [F], 600 paying customers [F], and an 85% margin [F]. Those details are more informative than MRR alone because they begin to show breadth and economics, though they still do not disclose retention, concentration, or a sale price.
Use Stripe’s SaaS metrics reference to keep metric definitions consistent. If “MRR” includes setup fees, annual cash collected upfront, or services, restate it before a buyer does.
Revenue evidence is not a transaction comparable
The cases below compare operating signals, not acquisition multiples. They show why two products with impressive topline figures can deserve very different diligence. ProvenStartups would use them to frame questions, then require transaction price, normalized earnings, and deal terms before calling any case a genuine sale comparable.
| Case | Published operating evidence | Category / difficulty | What a buyer still needs |
|---|---|---|---|
| Letterly | $250K/mo [C] | Simple Tool, 2/5 | Retention, channel durability, profit |
| nano-banana.ai | ≈$115K/mo net profit for one month [C] | AI Website, 1/5 | Multi-month history, dependency risk |
| StoryShort.ai | $35K/mo across three apps [F] | AI Website, 3/5 | Per-product accounts and churn |
| Revid (rabbit) | $600K+/mo [F] | SaaS, 4/5 | Normalized profit and owner workload |
The distinction matters. Selling Shovels in the OpenClaw Ecosystem reached $40K in subscriptions in two weeks [C]. That proves rapid demand, not durable retention. Social Wizard + Clean Eats reports $1.5M across both apps in 12 months [F] and 90%+ margin [F], but combined reporting prevents a buyer from valuing either app cleanly.
Use the full ProvenStartups index to find operating references, then label them correctly. A revenue case becomes a sale comparable only when the consideration, earnings basis, included assets, financing, earn-outs, and closing status are known.
Where popular SaaS exit advice fails
Popular advice says recurring revenue plus a marketplace multiple produces a realistic asking price. ProvenStartups’ data contradicts that shortcut: the cohort supplies abundant revenue evidence but no disclosed completed-sale pair from which to calculate a defensible multiple. Revenue proof and transaction proof are different datasets, and pretending otherwise manufactures precision.
Even scale does not close the gap. Outrank is pushing toward $1M/mo [F], while AEO Service reports a $2,000/mo retainer from one client [F]. The first raises questions about profit and growth durability; the second exposes obvious customer concentration. Neither figure reveals a buyer’s price.
The site-wide pattern reinforces the warning. ProvenStartups indexes 406 graded ideas, including 266 software/SaaS products and 38 cautionary tales. Its evidence pool contains 57 third-party verified [V], 184 founder-reported [F], 121 creator-relayed [C], and 44 unverified [U]. A polished listing cannot upgrade weak evidence.
How to prepare and sell a SaaS
Run the sale like a reproducible deployment: freeze definitions, assemble evidence, remove founder-only dependencies, then invite offers against the same data room. Do not choose a price first and reverse-engineer support. A serious buyer should be able to reproduce revenue, costs, retention, and operations without relying on your narration.
- 1.Normalize the accounts. Reconcile billing, bank, refunds, taxes, contractors, hosting, and discretionary expenses month by month.
- 2.Build the diligence trail. Export customer and subscription data, preserve invoices, and write a metric dictionary.
- 3.Reduce key-person risk. Move secrets, domains, vendor accounts, support procedures, and deployments into transferable systems.
- 4.Disclose fragility early. Identify platform dependence, licensed models, single-channel acquisition, concentration, security issues, and unresolved claims.
- 5.Set process terms. Define included assets, cash treatment, transition support, exclusivity, financing, earn-outs, and the evidence required before closing.
Investopedia’s exit strategy overview provides the broader planning context. For the mechanics around valuation, agreements, and transfer, use the SBA’s guide to selling a business and qualified legal and tax advisers.
Do not hide mixed businesses inside one headline. Buyers would need separate books for each product, just as they would for a portfolio. If the numbers cannot be separated, expect uncertainty to be treated as risk rather than upside.
FAQ
The short answers are consistent: prove the earnings, disclose the dependencies, and do not present a revenue case as a sale comparable. A marketplace can introduce buyers, but it cannot repair ambiguous metrics or founder-dependent operations. The best preparation makes every material claim reproducible from records.
Where can I sell a SaaS?
Acquire.com, the MicroAcquire search term, brokers, and direct outreach can all surface potential buyers. The channel matters less than buyer fit and process discipline. Use the same evidence pack for every bidder, protect sensitive data in stages, and compare deal structure rather than headline price alone.
What multiple should I use to sell my SaaS?
No specific multiple is supported by this dataset. The cited cases publish operating figures but not the completed price-plus-normalized-profit pairs needed to calculate real transaction multiples. Refuse false precision. Establish maintainable earnings, risk, growth quality, required labor, and deal terms, then compare actual offers on the same basis.
Can a solo founder sell a SaaS?
Yes, but transferability is the test. The cohort includes 138 solo-run projects, so solo operation is common, not disqualifying. Document support, deployment, sales, billing, and vendor relationships so the buyer is not purchasing an undocumented job that only the founder knows how to perform.
How much revenue is enough before selling?
There is no supported threshold. Site-wide, 106 cases publish a clean monthly figure: 8 are under $1K/mo, 18 are $1K–10K/mo, 54 are $10K–100K/mo, and 26 exceed $100K/mo. Those bands describe observed projects, not sale eligibility; evidence quality and buyer fit still control.
Does AI-generated code make a SaaS harder to sell?
Not by itself. Across ProvenStartups, 211 distinct projects mention at least one AI coding tool, but buyers still need ownership clarity, maintainability, security, tests, and a reliable deployment path. The relevant question is whether another operator can safely understand and run the system, not which editor produced the first commit.