About
Business

SaaS Acquisition Due Diligence: What to Verify Before You Buy

A step-by-step due diligence guide for SaaS acquisitions, covering revenue verification, churn, tech stack, legal checks, and data protection.

SaaS Acquisition Due Diligence: What to Verify Before You Buy

Why Due Diligence Decides the Deal

Due diligence is the process of checking that a SaaS business is actually what the seller says it is before money changes hands. It is the stage where attractive listings either hold up to scrutiny or quietly fall apart. A thorough review will not always kill a deal; more often it adjusts the price, reshapes the terms, or surfaces conditions that protect you after closing. Skipping it, by contrast, is how buyers inherit problems they could have seen coming.

The mindset that serves you best is friendly scepticism. Assume the seller is honest but imperfect, and that some numbers are optimistic rather than deliberately false. Your job is to reconcile every important claim against independent evidence. Where the evidence confirms the story, you gain confidence. Where it does not, you have found a point worth negotiating. Good diligence is less about catching a liar and more about understanding exactly what you are buying.

Plan to work through the business in layers: the money first, then the customers, then the technology, and finally the legal and operational wrapper that holds it together. Each layer builds on the one before, and weaknesses in an early layer often explain anomalies in a later one.

Verifying Revenue and Financial Health

Revenue verification is the heart of SaaS diligence. Start by asking for direct access to the payment processor dashboard and, ideally, read-only access to the bank account or exported statements. Claimed monthly recurring revenue should reconcile against money that actually landed. Be alert to common distortions.

  • Trials counted as customers: free trials or heavily discounted plans inflating the paying-customer count.
  • Annual plans mishandled: a yearly payment booked as a single month's revenue, overstating the run rate.
  • One-off fees blended in: setup charges or consulting income mixed into recurring totals.
  • Refunds and chargebacks ignored: gross revenue shown without the deductions that reduce it.

Beyond the top line, examine the cost base. Hosting, third-party APIs, email providers, and payment fees all eat into margin, and some scale with usage in ways that surprise new owners. Ask for a simple month-by-month profit view over the trailing period so you can see trends rather than a single snapshot. A business that looks profitable on average but is sliding month to month tells a different story than one holding steady.

Assessing Customers, Churn, and Growth

Revenue only means something if the customers behind it are likely to stay. Request a breakdown of the subscriber base that shows how revenue is spread across accounts. If a small number of customers make up a large share of the total, their departure would hurt disproportionately, and you should understand how secure those relationships are.

Study churn carefully, both the rate and its pattern. Stable, low churn suggests a product people rely on. Churn that spikes around price changes or feature removals hints at fragility. Ask how new customers are acquired, and whether that channel is durable. A business that depends entirely on one traffic source, one affiliate, or the founder's personal audience carries a risk that a diversified acquirer would price down.

It is also worth speaking, where appropriate and permitted, with a sample of customers or reading support history. The tone of those interactions reveals whether the product is loved, tolerated, or resented. Satisfied customers who have been subscribed for a long time are among the strongest evidence that the revenue will survive a change of ownership.

On the technical side, review the codebase, infrastructure, and dependencies. You are looking for whether the product can be maintained by someone other than the current owner. Outdated frameworks, undocumented systems, and reliance on a single fragile integration all represent future costs. Confirm who owns the code, the domain, and the accounts the service runs on, and make sure every credential and asset is scheduled to transfer cleanly at closing.

Legal diligence covers the contracts and commitments that come with the business. Review the terms of service, any outstanding customer agreements, intellectual property ownership, and whether any third-party licences restrict a sale. Open disputes, unusual refund promises, or lifetime deals that commit you to perpetual service all belong on your list.

Data protection deserves focused attention, because a SaaS business is built on personal data. The subscriber, member, and follower records inside the product are personal data, and the law does not treat them as an inventory item that can be sold separately. They transfer only as part of the whole business being acquired, and once you own them you step into the seller's obligations: you must honour the consent each person gave and the privacy terms they were shown. Verify that the seller collected that data lawfully, that a clear privacy policy exists, and that there is a record of how consent was obtained, so you are not inheriting a liability dressed up as an asset.

Structuring Findings Into Terms

Diligence is only useful if it changes what you do. As you work, keep a running log of every issue, rating each by how serious and how certain it is. Minor, well-understood items can be noted and moved past. Serious or uncertain ones need a response before closing.

Those responses usually take one of a few shapes: a price reduction to reflect a risk, a holdback or earnout that ties part of the payment to the business performing as described, a warranty in which the seller formally stands behind a claim, or a condition that something be fixed or clarified before completion. A transition period, during which the seller remains available to hand over knowledge, is one of the most valuable terms you can secure, especially for an owner-dependent product.

Approached this way, due diligence stops being a hurdle and becomes the foundation of a fair deal. You end with a clear-eyed picture of the business, a price that matches its real condition, and protections for the risks you could not fully resolve. That is a far stronger position than trusting a listing and hoping for the best.

Frequently Asked Questions

What is the single most important thing to verify?

Revenue, verified against independent evidence rather than the seller's own spreadsheet. Reconcile claimed recurring revenue against payment processor records and bank deposits. If the money does not line up, nothing else in the valuation can be trusted.

How long should SaaS due diligence take?

It varies with the size and complexity of the business, but rushing is where buyers get hurt. Give yourself enough time to work through the financial, customer, technical, and legal layers properly. A seller who refuses any reasonable review period is itself a warning sign.

Do I need technical skills to assess the code?

Some technical understanding helps, and if you lack it you can bring in a developer to review the codebase and infrastructure. The key questions are whether the product can be maintained without the current owner and whether it rests on fragile dependencies. Those answers shape both the price and your post-sale risk.

What are my data-protection obligations after buying?

The subscriber and member data transfers only as part of the whole business, never as a standalone list, and you inherit the seller's duties toward those people. You must honour the consent they gave and the privacy terms they were shown. Confirm during diligence that the data was collected lawfully so you are not taking on a hidden liability.

Advertisement
A

Abhishek

Writer, Internet Marketing

Abhishek writes about digital marketing, advertising and growth — from paid media to content strategy for online businesses.

More in Business

View all

Keep up with the web & AI

New guides and analysis on SEO, e-commerce, domains and AI — every week.

Subscribe via RSS Browse all topics