Due-diligence checklist for buying a small online business
What to check before you pay for a small SaaS, app, content site or online store. Work through it after the seller accepts your offer in principle and before money moves. Ask for live, read-only access wherever you can: screenshots are easy to fake.
free · plain English · last updated 2026-11-20
Revenue and money
The numbers in the listing are what the seller reports. Check them at the source.
- Read-only access to the payment provider (Stripe, Paddle, Lemon Squeezy, Gumroad, App Store Connect, Google Play Console, Shopify, an affiliate dashboard), or a live screen share where you choose what to click.
- Revenue month by month for the last 12 months (or since launch), not just the latest month.
- Refunds, chargebacks and failed payments over the same period.
- For subscriptions: MRR, number of paying customers, monthly churn and how many are on annual plans paid up front.
- How much of the revenue comes from the largest customer, and from the top five.
- Every running cost: hosting, databases, model or API bills, email tools, plugins, contractors, ads.
- How profit was worked out, and whether it includes paying the owner for their time.
- Payouts that match the revenue: deposits in the bank or payout reports from the provider.
- Sales tax or VAT: whether it is collected where it needs to be, and anything owed.
Traffic, users and audience
- Read-only access to analytics (Google Analytics, Plausible, Search Console) for at least 12 months.
- Where visitors come from: search, social, paid ads, one big referrer. One source doing most of the work is a risk.
- Any drop after a search engine update or a change of platform rules.
- Active users, signups per week and how many become paying customers.
- Email list size, how it was collected, and whether subscribers agreed to hear from the business (not from the person).
- Social accounts and communities: follower counts, and whether they can move to you.
- App store ratings and recent reviews; support tickets and common complaints.
Product and code
- A live demo, then a look at the code itself (a read-only invite to the repository).
- Who wrote the code: the seller, contractors or a template. Contractors’ work should be assigned to the seller in writing.
- Open-source licences of the main libraries, and any paid licences that need to be renewed in your name.
- How it is hosted and deployed, and whether you (or a developer you trust) can run it.
- Third-party services and API keys it depends on, and what each costs.
- Known bugs, outages and security incidents, and whether backups exist and restore.
- Customer data stored, where, and who can see it.
What transfers to you
Write the full list into the letter of intent so nothing is missing at handover.
- Domains and the registrar account (or a registrar-to-registrar transfer).
- Code repository, hosting and database accounts.
- App store listings, moved to your developer account through the store’s own transfer process.
- Payment provider: some accounts can’t change owner, so agree how customers move to yours.
- Email list, email-sending account and templates.
- Social accounts, communities and any newsletter platform.
- Content, designs, logos, trademarks and brand assets.
- Supplier, affiliate and partner agreements, which may need the other side’s consent.
- Stock, if any, and where it is stored.
Legal and risk
- The seller (or their company) actually owns everything being sold.
- No open disputes, claims, takedown notices or platform warnings.
- Terms of service and privacy policy exist and match how the product works.
- Personal data can lawfully move to a new owner (check the privacy policy and local rules).
- Any customer contracts that can’t be assigned without the customer agreeing.
- The business follows the rules of the platforms it depends on (app stores, marketplaces, ad networks).
The seller and the handover
- Why they are selling, in their own words.
- How many hours a week the business really takes, and on what.
- How long they will help after the sale (for example 30 days of answering questions) and how.
- Whether they will agree not to build a competing product for a period.
- Anything they plan to keep (a newsletter, a related product, a domain).
Red flags
Not proof of a problem, but stop and ask more questions if you see any of these.
- Only screenshots, and no live or read-only access to revenue or analytics.
- A revenue or traffic spike in the last month or two before the listing.
- Most revenue from one customer, one channel or one platform.
- Pressure to decide fast or to skip escrow.
- Requests to pay by gift card, crypto or a personal transfer outside escrow.
- Different numbers in different places (listing, call, dashboard).
Closing
- A signed letter of intent with price, what is included, the due-diligence period and handover.
- For the sale itself, an asset purchase agreement, reviewed by a lawyer.
- Payment through escrow, released only when you have checked each asset is yours.
- A handover checklist ticked off together: every account moved, passwords and two-factor changed, the seller’s access removed.
Questions
- How long does due diligence take on a small online business?
- For a business under $50,000, one to two weeks is common. Agree the period in the letter of intent so both sides know when it ends.
- Should I pay for due diligence help?
- For a few thousand dollars, most buyers do it themselves with a checklist like this one. For a larger deal, an accountant to check the numbers and a lawyer to review the agreement are worth the cost.
- Is this checklist legal or financial advice?
- No. It is a list of things to check, written in plain English. Have a lawyer or accountant review anything you are unsure about before you sign or pay.