Make the handover clear before development
Your project agreement should describe repository access, custom code, design assets, documentation and the accounts needed to operate the product. Record which components are third-party services or licensed dependencies, and who manages hosting, domain names and deployment access.
What to prepare for your project
Ask for an agreed handover checklist covering source code, configuration, account access, data exports and operating instructions. Confirm the responsibilities for ongoing maintenance alongside the initial build.