The mechanics of handing over AI-built software are the same everywhere: evidence out of the build, verification in a clean environment, a document the other side can check. What changes is who is standing on each side and what they stand to lose. These are the eight situations we see most, each with its own failure mode and its own version of the fix.
The solo builder's delivery: turning a fortnight of agent-assisted work into a handover a client pays for without a flicker of doubt.
A delivery standard across the whole team: every project closes the same way, every client gets the same proof, juniors can run it.
The successor does not need your opinions, they need your evidence: what ran, what was decided, and what nobody ever checked.
Buyers discount what they cannot verify. A passport turns due diligence from a trust exercise into a checkable artifact, and that moves price.
The codebase your company runs on was built at prompt speed. Day one for your engineer should start with a map, not archaeology.
Ending an engagement cleanly, from either side of it: a named record of what was delivered, verified, and left open.
The demo won the budget and now real engineers inherit it. What the prototype needs to carry with it to survive the promotion.
Six months from now you are the recipient. The cheapest handover you will ever do is the one to yourself, while the context still exists.