How to Write a Website Brief That Gets Comparable Quotes
Quotes are only comparable when every agency prices the same thing. A good website brief makes that possible: a few pages that describe what the site must achieve, which page types and features it needs, who supplies the content, which quality targets it must meet, who owns what – and, just as important, in what format you want the answer. Below is a structure you can copy and fill in.
Why quotes for "the same website" differ so much
With a vague brief, each agency fills the gaps with its own assumptions. One prices a template with your logo, another a custom design. One includes texts and translations, another expects you to supply them. One includes redirects from your old site and a year of updates, another does not mention them. The totals can differ dramatically, and none of them is necessarily wrong – they simply describe different projects. A clear brief removes most of that guesswork and lets you compare price, approach and quality instead of comparing assumptions.
1. Your business and the goal of the site
- who you are, what you sell, where and to whom;
- the main goal: enquiries, online sales, bookings, recruitment or information;
- how you will measure success, for example the number of enquiries per month;
- the key tasks visitors must be able to complete.
A practical format for those tasks is the user story described in the UK government's Service Manual: "As a… I need/want/expect to… so that…", with acceptance criteria phrased as "it's done when…". For example: "As a fleet manager, I want to request a quote for 20 vehicles so that I can compare suppliers. It's done when the form accepts the number of vehicles and I receive a confirmation e-mail." The Service Manual calls the goal the most important part of a user story. Stories like this tell the agency what matters without dictating how to build it.
2. The current situation
If you already have a site, give its address, what works and what does not, roughly how many pages it has and whether it brings visitors from Google. If it does, state that keeping your search rankings is a requirement – then every quote must include a map of old and new URLs and the redirects. Our article on redesigning without losing Google rankings explains what that involves.
3. Page types and structure
List page types rather than a page count: home, service page (eight, same layout), product list, product page, article, about us, careers, contact. Add a draft menu if you have one. The number of different page types is one of the biggest drivers of design and development time, so this list makes quotes far more comparable.
4. Features and integrations
Split features into three groups: must have at launch, should have, and later. For each integration, name the system (invoicing, stock, courier, CRM, payment provider), say whether it has a documented API and who can give access to it. Integrations are the hardest part to price; without these details agencies will either add a generous safety margin or leave the item out.
5. Content and languages
- Who writes the texts, and are they ready?
- Who provides photos and video, and are they licensed for use on the web?
- How many languages, and who translates?
- How much content needs to be moved from the old site?
6. Quality targets
Write measurable targets so every agency prices the same standard:
- Speed: Core Web Vitals in the "good" range as defined on web.dev – Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads.
- Accessibility: a named WCAG version and level, for example WCAG 2.2 level AA. W3C encourages using the latest version, and content that meets WCAG 2.2 also meets 2.1 and 2.0. The Scottish Government's Service Manual advises that any contract should state the agreed level of compliance, and warns that vendors' accessibility claims "can often be overestimated" – so ask how it will be tested.
- Devices and browsers: current versions of the main browsers on phones and computers.
- SEO basics: editable titles and descriptions, a sitemap, clean URLs, redirects from old addresses.
- Security and privacy: HTTPS, spam protection on forms, where form submissions are stored and who can see them.
7. Ownership and access
This section is often missing and causes the most trouble later. State that:
- the domain is registered in your company's name and you hold the login. ICANN's guidance for registrants of generic domains such as .com is clear that the registrant must keep contact details accurate and assumes sole responsibility for the registration and use of the domain;
- hosting, analytics and Google Search Console accounts belong to you, with the agency added as a user. Google notes that a Search Console property must have at least one verified owner, or no users will have access to it;
- you receive the source code – or at least the right to use and modify it – together with documentation;
- licences for themes, plugins, fonts and photos are in your name or can be transferred to you.
8. Support after launch
Ask what is included after launch: hosting, updates, backups, monitoring, response times for problems and the price of typical changes. Ask for this as a separate line, so that a low build price with expensive support does not look cheaper than it really is.
9. Budget and timeline
Give a budget range if you can. It does not weaken your position; it tells agencies whether to propose a template-based site or a custom one, and it saves time on both sides. State the date that really matters – a trade fair, a season, a product launch – and any periods when you cannot review work.
10. What you want back
Ask every agency to answer in the same structure, and compare the answers side by side:
| Item | Agency A | Agency B | Agency C |
|---|---|---|---|
| Design: template or custom | |||
| Page types included | |||
| Features and integrations included | |||
| Content, translations, photos | |||
| Speed and accessibility targets, and how they are tested | |||
| Redirects and migration from the old site | |||
| Ownership of code, domain and accounts | |||
| Timeline and milestones | |||
| Price by stage | |||
| Yearly running and support costs | |||
| What is excluded |
Also ask for a list of assumptions, two or three comparable sites the agency has built, and who will actually work on your project.
Common mistakes
- "Like the big online stores, but simpler." Name the specific functions you liked instead.
- Only design wishes. Colours and fonts, but nothing about goals, content or features.
- Integrations mentioned only in a meeting. If it is not in writing, it may not be in the price.
- A fixed price for an open scope. Either fix the scope or agree how changes will be priced.
- Different information for different agencies. Send everyone the same document and share answers to questions with all of them.
A short template to copy
- About us and the goal of the site (with a measurable target)
- Key user tasks, written as user stories
- Current site and what must be kept
- Page types and draft menu
- Features: must have, should have, later
- Integrations and available APIs
- Content, photos and languages – who does what
- Quality targets: speed, accessibility, browsers, SEO, security
- Ownership and access
- Support after launch
- Budget range and key dates
- Required format of the quote
Our company website checklist is a useful companion when you list page types and content. If you would like a second pair of eyes on your brief, or a quote for website development based on it, send it to us.
Sources
- Writing user stories – GOV.UK Service Manual
- Web Vitals – web.dev (Google)
- WCAG 2 Overview – W3C Web Accessibility Initiative
- Building accessibility into projects – Scottish Government Service Manual
- Registrants' Benefits and Responsibilities – ICANN
- Managing owners, users, and permissions – Search Console Help