Key takeaway
Due diligence is the investigation a buyer carries out to confirm a business is what it appears to be. For online businesses it's largely a data exercise: every important figure in a listing should trace back to a source you can see yourself.
1. Financials
- [ ] Monthly profit and loss statements for at least 12 months, ideally 24.
- [ ] Revenue reconciled to payment-processor reports and bank deposits.
- [ ] Every expense listed, with invoices for large or recurring items.
- [ ] Add-backs (owner pay, one-off costs) explained and evidenced.
- [ ] Refunds, chargebacks and failed payments reviewed.
- [ ] Seasonality understood: compare the same months across years.
- [ ] Any outstanding liabilities, debts or disputes disclosed.
2. Revenue sources
- [ ] Share of revenue from each source (affiliate programmes, ad networks, subscriptions, sponsors, marketplaces).
- [ ] Largest customer, sponsor or programme and its share of revenue.
- [ ] Terms of each programme or contract, and whether they transfer to a new owner.
- [ ] Recent changes to commission rates, ad rates or prices.
3. Traffic and usage
- [ ] Read-only analytics access covering at least 12 months.
- [ ] Traffic by channel: organic search, direct, email, social, referral, paid.
- [ ] Search-console data: clicks, impressions, top queries and any manual actions.
- [ ] Traffic trend compared with the timing of known search-engine updates.
- [ ] For SaaS and apps: active users, retention by cohort, and sign-up sources.
- [ ] For newsletters: list growth, unsubscribes, opens and clicks, and consent records.
4. Operations
- [ ] Owner hours per week, and exactly what the owner does.
- [ ] Standard operating procedures for recurring tasks.
- [ ] Contractors and staff: roles, costs, agreements and whether they'll stay.
- [ ] Suppliers (ecommerce): terms, lead times, alternatives.
- [ ] Customer support volume and tools.
5. Assets and legal
- [ ] Domain ownership and registrar access.
- [ ] Ownership or licences for content, images, code and designs.
- [ ] Trademarks, if any, and whether they're registered.
- [ ] Terms of service and privacy policy, and compliance with the data-protection laws that apply to the customers.
- [ ] Customer contracts and whether they can be assigned.
- [ ] Any legal claims, takedown notices or platform warnings.
6. Technical (SaaS, AI and apps)
- [ ] Code review: structure, dependencies, security practices, tests and documentation.
- [ ] Infrastructure: hosting, costs, backups, monitoring and who holds admin access.
- [ ] Third-party services and APIs the product depends on, and their terms.
- [ ] For AI products: model providers, cost per request, fallback options, and rights to any training data.
- [ ] For apps: store console access, crash rates, policy status, and the store's transfer process.
7. Marketplace and platform accounts
- [ ] Account health for marketplaces, ad accounts and app stores.
- [ ] Whether each account can be transferred, or must be replaced.
- [ ] Reviews and ratings that move with the account.
How to score what you find
Mark each item Pass, Concern or Fail so you can compare it with the price. Use this table for the items that matter most.
| Check | Pass | Concern | Fail | How to verify |
|---|---|---|---|---|
| Revenue | Matches processor reports and bank deposits | Small unexplained gaps | Cannot be matched to deposits | Compare monthly totals from the processor with bank statements |
| Profit | Each cost has an invoice or statement | Some add-backs lack evidence | Add-backs that look like normal costs | Ask for receipts for every add-back |
| Traffic or usage | Read-only analytics for 12 months or more | Only screenshots offered | Refused access | Check the analytics account yourself |
| Ownership | Seller controls domain, accounts and code | Some assets sit with a contractor | Seller cannot prove ownership | Confirm at the registrar, platform and repository |
| Dependence | No source is more than half of revenue | One source is a large share | Hidden reliance on one source | Break revenue and traffic down by source |
| Handover | Written plan and support period | Informal promise | Seller refuses any transition | Put the plan in the agreement |
A single Fail on revenue, ownership or access is usually reason to stop. Concerns can often be solved with a price change or a contract term.
Extra checks by business type
- Content sites: top pages by traffic and what share of traffic they bring; whether articles were written in-house or by freelancers who can reclaim rights.
- Ecommerce: stock count and value, supplier terms, return rates and the channels sales come from.
- SaaS and apps: churn by cohort, hosting and third-party costs, store or platform policy status and a code review.
- Newsletters: list growth and unsubscribes, how subscribers consented, and whether the sending platform lets the list move.
- Marketplace accounts: whether the platform allows the account to change hands at all.
Red flags
- The seller only provides screenshots, or refuses read-only access.
- Revenue can't be matched to deposits.
- A sudden traffic or revenue spike just before listing.
- Unexplained add-backs that inflate profit.
- Heavy dependence on one source that the listing doesn't mention.
- Reluctance to agree a transition period.
How VALUERAQ verification fits in
Some listings on VALUERAQ show a verification status, which means our team has checked specific evidence, such as revenue against payment-processor records. Verification reduces risk but doesn't replace your own due diligence.
Frequently asked questions
How long does due diligence take?
For small websites, days to a couple of weeks. For SaaS or larger businesses with code reviews and legal checks, several weeks.
Should I pay for professional help?
For larger purchases, yes: an accountant for the financials, a lawyer for the agreement and a developer for technical checks cost little compared with the risk.
What is the most important single check?
Matching reported revenue to money that actually reached the bank. If the seller's figures do not tie to deposits, nothing else on the list can be trusted.
Do I need to check everything on a very small site?
Scale the depth to the price, but never skip revenue, ownership and access. Those three checks cost little and catch the largest problems.
What if the seller asks me to sign an NDA?
That's normal before sharing sensitive data. Read it carefully, and make sure it doesn't restrict you unreasonably if the deal doesn't go ahead.
Next step
Browse listings, then use this checklist before you make an offer.
Written by VALUERAQ Editorial Team. The VALUERAQ editorial team writes and maintains the platform's guides, methodology and glossary. Every guide is reviewed against the published methodology before publication and when the methodology changes.