How to Buy a SaaS Business

SaaS businesses — software tools with recurring subscription revenue — are among the most sought-after acquisition targets because of their predictable cash flow and high margins. This guide walks through every step of the acquisition process, from evaluating MRR and churn to auditing the codebase and completing the handover. See also: general website buying guide, the website valuation guide, and the due diligence guide.

1. 1

   Define your SaaS investment criteria

   Before searching, establish your criteria: target MRR range ($500–$5,000/month for micro-SaaS, $5,000–$30,000/month for small SaaS), maximum acceptable monthly churn rate (under 3% is the threshold most investors use), technical requirements (can you manage the product without a developer, or do you need to hire one?), and growth stage preference (stable cash-flowing tool vs. early-growth product). Being specific about criteria saves significant time when reviewing listings and prevents emotional over-bidding on a product that does not fit your skills.

2. 2

   Understand the key SaaS metrics

   SaaS businesses are evaluated on different metrics than content sites or eCommerce stores. The core metrics: MRR (Monthly Recurring Revenue) — the predictable subscription revenue baseline; monthly churn rate — the percentage of customers cancelling each month (under 2% is strong, over 5% is a serious concern); Net Revenue Retention (NRR) — whether existing customers expand or contract their spend over time; LTV:CAC ratio — lifetime value per customer divided by acquisition cost (3:1 or higher is healthy); ARPU — average revenue per user. Request a minimum of 12 months of all these metrics before evaluating any SaaS acquisition.

3. 3

   Find SaaS businesses for sale

   Browse active SaaS listings on Buy Sites Direct, where founders sell directly to buyers with no broker or commission fees. Filter for SaaS specifically and review listings by MRR, asking price, and growth trend. Focus on listings that provide monthly MRR, churn, and customer count data — transparent sellers with clean metrics make for smoother acquisitions. Listings without revenue data or those showing a recent MRR spike just before listing require extra scrutiny during due diligence.

4. 4

   Evaluate the product and business model

   Before going deeper, answer four questions: (1) Is the revenue truly recurring and contracted, or are customers on month-to-month plans that could cancel any time? (2) Is the product dependent on a third-party API, platform, or data source that could be deprecated or repriced? (3) What does the customer base look like — is MRR concentrated in one or two large customers, or distributed across many small ones? (4) Does the product have a moat — is it genuinely differentiated, or could a competitor replicate it cheaply? A SaaS business with concentrated MRR, no moat, and high API dependency is worth significantly less than headline metrics suggest.

5. 5

   Audit the codebase and technical infrastructure

   Even if you are not technical, hire a developer to review the codebase before making an offer. They should assess: the programming language and framework (is it modern and maintainable, or an obsolete stack that will be expensive to support?); security vulnerabilities (authentication, data handling, known CVEs in dependencies); hardcoded secrets or credentials in the repository; third-party service dependencies and their pricing model; hosting infrastructure and estimated monthly costs as the user base grows; and quality of existing documentation and test coverage. Budget $300–$1,000 for an independent code review — it is the single best way to avoid expensive surprises post-acquisition.

6. 6

   Conduct SaaS-specific due diligence

   Beyond standard revenue and traffic verification, SaaS due diligence requires additional checks: request customer-level MRR data (anonymised is acceptable) to verify churn figures; ask for cohort analysis showing how different customer cohorts retain over 12 months; verify integration and API dependencies are transferable to a new owner; check Terms of Service for any restrictions on assignment of customer contracts; confirm that payment processor accounts (Stripe, PayPal, etc.) can be transferred or have a migration path; and review all customer support tickets from the past 3 months to understand ongoing issues and feature requests. Also confirm whether the founding team holds any technical knowledge that is not documented and would be lost at handover.

7. 7

   Make an offer and negotiate deal terms

   Most SaaS businesses are priced at 2–5x Annual Recurring Revenue (ARR) or 40–60x monthly SDE. Price against the trailing 12-month average MRR, not a recent peak. If churn is above category average or MRR growth has stalled, negotiate a lower multiple. Consider asking for seller financing — a 60–70% upfront, remainder over 12–18 months structure is common in SaaS deals and aligns incentives for a good handover. Request a 30–60 day transition support period and a 30-day earnout provision tied to MRR retention post-close, especially for larger transactions.

8. 8

   Complete the SaaS handover

   SaaS handovers are more complex than domain-plus-content transfers. The full handover checklist includes: source code repository (GitHub, GitLab — confirm full ownership and access); hosting and infrastructure (AWS, GCP, Heroku, Render — account transfer or credential handover); domain name and DNS records; payment processor account (Stripe account transfer or new account with webhook migration); customer database; email marketing and transactional email platform; all third-party API keys and service accounts; legal business entity documents if doing an entity sale; and any customer contracts. Confirm access to every item before escrow releases funds. Allow 1–3 weeks for a full SaaS handover — it is longer than a content site transfer.