Decision FrameworkDecision layer

Sitedropper: Buy vs Skip for Agencies Shipping AI-Built Client Sites

IF your delivery team already builds client sites inside Claude Code, Codex, Cursor, Antigravity, or Pi and needs a review gate before client sharing, THEN the Free tier ($0/month, up to 3 projects, 30 deployments per month) is enough to validate the Analyze, Build, Deploy pipeline on one real client project. IF you need custom domains, private sharing by verified email, or more than 30 deployments per month, THEN the decision moves to Starter at $2.5/month ($2.08/month annual) or higher, and the buy case rests on whether those client previews replace manual cloud setup you currently bill hours for. IF your clients work in traditional IDEs or non-MCP workflows, THEN skip, because the ZIP upload and REST API paths are the only fallback and the core value is agent integration.

By InnovaAI ResearchPublished Updated

Decision Frame

Sitedropper: Buy vs Skip for Agencies Shipping AI-Built Client Sites

IF your delivery team already builds client sites inside Claude Code, Codex, Cursor, Antigravity, or Pi and needs a review gate before client sharing, THEN the Free tier ($0/month, up to 3 projects, 30 deployments per month) is enough to validate the Analyze, Build, Deploy pipeline on one real client project. IF you need custom domains, private sharing by verified email, or more than 30 deployments per month, THEN the decision moves to Starter at $2.5/month ($2.08/month annual) or higher, and the buy case rests on whether those client previews replace manual cloud setup you currently bill hours for. IF your clients work in traditional IDEs or non-MCP workflows, THEN skip, because the ZIP upload and REST API paths are the only fallback and the core value is agent integration.

When is it the right choice?
  • Your agency already runs client builds inside at least one supported agent (Claude Code, Codex, Cursor, Antigravity, or Pi) and wants the workspace project pushed to a live HTTPS URL without configuring cloud infrastructure.
  • You need a Draft-first review gate: every deployment starts in Draft visibility, and password-protected or verified-email private sharing lets you collect client feedback before switching to public access.
  • Deployment volume per client stays under the Free tier's 30 deployments per month across up to 3 projects, so you can pilot on real client work at $0 before committing to Starter at $2.5/month.
  • You sell dev-focused retainers where a fast client preview URL shortens the feedback loop, and the Starter tier's custom domain connection ($2.5/month, or $2.08/month annual) is a line item you can absorb or rebill.
  • You want a productized entry offer: a single-page AI-built site deployed to a live Sitedropper HTTPS URL, with custom domain and password-protected staging, fits a fixed-fee local launch package.
When should you skip it?
  • Your clients build in traditional IDEs or non-MCP workflows, so the hosted MCP endpoint delivers nothing and you are left with ZIP uploads or REST API calls that any static host already handles.
  • You need horizontal resale across non-technical client verticals: the tight agent integration limits appeal beyond dev-focused retainers, and there is no white-label layer to put your agency's brand on the deployment.
  • Your monthly deployment volume across client projects exceeds what the tiers cover, and the per-project structure (3 projects on Free) forces plan upgrades before the workflow proves itself on retainer work.
  • You require infrastructure control (custom build steps, server-side runtimes, environment variables) that a Draft-to-public URL pipeline does not expose, making it a poor fit for complex client applications.
  • Your delivery model depends on clients owning their own hosting accounts and credentials, since routing deployments through Sitedropper adds a vendor in the middle of the client relationship.
ai-agents