Buying a Small SaaS Business: A Technical and Customer Due Diligence Workflow
SaaS acquisitionstechnical due diligencecustomer metricstransition planning

Buying a Small SaaS Business: A Technical and Customer Due Diligence Workflow

AAcquire Club Editorial Team
2026-11-16
8 min read

A reusable checklist for evaluating a small SaaS business across code, infrastructure, security, customers, metrics, and transition risk.

Buying a small SaaS business requires more than confirming recurring revenue. This reusable due diligence workflow shows what to request, test, and document across the product, infrastructure, security, customers, finances, and founder handover before you make an offer.

Overview

A small SaaS acquisition can look simple from the outside: a subscription product, a payment account, and a list of customers. In practice, the value may depend on undocumented code, one cloud account, a founder who handles every support request, or a retention problem hidden by new sales. The purpose of due diligence is to replace assumptions with evidence and to identify risks that should change the price, deal structure, or transition plan.

Work through the review in stages rather than requesting every possible document at once. Start with enough information to decide whether the opportunity deserves deeper investigation. Then test the technical and customer claims that support the seller's valuation. Finally, convert unresolved issues into conditions for closing, seller warranties, an earnout, a holdback, or a post-close task list. For broader context on valuation, see how to value an online business and compare the implications of different online business deal structures.

A practical evidence standard

For each important claim, classify the evidence as verified, partially verified, or unverified. A dashboard screenshot may support a revenue claim, but a direct read-only view or export is stronger. A seller's explanation of code ownership is useful context, but signed assignments and repository history are better evidence. Keep a diligence log with four columns: claim, evidence received, risk, and next action.

Do not treat every technical imperfection as a deal breaker. A small SaaS may have limited test coverage or informal documentation and still be a sound acquisition. The key questions are whether you understand the exposure, can operate the product after closing, and have priced the work and downside realistically.

Checklist by scenario

1. Initial screening: should you investigate further?

  • Request a clear description of the product, target customer, pricing plans, included assets, and reason for sale.
  • Reconcile reported revenue to payment-processor exports, invoices, or accounting records for a representative period.
  • Ask for monthly recurring revenue, annual recurring revenue, active customers, cancellations, refunds, and expenses using consistent definitions.
  • Identify the seller's weekly workload, including development, support, sales, operations, and vendor management.
  • Confirm that the proposed transaction includes the domain, brand assets, code, customer data, documentation, social accounts, analytics, and required contracts.
  • Check whether any customer, channel, employee, contractor, or vendor represents an unusual concentration risk.

At this stage, avoid relying on an attractive multiple without understanding what earnings actually include. A low-maintenance product with stable customers is materially different from a product that requires the founder to repair production issues every weekend.

2. Technical diligence: can you operate and improve the product?

Ask the seller to provide a technical inventory and a guided walkthrough. Your request list should include:

  • Repository URLs, branch structure, commit history, deployment process, test suite, and release notes.
  • Written confirmation that the seller or company owns the code, designs, documentation, and other transferred intellectual property.
  • All contributors, contractors, agencies, and employees who worked on the product, plus their agreements or intellectual-property assignments where applicable.
  • Application architecture, programming languages, frameworks, databases, background jobs, APIs, and integrations.
  • Infrastructure accounts, hosting configuration, domain registrar access, DNS, backups, monitoring, logging, and disaster-recovery procedures.
  • Dependency manifests and a list of major third-party services, licenses, versions, renewal dates, and account owners.
  • Recent uptime history, incident records, performance bottlenecks, open bugs, technical debt, and known security issues.
  • Local setup instructions that allow a new operator to run the application without undocumented founder knowledge.

Use a supervised, read-only review wherever possible. Confirm that a fresh environment can be created from the documented process, that backups can be restored, and that a deployment can be rolled back. Review secrets management carefully: credentials should not be embedded in source code, shared through personal accounts, or transferred in plain text. Before closing, rotate credentials and establish new ownership for critical services.

3. Security and dependency review

Match the review to the product's data and risk profile. Determine what customer information is collected, where it is stored, who can access it, and how accounts are deleted. Ask for the privacy policy, terms, data-processing agreements if used, security questionnaire responses, incident history, and any customer commitments that the buyer would inherit. These documents may need legal review; this checklist is not a substitute for it.

Review authentication, authorization boundaries, administrator access, multi-factor authentication, password-reset flows, logging, rate limits, encryption practices, and dependency update procedures. Pay special attention to AI APIs, payment integrations, email services, analytics tools, and other external systems that could change pricing, availability, data handling, or output quality. Verify that the business can continue if one critical provider changes its terms or becomes unavailable.

4. Customer and revenue diligence: are the subscriptions durable?

Request customer-level data in a privacy-conscious format, such as anonymized identifiers, signup date, plan, starting recurring revenue, current recurring revenue, cancellations, expansion, contraction, refunds, and last activity. Use it to calculate and reconcile the following:

  • Logo churn: the proportion of customers lost during a period.
  • Revenue churn: recurring revenue lost through cancellations or downgrades, ideally shown separately from expansion.
  • Net revenue retention: starting customer revenue plus expansion, minus contraction and churn, divided by starting revenue.
  • Cohort retention: how customers acquired in the same period remain active or generate revenue over time.
  • Average revenue per account: recurring revenue divided by the relevant customer count, with the calculation period stated.
  • Customer acquisition cost and payback: marketing and sales spend compared with the customers and gross profit it produces.

