SmartCuts · 14 August 2026 · 4 min read

Can you build a website with AI if you're not a developer? Yes, but it isn't one button.

By Esmarie Swanepoel, AI Brain & Automation Architect

The short answer

Yes, a non-developer can build a working website with AI, but not with one button. Esmarie Swanepoel's build took 15 extra tools and 32 versions, because AI gets the first 80% done fast and quietly breaks things in the last 20%. The people who succeed stay the pilot: they review, test and understand every decision rather than accepting whatever the AI hands back.

I am sorry (not really) if this offends any tech bro whose eyes it may be subjected to. #sorrynotsorry

Let me tell you what it actually took to vibe-code a website, as a non-coder, using Claude: 15 additional tools and 32 iterations. Not one AI button. Fifteen separate systems I had to learn, connect and troubleshoot when they refused to talk to each other. Thirty-two versions of a single HTML file, because the AI that confidently handed me something that looked finished had quietly broken something two steps back.

I like to call it the AI-Button-Hype: the human presses a button, sits back and watches. Et voilà, the work is done, the magic wand has waved. Right?

Wrong. So, so very wrong.

And before anyone reaches for the obvious rebuttal, "that's because you're not a developer": well, duh. That is precisely the point. The pitch was never "vibe coding works if you already know how to code." The pitch was: tell AI what you want, and it builds itself. No developer required. I tested that exact dream. It did not.

The inventor of the term never promised you this

Andrej Karpathy, the AI researcher who coined "vibe coding" in February 2025, was admirably honest about what it meant in practice: accept every AI suggestion, stop reading the changes, paste error messages back in, and let the code grow beyond what you fully understand. His own verdict was that it's fine for throwaway weekend projects.

Throwaway. Weekend. Projects. Not a business's home on the internet. Not something with your name, your credibility and your clients attached to it.

Developer Simon Willison drew the sharpest line in the whole debate: if an AI wrote every line of your code, but you've reviewed, tested and understood it all, that's not vibe coding. That's using an AI as a typing assistant.

By that definition, I never actually vibe-coded anything. I reviewed. I tested. I understood every decision well enough to catch the 32nd version's mistakes before they went live. That's not me falling short of the dream. That's me doing the actual work the dream was selling as optional.

The statistic that should worry you more than any bug

A study by METR, one of the most rigorous independent research groups on AI coding tools, found that experienced developers using AI were 19% slower, even though they believed they were faster.

Not "AI made no difference." Slower, and confident they were faster.

That tracks with my own late nights. The first 80% of any AI-assisted build is lightning fast. It bedazzles you. You start to believe the hype yourself, because for a moment, it's true. But almost nobody talks about the 20% that comes after: the part where the pretty, beautifully veneered delivery has to actually work. Hello to my 32 HTML versions.

The oldest evidence isn't in a codebase. It's in a cockpit.

A tool that does 80% of the work brilliantly while quietly eroding your ability to handle the remaining 20% isn't new, and it didn't start with AI. Aviation researchers have studied it for decades as automation complacency: the more an autopilot does, the more a pilot's hand-flying skills fade, in novices and experts alike. Pilots become passengers in their own cockpit, and the gap only shows the moment the automation fails and they need a skill they no longer fully have.

If that made your stomach drop a little, good. It should.

Researchers describe the same dynamic in AI use: it produces either cognitive growth or cognitive decline, and the deciding factor is whether you stay reflective, engaged and in the loop, or hand over the controls and stop watching.

Pilot versus passenger is the measurable difference between a build that works and one that quietly rots underneath its confident surface.

What actually happened

The site exists now. It came from me, myself and I, with the help of 15 tools I'm now genuinely thankful to have mastered. But it took a human who knows how to drive AI, not sit as a passenger in its car. It takes a system. Not prompting.

That's the real skill gap in this industry right now, and nobody selling you a single "just prompt it" tool has any incentive to name it.

If you're building right now

If you're stuck, on a tight budget, or need help shipping something real with AI, I've already paid the school fees so you don't have to. Tell me what you're building and email me for 1:1 time.

In a tech world, I bet on people.xo Esmarie

This piece first went out as a SmartCuts newsletter. Get the next one in your inbox on Substack.

Questions

Quick answers

What is vibe coding?

Vibe coding is a term coined by Andrej Karpathy in 2025 for building software by describing what you want to an AI and accepting its code without closely reviewing it. He described it as suited to throwaway weekend projects.

Can a non-developer build a business website with AI?

Yes, but expect to learn several supporting tools, work through many versions, and review and test every change. The first 80% is fast; the last 20% needs a human who understands what was built.

Does AI make developers faster?

Not always. A 2025 METR study found experienced open-source developers were 19% slower with AI tools, even though they believed they were faster.

Your next step

Find out how much of your business lives only in your head.