Before you build a website, nail down seven things: your goal, your audience, your sitemap, your content, your brand assets, your required functionality, and how you'll measure success. Most website projects go over budget and past deadline for one reason — they start building before these are settled. This checklist front-loads the decisions that are cheap to make on paper and expensive to change mid-build.

1. Define the goal in business terms

What is the site for? “Generate 20 qualified leads a month” is a goal; “look modern” is not. Everything downstream — structure, design, copy — should trace back to a concrete outcome. If you can't name it, that's the first thing to fix.

2. Know your audience

Who's the buyer, what do they need to know, and what objections do they carry? A site written for everyone converts no one. The clearer the audience, the sharper every page can be.

3. Map the sitemap

List the pages and how they connect before anyone designs. The sitemap is the plan; changing it after the build is like moving walls after the drywall's up. Work backward from the buyer's journey to decide what deserves a page.

4. Line up content

Content is the single biggest cause of stalled web projects. Decide who's writing the copy and sourcing images before the build starts — because a finished design with placeholder text can't launch. If you need help, budget for it; see how content factors into web design cost.

5. Gather brand assets

Logo files, brand colors, fonts, and any existing style guidelines. If they don't exist, that's a branding step to handle first — designing around undefined brand is rework waiting to happen.

6. Specify functionality

List everything the site must do: contact forms, booking, e-commerce, memberships, CRM or payment integrations. Functionality is the biggest driver of scope and cost, and the most common source of mid-build surprises when it's discovered late.

7. Decide how you'll measure success

Define the metrics upfront — leads, sales, form submissions, calls — and make sure analytics will track them from day one. A site you can't measure is a site you can't improve.

Put it in front of your designer

Hand this checklist, answered, to whoever builds your site and the project gets faster, cheaper, and calmer. A good agency will run you through exactly these questions in discovery — see how a strategist-led build starts here before any design work.

Frequently asked questions

What do I need before building a website?

A defined goal, a clear audience, a sitemap, your content, brand assets, a list of required functionality, and success metrics. Settling these before the build prevents the delays and cost overruns that come from deciding them mid-project.

What's the most common reason web projects stall?

Content. Designs get finished and then wait weeks for copy and images. Deciding who produces content — and when — before the build starts is the single biggest way to keep a project on schedule.

Do I need branding done before web design?

Ideally, yes. Logo, colors, and fonts should exist before design begins; building around undefined brand leads to rework. If branding isn't settled, handle it as a first step rather than mid-build.