How I Build Websites With AI in Under an Hour

If you'd told me two years ago I'd be delivering a fully functional, professional website in under an hour, I would have laughed. A basic site used to take me a full day — layout decisions, writing copy, tweaking CSS, testing on mobile, fixing browser quirks. A full business website? Two or three days easy.

That's changed completely. Not because I've gotten faster at the traditional process, but because the process itself has changed.

Here's exactly how I build websites with AI in under an hour in 2026, and what this shift means for freelancers and developers.

Why Speed Matters (And Why It's Not About Cutting Corners)

Before I get into the process, let me be clear about something: building faster doesn't mean building worse. The sites I produce now are better than what I was building manually two years ago. Better copy, better structure, better performance.

Speed comes from removing the friction that was never creative work to begin with — blank-page syndrome, repetitive code patterns, time spent on boilerplate that every site needs. AI removes that friction. The actual craft — understanding the client, knowing what makes a site convert, applying good judgement — that's still 100% human.

But for freelancers, speed is a business advantage. If a job takes you 1 hour instead of 8, you can either:

All three are competitive advantages that compound over time.

The Stack I Use

I'm not going to pretend there's one magic tool that does everything. It's a combination:

The key is how these tools talk to each other in the workflow. Let me walk you through it.

The 60-Minute Website Build Process

Minutes 0-10: Brief and Structure

Before I write a single line of code or design anything, I drop the client brief into Claude.

The brief is usually minimal — a few sentences about what the business does, who their customers are, and what they want the site to achieve. That's enough.

I ask Claude to:

In 3-4 minutes, I have a complete content skeleton. The copy isn't final — I'll refine it — but it's 80% of the way there. The structural thinking that used to take 30 minutes of staring at a blank screen? Done.

Minutes 10-25: The Build

This is where Cursor comes in. I open my base WordPress template or a clean HTML/CSS starter, and I start building.

Cursor understands context. If I'm working in a WordPress theme file and I say "add a hero section with a headline, subheadline, CTA button, and a background image overlay," it writes the code. Not a template — actual code that fits the pattern of what I'm already building.

When I need a custom CSS effect, I describe it. When I hit a bug, I paste the error and ask what's wrong. The debugging loop that used to eat 20 minutes of a build is now under 5.

For client sites, I'm not building from scratch every time. I have a base template that handles:

Cursor helps me customise this quickly for each client. The unique parts — the hero, the services section, the about page — those get built fresh but assisted by AI.

Minutes 25-40: Content and Copy Refinement

The copy Claude generated in step one gets dropped into the site. Then I review it.

This is where the actual skill comes in. AI copy is good but it needs human judgement to make it great. I'm checking:

I'll rewrite sections that feel off, tighten headlines, make sure contact details are correct. This takes 10-15 minutes, not the hour it used to take because I'm editing, not writing from scratch.

Minutes 40-55: Mobile Check, Performance, Final Polish

This is the part most people rush and regret. Even with AI-assisted builds, you need to check:

Cursor helps here too. I can ask it to review my code for common performance issues or accessibility problems. It flags things I might miss.

Minutes 55-60: Delivery Prep

Screenshot for my portfolio. Write a brief handover document for the client (what they can edit, what to leave alone, how to add blog posts if they want). Send for review.

Done.

What This Changes for Freelancers

If you're freelancing in web development or WordPress, this shift changes the economics of your business.

The old model: Charge by the hour, grind through builds, compete on price.

The new model: Charge for outcomes and speed. A client doesn't want to pay for 8 hours of your time — they want a professional website that brings them customers. If you can deliver that in 1 hour, you can price by value, not by time.

I've seen freelancers charge £500-1,000 for a basic business website. At the old pace, that's reasonable (£60-80/hour for 8 hours work). At the new pace, that's exceptional earnings for your time investment. And because you're delivering faster, clients are happier and leave better reviews.

The freelancers winning right now aren't the ones who resisted AI. They're the ones who picked it up early, built efficient workflows, and now offer things the slow-and-manual crowd can't compete with.

The Learning Curve

I want to be honest: there's a learning curve.

Cursor takes a day to get comfortable with. You need to learn how to write prompts that get useful code back — too vague and you get generic output, too specific and you'd have been faster writing it yourself.

Claude for copywriting takes practice too. You need to learn how to brief it — what context it needs, how to ask for the tone you want, when to accept the output and when to push back.

But the learning investment is measured in days, not months. And the compound interest on that investment is enormous. Every build you do gets faster as you refine your workflow.

If you want to see this process in real time, I document my builds on YouTube at @prompttocode — I walk through AI-assisted coding and website builds in actual screen-share videos, not polished tutorials. Just real builds, real mistakes, real workflow.

Getting Started Today

You don't need to overhaul your workflow overnight. Pick one part of the process and introduce AI there first:

If you struggle with copy: Start with Claude. Next time you have a site to build, drop the brief into Claude and ask for homepage copy. Compare what it gives you with what you would have written. Iterate from there.

If you lose time to debugging: Try Cursor. Paste errors in, describe what you're trying to build, and see what comes back. The debugging alone will save you hours per month.

If you want the full workflow: Start from scratch with a simple site for yourself or a friend. Use AI throughout. You'll hit friction points, but you'll learn faster than any tutorial.

The gap between freelancers who use AI and those who don't is widening every month. 2026 is still early enough to get ahead of it.

If you want to hire someone who builds this way — fast, clean, professional — or if you want to discuss a WordPress project, you can reach me at kylanjari@gmail.com.

And if you want to watch AI-assisted builds happen in real time, subscribe to @prompttocode on YouTube.