# Publish and hand off a client site

Keep the builder, the generated project, and the client’s hosting responsibilities clear.

Applies to Build 1.1.0. Updated September 15, 2026.

## 1. Keep the project source

1. Export the generated project’s source and keep a backup.
2. Extract it into a separate folder and read its README and package scripts.
3. Install its documented dependencies and run its build. Resolve actual errors before deployment.
4. Check that no private keys or credentials are committed in the project.

## 2. Choose the target account

Decide whether the site belongs in your agency’s hosting account or the client’s account. Check the generated project’s runtime requirements before choosing a host.

Use the project’s deployment instructions. Configure environment values privately in the hosting service, connect the domain, and verify HTTPS. There is no universal deployment command for every app Build can generate.

## 3. Test the published site

1. Open the public URL in a signed-out browser.
2. Check the main pages, navigation, mobile layout, and any restricted pages.
3. Submit a test form and verify its destination. Test payment flows in the appropriate test environment if the project uses payments.
4. Confirm approved content, contact details, and any privacy or consent flows needed by the site.
5. Check that updates can be deployed and the previous working version can be restored.

## 4. Give the client a clear handoff

1. Share the final site URL and the agreed access method.
2. Document who owns the domain, hosting, source repository, and connected services.
3. List ongoing costs and who pays them.
4. Record what was tested, any remaining work, and how to request updates.
5. Keep a source backup and the deployment instructions with the project.