How to Build a Website with Claude Code (Even If You're Not a Developer)

Building a business website used to mean one of two things: spend thousands on a developer, or spend weeks fighting with a website builder. Neither option is great if you're a solo founder who needs a professional site without a massive budget or a steep learning curve.

I built the Stepping Stones AI website entirely inside Claude Code. From scratch. No designer, no agency, no template. Here's how the process worked, what I'd do differently, and whether this approach makes sense for you.

Why Claude Code works for building websites

Claude Code isn't a website builder in the traditional sense. It doesn't give you drag-and-drop templates or a visual editor. What it does is generate code based on your instructions, edit files in your project folder, and iterate with you until the result is right.

Think of it as working with a developer who's sitting next to you. You describe what you want. It builds it. You say "that heading is too big" or "move the CTA above the fold." It updates the code immediately.

The advantage over a traditional developer is speed and cost. The advantage over a website builder is flexibility. You're not constrained by templates. If you can describe it, Claude Code can build it.

The stack I used and why

The site runs on Next.js, a React-based framework that handles routing, page generation, and performance out of the box. I chose it because Claude Code works well with React and Next.js. The code generation is reliable and the framework handles a lot of the heavy lifting automatically.

You don't need to understand React to use this approach. Claude Code handles the technical details. You need to understand what you want your site to look like and what it should say.

The project lives in a folder called `SSAI Website/` in my workspace, right alongside my client files, content pipeline, and agent team. Everything in one place.

How the build process works, step by step

The build wasn't a single prompt. It was a conversation over multiple sessions.

Architecture first. Before any code was written, I described the site structure: which pages, what sections on each page, the navigation layout, and the content hierarchy. Claude Code generated the file structure and routing.

Section by section. I worked through each section of each page individually. Hero section, services overview, about page, contact form. For each one, I described what I wanted and Claude Code wrote the code.

Content from existing files. Because my brand voice guidelines and service descriptions were already in the workspace, Claude Code referenced them directly. The site copy sounded like me from the first draft.

Iteration. When something didn't look right, I said so. "Make the hero section taller." "Change the button colour to match my brand." "Rewrite this paragraph, it's too formal." Claude Code updated the code in place. No switching between tools.

What went well

Three things stood out.

Speed. The basic site structure was up within a couple of hours. A comparable build with a freelance developer would take days or weeks, depending on availability.

Consistency. Because my brand voice file was in the workspace, the site copy was consistent from the start. No briefing a copywriter. No reviewing drafts that don't sound like me.

Everything in one place. The website project sits alongside my content pipeline, client folders, and automations. When I update my services or brand voice, the context is already there for the next iteration.

What was tricky

Visual design decisions. Claude Code can generate layouts, colours, and spacing. But it can't tell you whether something "feels" right. That's still a human job. I spent time adjusting visual details that Claude Code couldn't judge for itself.

Complex interactions. Custom animations, hover effects, and interactive elements need more specific guidance. Simple requests work well. Detailed visual effects require more back-and-forth.

Mobile responsiveness. The generated code was mostly responsive, but I needed to check and adjust a few elements on smaller screens. This is true of any build, not just AI-assisted ones.

Who this approach suits

This works best for solo founders, freelancers, and small businesses who want a professional site without a large budget. You need to be comfortable giving clear instructions and making decisions about what you want. You don't need to understand code.

It's less suited for complex web applications, e-commerce sites with hundreds of products, or businesses that need custom integrations with legacy systems. For those, you still want a developer.

But for a clean, professional business website? Claude Code can do it. I'm proof.

If you're thinking about building a site with AI, start with a clear plan for your pages and sections. Write down what you want before you open Claude Code. The clearer your brief, the better the output.