The four stages of a website that works

The short answer

A website that works gets made in four stages:

1. Messaging. Who are we talking to, and what do they need to hear?
2. Copy. The actual words.
3. Design. How those words get seen and read.
4. Build. How it all runs, loads and gets found.

In that order.

Most sites that look like templates didn’t skip the template. They skipped stage one and two.

A call I had this week

I was talking with someone recently who runs operations for a small practice. They’d spent years managing big technical teams before this. They know how to read a wireframe. They know what a good site feels like.

Their site was built by a vendor that dropped their copy into a template. It’s better than what they had before. It still looks like a template.

What they said stuck with me. Paraphrasing: I can tell the hero is wrong. I just can’t tell you how to fix it. I need someone to look at everything we’ve given them and say, “Here’s what we should do, here’s why, and here’s what you’ll get out of it.”

That’s the job. And it’s four jobs, not one.

Stage 1: Messaging

Before anyone writes a headline, answer three questions:

• Who is this for? Not “everyone who needs us.” The person most likely to hire you, and the one you most want.
• What are they trying to get done? The job to be done, in Clayton Christensen’s phrase. People don’t want a website or a consultant or a CRM. They want the result. Christensen and his co-authors make the case in Know Your Customers’ “Jobs to Be Done” (Harvard Business Review, 2016).
• Why you? What you do that the next option doesn’t, said in a way the reader can repeat to someone else.

I spent four years as a StoryBrand guide. The framework is simple: your customer is the hero, you’re the guide, and the site’s job is to show them the plan and the stakes. It’s a good way to do this stage. So is jobs to be done. So is a long talk with your five best customers.

The framework matters less than doing the stage at all.

What to have when messaging is done

• A one-line description of who you help and how.
• The three to five problems your best customers had before they found you.
• What changes for them after.
• The objections you hear on sales calls, and your honest answers.
• The one next step you want a visitor to take.

If you’re in a sensitive field, add one more: the tone. Someone looking for help with something hard needs to feel understood before they feel sold to. Empathy first. Then authority: we’ve done this, we can help, here’s how.

Stage 2: Copy

Messaging is what you mean. Copy is what you say.

This is the stage most businesses hand to AI now. I understand why. It’s fast and it’s cheap, and I use it every day. But a first draft from a chatbot tends to sound like everyone else’s first draft from a chatbot.

A copywriter who knows your messaging does three things AI can’t do alone:

• Chooses. What to leave out matters as much as what goes in.
• Sounds like you. Not like a brochure.
• Writes for skimmers. Jakob Nielsen’s analysis of real browsing data found people read about 20% of the words on an average web page (Nielsen Norman Group, 2008). Headlines, subheads and the first line of each section do most of the work.

On one of the best sites I’ve worked on, I brought in a copywriter who used to be a StoryBrand guide too. The design was good. The words are why it works.

What to have when copy is done

• Final copy for every page, in a doc, not in the design file.
• Headlines and subheads that tell the story on their own.
• Every claim checked. If there’s a number, there’s a source.
• A clear call to action on every page, pointing to the same next step.

I’m not a copywriter, and I say so. On bigger projects I bring one in. If you’re doing it yourself, write first, then use AI to tighten. Never the other way around.

Stage 3: Design

Now the words get a shape.

The goal isn’t to win an award. (This site is a little different. It’s my portfolio, so it gets to show off.) For most businesses, design has one job: get the message read, by everyone, on every device.

That means:

• Contrast. WCAG 2.2, the accessibility standard most organizations work to, asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. WebAIM’s 2026 scan of the top million home pages found low-contrast text on 83.9% of them. It’s the most common accessibility failure on the web, and the easiest to fix.
• Readable type. Big enough body text, short line lengths, real hierarchy. The H1 doesn’t have to be the biggest thing on the page, but the most important thing does.
• Images that mean something. A photo of the outcome, or the person you help, or the problem. Not a stock handshake.
• One clear path. Each page leads somewhere. If everything is a button, nothing is.
• Mobile first. Plenty of people will meet you on a phone first. Design for that, then scale up.

Accessibility isn’t a nice extra. If you serve the public, and especially if you serve people who might be struggling, everyone needs to be able to use your site. WebAIM found detectable accessibility failures on 95.9% of home pages. That’s the bar to beat, and it’s low.

What to have when design is done

• Page designs for desktop and mobile.
• A small component library: buttons, cards, sections, forms. Not a new layout for every page.
• Contrast and type checked against WCAG.
• Sign-off from the person who owns the business, not just the person who manages the project.

Stage 4: Build

Last, and only last, we build it.

The build decides three things you’ll feel for years:

1. Speed. Google’s Core Web Vitals set the targets: the main content loads within 2.5 seconds, the page responds to a tap within 200 milliseconds, and nothing jumps around while it loads. Google says its ranking systems use Core Web Vitals, and visitors notice a slow page long before Google does.
2. Search. Clean structure, real headings, metadata, redirects from any old pages. If you’re redesigning, plan the move so you keep the traffic you earned. I wrote about that in Should you rebuild your website with AI?
3. Who can change it. This is the one people forget.

Build for the person who edits it next

I build most sites in Webflow with a framework called MAST. Frameworks like it (Client First and Lumos are the other common ones) give a site a set of building blocks: sections, grids, buttons, cards. Your team adds a page by snapping blocks together in the editor. Nobody needs to know CSS. Nobody makes 400 slightly different versions of the same button.

That matters more now than it did a year ago. AI tools can build pages fast, but left alone they tend to invent new styles every time. Give them a framework and tell them to stick to it, and they build pages that look like they belong.

The person on my call put it well. They’re planning for the day they hand the site to someone else. They want it stable, documented and editable by whoever comes next.

That’s the right goal for any build.

What to have when the build is done

• A site that passes Core Web Vitals on mobile.
• Redirects from every old URL.
• Analytics and search console set up and tested.
• Editor access for your team, and a short guide to using it.
• Every account (domain, DNS, hosting, forms) in your business’s name.

Why the order matters

Each stage is the brief for the next one.

Messaging tells the copywriter what to say. Copy tells the designer how much space each idea needs. Design tells the developer what to build. Skip one, and the next stage is guessing.

That’s where template sites come from. The template is the design, made before anyone knew what you’d say. So your words get poured into someone else’s shape. It fits, roughly. It never quite fits.

It also explains why projects run long. It’s rarely the build. It’s the copy arriving after the design is done, and the design getting redone to fit it.

How this fits how we work

These four stages are how a website gets made. They sit inside how we run a whole project, which you can read on our process page: diagnose, architect, implement, iterate.

Not every project needs all four stages from scratch. Sometimes the messaging is solid and the site just needs a better build. Sometimes the build is fine and the words need work. The Systems Diagnostic is how we figure out which.

If your site looks like a template and you can’t put your finger on why, book a call. We’ll tell you which stage got skipped.