How I build WordPress sites faster with AI (without the slop)

Two stories dominate AI and web development right now. Both are wrong. One says AI quietly builds your whole site while you sleep. The other says everything it touches comes out as generic slop. The truth is duller, and far more useful: AI is very good at the repetitive parts of a build and useless at the parts that actually matter. Knowing which is which is the whole job.

So here's the real version. This is how I use it on a WordPress build, start to finish.

The design is settled first

Nothing gets built until the design is agreed in Figma. Nothing. That matters for AI specifically, because a clear, settled design is the thing that makes the next step reliable in the first place. Vague brief in, vague everything out. Proper comp in, structured components out.

AI does the scaffolding, not the thinking

I built my own tooling for this. It pulls a design straight out of Figma and turns it into real, structured page components in WordPress. The layout, the fields, the boilerplate that normally eats hours of an agency's time? Done in minutes. This is the part AI is genuinely good at: repetitive, well-defined, tedious work.

What it does not do is decide how the site should be built. It doesn't set the architecture, doesn't choose what to cut for speed, doesn't judge whether a component is actually right for the job. That's still me. That's the point.

Then I build it by hand

The scaffold is a starting point. Not a finished site. I take it and craft every component to the design, by hand, on a lean theme I've written myself. No Elementor. No Divi. No page-builder plugins stacked on top of each other until the whole thing crawls. That's a deliberate choice, and it's why the sites come out fast instead of bloated.

Held to a number, not a vibe

Every page has to hit a strict performance budget, measured on a throttled mobile rather than on my laptop where everything looks quick. Too heavy? Too slow? It doesn't ship until it's fixed. AI helps me get there faster. The standard doesn't move.

So what do you actually get

You get the same thing an agency would build, delivered in less time and for less money, and genuinely fast, because speed was a rule enforced the whole way through rather than something bolted on at the end. Automation does the grind. A senior developer's judgement sits on top. One without the other is how you end up with slop.

I've written up the full process, step by step, over on the how I build page. Want a site built this way? book a free 30-minute surgery and I'll walk you through how I'd approach yours.