The single biggest cause of web design projects going over budget, over time, or simply not landing well is a vague brief. Not bad designers, not difficult clients, vague briefs. When you brief a designer without clear goals, examples, or constraints, they fill the gaps with their own assumptions, and the result is rounds of revisions, growing frustration on both sides, and a website that ends up being a compromise rather than a solution.
A solid brief does not need to be a lengthy document. It needs to answer the questions that shape every design decision. It is not about telling the designer what the website should look like. It is about telling them what the website needs to do, for whom, and why.
Start with your business, not the website
Before you think about pages, colours, or features, a designer needs to understand your business: not just what you sell, but why customers choose you over the alternatives, what problems you solve, and who your best customers actually are. Answer these questions before your first conversation:
- What does your business do? In one or two sentences, as simply as possible.
- Who are your ideal customers? Not everyone, be specific. Age range, location, situation, what they are worried about when they come to you.
- What do you do better than competitors? Why should someone choose you?
- What is the one thing you want the website to achieve? More enquiries, online bookings, product sales, or building credibility. Pick the primary goal.
If you cannot answer these questions clearly, that is worth knowing before the project starts. A website built without a clear audience and goal is decoration, not a business tool.
Define the primary action
Every effective business website has a primary action it wants visitors to take: filling in a contact form, calling a phone number, booking a slot, buying a product, or downloading a lead magnet. Most designers will ask you this, but knowing your answer before they do means the conversation starts in the right place. Secondary actions matter too. Someone not ready to enquire yet might want to read a case study or check your service area, and these secondary paths should be planned for, not bolted on later.
List the pages you need
You do not need to design the site structure yourself, but a rough list helps the designer understand the scope. A simple service business might need a home page, services (one page or separate pages per service), an about page, a contact page, and testimonials or case studies. An ecommerce business needs product pages, a checkout flow, and a returns policy. Think through what a visitor would need to find to feel confident contacting or buying from you. That is your page list.
Share examples of sites you like, and why
This is one of the most useful things you can give a designer. Find three to five websites, ideally in adjacent industries rather than your direct competitors, that have a look and feel you respond to, and explain what specifically you like about each one. Saying "I like this one" tells a designer very little. Saying "I like the way this site uses white space and has a clear hierarchy so I always know where to look next" tells them a great deal. Share examples of what you do not want too. You do not need to know design terminology: "this feels too corporate and cold" is more useful than trying to describe specific visual techniques.
Brand assets and existing guidelines
If you already have a logo, brand colours, or fonts, share them. If you have none of these things, say so explicitly, since the designer may need to factor in brand creation as part of the project scope. Share your logo in the original file format, usually .svg or .ai, rather than a screenshot or a low resolution PNG. A designer who starts with a blurry logo image has to recreate or work around it, which adds time and cost.
Technical requirements
Think through any specific technical needs before the conversation: whether you need a content management system and who will update the site, whether you have an existing domain and hosting, what integrations you need (booking systems, CRMs, email marketing, payment gateways), whether you have existing content or need copywriting, and whether accessibility requirements apply. You may not know all the answers yet, and that is fine. Flag them as open questions rather than leaving them out, and a designer who knows what to expect can raise them at the right time.
Timeline, budget, and competitor context
Be honest about your timeline. If you have a hard deadline, a product launch, an event, a grant application, say so, since a rushed brief costs more or produces worse results, usually both. Sharing your budget is one of the most productive things you can do at the brief stage. It lets the designer tell you immediately whether your expectations are realistic and, if not, what is achievable within your number. Many clients avoid sharing their budget for fear of being charged the maximum, but the opposite is more often true: a designer who knows the budget can design an approach that fits it rather than proposing something that does not.
Share three to five competitor websites too, not so the designer can copy them, but so they understand the visual landscape you operate in. In some industries, standing out from a sea of similar sites is the goal. In others, credibility comes from looking like a peer of established players, and the designer cannot make that call without knowing what the market looks like.
What makes a brief go wrong
The most common brief failures are:
- No defined audience. Everyone, or people who need our service, is not an audience. The more specific you are, the more targeted the design can be.
- No primary goal. A site that tries to do everything equally ends up doing nothing particularly well.
- Vague aesthetic direction. Modern and professional describes almost every business website ever built. Share examples instead.
- Missing technical constraints. Discovering mid-project that the site needs to integrate with a legacy system adds time and cost.
- Scope creep after sign-off. If you add pages, features, or sections after the project has started, expect the quote to change. The brief is what the quote is based on.
A one-page brief template
Business: what you do and who for, in two sentences. Goal: the one thing the website should achieve. Audience: who your ideal customer is. Pages: a rough list of sections needed. Examples: three sites you like, with a note on why. Assets: logo as a vector file, brand colours, fonts. Technical: CMS needed, integrations, existing hosting. Timeline: ideal launch date, hard deadline if any. Budget: your range.
Briefing for an AI-assisted or rapid-build project
If you are working with someone who uses AI tools to accelerate the build, which is increasingly common, the brief matters even more, not less. AI-assisted design can produce a working site quickly, but it follows the direction it is given. A vague brief produces a generic site at speed. A specific brief produces something that actually reflects your business. See our guide on custom builds versus off-the-shelf platforms for more on how this trade-off plays out in practice.
What happens after the brief
Once you hand over a brief, a good designer comes back with questions. That is a good sign, not a bad one: it means they are thinking about the project rather than jumping straight into visuals. Expect them to clarify your audience, push back on anything vague, and confirm technical constraints before they start. If a designer accepts a vague brief without asking a single question and immediately presents you with designs, treat that as a warning sign. Our guide on how to choose a web designer covers the earlier part of this decision, before you get to briefing stage.
Frequently Asked Questions
What should I include in a web design brief?
Your business and audience, the purpose of the site, specific pages needed, examples of sites you like, your brand assets, technical requirements, timeline, and budget. The more specific you are on goals and audience, the better the outcome.
How long should a web design brief be?
It does not need to be long. One to two pages covering the essentials is usually enough for a small business site. The goal is clarity, not length. A brief with ten clear bullet points beats a five-page document full of vague aspirations.
Do I need to know exactly what I want before briefing a web designer?
You do not need every detail worked out, but you should know your goals, your audience, and the main action you want visitors to take. A good designer helps fill in the gaps, but they cannot define your business objectives for you.
Should I share my budget with a web designer?
Yes. A designer who knows your budget can tell you immediately whether it is realistic, or suggest what is achievable within it. Hiding your budget to avoid being overcharged usually results in proposals that miss the mark in both directions.
Before you start
Take the time to prepare a proper brief before your first conversation with a designer. It is the single most valuable hour you can spend on the project, and it shapes everything that follows. If you want a second pair of eyes on your brief before you send it, get in touch.
