Websites

Website Brief Template: The Questions to Answer and Mistakes to Avoid

Website Brief Template: The Questions to Answer and Mistakes to Avoid

A website brief is a two-to-four-page document answering the questions your web designer will ask anyway: what the site is for, who it’s for, what visitors should do on it, which content and features it needs, what it must connect to, how much you can spend and by when. A good brief describes goals and constraints, not a finished design. Below you’ll find a ten-section template to copy and the mistakes that make quotes for the same site vary several times over.

What is a website brief, and why write one?

A brief is a short description of the project from the client’s side. It says what problem the site should solve, who will use it, what you already have and what’s missing, and the budget and time limits you’re working within. It doesn’t need polished formatting or industry jargon. It needs to be specific.

A well-written brief gives you three things. First, comparable quotes: when several agencies get the same information, price differences reflect their approach, not the fact that each pictured a different site. Second, fewer revision rounds, because decisions about goals and scope are made before design starts. Third, a shared definition of success you can come back to after launch. If you’ve wondered why quotes for the same website can differ several times over, we cover that in how much does a website cost.

Brief, specification and proposal: what’s the difference?

Document Who writes it The question it answers When
Brief The client Why, for whom, what we have, what the constraints are Before asking for quotes
Proposal with scope The agency Exactly what we’ll build, for how much and by when After the brief and a call
Specification (workshop, discovery) The agency with the client How we’ll build it: structure, features, integrations, acceptance criteria At the start of the project

The most common misunderstanding is a client trying to design the site in the brief: drawing layouts, choosing colours and animations. That’s the agency’s job. Your advantage is what you know about your customers, your offer and your business, and that’s exactly what belongs on paper.

How do you write a website brief, step by step?

  1. Decide who decides. One person who signs off the project and has time to answer questions. A committee of five slows every stage.
  2. Gather data before you write. Customer questions from emails and calls, top pages in Search Console, where enquiries come from, the objections your sales team hears most.
  3. Answer the template questions below. Briefly, in bullet points. If you don’t know something, write “don’t know”. That’s information too.
  4. Set priorities. Mark each feature as must-have, should-have, could-have or won’t-have (the MoSCoW method).
  5. Attach materials. Logo, brand guidelines, copy, photos, logins, examples of sites you like.
  6. Send the same brief to a few agencies. Two or three, not ten. How to pick them and what to ask on the first call is in our guide on how to choose a web design agency.

The website brief template

Copy the questions below into a document and answer under each one. You don’t have to fill in everything, but every empty section is something the agency will ask about or, worse, something it will assume. First, a cheat sheet: the key question from each section and an example of a good answer.

Section Key question Example of a good answer
1. Company and goal What should change because of the site? “15–20 heat pump installation enquiries a month in our region; today we get 4”
2. Audience Who buys, and what do they ask before buying? “Homeowners; they ask about cost, grants and installation time”
3. Competitors Why do customers choose you? “Our own service team, replies within 24 hours, 300 reviews”
4. Structure and content Who supplies copy and photos, and when? “We write the copy ourselves by 15 January; we have project photos”
5. Features What must work on day one? “A form with a heating-output calculator; the rest can wait”
6. SEO and current site What earns traffic today and must not disappear? “The grants guide, 40% of clicks from Google”
7. Integrations Where should form and order data go? “Leads to the CRM, invoices to our accounting software”
8. Look and brand What stays from the current identity? “Logo and colours stay, everything else gets a refresh”
9. Technical and legal Who controls the domain and hosting? “The domain is ours; hosting sits with the previous developer”
10. Budget and timing What can you spend, and is the date fixed? “A range for the build and for year-one maintenance; live before the March trade show”

The examples are made up, but they show the level of detail that helps.

1. Company and project goal

  • What does the company do? Describe it in two or three sentences, the way you would to a customer on the phone.
  • Why now: a new business, a redesign, a rebrand, a new service, problems with the current site?
  • What is the site’s main goal? Pick one: enquiries, sales, bookings, recruitment, credibility before a sales call.
  • How will you measure success in 6–12 months? Enquiries, conversion rate, organic traffic, sales.
  • What single action should a visitor take on the site?