Definitions matter more than polished labels. Confirm the period, treatment of annual plans, pauses, failed payments, free users, trials, refunds, and one-time charges. Reconcile the result to the payment platform and general ledger. Read support conversations and cancellation reasons, then speak with a small, representative selection of customers with the seller's permission. Look for product gaps, promised features, undocumented discounts, and relationships tied primarily to the founder.

5. Pricing, support, and transition planning

Document each plan, feature gate, discount, grandfathered customer, trial rule, usage limit, and billing exception. Ask how often prices have changed and whether customers have received informal promises. Measure support volume by channel, response expectation, recurring issue, and time required from the founder. A product with modest revenue may still be attractive if support is predictable; it may be risky if one complex customer consumes most operating capacity.

Create a 30-, 60-, and 90-day handover plan. It should cover introductions to important customers and vendors, transfer of accounts, release procedures, incident response, financial reporting, support escalation, product roadmap context, and unresolved negotiations. Require the seller to record walkthroughs for tasks that are difficult to learn from written instructions. Include a defined availability period after closing, with scope and compensation agreed in the purchase documents.

Reusable request-list template

Send a version of this list after an initial conversation and mark every item as received, verified, or outstanding:

  1. Revenue and expense exports, customer and subscription data, refunds, failed payments, and tax records relevant to the transaction.
  2. Repository access, contributor agreements, architecture notes, dependency files, deployment instructions, and issue backlog.
  3. Hosting, domain, DNS, monitoring, backup, email, analytics, payment, support, and third-party service inventories.
  4. Security, privacy, incident, access-control, and data-retention documentation.
  5. Customer contracts, vendor agreements, licenses, complaints, refunds, and material support threads.
  6. Founder workload breakdown, operating procedures, roadmap, known risks, and proposed transition calendar.

What to double-check

Use a simple risk rating to keep the review proportional and actionable:

RatingMeaningBuyer response
LowEvidence is complete and the issue has a manageable effect on operations.Record it and include it in the handover plan.
MediumEvidence is incomplete, or the issue creates a meaningful but measurable cost or dependency.Request a test, mitigation, price adjustment, or contractual protection.
HighThe issue could threaten ownership, revenue continuity, security, or your ability to operate.Pause the deal until resolved, or walk away.

Double-check anything that changes the downside case: a single customer producing a large share of revenue, a payment account that cannot be transferred, code written by a contractor without clear rights, a domain or trademark conflict, undocumented infrastructure, or churn that rises in older cohorts. Also test whether reported profit excludes founder labor, essential software, refunds, taxes, or necessary development work.

Confirm the transfer mechanics before agreeing to close. Decide which legal entity, contracts, accounts, data, and intellectual property are included. Establish who controls the payment account during the transition, how customer notifications will work, and what happens if a key account cannot be assigned. A separate website acquisition due diligence checklist can help organize commercial and offer-stage questions.

Common mistakes

  • Accepting dashboard totals without reconciliation. Ask for underlying exports and explain every difference between analytics, billing, and accounting records.
  • Reviewing code but not ownership. Technical access does not prove that the seller can transfer all intellectual property.
  • Ignoring founder dependency. Quantify the hours and judgment required to support customers, deploy releases, and manage vendors.
  • Using one churn number. Separate logo churn, revenue churn, failed payments, voluntary cancellations, and cohort retention.
  • Testing only the happy path. Review cancellations, refunds, failed renewals, data exports, account deletion, outages, and restore procedures.
  • Leaving transition terms vague. Put access, introductions, documentation, availability, and post-close responsibilities in writing.
  • Letting urgency replace evidence. If a seller will not provide reasonable verification, treat that refusal as a risk rather than a reason to skip the check.

When to revisit

Revisit this workflow before signing a letter of intent, after receiving a major new data set, and immediately before closing. Recheck the core metrics if the diligence period crosses a billing cycle, renewal season, or material product release. Customer retention, payment failures, support volume, and infrastructure costs can change while a deal is being negotiated.

Update the checklist at least every six months and sooner when the product adopts a new cloud provider, AI service, payment platform, authentication method, or data workflow. Security expectations and vendor dependencies evolve, so an old review may not answer a new risk. Also revisit the transition plan after the first 30 days of ownership: compare actual support hours, incidents, churn, and cash collection with the assumptions used in your offer.

Next step: create a diligence folder, copy the request-list template, and assign every item an owner and due date. Do not make an offer based only on the seller's headline metrics. Build a short risk register, price the work required to reduce each material risk, and make your final decision only when the evidence, deal terms, and handover plan agree. For ongoing tracking after acquisition, use an online business acquisition KPI dashboard and compare actual performance with the assumptions documented before closing.

Related Topics

#SaaS acquisitions#technical due diligence#customer metrics#transition planning
A

Acquire Club Editorial Team

Editorial Team

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.