A system is not delivered when the demo works on localhost. It is delivered when another person can operate, recover, and extend it without tribal knowledge.
For institutional and local-business software, production handoff is part of the product. If deployment depends on undocumented manual steps, maintainability collapses on week two.
Define the operable unit
Before launch, write down the minimum operable unit: application code, environment variables, database migrations, storage, process manager, reverse proxy, backups, and logs.
Separate secrets from folklore
Credentials, keys, and environment differences should live in known places with known owners. A handoff document that says “ask me later” is not a handoff.
Make failure visible
Ensure operators know where logs are, how to restart services, and how to verify health after deploy. Rollback does not need to be glamorous—it needs to be rehearsed.
Day-one checklist
- Can a new operator deploy with the written steps alone?
- Are migrations and backups part of the release path?
- Is there a smoke test for the critical workflow?
- Are ownership and escalation contacts explicit?
- Can the system be restored from backup without guesswork?