Separate projects and their configuration
Use a distinct project for each client site. Give it a clear name and keep its required environment variables, integrations, and source location documented. That separation helps avoid applying an update or a credential to the wrong app.
When an agent operates several projects, include the client’s project name or live address in every deployment request. Ask it to resolve the existing project before updating it.
Review the actual experience with the client
A live review URL makes routes, navigation, and interactions available in context. Check the agreed flows before calling the work finished: contact submissions, product navigation, booking handoffs, and the mobile experience are common acceptance points.
Use templates to accelerate an appropriate starting point, then adapt the brand, content, and behavior to the brief. Distinguish an interactive demonstration from a production integration so a client knows what is ready and what needs configuration.
Leave a maintainable handoff
Record how to run the project locally, which source revision is live, how configuration is managed, and how future deployments should be made. Keep secrets out of the handoff document; name the supported credential flow instead.
Discuss required account access, workload permissions, and capacity with the client before production use. build.host is not promising agency-specific billing, an automatic ownership-transfer flow, or an SLA through this page.