The quality of a website project is usually decided before any design work begins — in the brief. A clear brief gets you an accurate quote, a realistic timeline and a website that actually does what your business needs. A vague brief gets you misunderstandings, extra costs and a site that looks fine but misses the point. Learning how to brief a web designer is not difficult, and it does not require technical knowledge. It requires answering, in writing, a set of straightforward questions about your business and what you want the website to achieve.

This guide explains what a good brief contains, section by section, what designers actually do with the information, and the mistakes that most often cause projects to drift. Whether you are commissioning your first website or replacing an old one, an hour spent on the brief will save you many hours later.

Why the brief matters so much

A designer cannot read your mind, and they do not know your business the way you do. Everything they assume in the absence of information is a risk: they might assume you will write the content, that your logo is ready, that the site needs five pages when you imagined fifteen. Assumptions that surface mid-project become delays and extra charges. A brief replaces assumptions with shared facts.

The brief also protects you when comparing quotes. If three designers quote against the same written brief, the quotes are comparable. If each quotes against a different conversation, you are comparing three different websites at three different prices, and the cheapest is often cheapest because it quietly includes the least.

What to include in your brief

1. A short introduction to your business

Two or three paragraphs are enough: what your business does, who your customers are, where you operate, and how long you have been trading. Include what makes customers choose you — not marketing slogans, just the honest reasons people give. This context shapes every design decision that follows, from tone of voice to which services get prominence.

2. The goals of the website

State plainly what the website is for. Generate enquiries? Sell products online? Take bookings? Support existing customers? Recruit staff? Most sites have one main goal and one or two secondary ones — say which is which. A designer who knows the main goal will prioritise it in every layout decision; a designer who does not will treat everything as equally important, which means nothing stands out. Be specific where you can: "most enquiries should come through the quote form" is a goal a designer can build towards.

3. The pages and features you need

List the pages you expect — for example home, about, individual service pages, gallery, testimonials, blog, contact — and any features: online shop, booking system, contact forms, maps, live chat, customer logins, multiple languages. Separate the essentials from the nice-to-haves. If you are replacing an existing site, say which pages and content should carry over and which should be dropped. If you are unsure about scope, that is fine — say so, and say what the site must achieve; a good designer will propose a structure based on the services they offer.

4. Content: what exists and what is needed

Be honest about content. Do you have a logo and brand colours? Finished text, or rough notes, or nothing yet? Photographs of your work, or will images need to be sourced? Who will write the final pages, and by when? Content is the single most common cause of website delays, and it is almost always because nobody stated at the start who was producing it. If you need help with writing, say so in the brief — it affects both price and timeline. Our guide on how to write website content that sells can help you prepare.

5. Examples of websites you like and dislike

Share two or three websites you like — competitors or completely unrelated businesses — and say specifically what you like about each: the colours, the layout, how the services are presented, the general feeling. Do the same for anything you dislike. "I like this one" without explanation is hard to act on; "I like how this one puts the phone number everywhere and keeps pages short" is a design instruction. This section prevents the most painful moment in web projects: the first design reveal going in a direction you never wanted.

6. Technical and practical details

Cover the unglamorous essentials:

  • Do you already own a domain name, and where is it registered?
  • Do you have hosting, or should the designer arrange it?
  • Do you need business email addresses set up?
  • Must the site connect to any tools you already use — accounting, booking, email marketing, a CRM?
  • Who will update the site after launch: you, your team, or the designer?
  • Are there legal requirements — privacy policy, cookie consent, industry regulations, accessibility standards?

7. Budget and timeline

Many owners are reluctant to state a budget, fearing the quote will simply match it. In practice, stating a realistic budget range helps the designer propose the right scope instead of guessing — there is little value in a proposal for a large site if your budget suits a focused one, or vice versa. If there is a deadline — a launch date, a season, an event — say so and say whether it is fixed or flexible. Designers plan their schedules around this information, and surprises help nobody. If you want to understand how scope translates into cost before setting your budget, our guide on how much a small business website costs explains what drives the price.

8. How decisions will be made

Name one person as the main contact and decision-maker, even if several people will give opinions. Projects stall when feedback arrives from five directions, sometimes contradictory, or when nobody is sure who can approve a design. State how you prefer to communicate and how quickly you can usually respond — the project's pace depends as much on your feedback speed as on the designer's work speed.

