Using AI to build client websites: the 3-day site in 3 hours

The build really did collapse. A small business landing page that took a day and a half of drafting and layout now comes out of a prompt in under an hour, good enough to put in front of a client. That part of the promise holds.

A client project was never just the build. It was the brief, the decisions the client had not made yet, the copy that arrived late, two rounds of revisions, publishing, the domain and the handover. None of those got ten times faster.

So "three days to three hours" is a shape, not a measurement. Three hours is a real number for a real case: one page, content supplied, design decisions made, domain already delegated, the agent connection authorized weeks ago. It is not the number for the project in front of you today.

Where the three days actually went

Three days was rarely three calendar days. It was three working days of billable attention spread across two or three weeks of waiting:

• Brief and decisions. Two or three hours, plus the calendar time a client takes to decide what the page is for.
• Collecting content. An hour or two chasing copy, photos, a usable logo and permission to use any of it. Days of waiting.
• Structure and first copy pass. Three or four hours.
• Design and build. Eight to ten hours. The leg everyone is talking about.
• Revision rounds. Three or four hours, stretched across a week of replies.
• Publishing. An hour or two, more if the host wants a repository and a build command the page never needed.
• Domain and HTTPS. Half an hour of work, then waiting that is not yours to control.
• Handover. An hour or two on who owns what, where enquiries go, and what happens when the client wants a word changed.
• The edits afterwards. Recurring, unbilled, never in the estimate.

Twenty to twenty-seven hours. That is where "three days" came from, and design and build was the largest single block at under half the job.

The 10× is real, and it lands on one leg

Take that eight-to-ten hour block. Give a coding agent a clear brief, a colour palette and the client's copy, and you get a complete responsive landing page in well under an hour, including the passes where you say the hero is too tall.

That is the most reliable thing anyone can currently say about using AI to build client websites. The drafting leg fell by roughly an order of magnitude, hardest where freelance work is densest: small commercial sites, landing pages, portfolios, one-page brochures.

What made it possible was not a better website builder. A description in plain language became a viable input, so your brief is now the build instruction. The trouble starts one line later, when that shift gets applied to the stages above and below it.

What a 10× on 40% of the job does to the total

Run the numbers. Call the project twenty-four working hours, with design and build at nine of them, a bit under forty percent. Make that leg ten times faster and it becomes one hour, so twenty-four hours becomes sixteen. Not ten times faster. About one and a half.

A tenfold improvement on forty percent of the work cannot produce a tenfold improvement overall, and no amount of better prompting changes that. Once the build is down to an hour, making it thirty minutes buys you thirty minutes. The remaining fifteen hours are waiting on people, on files, on approval and on the publishing steps at the end.

So the honest headline: the three-day site now takes about two days, and the way to reach three hours is not to speed up the build again. It is to delete stages that were never about building.

The stage nobody puts a number on

Easy to check, because the pages selling the speed are all still online.

WordPress.com's AI Website Builder for Agencies promises "fully-designed, content-ready websites in seconds" and offers to "save hours on repetitive site setups." The single numeric figure in the post is "30 free prompts." How many hours, out of how many, is never stated.

Straydog Branding's guide to how creative agencies use AI for client websites says AI "dramatically speeds up the concept phase," and its own FAQ asks whether AI tools reduce agency costs and answers that they "can reduce production time and streamline workflows." Across fifteen hundred words there is not one hour, percentage or before-and-after.

The most useful piece admits the least speed. Rosanna Bossom's post on how she uses AI in her website design business lists briefs, brainstorming, content repurposing, cleaning spreadsheets and transcription, then draws a line: "I personally DON'T use any AI tools in my actual design or website set up process right now; I design my client websites from scratch on Squarespace." A LinkedIn piece by Mark Hinkle sums up in the same spirit: AI will not build your entire website from one prompt.

None of these are dishonest. They are all measuring the same leg, in adverbs, and none follows the project to the end.

The last mile is where the days still hide

Look again at the fifteen hours that survived. Much of it is not craft, it is logistics, and it is why a finished folder of files is not a delivered project.

Publishing. The files exist and nobody can open them. Most hosting was designed for applications, so the shortest published route to a public address starts with a repository and a build configuration a landing page does not have. That is the argument behind vibe deployment. And if the site currently lives inside a chat, a published artifact is a link on someone else's domain, not a site your client owns.

The domain. Half an hour of work, then a wait that belongs to the internet. DNS records carry a TTL, and you are waiting for the old answer to expire from other people's caches. Squarespace tells customers 24 to 48 hours; GoDaddy says a few minutes to several hours. The mechanism is in connecting a custom domain in one record. No model will ever compress this stage.

The edits that come later. A client will ask for a changed phone number three weeks after sign-off. Five minutes or an afternoon depends on whether your host lets you change one file on a live site or expects you to republish the lot.

The handover. Who owns the domain. Where the enquiry form sends submissions. Whose payment account is behind the buy button. Who makes the next change. This stage did not shrink at all, and pretending otherwise is how freelancers end up doing unpaid support for two years.

What a three-hour client site actually requires

The headline is achievable and conditional, and the conditions separate the demo from your Tuesday.

• It is one page, or a very short site.
• The client supplied the copy and the images, and has the rights to them.
• The design decisions are made before the first prompt: colour, tone, what the page is for.
• The address is the platform's, or a domain already delegated and resolving.
• Your agent is already connected and authorized. A one-time step, so counting it in every project is counting it wrong.
• There is no enquiry form, no checkout, nothing behind the page.

The page still needs a coherent commercial sequence, and our review of five one-page website examples shows how offer, proof, objections and one next action share a URL without turning the scroll into an archive.

Meet all six and three hours is not optimistic. Miss two and you are back to a week of calendar, most of it waiting for someone else.

What still takes days, and always will

The stages AI has not touched are not technical, which is why no tool announcement will fix them.

Client decisions take as long as the client takes. Content is still the commonest reason a site sits unfinished. Approval rounds run at the speed of email, and a round is shorter when the client answers on the page itself rather than in a thread of replies. If the domain needs its nameservers changed rather than a record added, the wait is genuinely slow and always was.

Most things with a backend, a checkout or a login, are still real work with real consequences. A working enquiry form is the one exception: Birta receives those directly now, with no separate service to wire up.

What changes is your week, not your price list

The useful conclusion is not that you build the same site cheaper. The shape of the week changed: the largest block of focused production work stopped being the largest block. Whether that becomes more projects, more attention on positioning, or fewer evenings is a decision rather than an outcome.

What it should not become is a promise of ten times faster delivery to a client whose copy has not arrived. Pricing is a separate question, and how much to charge when the AI did the building is the answer to it.

Where Birta fits

Birta claims the publishing stage, plus one most hosts leave out: a form that actually receives something.

A connected agent publishes the finished site to a public HTTPS address and publishes again after each round of changes, with no repository or build pipeline between. Edits go file by file through the same connection, so a one-word change does not mean republishing everything. Images and fonts travel with the site; video and PDFs need a public URL elsewhere. Every publish is kept as a version and a bad one rolls back. You can point a domain at it with HTTPS. The same agent can declare an enquiry form and get its submissions landing in your panel, without a separate form service.

For a client site whose point is bringing them enquiries, the lead-gen page walkthrough covers what belongs on the page and which plan limit the client hits first. The mechanism behind the connection is MCP, explained without the infrastructure vocabulary, and the exact steps for one tool are in the Claude Code deployment guide.

What Birta does not do is the rest of the list. It will not collect the client's copy, sit through the approval round, make the DNS wait shorter, or run the checkout. Those are still your hours, and they are now the majority of the project.

Frequently asked questions