Skip to content

Due diligence checklist for buying an online business

Indiemaker · Updated 17 November 2026

The short answer

A due diligence checklist for buying an online business covers five areas: financial, customer, technical, legal and operational. Confirm the revenue at its source, check the customers will stay, make sure you can run the code, establish that the seller owns what they are selling, and find out what only the seller knows how to do.

How should you use this due diligence checklist?

Work through it in order, between agreeing a price in principle and signing. This due diligence checklist is written for small online businesses: SaaS products, apps, stores, content sites and newsletters. Due diligence has one purpose, which is to confirm that what was described is what exists, while you can still change the price or walk away.

Start with the financial section, because nothing after it matters if the numbers do not hold. For each item, ask for evidence at the source, not a summary the seller prepared.

What is on the financial checklist?

You are confirming that the money is real, was actually collected, and that the profit figure is honest.

  • Twelve months of revenue, by month, seen in the payment provider itself on a live screen-share or through read-only access.
  • Payouts matched against bank statements for the same months.
  • Refunds, chargebacks and disputes by month.
  • Every running cost by month: hosting, tools, fees, contractors, advertising.
  • The seller's SDE calculation, with each add-back explained. Rebuild it yourself.
  • Any cost the seller calls optional that you would have to keep paying.
  • Unpaid bills, taxes owed, or money owed to customers, such as prepaid annual plans.

On Indiemaker, a listing marked Revenue Verified has its revenue confirmed through a connected payment provider. Figures a seller typed in are owner-declared. Either way, do your own checks. How to verify a seller's revenue gives the method.

What is on the customer and traffic checklist?

You are confirming that the income will still be there after the seller leaves.

  • Customer count by month, with new and cancelled customers shown separately.
  • Churn for each of the last twelve months.
  • The share of revenue from the five largest customers.
  • Where new customers come from, by channel, from the analytics account itself.
  • How much traffic depends on one search term, one platform or one partner.
  • Whether any channel depends on the seller's personal name or accounts.
  • Support volume and the most common complaints.
  • For content sites: traffic by page, and whether a few pages carry most of it.
  • For stores: repeat order rate, supplier terms, and whether suppliers will deal with you.

What is on the technical checklist?

You are confirming that you, or someone you hire, can run and change the product.

  • Access to the full code repository, with its history.
  • A fresh deployment from the repository to an account you control. If it cannot be done, find out why.
  • A list of every outside service the product uses, and the monthly cost of each.
  • How backups are taken, and proof that a restore has worked.
  • How secrets and keys are stored, and a plan to change them all on handover.
  • The age of the main frameworks and dependencies, and anything no longer supported.
  • Any changes made directly on the live system that are not in the repository.
  • For mobile apps: whether the app meets the store's own criteria for transfer.
  • For code built largely with AI tools: which tools, and whether anyone can explain how the code works.

If you cannot judge code yourself, pay an independent developer to review it.

What is on the legal checklist?

You are confirming that the seller owns each asset and is free to transfer it. This list tells you what to ask. It is not legal advice, and a lawyer should read the answers on any deal of size.

  • Who wrote the code, and a signed IP assignment from every contractor or co-founder who contributed.
  • The domain registration, showing the seller or their company as the owner.
  • Open-source licences in the dependencies, checked for terms that conflict with commercial use.
  • Customer terms and any larger contracts, read for clauses on transfer to a new owner.
  • Whether customer data may lawfully pass to you.
  • Any trademark on the product name, held by the seller or by someone else.
  • Any dispute, complaint or legal threat, past or present.
  • Whether a former partner, employee or investor has any claim on the business.
  • Whether the sale is of assets or of company shares, and what liabilities come with it.

What is on the operational checklist?

You are finding out what the seller does that is written down nowhere.

  • A week in the life: every regular task and how long it takes.
  • Written instructions for deployment, billing, support and the monthly routine.
  • A list of every account, who it is registered to, and how each one transfers.
  • What broke the last three times something broke, and how it was fixed.
  • Which tasks only the seller knows how to do.
  • How many hours of help the seller will give after the sale, and for how long.

If the written instructions do not exist, ask the seller to write them during diligence and make that a condition of the sale.

How deep should you go for the size of the deal?

Match the effort to the money. Every item above applies at any size. What changes is how hard you press on each.

What you are buying Where to spend most effort
A small project with little or no revenue Technical and legal: can you run it, and does the seller own it. See due diligence on a pre-revenue asset
A business with steady income in the tens of thousands Financial and customer checks at source, plus a paid code review
A six-figure purchase All five areas in full, a lawyer on the agreement, an accountant on the numbers. See due diligence for a $100,000 deal

What do you do with what you find?

Sort each finding into one of three piles.

  1. It ends the deal. Revenue that cannot be confirmed, an asset the seller does not own, a seller who refuses access they earlier agreed to.
  2. It changes the price. A cost that was left out, a customer about to leave, code that needs rework. Put a figure on it and reopen the price with the evidence.
  3. It goes in the agreement. Things the seller must fix, hand over or confirm in writing before or after completion.

If the business looks perfect, look again, and read red flags in a six-figure listing for the patterns worth a second look.

Checks reduce risk. They do not remove it. Keep the buyer's money in escrow until every asset on the schedule has moved, which is how payment and handover work on Indiemaker through Escrow.com.

Related: due-diligence, due-diligence-for-a-100k-deal, how-to-verify-a-sellers-revenue, red-flags-in-a-six-figure-listing

See what a business at this level is listed at.

Everything on sale between $50,000 and $150,000, on the same fields.