Most disappointing website projects were not doomed by bad designers. They were doomed by a vague brief. When an agency does not truly understand what you are trying to achieve, they fill the gaps with guesses — and every wrong guess costs a revision, a delay and a slice of goodwill on both sides. Learning how to brief a web design agency properly is the single highest-leverage thing you can do before a project starts, and it barely costs you anything but thought.
Why a good brief matters more than you think
A brief is the shared map. It aligns your expectations with what the agency builds, so that when the first designs land, you are reacting to something aimed at the right target rather than a shot in the dark.
The cost of a poor brief shows up as scope creep. You did not mention you needed a booking system, so it was not quoted or built, and now it is a mid-project change request. You never defined the audience, so the tone is wrong and everything gets reworked. Multiply these across a build and a project that should have taken eight weeks stretches to sixteen, with a bill to match.
A good brief does the opposite. It lets the agency quote accurately, plan properly and design with confidence. It protects you from surprise costs and protects them from endless "can you just change" requests. Everyone moves faster.
What to include in the brief
You do not need a beautiful document. A clear one will do. Cover these areas.
1. Your business and what you actually do
Start with context. What does your business do, who are your customers, what makes you different from competitors, and where does the website sit in how you win work? An agency that understands your business makes better decisions on every page.
2. The goals of the website
Be specific about what the site is for. "A new website" is not a goal. "Generate more qualified enquiries from local homeowners" is. "Sell our products directly and reduce phone orders" is. "Look credible enough to win larger B2B contracts" is. Name the one or two things that matter most, because design decisions flow from goals.
3. Your audience
Describe who you are trying to reach. A site for time-poor facilities managers looks and reads differently from one for young consumers buying a gift. Include what they care about, what reassures them, and what might put them off. If you have different audience segments, say which is the priority.
4. Must-haves and functionality
List the features you genuinely need: contact forms, online booking, e-commerce, a customer login area, a blog, integration with your CRM or accounting system, multi-language, accessibility requirements. Separate the must-haves from the nice-to-haves — that distinction is gold for a quote.
5. Examples you like and dislike
Show three to five websites you admire and, importantly, say why. Is it the clean layout, the tone, the photography, the ease of navigation? Also show a couple you dislike and why. This gives the agency a visual vocabulary far faster than paragraphs of description. They do not need to be competitors.
6. Content: who is writing it
Content is the single most common cause of delay. Be honest: do you have copy and photography ready, or do you need help? If the agency is writing content or sourcing images, that must be in scope from the start. A gorgeous design with placeholder text cannot launch.
7. Budget and timeline
Share a real budget range. Agencies are not trying to spend all your money; they are trying to recommend the right solution, and they cannot do that blind. A £4,000 budget and a £20,000 budget lead to genuinely different, both valid, approaches. Hiding the number wastes everyone's time on a proposal that misses. Likewise, share any real deadline — a trade show, a product launch, a lease starting — and say if it is firm or flexible.
8. How you will measure success
Six months after launch, how will you know it worked? More enquiries, a higher conversion rate, more online sales, shorter sales cycles, fewer support calls? Naming the success metric keeps the whole project honest and gives you both something to aim at.
Common briefing mistakes to avoid
Confusing "looks nice" with "works"
Aesthetics matter, but a beautiful site that does not convert is a failure. Brief around outcomes, not just appearance.
Hiding the budget
The most common mistake. It does not get you a better price; it gets you a proposal built on guesswork.
Too many decision-makers, no owner
If five people must approve everything and none of them owns the project, feedback contradicts itself and nothing gets signed off. Nominate one decision-maker who consolidates internal opinions before they reach the agency.
Vague feedback later
"I don't love it" is not actionable. "The headline doesn't speak to our audience and the photos feel too corporate" is. Good briefing habits carry through the whole project, not just the start.
Skipping the content question
Assuming content will "sort itself out" is how projects stall for months. Decide upfront who writes and supplies what.
Questions a good agency should ask you
A brief is a conversation, not a one-way document. A good agency will push back and probe. If they do not ask questions like these, be wary:
- What does success look like in numbers?
* Who is your ideal customer, and what stops them buying today?
* What is working and not working on your current site?
* Which of these features are genuinely essential versus aspirational?
* Who owns sign-off, and how quickly can you give feedback?
- Is your budget fixed, and what does it need to cover?
These questions are a sign of an agency that wants the project to succeed, not just to start the invoice clock.
A simple brief template outline
You can draft this in a single document in under an hour:
-
About us — what we do, who we serve, what makes us different.
-
Project goals — the one or two outcomes that matter most.
-
Target audience — who we are reaching and what they care about.
-
Must-have features — essentials, then nice-to-haves listed separately.
-
Look and feel — three to five example sites we like and dislike, with reasons.
-
Content — what we have ready, what we need help with.
-
Budget range — a real number or bracket.
-
Timeline — any fixed dates and whether they are firm.
-
Success metrics — how we will judge it in six months.
-
Decision-maker — who signs off and how fast we can respond.
Fill that in and you are ahead of the overwhelming majority of clients an agency ever meets.
How a good brief saves you money
Every hour an agency spends guessing is an hour you pay for, either directly or in delay. A clear brief compresses the discovery phase, produces an accurate fixed quote, and slashes the number of revision rounds. Projects that start well tend to finish on time and on budget. Projects that start vague tend to overrun on both. The brief is where that fork in the road is decided.
Where NetTrackers fits
We would rather spend an extra hour understanding your business than a week rebuilding the wrong thing. Our web design and development process starts with a proper discovery conversation, so the brief becomes a shared plan rather than a wish list. One team, one strategy, and a fixed price so you know the cost before we begin.
Not sure how to shape your brief? Book a free strategy call and we will help you define goals, scope and success — no contracts, month-to-month, and a free website review included.
Frequently asked questions
How long should a website brief be?
Long enough to be clear, short enough to be read. A focused two to four pages covering goals, audience, features, budget and timeline beats a twenty-page document nobody finishes.
Do I need to know exactly what I want before briefing an agency?
No. You need to know your goals and constraints. A good agency helps translate those into the right solution — that is part of what you are paying for.
Should I really share my budget?
Yes. It is not a negotiation trap; it lets the agency recommend the right approach and gives you an accurate quote instead of guesswork.
What if I don't have content ready?
Say so upfront. Content is the most common cause of delay, so agreeing who writes and supplies copy and images at the briefing stage keeps the project on schedule.
Should the brief include specific competitor or example sites?
Yes — it's one of the most useful things you can add. Two or three sites you admire (and one or two you dislike), with a sentence on why, tells an agency more about your taste and goals than a page of adjectives. Be clear whether you're pointing at the look, the functionality, or the underlying strategy, since a site can be worth referencing for one and not the others. Concrete examples turn subjective words like "clean" or "premium" into something a designer can actually act on, and they surface mismatched expectations early — before they cost you a redesign.