In short
Day 90. We hand over the keys, the instructions and the files. Your team already runs it. Nothing is held.
Hand-off is when the system becomes yours in fact, not just in the contract. The instruction files, the documentation, the code, the accounts, and the keys are transferred, and the people who will run it have already been running it alongside us.
It happens in every engagement, on day 90, at the end of the own month. Everything lives in your accounts from the start. That is deliberate. A company that can leave with everything has no reason to worry about staying.
Hand-off is possible because everything is files and the files were written to be read by someone who was not in the room. If a system cannot be handed off, it was not built right.
Example
What it looks like.
Hand-off checklist, day 90:- Instruction files reviewed with the operator, line by line.- Documentation current as of today.- Accounts transferred; our access removed.- One dry run with us watching and not touching.
Related
Read next.
- source filesWhat a design studio hands over when the work is done. Here: the instruction files, the documentation, the code, the repository, the keys. All yours, in your accounts.Read the definition
- documentationThe written record of how a system works. Here, the agent keeps it current, so the person who was not in the room can take over.Read the definition
- portabilityYour agents are files. They move to any harness, any model, any host. Leaving is copying a folder.Read the definition
- Ninety-day transformationA fixed three months, in and out. Build in month one, live by day 30. Adopt in month two. Own in month three, when we hand over the keys, the instructions and the files.Read the definition