A website design brief is a short document, usually two to four pages, that tells a web designer what your business does, who the site is for, what it must achieve and what you can spend. Write it around one question: what should a visitor do on this site that makes you money? Answer that, add your pages, content, budget and deadline, and any good agency can quote accurately and build the right thing first time.
Most small business owners we meet have never written one. That’s normal. You’re busy running the business, and nobody hands you a template. This guide gives you the structure, a worked example and the mistakes that cause the most pain later.
TL;DR
- A brief says what you want to achieve and why. A requirements document, which is the detailed list of what the site must do, sits underneath it.
- Lead with one main goal and a number you can measure, such as enquiries per month, not a list of wishes.
- Name your audience, your pages, your content and who signs things off, and say who is supplying the words and photos.
- Share your budget range and deadline. It lets the designer propose the right solution instead of guessing.
- Keep it to a few pages. A clear short brief beats a vague long one.
Table of Contents
- What a website design brief is (and isn’t)
- Why it’s worth an hour of your time
- The sections of a good brief
- A short brief you can copy
- Mistakes that cost small businesses money
- What to expect after you send it
- Our perspective
- Where we can help
- FAQ
- Sources
What a website design brief is (and isn’t)
Think of the brief as the conversation you’d have with a designer if you had three hours and a very patient listener, written down. It covers your business, your customers, the problem the site must solve and the practical limits: money, time and people.
You’ll also hear “website requirements document”, “web design brief”, “creative brief” and “website project brief”. In practice they overlap. The useful distinction is this: the brief explains what you want to achieve, while the requirements say what the site must do and look like to get there. A requirement might be that the homepage has one main call to action above the fold, or that checkout works on a phone without sideways scrolling, as one design team’s guide to requirements puts it. For a small business you can keep both in one document: the first page is the brief, the last page is the requirements list.
The UK’s national design body makes the same point about buying design in general. In its Design Buyers’ Guide, it says the clearer your objectives, the easier it is to measure the value of what you spend, and that even for hard-to-measure projects you should agree a quantifiable measure of the effect on your business.
Why it’s worth an hour of your time
Without a brief, the first conversation with an agency turns into guesswork. You say “something clean and modern”. They hear a brochure site. You wanted bookings. Three weeks in, you’re both frustrated and the invoice has crept up.
A brief fixes that in three ways:
- Quotes become comparable. If you ask two or three suppliers to price the same brief, you can see what’s in each one rather than comparing apples with a fruit bowl.
- Scope stays honest. When someone says “can we add a members’ area?”, you can look at the brief and decide whether it serves the goal.
- You find out what you think. Writing down who your best customer is often shows you the homepage you’d been circling.
If you’re still deciding who should build the site, our piece on choosing a web design agency for a small business covers what to look for before you send anything.
The sections of a good brief
Here’s the order we’d use. Each part has a job, and none of them needs more than a paragraph or a short list.
1. About your business
Three or four sentences: what you sell, where you work, how long you’ve been going, and what makes customers choose you over the next firm. Add your current website address if you have one, and what’s wrong with it in plain words (“it takes ages to load on my phone”, “people ring me to ask things the site should answer”).
2. The goal, and how you’ll know it worked
This is the most important section, so don’t skip the numbers. A goal is the purpose of the project. Objectives make it measurable. Requirements are what gets built.
A worked example for a plumber in Chesterfield:
- Goal: get more local people to request a boiler service online.
- Objectives: move from about 6 online enquiries a month to 15 within six months, and cut the number of phone calls asking for prices.
- Requirement: a boiler service page with a short enquiry form as the main call to action, and a price guide on the same page.
The numbers above are an illustration, so swap in your own. If you don’t know your current figures, say so, and set up basic tracking first. Our guide to conversion rate benchmarks helps you judge what a realistic target looks like, and measuring website ROI shows where to look for the numbers.
Pick one main goal and, at most, two secondary ones. A site that tries to do ten things well usually does none of them.
3. Your audience
Describe the one or two types of person who most often become customers. Skip demographics for their own sake. Say what they’re trying to do, what worries them and what device they’ll probably be on. “A homeowner in their forties, searching on their phone in the evening after a boiler has packed in” tells a designer more than “ages 35 to 55”.
4. Pages and structure
List the pages you think you need. For most small businesses that’s a homepage, a page per main service, an about page, a contact page and perhaps a page of reviews or case studies. Note any that must exist for a practical reason, such as a pricing page or a service-area page for each town you cover.
If you’re unsure, say that. A good designer will suggest a structure. What helps them is knowing what customers ask you most often, because those questions decide what the pages must answer. Our article on what a good small business website looks like gives a picture of the finished result to aim at.
5. Content: who writes it, and when
This is the part most people forget, and the one that delays more launches than anything else. Spell out:
- Who writes the words, you or the agency.
- Who supplies photos. Real pictures of your team and work almost always beat stock images.
- What you already have: logo, brand colours, fonts, testimonials, price lists.
- The date you’ll hand it all over.
Be honest about your time. If you can’t find three hours a week for a month, say so now and plan around it.
6. Features and technical needs
This is your requirements list. Keep each item as something you could check off: “online booking form that emails me and the customer”, “blog I can edit myself”, “WhatsApp button on mobile”. Also mention anything the site has to connect to, such as an email system, a booking tool or a customer database.
Three technical points are worth writing down even if you don’t understand them yet:
- Speed on mobile. Google’s Core Web Vitals are the standard measures of page experience. Its guidance is for the largest content to load within 2.5 seconds, for the page to respond to taps within 200 milliseconds, and for the layout not to jump around as it loads. Ask for these as targets.
- Cookies and privacy. If the site sets cookies that aren’t essential, such as analytics or advertising ones, the ICO’s guidance says you must tell people what they do and get their consent first. Put “compliant cookie consent” in the brief so it’s built in, not bolted on.
- Findability. If you want local customers to find you on Google, say which towns and services matter. That shapes page titles and structure from day one, which is cheaper than retrofitting it. Our overview of building a search-engine-friendly website explains the basics.
7. Look and feel
Show, don’t describe. Collect three or four sites you like and note one thing about each (“the clear pricing”, “the big phone number”). Add one or two you dislike and say why. Words like “modern” and “professional” mean something different to everyone, whereas examples don’t.
8. Budget
Give a figure or a range. Hiding it doesn’t get you a better price. It gets you quotes for wildly different things. If you say “around £3,000 up front” or “I’d like to spend a set amount each month”, the designer can tell you what’s realistic and what to leave for phase two.
It helps to know the two common pricing shapes: a one-off project fee, or a monthly plan that covers the build and ongoing care. Say which suits your cash flow. Our own web design plans are monthly: Starter is £120 per month, Growth is £170 per month and Smart is £560 per month. Whatever route you choose, ask what’s included after launch, such as hosting, edits and security updates, because those costs recur.
9. Timeline
Give a target launch date and the reason behind it: a trade show, a busy season, a new premises. A real reason helps the designer decide what to build first. Allow time for your own feedback rounds, since slow replies are the usual cause of a missed date.
10. People and sign-off
Name one person who makes final decisions. If three partners each give separate feedback, the project stalls. Say who the day-to-day contact is, how you prefer to communicate and how quickly you can usually respond.
A short brief you can copy
Here’s a skeleton. Fill each line in a sentence or two.
| Section | What to write |
|---|---|
| Business | What you do, where, for whom, and what sets you apart |
| Main goal | One sentence, with a number and a timeframe |
| Audience | The one or two people you most want to reach, and what they’re trying to do |
| Pages | Your must-have pages and anything you’re unsure about |
| Content | Who writes it, who supplies photos, what exists, hand-over date |
| Features | A checklist of things the site must do |
| Look and feel | Three sites you like, one you dislike, and why |
| Budget | A figure or range, and one-off or monthly |
| Timeline | Launch date and the reason for it |
| Decision-maker | One name, plus how you’ll communicate |
Paste that into a document, answer each row, and you have a working brief.
Mistakes that cost small businesses money
Writing a wish list instead of a goal. “Attractive, user-friendly, SEO-friendly” describes every website ever built. Say what the site should make happen.
Leaving out the budget. Covered above, but it’s the most common one, so it’s worth repeating.
Forgetting the content. A beautiful template with no words in it can’t launch. Agree who writes what, and by when.
Copying a competitor. Their site was built for their customers and their problems. Borrow ideas, not the layout.
Over-specifying the design. If you dictate every pixel, you pay for a designer and then ignore their expertise. Describe the problem and the outcome, and let them propose the solution.
Ignoring life after launch. Sites need updating, backing up and keeping secure. Put “ongoing support and content changes” in the brief so it’s priced from the start.
Writing 20 pages. A long brief hides what matters. If it runs past four pages, move the detail into an appendix and keep the front page for goals and constraints.
What to expect after you send it
A good agency won’t just return a price. It will ask questions, and some of them will challenge your assumptions. That’s a sign it has read the brief. Expect a call or meeting to go through goals and priorities, then a proposal that says what’s included, what’s not and what happens next.
When proposals arrive, check that each one answers your main goal, lists the pages and features you asked for, and states the timeline and the ongoing costs. If something in the brief is missing from the quote, ask why. It’s your document, and the proposal should follow it.
Our perspective
We read a lot of briefs, and the best ones aren’t the longest. They’re the ones where the owner has clearly thought about a single customer and a single outcome.
The briefs that worry us are the ones that say “we want a new website” and nothing else. That’s rarely about design. It’s usually a manual bottleneck somewhere else in the business: enquiries arriving by WhatsApp, email and phone, and nobody sure which ones got answered. The website is where that mess begins, so we like to ask about it early.
That’s one reason we built SmartFlowCRM, which brings WhatsApp and email into one place so leads don’t slip through. If your brief says “get more enquiries”, it’s worth also writing down what happens to an enquiry once it lands.
We’re a Derbyshire team, so we’d rather sit down with you and talk it through in person than have you wrestle with a template alone. And because we offer unlimited content changes, the brief doesn’t have to predict every sentence you’ll ever want on the site. Get the goal, audience and structure right, and the rest can be improved as you learn what your customers respond to.
Chris
Where we can help
If you’ve got a draft brief, or only a rough idea and a deadline, we can turn it into a clear plan with you. Our web design plans start at £120 per month, and if leads are getting lost between channels, our CRM plans start at £130 per month for Silver and £260 per month for Gold. Tell us your main goal and your budget, and we’ll show you how we’d approach it.
FAQ
How long should a website design brief be?
Two to four pages is plenty for a small business site. Put goals, audience and budget up front, and anything detailed, like a full feature list, in an appendix. If a supplier needs more, they’ll ask.
Should I put my budget in the brief?
Yes. A budget range lets the designer propose what’s achievable and suggest what to leave for a second phase. Without it you get quotes for very different projects, which makes them hard to compare.
What’s the difference between a design brief and a requirements document?
The brief explains what you want to achieve and for whom. The requirements list what the site must do, such as a booking form or mobile-friendly checkout. For a small site, one document with both parts works well.
Do I need a template?
A template helps you remember the sections, but it’s the answers that matter. Use the ten-row table above as a starting point, and write each answer in plain sentences rather than filling boxes with single words.
Can I write the brief if I don’t know the technical side?
Yes. Describe your customers, your goal and what the site must help people do. Leave the technology to the designer, and ask them to explain any choice they recommend in plain English.
Sources
- Design Buyers’ Guide, Design Council
- Website Design Requirements: How to Brief Your Design Team, Marker.io
- Web Vitals, web.dev
- Cookies and similar technologies, ICO
Recommended
- What does a good small business website look like?
- Design 101, Wireframes and Prototyping
- Website Content Audit: A Practical Guide for Small Businesses
- Web design 101, Web Design Jargon Busting
Related reading: Core web vitals: a practical guide · Conversion rate benchmarks for 2026 · Lead capture forms that generate quality leads
