SaaS Acquisition Checklist: Metrics, Churn, Revenue Quality, and Codebase Review

Overview

If you want a practical way to buy a SaaS business without getting trapped by surface-level metrics, start with four questions: Is the revenue real and durable? Do customers stay long enough to support the price? Is the product stable and maintainable? Can you operate the business after the founder exits?

That framing matters because SaaS valuation often compresses a lot of risk into a small set of headline numbers. Buyers naturally focus on monthly recurring revenue, annual recurring revenue, growth rate, seller’s discretionary earnings, and headline churn. Those are useful, but they are only the beginning of proper SaaS due diligence.

Recent buyer-focused market commentary from FE International points to a more active SaaS acquisition market, with transaction volume rising in 2025 and valuations in parts of the private market appearing more normalized than the public market. That is useful context, but it should not be mistaken for a shortcut. More deal flow does not reduce the need for discipline. In active markets, weak businesses can be packaged more cleanly, and hurried buyers can overpay for revenue that is less recurring than it looks.

A durable SaaS acquisition checklist usually covers six areas:

• Financial quality: recurring revenue, margins, add-backs, deferred revenue, and cash collection.
• Customer quality: logo churn, revenue churn, expansion revenue, concentration, and contract terms.
• Growth quality: channel mix, customer acquisition cost patterns, organic vs paid growth, and dependence on one channel or one integration.
• Product and technical quality: codebase health, infrastructure, security, documentation, deployment practices, and technical debt.
• Legal and operational quality: IP ownership, contractor agreements, compliance, transferability, and support burden.
• Transition quality: founder dependence, handoff needs, key employees, and first-100-day priorities.

If you are earlier in the buying process, it may help to pair this checklist with How to Buy a Small Online Business: Step-by-Step From Search to Close. If you are comparing multiples across asset types, Online Business Valuation Multiples by Business Type: SaaS, Ecommerce, Content, and Agencies adds context for pricing discipline.

One useful mindset: treat every SaaS listing as a claim set that needs verification. Sellers are not necessarily misleading you; they are presenting the business from the most favorable angle. Your job is to convert a listing into an operating reality.

Checklist by scenario

Use this section as a working checklist depending on the type of SaaS business you are evaluating. The core categories stay the same, but the order of importance changes by scenario.

Scenario 1: Buying a small bootstrapped SaaS from a founder

This is common in micro acquisitions and founder-to-founder deals. The product may be profitable, simple, and attractive precisely because it has been run lean. It may also rely heavily on one person.

• Verify revenue by source. Reconcile Stripe, Paddle, app marketplace payouts, bank statements, and accounting records. Make sure booked revenue matches collected cash where possible.
• Separate true recurring revenue from setup or services revenue. A software business with meaningful one-time onboarding or custom work should not be valued the same way as clean subscription revenue.
• Review churn by cohort, not only by month. A flat monthly churn figure can hide poor retention in recent customer cohorts.
• Measure concentration. Check what percentage of MRR comes from the top five customers, one pricing tier, one vertical, or one affiliate partner.
• Map founder dependence. Ask what the founder does weekly across support, sales, product decisions, bug triage, billing exceptions, and customer success.
• Review documentation. Look for onboarding docs, deployment steps, architecture notes, support macros, and product roadmaps. Thin documentation increases transition risk.
• Confirm IP ownership. Make sure code, designs, domains, and trademarks are assigned to the business and not sitting informally with freelancers or former collaborators.

Scenario 2: Buying a growth-stage SaaS with a team

At this stage, the risk shifts from pure founder dependence toward systems quality, management depth, and whether growth is efficient or artificially maintained.