2. Audience

  • Who makes the buying decision, and who uses the product or service?
  • What do customers ask before buying? Write the questions down in their words.
  • What worries them, and what holds them back?
  • Which devices do they use? If you have Google Analytics, check the share of mobile.
  • Which languages and markets do you serve?

3. Competitors and differentiators

  • List 3–5 competitors with their URLs. What do they do well, and what annoys you about them?
  • Why do customers choose you? Ideally in quotes from reviews or conversations.
  • What proof do you have: projects, reviews, certifications, numbers, awards, well-known clients?

4. Structure and content

  • Which pages or page types do you expect? A list is enough: home, services, case studies, blog, contact.
  • Who will write the copy, and by when? Do you need a copywriter?
  • Do you have photos and video, or do you need a shoot or animation?
  • Which content from the current site moves across, and what gets deleted?
  • Are you planning a blog or guides? Who will write them, and how often?

5. Features

  • Forms: which fields, where do submissions go, who replies?
  • Calculator, configurator, bookings, online payments, shop, customer accounts, search, filters, chat?
  • Languages: how many, and will content be translated or written separately?
  • Give each feature a priority: must, should, could, won’t.

6. SEO and the current site

  • The current site’s address, the platform it runs on and a list of logins: domain, hosting, Search Console, Google Analytics.
  • Which pages bring traffic and enquiries today? A Search Console export for the last 12 months is enough.
  • Which searches do you want to be found for? Do you work locally and have a Google Business Profile?
  • Do you care about appearing in AI answers such as ChatGPT or Google AI Overviews?

This section saves the most money. If URLs change during a redesign, each one needs a 301 redirect to its new equivalent, as Google’s guidance on site moves with URL changes explains. We describe how to plan it on our page about website migration without losing SEO.

7. Integrations and data

  • CRM, newsletter, booking system, ERP, stock management, invoicing software?
  • Payments (for example Stripe, PayPal or local methods) and shipping (couriers, parcel lockers)?
  • Analytics and ads: Google Analytics, Google Ads, Meta pixel, session recording tools?
  • Should anything run automatically, for example a form lead going into the CRM and triggering a welcome email?
  • Who owns the data, and where must it be stored?

For shops and sites that take payments, think about invoicing early. In Poland, for example, the national e-invoicing system KSeF became mandatory for the largest companies on 1 February 2026, for other taxpayers on 1 April 2026 and will cover the smallest firms from 1 January 2027 (ksef.podatki.gov.pl). An invoicing integration written into the brief is cheaper than one bolted on after launch.

8. Look and brand

  • Do you have a vector logo, brand guidelines, fonts and colours? Is a rebrand planned?
  • Name 2–3 sites you like, with one sentence each on what exactly you like.
  • What do you definitely not want?
  • Are you thinking about animation, video or 3D? What would they be for?

9. Technical, legal and maintenance

  • Who is the domain registered to, and who has access to hosting and email?
  • Privacy (GDPR): who prepares the privacy policy, and which consents do forms need?
  • Cookies: do you run Google ads and need Google Consent Mode?
  • Accessibility: under the European Accessibility Act, e-commerce services in the EU have had to meet accessibility requirements since 28 June 2025, with micro-enterprises exempt; in Poland this is the Polish Accessibility Act (gov.pl). WCAG 2.2 is the usual benchmark.
  • Performance: do you require Core Web Vitals thresholds, meaning LCP up to 2.5 s, INP up to 200 ms and CLS up to 0.1 (web.dev)?
  • Who will update the site and run backups after launch? Do you need ongoing technical support?

10. Budget, timing and decisions

  • What is your budget range for the build, and separately for the first year of maintenance?
  • Is the deadline fixed (a trade show, a campaign, a season) or flexible? Why that date?
  • Who signs off each stage, and how long do you need to reply?
  • What kind of engagement do you want: a fixed project, phases, ongoing support?
  • Should copyright in the design and code transfer to you?

Example: a weak brief and a strong one

