What Happens When AI Builds Your Entire Website? The Good, the Bad & the Ugly

AI can now build a complete website from a short description, and the results are often better than people expect. They're also often worse than they look. I build client sites with AI coding tools every day, so here's my honest breakdown of what actually happens when you hand the whole job over.

The good

First drafts are genuinely fast. Something that once took days to reach a first look can now be on screen within an hour, which makes it far cheaper to try two or three design directions before committing to one.

It also lowers the barrier for anyone with no budget at all, and once the direction is clear, AI is excellent at the boilerplate and repetitive work that used to eat up a large chunk of a build: page templates, form handling, responsive layouts, the same component repeated with small variations.

The bad

AI tools don't know your business. They don't know your customers, what those customers worry about before they buy, or what's actually worked for similar businesses before. What they produce is plausible-looking, which isn't the same thing as effective.

Without someone checking, you can end up with a site that looks fine in a screenshot but has real problems underneath: slow load times, a mobile layout that breaks on certain phones, buttons a screen reader can't make sense of, or copy that describes your services in words your customers never actually search for.

The ugly

Then there are the outcomes that genuinely cost people time and money.

• Security nobody thought about. An unprotected form, an exposed admin area, or a dependency nobody ever updates. AI won't flag a risk you didn't think to ask about, and the first sign is often a hacked site.

• Content you can't take with you. Some platforms make it very easy to build and very hard to leave, so moving later means rebuilding from scratch.

• Weeks spent going in circles. Without the technical vocabulary to describe what's wrong, you end up asking the tool to "fix the layout" over and over while it confidently changes the wrong thing.

In my experience that last one is the most common, and the most frustrating, because it feels like you're nearly there the whole time.

Same technology, very different outcome

None of this means AI-built sites are bad. It means AI building the whole thing with nobody checking is a very different proposition from AI being used as a tool by someone who understands what good actually looks like. The technology is identical. The difference is whether the person driving it can spot a slow page, a broken layout or a security gap before your customers do.

What I'd actually do

• Use AI freely for drafts and exploring ideas, it's genuinely good at that

• Before anything goes live, test it on a real phone, run it through Google PageSpeed Insights and check you can export your content

• Get someone who understands code to review security and accessibility, because those are the problems you won't see from the front end

That's how I work: Claude Code does a lot of the heavy lifting, and I make the decisions and check everything it produces. If you've tried building a site with AI and got stuck, or you'd like a second opinion on one that's already live, get in touch and I'll take an honest look.

A quick note: this is my own opinion, based on what I've seen work in practice, not formal legal, financial or professional advice — your situation may differ, so do your own research before making a decision. These views are mine alone and don't reflect any employer or organisation I'm affiliated with.