• Check net revenue retention and expansion paths. Strong SaaS businesses are not only retaining accounts; they are expanding revenue through seats, usage, tier upgrades, or add-ons.
• Audit sales efficiency. Review pipeline stages, close rates, sales cycle length, CAC payback assumptions, and how much growth depends on paid acquisition.
• Assess team continuity. Identify key engineers, product owners, and account managers. Understand compensation, notice periods, and whether anyone is likely to leave after a sale.
• Inspect support and success load. If ticket volume is growing faster than revenue, margins may tighten post-close.
• Review infrastructure and scaling posture. Hosting costs, database performance, observability, and deployment reliability matter more once the business is larger.
• Test pricing durability. Ask when prices were last increased, what discounting is common, and how many accounts are on legacy plans.

Scenario 3: Buying a turnaround or under-managed SaaS

Some buyers specifically look for undervalued SaaS businesses with churn problems, weak onboarding, poor pricing, or neglected growth channels. These can work, but only if the problems are fixable and the purchase price reflects the cleanup.

• Diagnose the reason for churn. Is churn caused by low product-market fit, poor onboarding, weak customer support, bugs, pricing mismatch, or seasonal customer behavior?
• Identify fast operational wins. Look for obvious fixes such as billing cleanups, lifecycle emails, cancellation surveys, pricing page changes, or in-app onboarding improvements.
• Estimate remediation cost. Technical debt, overdue security upgrades, and migration work can absorb more capital than buyers expect.
• Stress-test the downside case. Model what happens if revenue drops for two or three quarters while improvements are implemented.
• Negotiate terms around uncertainty. When risk is harder to pin down, earn-outs, holdbacks, or seller transition commitments may be more useful than arguing only about headline valuation.

Scenario 4: Buying a product-led SaaS with strong self-serve growth

These businesses often look attractive because they scale with relatively lean teams. The key question is whether the apparent efficiency is durable.

• Review activation metrics. What percentage of signups reach first value? If top-of-funnel volume is high but activation is low, growth may be shallow.
• Check conversion by source. Traffic from SEO, product communities, integrations, affiliates, and paid search usually converts differently. A blended rate can hide weakness.
• Inspect trial-to-paid and freemium conversion patterns. Consistency matters more than one strong month.
• Examine usage concentration. If a small share of heavy users drives infrastructure cost or expansion revenue, margins and retention may be more fragile than they appear.
• Review analytics implementation. Product-led claims should be supported by credible event tracking, not rough estimates.

For buyers who also evaluate content-heavy software businesses, Content Website Valuation Guide: How Buyers Price SEO Traffic, Earnings, and Risk is useful when SEO is a major acquisition channel. And if you want a broader diligence template beyond SaaS, Website Due Diligence Checklist for Buyers: Revenue, Traffic, Ops, and Transfer Risks complements this article well.

What to double-check

This section covers the items that deserve a second pass before you sign a letter of intent, finalize a valuation range, or release funds into escrow. These are the areas where buyers most often discover that a “good business” and a “good acquisition” are not the same thing.

1. Churn definitions

Ask exactly how churn is being measured. Logo churn, gross revenue churn, and net revenue churn answer different questions. A seller may present the most flattering version without explaining the distinction. Also ask whether churn excludes annual plans that have not yet come up for renewal, paused accounts, failed payments, or involuntary churn from billing issues.

2. Revenue quality

Recurring revenue is not automatically high quality. Double-check:

• How much MRR comes from monthly vs annual plans
• Whether annual contracts are prepaid or invoiced
• How often customers receive discounts
• Whether there are refunds, credits, or chargebacks affecting net collections
• How much revenue depends on one-time setup, migration, or implementation fees
• Whether growth came from sustainable demand or a short-lived launch, partner promotion, or one enterprise contract

Revenue quality is one of the cleanest bridges between SaaS metrics for acquisition and actual valuation discipline.

3. Customer concentration and segment risk

A small SaaS business can look diversified because it has many customers. In reality, dependence can sit elsewhere: one industry, one geography, one integration, one sales partner, or one feature set. Look at concentration from multiple angles, not only by account count.

4. Codebase maintainability

You do not always need a full enterprise-grade technical audit for a smaller SaaS deal, but you do need confidence that the code can be maintained without heroic effort. Ask about:

