How to brief a web design agency (and not waste £10k)

A friendly guide to writing a brief that actually gets you a good website. What a web design agency needs from you, what to leave out, and how to spend your money once instead of twice.

If you are about to spend real money on a website, the brief is the part that decides whether you get a good one. We have read hundreds. The best ones are short and clear about the goal. The painful ones are long lists of features with no sense of why. This is a plain guide to how to brief a web design agency, written from the other side of the table, so your money does the job you wanted.

A brief is not a spec you have to get perfect. It is a way to tell a web design agency what success looks like, so we can argue with you early, while changes are free, instead of late, when they cost £10k. Get this part right and the rest of the project is calm.

Lead with the goal, not the feature list

The single most useful line in any brief is a sentence about the job the site has to do. Win more enquiries. Sell tickets. Stop people phoning to ask the same five questions. Look credible enough to close a deal you already started.

Notice that none of those mention a slider, a parallax header or a mega menu. Features are answers. The goal is the question. If you hand us a wishlist of features, we build the wishlist. If you hand us the goal, we build the thing that hits it, and we will often talk you out of half the wishlist on the way. That conversation alone is worth having.

Describe your customers and what you want them to do

Tell us who the site is for, in human terms. A plumber chasing local emergency work has a very different site to a consultancy selling a £30k retainer. Same web, completely different decisions.

Then name the one action you want a visitor to take. Call, book, buy, fill in the form, download the guide. A site that wants people to do everything tends to get them to do nothing. One clear action per page keeps the whole thing honest.

Bring examples, and say why

Three or four sites you like will tell us more than three paragraphs of adjectives. The "why" matters more than the "what". "I like this because the booking is two clicks" is useful. "I like this because it feels premium" is a start, but we will ask what premium means to you.

Bring a couple you dislike too. Knowing what makes you wince saves a whole round of revisions. None of this means we copy them. It means we can see your taste before we design, instead of guessing and reworking.

Be honest about budget

This is the one people hate, so here is the honest case for it. A budget is not us finding the ceiling and pushing to it. It is the only way we can scope the right thing. A £3k brief and a £15k brief are different projects, and we would design them differently from day one.

If you hide the number, you get a quote built on guesses, and usually two rounds of trimming to reach a figure you could have told us at the start. Give a range. We will tell you what fits inside it, and we will be straight with you if your goal needs more than you have, or less. Our guide to what a UK website costs gives you sensible ranges to anchor on, and the web development page shows how we scope a build.

Get your content ready

Here is the quiet truth of this industry. Most projects do not run late because of design or code. They run late waiting for content. The copy that never arrives. The team photos still on someone's phone. The product list that lives in three different spreadsheets.

You do not need it all polished before you start. You do need a plan for who is writing it and by when. If you would rather we wrote it, say so in the brief and budget for it. Either way, deciding this up front is the single biggest thing you can do to keep the project on time.

Agree how you will measure success

Decide, before we build, what a good outcome looks like in numbers. More enquiries a month. A booking rate that goes up. Fewer "how do I" emails. If success is only ever a feeling, nobody can tell whether the spend worked.

This also shapes the build. A site measured on enquiries gets tracking and a fast form. A site measured on bookings gets the booking flow polished above all else. Tell us the number you care about and we will build towards it.

Name the practical things

The boring details prevent most of the friction. Put these in the brief and the project runs itself.

• The deadline, and why: "before our trade show in March" is far more useful than "soon". A real reason lets us plan around it.
• Who signs off: one named decision-maker. Design by committee is where good projects go to die.
• What you are providing: logo, brand colours, copy, photos, access to your domain and hosting. List what exists and what does not.
• What you already have: an old site, analytics, a CRM, booking software. We can often keep and connect these instead of starting from scratch.

What a good brief contains

If you want a checklist to write against, here it is. You do not need every line, but the more of these you can answer, the sharper your quote.

• The goal of the site in one sentence
• Who your customers are and the one action you want them to take
• Three or four sites you like, and why
• A budget range, given honestly
• Who is writing the content, and by when
• How you will measure success
• The deadline and the reason behind it
• The one person who signs off
• What you are providing and what you need from us
• Any tools or accounts you already use that the site should connect to

Red flags in an agency

A brief works both ways. While you are sizing us up, watch for these.

• Guarantees of page-one rankings: nobody can promise Google's results. Anyone who does is selling you something they cannot deliver.
• No questions back: if an agency quotes off your brief without asking a single thing, they are guessing. Good ones push back before they price.
• They own your site and domain: you should own your domain, your hosting account and your content. If leaving means losing everything, that is a trap, not a service.

If you are still weighing up what to build the site on, our guide to WordPress vs Webflow vs headless covers the trade-offs in plain terms.

FAQ