Selling a subscription business is a different exercise from selling a one-time-purchase website — buyers are really acquiring a recurring revenue stream, so MRR, churn, and billing continuity carry the whole valuation. Here's how to document it, price it, and transfer it without disrupting a single paying customer.
Bottom line:Buyers price a SaaS product on recurring revenue quality, not just its current size — low churn and diversified customers matter more than a single big spike in MRR. List free on Siterifty with clean billing exports, and let escrow protect the sale through the subscriber migration.
A website sale is largely about a snapshot of value. A SaaS sale is about a stream — the buyer is betting on it continuing.
When someone buys a content website, they're mostly buying what already exists — traffic, content, domain authority. When someone buys a SaaS product, they're buying the expectation that current subscribers keep paying next month, and the month after. That makes the quality and durability of your recurring revenue — not just its current size — the central thing being priced.
Documenting MRR the way buyers trust
Export 6–12 months of billing history directly from Stripe, Paddle, or your processor — not a spreadsheet you compiled manually
Show active subscriber count over time, not just a current total
Break down revenue by plan tier if you have multiple pricing plans
Include cancellations/churn events in the same export period
Note any one-time spikes (annual plan renewals, a single large customer) that could misrepresent typical monthly performance
A direct processor export is worth far more to a buyer than a self-reported number — it's independently verifiable and reflects exactly what a buyer will see once they have access themselves.
Why churn matters more than raw MRR
Two products with identical current MRR can be worth very different amounts depending on how fast customers are leaving.
Monthly churn
What it implies
Buyer impact
Under 3%
Strong retention, product-market fit
Higher multiple — revenue is durable
3%–7%
Typical for many small SaaS products
Standard multiple range
Over 7%
Revenue base needs constant replacement
Lower multiple — buyer discounts for replacement cost
If your churn is on the higher side, be upfront about it and about what's driving it — buyers will calculate it themselves from your billing export regardless, and getting ahead of the number builds more trust than letting them discover it unexplained.
Valuing your SaaS product
Small SaaS products commonly sell for a multiple of ARR (annual recurring revenue) or a higher multiple of MRR, adjusted for churn, growth trend, and customer concentration. A product growing steadily with low churn and no single customer representing an outsized share of revenue sits at the top of typical ranges; a flat-or-declining product with high churn or one dominant customer sits at the bottom.
The buyer-side companion to this page — what buyers specifically evaluate before acquiring a SaaS product — is covered in the SaaS Acquisition Guide. Reading it from that angle will sharpen what you choose to document and highlight as a seller.
Transferring billing and subscribers
This is the step that determines whether existing customers experience a smooth handoff or a disruptive one.
Most processors (Stripe, Paddle) support migrating a customer and subscription list to a new account — check your processor's specific transfer/migration process
Plan the cutover for a low-activity period if possible, to minimize the chance of a billing hiccup affecting an active subscriber
Confirm with the buyer that existing subscriptions continue billing correctly post-migration before considering the sale complete
Decide whether the buyer inherits your support email/domain or transitions customers to new contact channels — communicate this clearly either way
Because subscriber migration has real technical risk and can't be easily undone, this is exactly the kind of multi-step handoff escrow is built for — payment stays secured until the buyer confirms billing is working correctly on their end.
The selling process, step by step
1
Export clean billing history
Pull 6–12 months of MRR, subscriber count, and churn directly from your processor.
2
List with the full financial picture
Create your listing with MRR, churn, and customer concentration disclosed upfront.
3
Price using ARR/MRR multiple, adjusted for churn
Anchor to typical ranges, then adjust for your specific retention and growth profile.
4
Field detailed financial questions
Serious SaaS buyers will ask granular questions about cohort retention and revenue concentration — have the data ready.
5
Buyer pays into escrow
Funds are held securely while the codebase and billing migration happen.
6
Migrate code, then billing/subscribers
Transfer the codebase first, then execute the subscriber/billing migration with your processor.
7
Escrow releases once billing is confirmed working
Once the buyer verifies subscriptions are billing correctly on their end, funds release to you.
Communicating the change to customers
Existing subscribers don't need to know the moment you list — but plan a short, honest note for around the time of transfer, reassuring them their subscription and service continue uninterrupted. A well-handled ownership transition is invisible to end users; a poorly handled one generates support tickets and cancellations right when the buyer is forming their first impression of the product they just bought.
Mistakes that spook SaaS buyers
Reporting revenue without a processor export. Self-reported numbers with no way to verify them are a common reason serious buyers walk away.
Hiding high churn instead of explaining it. Buyers calculate churn from the data regardless — an unexplained high number reads worse than a disclosed one with context.
One customer representing most of the revenue. If this applies to you, disclose it directly — buyers will find it in the data and price it in either way.
Migrating billing before payment clears escrow. Sequence this after funds are secured — a billing migration is hard to reverse cleanly.
FAQ
What multiple does a SaaS product sell for?
Commonly a multiple of ARR or MRR, adjusted for churn, growth trend, and customer concentration — low-churn, diversified-customer products sit at the higher end.
How do I document MRR for a buyer?
Export 6–12 months of billing history directly from your payment processor, showing revenue, subscriber count, and churn — not a self-compiled spreadsheet.
How does churn affect what my SaaS is worth?
Higher churn means the revenue base needs constant replacement, which reduces the multiple buyers are willing to pay relative to a low-churn product at the same MRR.
Can subscribers and billing be transferred to a new owner?
Yes — most processors support migrating a subscriber/billing list, though the process varies by provider. Confirm it's working before releasing funds from escrow.
Ready to sell your SaaS product?
Reach buyers evaluating recurring-revenue products specifically — every deal escrow-protected through the full migration.
This guide explains how to sell a SaaS (subscription) product online, distinct from selling a one-time-purchase website because buyers are pricing a recurring revenue stream. It covers documenting MRR using direct payment-processor exports (Stripe, Paddle) rather than self-reported numbers, why churn rate affects valuation more than raw MRR size, valuing a SaaS product on an ARR/MRR multiple adjusted for churn and customer concentration, transferring billing and subscriber migration safely between processor accounts, and communicating the ownership change to existing customers without disrupting service.
Siterifty is a marketplace for indie developers to buy and sell SaaS products, apps, websites, games, templates, and source code, with free listings and escrow protection covering both codebase and billing migration.
How to Sell a SaaS Product Online (2026 Guide) | Siterifty
