SaaS acquisition guide for careful buyers
Use this guide to evaluate SaaS businesses with a practical process for MRR quality, churn, customer concentration, code ownership, infrastructure, contracts, and transfer readiness.
A strong SaaS review looks beyond headline MRR.
Serious buyers need to understand how revenue is earned, how durable customers are, what the software requires to operate, and which obligations continue after closing.
SaaS review areas
Review the business in layers so price, proof, technical risk, and transfer work are visible before a transaction decision.
MRR quality
Review current MRR, expansion, contraction, failed payments, refunds, plan mix, payment processor exports, and whether revenue depends on a few customers or one sales channel.
Customer durability
Ask for churn context, cohort behavior, renewal patterns, support burden, customer concentration, and any commitments that would transfer to the buyer.
Technical ownership
Confirm repository access, deployment steps, infrastructure ownership, third-party services, license obligations, dependency health, and whether contractors assigned their work.
Operational handoff
Map billing, domains, cloud accounts, analytics, support inboxes, documentation, credentials, monitoring, and seller support expectations before closing.
Buyer process checklist
- Define the target profile: revenue range, customer type, technical stack, owner involvement, growth channel, and risk tolerance.
- Compare headline MRR with processor data, subscription exports, churn history, refunds, discounts, tax handling, and current active customer counts.
- Review product usage, support tickets, incident history, uptime expectations, roadmap obligations, and customer commitments that may affect post-close operations.
- Inspect code ownership, production access, deploy process, environment variables, domains, analytics, email, billing tools, and vendor dependencies.
- Write closing and transition terms around account transfer timing, seller support, customer communications, and unresolved technical or legal items.
Evidence to request and document
A useful review separates what the seller has shown from what still needs independent confirmation.
Revenue evidence
- Payment processor exports, subscription dashboard screenshots, MRR movement, refund history, active plans, and customer concentration notes.
- Cost context for hosting, support, contractors, tooling, affiliate payouts, chargebacks, taxes, and paid acquisition if applicable.
Product evidence
- Repository access, deployment notes, infrastructure diagrams, dependency lists, test or QA notes, incident history, and known technical debt.
- Usage analytics, activation paths, retention signals, support themes, feature requests, and product constraints that affect maintainability.
Transfer evidence
- Domain ownership, cloud accounts, email systems, billing ownership, analytics, support tools, third-party vendor terms, and access handoff sequence.
- Customer contracts, privacy obligations, data processing terms, contractor assignments, and written seller support expectations.
Frequently asked questions
What should buyers verify before acquiring a SaaS business?
Buyers should review MRR quality, churn, customer concentration, refund history, costs, code ownership, infrastructure, customer obligations, data handling, and the account transfer plan before deciding whether to proceed.
Is MRR enough to value a SaaS acquisition?
No. MRR is only one input. Buyers should also review retention, gross margin, growth channel quality, support load, technical debt, customer concentration, transfer risk, and seller support terms.
What SaaS assets usually need a handoff plan?
A handoff plan commonly covers source code, hosting, domains, billing, analytics, email, support tools, customer records, documentation, monitoring, and any third-party services needed to operate the product.
Does AppsVerified guarantee SaaS acquisition outcomes?
No. AppsVerified can organize listings, seller-provided artifacts, confidentiality controls, and transfer-focused resources, but buyers remain responsible for independent diligence and transaction decisions.