The delivery week, rewritten
The old model is familiar: a kickoff call, a moodboard, a template search, three revision rounds on a homepage that was never going to survive contact with real copy.
CloudSite starts from a generated first draft that already has structure — homepage, product detail, about, contact — written for the client’s actual product and market. The studio’s job shifts from construction to direction.
- Brief the generatorProduct, audience, tone, language. One project per client, isolated by slug.
- Direct, don’t draftEdit by chat: “warmer hero, move specs above the fold, add a dealer enquiry form.”
- Review on a linkShare a preview URL that expires in 24–72 hours — no staging logins for the client.
- Publish and hand overDeploy to Cloudflare Pages or Firebase, bind the client’s domain, deliver a clean project.
“We stopped quoting five days of build. The site is generated by lunch on day one; the rest of the week is positioning, photography and copy that actually closes.”
The economics of doing less
A five-page site used to mean template licensing, a page builder subscription and a developer hour for DNS. CloudSite folds all three into one workspace: generated pages, direct file access when you need precision, and domain binding that writes the DNS record for you.
Because every client project is independent, an agency can run twenty properties in parallel without a shared state to corrupt. Read-only tokens can be handed to a junior for QA; write tokens stay with the lead.