What happens after you send the brief

A good designer will respond with questions before quoting — treat that as a healthy sign, not a delay. They may propose a slightly different structure than the one you listed, and they should explain why in terms of your goals. The quote you receive should restate the scope in writing: pages, features, what is included, what is not, what you must supply, and the payment stages. Read that scope against your brief before accepting; anything you discussed that is missing from the written scope will not magically be included.

During the project, refer back to the brief when new ideas appear. New ideas are not bad — but each one should be a conscious decision about scope, time and cost, not a casual addition. A brief you can point to keeps those conversations friendly and factual on both sides.

Brief mistakes that cause the most trouble

  • "Just make it look modern." Modern means different things to everyone. Examples and specifics turn taste into instructions.
  • Copying a competitor's site as the whole brief. Their site serves their goals and their customers. Borrow elements, but brief from your own business.
  • Hiding the budget. Designers cannot optimise scope for a number they do not know; hiding it usually produces proposals that miss in both directions.
  • Assuming content is the designer's job by default. Sometimes it is, sometimes it is not — but it must be agreed in writing, with deadlines.
  • Designing by committee. Gather opinions, but let one person decide. A website that tries to please everyone in the office usually pleases no visitor.
  • No mention of aftercare. Who updates, backs up and looks after the site after launch should be settled before launch, not after the first problem.

Briefing for a redesign is slightly different

If you already have a website, your brief should also explain what is wrong with it. Be specific: enquiries dropped, the site is slow, it does not work on phones, the branding has changed, you cannot update it yourselves, customers keep asking questions the site should answer. Also say what is working and must not be lost — pages that bring in enquiries, content your customers rely on, anything that ranks well in search results. A redesign that throws away the parts of an old site that were quietly performing is a common and expensive mistake, and it usually happens because the brief described only the new site and never mentioned the old one's strengths.

Include access information in the practical section too: who controls the domain registration, the hosting account and any analytics. Projects regularly lose a week while everyone discovers that the only person with the passwords left the company two years ago. Gathering those logins before you brief anyone is unglamorous, genuinely useful work.

A short brief template you can copy

If a blank document feels daunting, copy these headings into a file and write two or three honest lines under each. That document, filled in plainly, is a better brief than most designers receive:

  • Our business: what we do, who for, and where.
  • Why customers choose us: the real reasons, in plain words.
  • The website's main goal: the one thing it must achieve first.
  • Pages and features needed: essentials separated from nice-to-haves.
  • Content status: what we have, what we need, who is producing it and by when.
  • Websites we like and dislike: with one line each on why.
  • Practical details: domain, hosting, email, tools to connect, who maintains the site afterwards.
  • Budget range and deadline: honest numbers and dates, fixed or flexible.
  • Decision-maker: one named person, and how quickly feedback will come.

Send that to two or three designers and you will get back quotes you can actually compare — which is the entire point of the exercise.

Finally, do not let the perfect brief become the enemy of starting. If you have covered the sections above honestly — even briefly — you have a better brief than most projects begin with, and a good designer will ask about anything still unclear. The brief is a working document, not an exam. Write what you know, mark what you do not, and send it.

Frequently asked questions

How long should a website brief be?

Long enough to cover the sections in this guide — for most small businesses, two to four pages of honest, specific notes. Length matters less than completeness: a short brief that answers the key questions beats a long one full of general statements about quality and excellence.

What if I do not know what pages or features I need?

Say so, and focus your brief on the business background, the goals, your customers and your budget. Proposing a structure is part of a designer's job. What they cannot invent is knowledge of your business, so the sections only you can write — goals, customers, content, examples — still need your input.

Should I really tell a designer my budget?

Yes, a realistic range. It lets the designer propose a scope that fits instead of guessing, and it saves you both time on proposals that were never viable. A professional will tell you honestly what is and is not achievable within your range rather than simply spending all of it.

Can I change the brief after the project starts?

You can, and most projects evolve a little. But treat changes as formal decisions: ask what the change does to the price and the timeline before it is done, and get it confirmed in writing. Small agreed changes are normal; a stream of casual additions is how budgets and deadlines quietly break.

If you are preparing a brief — or if you have the beginnings of one and would like a designer's eye on it before you commit — you are welcome to send it over via our contact page. We will read it properly, ask sensible questions, and reply with an honest view on scope and cost, with no obligation to go ahead.