How to brief a web design agency properly

A good brief is one of the most underrated tools in a web project. It's the document that decides, before any contracts are signed, whether the project will run smoothly or stall in the third week with everyone confused about what they agreed to.

Most briefs we receive land somewhere between thin and overstuffed. Either three bullet points on an email, or a 40-page document full of inherited corporate language that nobody on either side will read again. The useful brief sits in the middle, and it's surprisingly short.

What a brief is actually for

A brief has one job. It gives the agency enough information to quote accurately, plan sensibly, and ask the right follow-up questions before the project starts.

It is not a specification. You're not writing the website, you're describing the situation the website needs to solve. The agency's job is to take that and translate it into a structure, a design, and a build.

This distinction matters because the most common briefing mistake is to write the answer instead of the question. If you've already decided you need a homepage with seven sections, a parallax hero, and a testimonial carousel, you haven't briefed the agency, you've ordered a meal. A good agency will gently push back and ask what you're trying to achieve.

The bits that actually matter

A useful brief covers six things, and in our experience that's usually all it needs to cover.

The first is who you are and what you do, in the words you'd use to describe it to someone at a dinner. Skip the corporate boilerplate. The agency needs to understand the business in plain English before they can write or design anything for it.

The second is who the website is for. Not "everyone", not "B2B decision-makers", but the actual people who will be on the site making actual decisions. The more specific you can be, the better the design and copy will land.

The third is what the website needs to do. This is the commercial bit. Generate enquiries, support a sales team, recruit, sell directly, build credibility for partnerships, all of the above. If the site has a primary job, name it. If it has three jobs, rank them.

The fourth is what's wrong with what you've got now. The honest list. Pages that don't convert, sections that nobody updates, things you're embarrassed to send people to. This tells the agency what to fix and what to keep.

The fifth is your budget, or at least a range. We'll come back to this because it's the section most clients agonise over.

The sixth is your timeline, including any fixed dates. Conferences, product launches, end-of-financial-year deadlines, anything that the project has to land before. Honest constraints help the agency plan around them.

Why hiding the budget hurts you

A lot of clients leave the budget out of the brief on purpose. The thinking is that it'll get them a more competitive quote, or that the agency will tailor the proposal to what they think the client can afford.

In practice, the opposite happens. Without a budget, the agency has to guess what scope to propose, and they'll usually guess wrong in one of two directions. They'll either propose something that's far too expensive and get rejected, or they'll propose something that fits an imagined budget that turns out to be lower than what you actually had.

A budget range, even a wide one, lets the agency design a proposal that fits. "Somewhere between £10k and £20k depending on what you recommend" is enormously more useful than silence. You're not committing to spend the top of the range, you're giving the agency the information they need to make a sensible recommendation.

Things to leave out

Briefs get bloated when clients try to be helpful by including everything they can think of. A few things genuinely don't help and can confuse the conversation.

Long lists of competitor websites with no commentary on what you like about them. The agency can find competitors. What they need is to know which specific things resonate with you and which don't.

Detailed feature lists copied from another site. These usually arrive as "we want a hero with a video background, a sticky header, mega menus, a blog with categories, an interactive map, a custom-built calculator, a member portal, and a chatbot". Some of those might be right, most won't be, and presenting them as requirements forces the agency to either quote for things you don't need or push back before the conversation has started.

Mood boards with 200 images on them. A few carefully chosen references with a sentence on each is more useful than a Pinterest dump.

Brand guidelines, unless they're current and being followed. Old guidelines that the business no longer uses just create confusion about what the agency is supposed to honour.

The bit most people forget

The single most useful section in a brief is also the one most clients leave out. It's the section that describes the people and process on your side.

Who's the day-to-day contact? Who has final sign-off? Who else needs to be consulted before decisions are made? Are there stakeholders who will be brought in late and might overturn earlier decisions? Is there a content team, or will copy come from whoever has time?

Agencies that have done this for a while know that the project's success depends almost as much on these answers as on the design or build. The pattern we see most often is that projects run smoothly when there's one clear decision-maker, and they drift when sign-off is unclear or when stakeholders appear in week six with opinions that should have been heard in week one.

If you can flag this stuff in the brief, the agency can build a process around it. If you can't, ask yourself who the real decision-maker should be, and put their name in the document.

A useful brief in practice

Most of the best briefs we've received have been two to four pages. Long enough to give us real context, short enough that we'll actually re-read them in week three. They were written in plain English, included a budget range, named the decision-maker, and were honest about what wasn't working with the current site.

The brief that arrived with the most apologetic email ("sorry, this is probably too short") is often the one that produces the smoothest project. The brief that arrives as a 60-page Word document inherited from a procurement template usually signals a project that's going to be heavy going for everyone.

If you're not sure whether your brief is too thin, the test is whether an agency could quote a sensible price from it. If they couldn't, add more. If they could, stop writing and send it.

What happens after you send it

A good agency will read the brief, then come back with questions before they quote. The questions are part of the value. They're how the agency turns your description of the situation into a plan for solving it.

If an agency quotes against your brief without any follow-up questions, that's worth noting. Either the brief was unusually complete, or the agency is treating the project as a transaction rather than a conversation. The second one usually shows up later in the project as misunderstandings that should have surfaced earlier.

If you'd like to see how we use a brief in practice, our process page walks through what happens after a brief lands with us, and our web design service page covers what's typically included in a project. If you're earlier in the conversation and trying to work out what to budget, our recent post on how much a website actually costs in 2026 is the natural next read.