• Frameworks and versions in use
• Test coverage and deployment process
• Error monitoring and incident history
• Third-party dependencies and abandoned packages
• Single points of failure in infrastructure
• Data backups and recovery procedures
• Security patch habits and access control

If the seller cannot clearly explain how releases happen, who has production access, and what breaks most often, treat that as a meaningful risk signal.

5. Founder lock-in

Many small software businesses are really a product plus a founder’s memory. Double-check how much tacit knowledge is needed to price enterprise deals, handle edge-case support requests, update integrations, close the books, or calm down large customers. The more the business depends on founder judgment, the longer and more structured the transition should be.

6. Add-backs and normalized earnings

If the valuation is earnings-based rather than revenue-based, review every add-back carefully. Some are legitimate one-offs. Others are recurring costs in disguise. Be cautious with aggressive normalizations around compensation, infrastructure, contractors, or growth spend that the business still needs to operate.

7. Transfer readiness

Before closing, confirm the practical details: domain access, source repositories, hosting accounts, billing processors, analytics, app store credentials, DNS, support tools, documentation, and customer communication plans. Transfer mistakes can create revenue disruption even when the business itself is sound.

Common mistakes

The most expensive SaaS acquisition errors usually come from moving too fast on familiar metrics. Here are the patterns worth avoiding.

• Overweighting MRR and underweighting retention. A growing SaaS can still be unhealthy if new sales are masking weak customer retention.
• Accepting blended metrics at face value. Blended churn, blended CAC, and blended conversion rates can hide sharp differences across plan tiers and customer segments.
• Ignoring billing friction. Failed payments, collections issues, or weak dunning systems can make reported recurring revenue look better than cash reality.
• Assuming code quality from product polish. A polished interface does not mean the underlying system is stable, secure, or easy to improve.
• Missing pricing debt. Legacy discounts, underpriced enterprise usage, and outdated plan structures can hurt future margins.
• Confusing a good product with a good handoff. A product can be attractive while still being difficult to transfer because of undocumented workflows, employee uncertainty, or founder dependence.
• Using public SaaS multiples as a shortcut. Public comps can offer context, but small private SaaS deals usually trade on a different mix of risk, liquidity, and buyer profile.
• Skipping downside modeling. Every buyer should model at least one case where growth slows, churn worsens, or transition takes longer than expected.

One practical way to avoid these mistakes is to keep a written investment memo, even for a small acquisition. Summarize what you believe, what you have verified, what remains uncertain, and what specific issues would change your price or terms. That memo becomes your guardrail when a competitive process or an enthusiastic seller starts to speed up the timeline.

When to revisit

This checklist is most useful when reused, not read once. Revisit it at the moments when inputs change and when your own assumptions are most likely to drift.

• Before making an initial offer: Use the checklist to decide what you still need before setting a valuation range.
• Before signing an LOI: Tighten the list to the few issues that most affect price, structure, and transition terms.
• During confirmatory due diligence: Re-check churn definitions, revenue reconciliation, codebase risks, and transfer assets.
• Before seasonal planning cycles: If you are buying based on trailing performance, revisit whether recent churn, renewals, or pipeline seasonality changes the picture.
• When workflows or tools change: A migration to a new billing platform, analytics stack, hosting provider, or support tool can alter the reliability of historic metrics.
• In the first 30 to 100 days after closing: Reuse the checklist as an operating plan. The same items that mattered in diligence usually become the first levers for stabilizing and growing the business.

As a final action step, create a one-page scorecard before your next SaaS deal. Rate each target from 1 to 5 on revenue quality, retention, concentration, codebase health, founder dependence, and transfer readiness. Add a notes column for unresolved issues and a pricing column for how each risk should affect the deal. That simple habit makes it easier to compare multiple listings across a website marketplace or SaaS acquisition marketplace without getting distracted by whichever seller has the cleanest deck.

If your goal is to buy a SaaS business that remains attractive after the founder leaves, your best protection is not a perfect benchmark. It is a repeatable process. Metrics tell you what the business has done. Due diligence tells you whether you can safely own what happens next.