← All posts

AI Can Build Your Website. Here's What It Can't.

AI tools scaffold a decent-looking page in minutes. They get you about 60% of the way. The last 40% is where clients are won or lost.

AI Can Build Your Website. Here's What It Can't.

An AI website builder is a tool that generates a working page layout from a prompt, usually in a few minutes. v0, Lovable, Wix AI, and the rest are genuinely good at this. They pick a clean layout, fill it with placeholder copy, and hand you something that looks like a real website. If you have never seen one work, it feels like magic the first time.

I am not here to tell you the magic is fake. It mostly works. The problem is what "works" means. A page that loads in a browser and a page that turns a stranger into a paying client are two different things. AI gets you the first one fast. The second one is still the hard part, and it is the part that wins the work.

My rough split: AI gets you about 60% of the way. The last 40% is where the money is. Here is what lives in that 40%.

What can an AI website builder actually do well?

An AI builder is good at structure and speed. Give it a prompt and it returns a hero section, a few feature blocks, a footer, and a color scheme that does not clash. For a developer it is a fast way to skip the blank page. For a business owner it is a cheap way to see something on screen.

That is real value. But the output is a generic page that could belong to any business in your category. It does not know your customers, your margins, or the one thing you actually want a visitor to do. It guesses, and the guess is average by design, because it was trained on the average of everything.

Average does not sell. Specific sells. That gap is the whole job.

Why does AI miss the part that wins clients?

AI misses it because the part that wins clients is not a design problem. It is a judgment problem. It needs someone who knows your business and is willing to cut things that look nice but do not sell. A model optimizes for a page that looks complete. A developer optimizes for a page that gets one specific result. Those goals pull in different directions.

Four things AI consistently gets wrong on a site that has to win work:

1. Conversion architecture

Most AI pages give you everything at once: five buttons, three offers, a long menu, and no clear path. It looks busy and balanced. It also gives the visitor nowhere obvious to go. A site that converts has one main offer and one guided path to contact. Everything else is in service of that. Stripping a page down to one clear next step is a decision, and AI will not make it for you because it does not know which step matters. I wrote more about this in the 5-second homepage test.

2. Real performance

Speed is not a vanity score. It is a revenue metric. Google and Deloitte found that improving mobile load time by just 0.1 seconds lifted conversions, with retail conversions up about 8% in their study. Put another way, roughly every 100ms of delay costs you about 1% of conversions. In 2026, only about 47% of sites pass Google's Core Web Vitals "good" thresholds, so the other 53% are leaving money on the table. AI builders rarely ship a genuinely fast page. They lean on heavy frameworks, unoptimized images, and bloat you never see. Getting a real Largest Contentful Paint under a second on a phone is hands-on work. It does not come from a prompt.

3. A structure people and search engines trust

A page can look trustworthy and still be invisible. Clean heading order, honest copy, a clear contact path, real schema markup, and content written so both a human and an AI search engine can answer "what does this business do and who is it for" in one line. That last part matters more every month, as more people find businesses through AI answers instead of ten blue links. AI builders skip almost all of it because none of it shows up in a screenshot.

4. The judgment to cut what doesn't sell

This is the one that separates a 60% page from a finished one. Knowing what to remove. The slider nobody clicks. The third call to action that splits attention. The paragraph that sounds smart and converts no one. A model adds. It fills space because a full page reads as a complete page. Knowing what to delete comes from watching real sites win and lose real clients, and that judgment is the thing you are actually paying a developer for.

Next.js, and why the stack still matters

About 68% of JavaScript developers now reach for Next.js, and it is not a trend. It is the difference between a site that loads in under a second and one that drags. I build on Next.js and deploy on Vercel because it gives me control over the exact things AI builders fumble: image handling, render strategy, Core Web Vitals. A Wix AI page and a hand-built Next.js page can look identical in a screenshot and behave nothing alike on a real phone on 4G. You can see the kind of work this produces on my recent projects.

None of this is anti-AI. These tools are a real starting line, not a finish line. The 60% they give you is real. So is the 40% they cannot.

FAQ

Can I just use an AI website builder and skip hiring a developer? For a hobby page or a quick test, yes. For a site that has to bring in clients, the AI output is a starting point, not a finished product. It rarely loads fast enough, guides visitors to one clear action, or gets found in search without hands-on work.

Is an AI-built website bad for SEO? Not automatically, but most AI builders ignore the parts search engines reward: fast load times, clean structure, real schema, and content written to answer a clear question. Those are added deliberately, not generated by default.

How much faster is a custom Next.js site than a Wix or AI-built one? It depends on the build, but the gap is usually large on mobile. I aim for a Largest Contentful Paint under one second, where many template and AI pages sit at three seconds or more. Since roughly every 100ms costs about 1% of conversions, that gap is money.

Can I start with an AI builder and bring in a developer later? Yes, and it is a sensible path. Treat the AI output as a first draft. A developer then rebuilds the parts that decide whether a visitor becomes a client: the offer, the speed, and how the site is found. AI handles the first 60%. The last 40% is the work.


If your site looks fine but does not bring in work, the problem is usually in that last 40%. That part I can fix. Start a project or send me a message and I will tell you what a stranger sees, and what it is costing you.