A folded sheet of paper standing like a tent, orange on the inside.

Your web agency brief: what to include, with a template

We receive briefs in all shapes and sizes, from three lines in an email to a thirty-page presentation. Length tells us almost nothing about how useful the quote will be. What matters is whether the agency understands why the website is being built. That's what the brief is there to explain.

A requirements specification describes what needs to be built. A brief explains why, who it's for and what needs to improve. It comes first, and it determines whether the agency truly understands the project or simply responds to it.

The briefs that deliver the best results almost always have one thing in common: they're specific, start with the goal and are honest about what the client doesn't yet know.

What is a brief?

A brief is a short document that outlines the project before work begins: the background, goals, audience, constraints and deliverables. It gives the agency what it needs to recommend the right solution and work out the cost.

In a web project, the brief is the first document you send. For smaller projects, it can lead straight to a quote. For larger ones, it may lead to an initial meeting and a discovery phase.

Brief or requirements specification?

You often need both, but they serve different purposes.

  • The brief explains why and who it's for. It's short, one to three pages, and is written before you know exactly what needs to be built.
  • The requirements specification explains what and how. It's longer, more detailed and is written once the goals and workflows are clear.

Many people skip the brief and go straight to the requirements specification. That puts features ahead of goals, leaving the agency to price a solution without knowing what problem it needs to solve. It also gives the agency no opportunity to draw on its expertise and suggest alternatives.

What should the brief include?

Eight sections are enough for most web projects.

1. Background

Who you are, what you sell and why you're getting in touch now. Two or three sentences are enough. The agency needs to understand the context, not your entire company history.

2. Goals

The most important section. What should improve once the project is complete? More enquiries, fewer calls to customer service, a higher conversion rate in your online shop, a website your marketing team can update themselves?

A goal is measurable. "30 per cent more quote requests" is a goal. "A responsive website" is not.

3. Audience

Who will use the website, and what do they want to do there? Describe your two or three most important visitor groups and what you think they're looking for. This shapes the structure, content and design more than anything else.

4. What's working now

What should you keep from your current website? Pages that rank well on Google, forms that convert, features users value. These are often overlooked, and losing them can be costly.

5. Workflows and systems

What should happen when a visitor takes an action? Where does an enquiry go, and which systems might the website need to connect to? CRM, ERP, booking, newsletters? Integrations are often the most expensive part of a web project, but they can also make your internal processes significantly more efficient. A simple outline is enough, but you need one if you use external systems.

6. Constraints

Budget, target launch date, legal requirements such as accessibility and GDPR, and any technical constraints set by IT. Be honest about the budget. An approximate range lets the agency suggest something you can afford, rather than guess.

7. Who makes the decisions

Who is the main contact, who makes the decisions, and who else needs to be involved? A project with a clear owner moves faster and delivers better results than one where everyone contributes but no one decides.

8. What you don't know yet

The most underrated section. Be upfront about what's unclear: we don't know if we need an online shop, we haven't chosen a CMS, we're unsure how enquiries should be handled, we haven't decided which CRM system to switch to.

That's not a weakness. It helps the agency see where it can help, and where a discovery phase may be needed before it can give you a fixed price.

What to leave out of the brief

  • A list of features with no clear purpose. "Slider, chat, news feed" says nothing about what the website needs to achieve.
  • Detailed designs. Examples of websites you like are helpful, ideally with a sentence explaining why. Finished mock-ups tie the agency's hands before it understands the project.
  • Everything you can think of. A brief that tries to cover everything becomes as hard to read as a requirements specification. Anything that doesn't affect the goals, audience or budget can wait.

A template to get you started

Copy and fill it in. Keep each section short.

What happens next?

A good brief does three things for you.

  1. It gives you responses you can compare. When every agency works from the same goals and constraints, you can properly compare the proposals, not just the prices.
  2. It gives you better questions in return. An agency that understands the project asks questions about your needs. One that doesn't sends a standard quote.
  3. And it shows you when a discovery phase is needed. If the section on what we don't know yet is long, it's usually cheaper to work through those questions first than to ask for a fixed price straight away.

Frequently asked questions

Planning a public procurement for a new website?

Our guide Public procurement for websites takes you from the brief to the requirements specification, with a checklist covering ten areas. Download the guide