Topic Weak brief Strong brief
Goal “We need a modern, responsive website” “The site should bring in 15–20 heat pump installation enquiries a month in our region”
Audience “Anyone looking for heating” “Owners of detached houses; they mostly ask about cost, grants and installation time”
Features “Everything our competitors have” “Must: a form with an output calculator. Should: case studies filterable by town. Won’t: a shop”
Content “We’ll provide the content” “We’ll write the service pages by 15 January and need help with the guides”
Budget “Please send a quote” “A range for the build and a separate one for a year of support”
Deadline “As soon as possible” “Live before the trade show on 10 March; the second language can follow later”

Common website brief mistakes

  • Describing the look instead of the goal. “Modern, with animations” says nothing about why the site exists.
  • No budget. Without a range the agency guesses, and quotes swing from a modest template to a full-blown system. Sharing a budget doesn’t inflate the price; it lets the agency fit the solution to the money.
  • A wish list without priorities. Thirty features of equal weight means none of them matters.
  • “We’ll provide the content” with no date. The most common cause of delays we see. The finished design waits weeks for copy.
  • Ignoring the current site. Nobody checks what earns traffic, the new site launches with different URLs and organic traffic drops.
  • Integrations discovered at the end. A CRM, invoicing tool or booking system added after launch costs more than one planned from the start.
  • No logins. A domain registered to a previous developer, or a hosting password nobody knows, can hold up launch for weeks.
  • Copying competitors. A brief that says “we want it like X” leads to a site that doesn’t stand out.

What happens after you send the brief?

For us a brief is the start of a conversation, not a form to tick off. We read it and send back clarifying questions, usually about the goal, feature priorities and the current site. Then comes a short call where we agree what’s genuinely essential for launch. Only then do we prepare a quote with a written scope, stages and timeline, so it’s clear what you get and what’s left for later. For larger projects we start with a workshop that produces the specification.

No time for a full brief? Answer at least the key question from each section in the cheat sheet above. Ten sentences are enough to start a useful conversation about designing your website.

Got a brief ready, or want to work through these questions with us? Get in touch and paste your answers into the message. We’ll come back with clarifying questions and then a quote with a written scope.

Frequently asked questions

What should a website brief include?

The site’s goal and how success is measured, the audience, competitors and differentiators, structure and content, a prioritised feature list, details of the current site and SEO, integrations, brand guidelines, technical and legal points, plus budget, deadline and a single decision-maker. Two to four pages of specific answers is enough.

How long should a website brief be?

Usually two to four pages. Being specific matters more than length: one measurable goal, feature priorities, content delivery dates and a budget range. A thirty-page wish list makes quoting harder rather than easier.

Should I include a budget in the brief?

Yes. A budget range lets the agency fit the solution to what you can spend and lets you compare quotes for a similar scope. Without one, quotes swing from a simple template to a complex system, because every agency assumes something different.

What is the difference between a brief and a specification?

The client writes the brief, answering why the site is needed and who it’s for. The specification comes later, written with the agency, and describes how the site will be built: structure, features, integrations and acceptance criteria.

What about my current website when redesigning?

Include Search Console access or an export of the pages that bring traffic and enquiries. Those URLs need to be kept or 301-redirected to their new equivalents. Skipping this step is the most common reason organic traffic drops after a new site launches.

Can I send the same brief to several agencies?

Yes, and you should, because the same brief produces comparable quotes. Two or three agencies is a sensible number. Compare scope, stages and the questions they ask as well as the price. Good questions after reading your brief say a lot about an agency.

Sources

  1. Google Search Central – Site moves with URL changes
  2. Google Search Central – SEO Starter Guide
  3. Google Tag Platform – Consent mode overview
  4. gov.pl – Polski Akt o Dostępności: usługi handlu elektronicznego
  5. Ministerstwo Finansów – KSeF: etapy wdrożenia
  6. web.dev – Web Vitals
  7. W3C – Web Content Accessibility Guidelines (WCAG) 2.2

Need help with this?

We design and code company websites from scratch — no off-the-shelf templates, built for conversion, speed and visibility in Google and AI search.