A vague brief gets a vague quote. If a developer has to guess how
many pages you need, what your budget is, or what “modern” means to
you, the number they send back is a guess too, and it usually grows
once the real scope becomes clear.

Direct answer: a solid website design brief covers
seven things: your business and goals, your target audience, a list
of every page you need, your content readiness, your budget range,
your timeline, and examples of sites you like and dislike. Missing
any of these is the most common reason web projects run over budget
or over time.

Here’s what to put in each section, and why developers actually
need it.

Why the brief matters more than the meeting

Most business owners assume a good briefing conversation is enough,
and a written brief is just paperwork. In practice, the opposite is
true. A written brief forces you to make decisions before a developer
starts work, rather than during it, which is the single biggest driver
of scope creep and mid-project cost increases. It also gives you
something concrete to compare quotes against, since two developers
quoting from a proper brief are pricing the same project; two
developers quoting from a phone call are often pricing two different
projects.

1. Your business and goals

Start with what the website is actually for. A developer needs to
know:

• What your business does, in a sentence or two
• Who your main competitors are
• What the website’s single most important job is: generating
  enquiries, selling products, booking appointments, or simply existing
  as a reference point

Be specific. “I want more customers” is a goal every business
shares. “I want visitors to book a consultation without phoning us”
is a goal a developer can design around.

2. Your audience

Briefly describe who the site needs to convince. Are they local or
national? Are they comparing you against three competitors, or are
you their first search result? This shapes tone, structure, and how
much persuasion the copy needs to do.

3. A list of every page you need

This is the section most briefs skip, and it’s the one that causes
the most cost disputes later. List every page you can think of, not
just the obvious ones like Home and Contact. If you’re not sure what
a small business site typically needs, our guide to essential pages every small
business website needs is a good starting checklist to work from
before you write this section.

For each page, note roughly what it needs to contain. A “Services”
page that turns out to need five separate sub-pages once work starts
is a common source of disputed quotes.

4. Content readiness

Be honest about how much of your text and images already exist.
Developers price very differently depending on whether they’re
building around your finished copy or writing it from scratch. State
clearly:

• Whether you have final text ready, or need it written
• Whether you have your own photography, or need stock images or a
  shoot
• Whether you have existing branding (logo, colours, fonts) or need
  that created too

5. Budget range

A specific number, or even a range, gets a far more useful response
than leaving it blank. Developers scale their recommendations to
budget: a custom-built site and a well-configured template solve the
same problem at very different price points, and stating your range
up front lets them propose the right one. If you’re not sure what’s
realistic, our guide on typical UK website costs
breaks down what different budgets actually buy.

6. Timeline

State your ideal launch date and flag anything that’s fixed, such
as a trade show, product launch, or seasonal deadline. Be realistic:
most straightforward small business sites take four to eight weeks
from a confirmed brief to launch, and rushed timelines usually cost
more, not less.

7. Examples you like and dislike

Three or four reference websites, with a line on what you like
about each, save enormous back-and-forth during design. It’s just as
useful to include a site you actively dislike and why. “Not this” is
often clearer briefing than “something modern.”

A simple brief structure to copy

Common mistakes to avoid

• Leaving budget blank. This doesn’t get you a
  cheaper quote, it gets you a guess, which is often higher than
  necessary.
• Assuming “a few pages” is enough detail. List
  them. Vague page counts are the most common cause of mid-project cost
  increases.
• Skipping content readiness. If you haven’t
  written your copy yet, say so. It changes the timeline and the
  price.
• Sending a Pinterest board with no explanation.
  Reference sites without notes on what you actually like leave a
  developer guessing at your taste.

FAQs

How long should a website design brief be? Long
enough to cover all seven sections above properly, which for most
small businesses is one to two pages. Length matters less than
completeness.

Do I need a brief if I’m using a website builder
myself? Yes, in a lighter form. Even without a developer,
writing out your page list, goals and content readiness before you
start building will save you from restructuring the site halfway
through.

What if I don’t know my budget yet? Give a range
based on research rather than leaving it blank. A wide range, such as
“£1,000 to £3,000”, still gives a developer far more to work with than
no figure at all.

Should I write my own website copy before briefing a
developer? Not necessarily, but you should decide who’s
writing it and say so in the brief. Copywriting is frequently priced
separately, and leaving it unclear is a common source of quotes that
later increase.