Sitedropper Client Preview Pipeline (5-7 days)
Agencies deploy AI-built client sites to Draft HTTPS URLs through Sitedropper's hosted MCP endpoint, run a password-protected review gate, then flip to public or custom domain once the client signs off. Time: 5-7 days.
By InnovaAI ResearchPublished Updated
How do you implement it?
Sitedropper Client Preview Pipeline (5-7 days)
Agencies deploy AI-built client sites to Draft HTTPS URLs through Sitedropper's hosted MCP endpoint, run a password-protected review gate, then flip to public or custom domain once the client signs off.
- Sitedropper account created, with the Free tier (up to 3 projects, 30 deployments per month) sufficient for a pilot client
- At least one supported AI coding agent installed and authenticated: Claude Code, Codex, Cursor, Antigravity, or Pi
- A client web project already scaffolded inside that agent's workspace, ready for the Analyze, Build, Deploy pipeline
- Domain registrar access for the client if the Starter plan's custom domain connection will be used
- A named internal reviewer who owns the Draft-to-public approval decision
- 1.Register the Sitedropper account and connect the hosted MCP endpoint to one AI coding agent (Claude Code, Codex, Cursor, Antigravity, or Pi)
- 2.Run a throwaway project through Analyze, Build, Deploy to confirm a Draft HTTPS URL is returned
- 3.Record the deployment path and any agent-specific configuration quirks in an internal runbook
- 1.Select the first client project and deploy it from the agent workspace to a Sitedropper Draft URL
- 2.Verify the Draft visibility setting is active so nothing is publicly reachable yet
- 3.Capture the raw Draft URL for internal QA only
- 1.Switch the project to Password protected sharing and generate the client-facing preview link
- 2.Send the password-protected URL to the client with a structured feedback template
- 3.Log the client's first-round comments against the deployment record
- 1.Apply client revisions in the agent workspace and redeploy through the same MCP endpoint
- 2.Confirm the redeploy overwrites the existing Draft URL rather than consuming a new project slot
- 3.Reissue the password-protected link for round two
- 1.Move the client to the Starter plan ($2.5/month, or $2.08/month annual) once the project count or deployment volume approaches the Free tier ceiling of 3 projects and 30 deployments per month
- 2.Connect the client's own domain through the Starter custom domain option
- 3.Enable Private sharing by verified email if the client wants named-recipient access instead of a shared password
- 1.Flip the project from Draft to Public sharing after written client approval
- 2.Edit the Sitedropper URL slug to the client's preferred naming if the default is not presentable
- 3.Test the live HTTPS URL across desktop and mobile before announcing go-live
- 1.Hand off project controls to the client with a one-page guide covering Draft, Password protected, and Public modes
- 2.Document the ZIP upload and REST API fallback paths for any future non-agent deployments
- 3.Close the engagement with the deployment runbook archived for the next client
A single client deployment on the Free tier costs the agency $0 in tool spend, and the Starter plan at $2.5/month or $2.08/month annual is a rounding error against a retainer. The margin comes from the delivery model: the Local Launch offer is priced at $1,800 for 16h of setup, so the Sitedropper subscription is recovered on the first client and every subsequent deployment in that month runs at near-zero marginal tool cost.
- Live client site on a Sitedropper HTTPS URL with custom domain connected via the Starter plan
- Password-protected staging link used for the client review gate, archived with the feedback thread
- Deployment runbook covering the Analyze, Build, Deploy pipeline and the connected agent (Claude Code, Codex, Cursor, Antigravity, or Pi)
- Client handoff guide explaining Draft, Password protected, and Public sharing modes plus URL editing
- Fallback procedure for ZIP upload and REST API deployment when a project does not originate in a supported agent
The client's site resolves on its own domain over HTTPS from a Sitedropper deployment, the review gate has been passed in writing, and the client holds project controls with the runbook archived.
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
- Operating ProcedureSitedropper Client Preview Handoff (Delivery)