Sitedropper Client Preview Handoff (Delivery)
A sequence with 7 steps: Confirm the client project is deployed through the Analyze, Build, Deploy pipeline.
By InnovaAI ResearchPublished Updated
What are the steps?
Sitedropper Client Preview Handoff (Delivery)
- 01
Confirm the client project is deployed through the Analyze, Build, Deploy pipeline
Open the project in the Sitedropper dashboard and verify the build completed to a live HTTPS URL. If the agent session dropped mid-pipeline, redeploy from the connected agent (Claude Code, Codex, Cursor, Antigravity, or Pi) or upload the project ZIP through the browser.
- 02
Leave visibility set to Draft
Draft is the default state on every deployment. Do not switch to Public until the client has signed off. This is the review gate that keeps an unfinished build off the open web.
- 03
Generate a password-protected preview link
From the sharing controls, select Password protected and set a password the client can pass to their own stakeholders. Send the URL and password in separate messages so the credential is not forwarded with the link.
- 04
Move to verified-email sharing when the reviewer list is known
Starter plans and above support private sharing by verified email. Replace the shared password with named reviewer emails once the client confirms who needs access, which removes the risk of a forwarded password reaching an unintended recipient.
- 05
Connect the client's own domain before the go-live review
Custom domain connection is available from the Starter plan upward. Point the domain at the project while it is still in Draft so the client reviews the final URL, not a temporary Sitedropper URL they will never see again.
- 06
Flip the project to Public and log the deployment
After written client approval, switch visibility to Public. Record the deployment date, the plan tier used, and the domain in the client's delivery notes so the next retainer cycle knows what is already live.
- 07
Hand off project controls to the client contact
Walk the client through renaming the project URL, regenerating the Sitedropper URL after a rename, and switching visibility themselves. Confirm they can reach the dashboard before you close the delivery ticket.
More on Sitedropper
- StrategySitedropper: Why Draft-First Deploys Change Agency Delivery Economics
- ConceptSitedropper Draft Gate
- Evaluation RuleSitedropper Rule: Adopt Only When Your Delivery Stack Runs on MCP-Connected AI Coding Agents
- Decision FrameworkSitedropper: Buy vs Skip for Agencies Shipping AI-Built Client Sites
- Failure PatternThe Sitedropper Draft Gate Trap: Why Agencies Fail When Every Client Preview Stays Unpublished
- Implementation BlueprintSitedropper Client Preview Pipeline (5-7 days)