Built to be used.
Prepared to evolve.
Keep ownership, operating needs and future changes understandable after the launch moment.
A practical handover
Agree which source files, accounts, content tools and operating notes are included. Record who controls each service and its recurring costs.
Maintenance with boundaries
Updates, backups, monitoring and incident help can be scoped separately. Coverage, response arrangements and exclusions must be agreed before support starts.
A considered next release
Gather actual user feedback and operational needs. Prioritise the next improvement, review its dependencies and agree a new scope before building.