Buy the business. Control the system.
A technical route from the first inspection to the moment the seller can step away without taking part of production with them.
Start with the stage you are in
This page is the map, not a repeated master checklist. Each guide below answers a different question and hands the reader to the next stage.
- 01
Before you agree to buy
Map the production system, identify personal accounts and price the work needed to move them.
Technical due diligence before closing → - 02
Understand what control means
Separate possession of the repository from ownership of deployment, data, domains, recovery and revenue.
Why source code is not control → - 03
Run the transfer
Move the accounts in a deliberate order, preserve recovery routes and record every exception.
The transfer-day checklist → - 04
Verify after closing
Operate the business from buyer-owned accounts, remove residual access and close gaps with evidence.
Post-closing verification →
Keep the handover under control.
Assign owners and deadlines, distinguish seller claims from buyer tests, record evidence references and keep critical blockers visible until they are resolved.
What this guide does not decide
Technical verification does not replace legal, tax, security or financial advice. It gives the buyer a clearer record of which systems were checked, who controls them and what remains unresolved.