How to Write a Website Brief That Gets Better Quotes

If you ask three web designers for a quote using only the words “I need a new website”, you are very likely to receive three completely different prices for three completely different jobs.

That is not necessarily because one supplier is cheap and another is expensive. It is usually because each person has had to guess what you mean.

A useful website brief removes that guesswork. It explains what the business needs the website to achieve, what must be included, what can wait, what already exists and what could create extra work. The result is not just a better design process. It is a much fairer way to compare web design quotes.

If you are a UK small-business owner, your website brief does not need to be technical or twenty pages long. It needs to make the commercial goal, audience, scope, content, functionality, SEO risks, ownership and budget clear enough for a designer or agency to price the same job.

This guide includes a practical website brief template you can copy, plus the details that are often missed until they become delays, extra charges or SEO problems later.

Website brief template UK: the short version

If you only want the essentials, give every supplier the same answers to these ten points:

1. Business: what you sell, who you serve and where you operate.
2. Problem: what is wrong with the current website or process.
3. Primary goal: the main result the new website should help create.
4. Audience: who the priority customer is and what they need to know before contacting you.
5. Scope: pages, services, locations and content that must be included.
6. Functionality: forms, bookings, payments, ecommerce, logins or integrations.
7. Content: who supplies the copy, photos, videos, reviews and brand assets.
8. SEO and migration: existing rankings, important URLs and what must be protected.
9. Budget and timing: realistic range, deadline and what is driving it.
10. Ownership and support: who owns the domain, hosting, website, licences and what happens after launch.

That is enough to start a serious conversation. The rest of this guide explains how to make each answer useful.

What is a website brief?

A website brief is a document that explains the business problem the website needs to solve and the practical boundaries of the project.

It is not the finished website specification. You do not need to choose a WordPress theme, decide every heading, draw the sitemap or tell a developer which plugins to install unless you have a genuine technical requirement.

Your job is to explain the outcome, evidence and constraints. The web professional’s job is to recommend the most sensible structure and technical solution.

This distinction matters because over-specifying the design too early can lock a project into the wrong answer. A brief that says “we need a five-page site with a slider” is less useful than one that says “we need more qualified commercial enquiries, customers currently cannot understand our three core services, and the site must connect to our booking system”.

The biggest benefit: better quotes become easier to compare

A website brief is often described as a planning document. For a small business, it is also a buying tool.

Without a consistent brief, one quote may include copywriting, SEO migration, hosting and post-launch support while another includes design and build only. The cheaper proposal can look attractive until the missing work appears later as extras.

Send the same brief to every supplier and ask them to identify:

• what is included;
• what is excluded;
• what they need from you;
• what assumptions the price depends on;
• what would trigger an extra charge;
• what support is included after launch.

This turns the conversation from “why is one quote £1,500 and another £4,000?” into “what does each proposal actually deliver?”

If you are already comparing costs, our guide to UK website design costs explains why scope changes the price so dramatically. If the project is replacing an existing site, see the separate guide to website redesign costs in the UK.

1. Start with the business problem, not the design

The strongest briefs begin with a commercial problem.

Examples include:

• the website receives traffic but too few enquiries;
• customers keep asking questions that the site should answer;
• the business has added new services that are difficult to find;
• the site attracts the wrong type of enquiry;
• booking is handled manually and wastes staff time;
• the website looks much smaller than the business now is;
• the current site is difficult to update;
• important pages have strong Google visibility but the design is dated;
• the business has outgrown a DIY platform.

“Make it modern” is not a business problem. It may be part of the visual goal, but it gives a designer very little information about what success should look like.

A better sentence is: “We want the website to make our commercial services easier to understand and increase qualified quote requests from businesses in London.”

2. Define one primary website goal

A website can support several outcomes, but one should usually lead the project.

Your primary goal might be:

• qualified enquiries;
• phone calls;
• online bookings;
• ecommerce sales;
• appointment requests;
• job applications;
• customer self-service;
• credibility during tenders or sales conversations.

Secondary goals can still be listed. The point is to stop every page trying to do everything.

For example, a plumber’s website may primarily need emergency and planned-work enquiries. A consultant may need prospects to understand expertise before arranging a call. An ecommerce business may prioritise completed purchases while using guides to support product discovery.

When the primary goal is clear, the designer can make better decisions about page order, calls to action, forms, content and measurement.

3. Describe the customer by situation, not just demographics

“Men and women aged 25–65” rarely tells a web designer much.

Describe what is happening when the customer needs you.

A useful audience description might say:

“Our main customer is a London small-business owner whose existing website is outdated, slow or not generating enquiries. They usually contact us after trying to fix it themselves or after receiving conflicting advice from different suppliers.”

That tells the designer what the customer is worried about and what information can reduce uncertainty.

Include:

• who normally makes the buying decision;
• what triggers them to search;
• what they already understand;
• what they are nervous about;
• what commonly stops them contacting you;
• what makes an enquiry qualified or unsuitable.

This is also valuable for content planning because service pages should answer real buying questions, not just describe the company.

4. Separate must-haves from ideas

One of the easiest ways to lose control of a web project is to mix essential requirements with “it would be nice if…” ideas.

Use three columns:

This gives the supplier room to protect the essentials when the budget is tight instead of quietly removing important work.

5. List functionality in plain English

You do not need to know the technical solution. Describe what users and staff need to be able to do.

Examples:

• customers need to choose an appointment slot and pay a deposit;
• quote requests must go into the existing CRM;
• staff need to upload new case studies without a developer;
• customers need separate trade and retail prices after login;
• the site needs to sell subscriptions as well as one-off products;
• forms need to route different enquiries to different departments;
• the site must connect to an existing email marketing platform.

A developer can then work out whether that requires WooCommerce, a booking system, an API integration or something simpler.

If you are comparing platforms, our guides to WordPress vs Wix for small businesses and Shopify vs WooCommerce explain the practical trade-offs.

6. Be explicit about who is providing the content

Content is one of the most common reasons website projects overrun.

Do not write “content supplied” unless you know exactly what exists and who is responsible for it.

Your brief should identify:

• which existing pages are accurate;
• which pages need rewriting;
• who writes new service content;
• who supplies photographs;
• whether existing reviews can be reused;
• whether customer names and logos have permission to appear;
• who approves the final wording;
• whether product data needs importing;
• whether old blog posts or resources need migrating.

If the supplier is expected to write or rewrite the content, ask for that to appear as a separate line in the proposal. It is real work and should not be hidden inside “web design”.

7. Do not forget your existing SEO before a redesign

This is one of the most expensive omissions in a website brief.

If the current website already receives impressions, clicks, enquiries or backlinks, tell the supplier before they quote.

A redesign can affect URL structure, internal links, page content, headings, metadata, canonicals and redirects. Google recommends careful planning when URLs change, including mapping old URLs to relevant new ones, implementing permanent redirects and monitoring the move afterwards.

Google’s current site-move guidance also advises changing one major thing at a time where possible and monitoring Search Console during a move.

Include in your brief:

• access to Google Search Console if available;
• your most valuable organic landing pages;
• important service and location URLs;
• pages with external links;
• content that must not disappear;
• whether the domain or platform is changing;
• whether URL changes are expected;
• who is responsible for redirect mapping and post-launch checks.

Our technical SEO audit checklist gives you a broader list of checks to review before and after major website changes.

8. Explain what search visibility you actually want

Writing “SEO included” in a brief is too vague.

Explain what matters commercially. For example:

• “We want to be found for emergency website repair searches across the UK.”
• “Our priority is local visibility for accountancy services in Croydon and nearby areas.”
• “We already rank for several product categories and do not want those URLs lost during the rebuild.”

Google’s people-first content guidance encourages original, substantial information that helps readers complete their goal rather than content produced mainly to attract search visits. It also explicitly says there is no preferred word count. That is a useful principle for a website brief: ask for pages that answer customer needs properly, not pages written to hit arbitrary lengths.

You can read Google’s current people-first content guidance directly.

9. Include real trust material, not just a request for “testimonials”

Gather evidence before design starts.

That may include:

• real project photographs;
• customer reviews you have permission to quote;
• accreditations that can be verified;
• team photographs;
• before-and-after examples;
• case studies;
• service guarantees that are genuinely offered;
• company registration details where appropriate;
• delivery, response or coverage information you can substantiate.

Do not make up case studies, statistics or awards to fill the layout. If the evidence does not exist yet, say so in the brief and plan how it will be created.

10. State the budget range

Many businesses avoid giving a budget because they worry a supplier will simply quote the maximum.

In practice, withholding it often makes proposals harder to compare. One designer may plan a lean brochure site while another assumes custom photography, copywriting, advanced SEO and integrations.

A range is enough:

“We expect to spend £2,500–£4,000 if the proposal includes copy support, migration and launch checks.”

This lets the supplier tell you what is realistic within the budget and where trade-offs may be required.

If you have no idea what to budget, start with our UK web design pricing guide and then ask suppliers to separate essentials from optional extras.

11. Explain the deadline and why it exists

“ASAP” is not a project timeline.

If there is a fixed date, explain the reason:

• new shop opening;
• trade show;
• product launch;
• contract renewal;
• seasonal campaign;
• old hosting closing;
• rebrand launch.

Then identify what you can provide on time. A six-week website project is not realistic if photography, legal approval and service copy will not be ready for five weeks.

Good suppliers should challenge a deadline that creates unnecessary risk rather than simply promise anything to win the job.

12. Name the decision-maker

Projects slow down when five people provide separate feedback and nobody has authority to decide.

Your brief should name:

• the project owner;
• the person with final approval;
• any mandatory legal, compliance or technical reviewers;
• how feedback will be consolidated.

This is particularly important for small businesses where a director, office manager and external marketing consultant may all be involved.

13. Put ownership in writing before work starts

Ownership is often discussed too late.

Your brief should ask the proposal to confirm who controls:

• the domain name;
• hosting account;
• WordPress administrator access;
• Google Analytics and Search Console;
• business email;
• premium plugin licences;
• stock imagery licences;
• website copy and original design assets;
• backups.

You should also know what happens if you change supplier later.

That does not mean every licence must belong to the client. Agencies sometimes legitimately provide software under their own licence. The important point is that the arrangement is clear before you depend on it.

14. Include maintenance and support in the conversation

Launch day is not the end of a website’s life.

Ask each supplier:

• how long post-launch fixes are included;
• who handles WordPress, theme and plugin updates;
• who monitors backups;
• whether forms and key functionality are tested regularly;
• what happens if the site breaks;
• what ongoing work is included in a maintenance plan;
• how extra development is charged.

If you need ongoing help rather than a one-off build, our website maintenance and support service explains the difference between routine care, support and urgent fixes.

15. Make measurement part of the brief

A new website should not be judged only by whether everybody likes the design.

Define what you will measure after launch. Depending on the business, that might include:

• qualified form enquiries;
• phone calls;
• bookings;
• checkout completion;
• quote requests;
• organic landing-page traffic;
• visibility for priority service searches;
• reduction in irrelevant enquiries.

The goal is not to promise that a redesign will automatically increase every number. It is to make sure the website is built so the business can tell what changed.

A better way to organise the brief: knowns, unknowns and assumptions

Most website brief templates contain a list of questions. A more useful approach is to mark each answer as one of three types:

This prevents assumptions turning into expensive requirements without anyone testing them.

Example website brief for a local service business

Here is a shortened fictional example showing the level of detail that makes a quote useful.

Business: South London heating company serving homeowners and landlords across Croydon, Bromley and Sutton.

Current problem: The website gets some traffic but service information is mixed together, mobile contact is awkward and the company receives too many enquiries for work it does not offer.

Primary goal: Increase qualified boiler repair and installation enquiries.

Priority customer: Homeowners and landlords who already know they need a heating engineer and are comparing local providers.

Must-have scope: Home, boiler repair, boiler installation, servicing, landlord services, about, reviews, contact and clear service-area information.

Functionality: Quote form with service type, postcode and preferred contact method. Tap-to-call on mobile. Existing call-tracking number must remain.

Content: Current service copy is outdated. Supplier to edit and restructure it. Client provides approved reviews, team photos and accreditation logos.

SEO: Existing repair and servicing pages receive organic traffic. URLs should be retained where sensible. Any changed URLs must be mapped and redirected. Search Console access can be provided.

Budget: £2,500–£4,000 depending on content work and migration scope.

Timing: Target launch within eight weeks, but no immovable event date.

Ownership: Client owns domain and hosting. Proposal must state which licences remain dependent on the supplier.

After launch: Quote ongoing maintenance separately from the build.

A designer can price that brief far more accurately than “eight-page website for a heating company”.

What not to put in a website brief

A brief should guide the project without pretending you have already designed it.

Avoid:

• copying a competitor’s website: explain what you like about the experience rather than asking for a clone;
• fixed technical choices without a reason: “must use plugin X” is useful only when there is a genuine dependency;
• invented SEO requirements: do not demand 2,000 words on every page or a certain keyword density;
• unverified statistics: do not build the strategy around assumptions you have never checked;
• every idea anyone has suggested: separate launch requirements from the wish list;
• passwords or sensitive customer information: share access securely later, not inside a brief circulated to multiple suppliers.

Website quote comparison checklist

Once the proposals arrive, compare them against the brief instead of comparing only the total price.

If you are deciding between types of supplier as well as prices, our comparison of a web design agency versus a freelance web designer covers the practical differences in support, capacity, expertise and cost.

Copy-and-paste website brief template

You can paste the following into an email or document and fill in the answers.

Business name:
[Your business]

What we do:
[Services/products, market and service area]

Why we are changing the website now:
[Business problem or trigger]

Primary goal:
[Enquiries, sales, bookings, applications, credibility]

Priority customer:
[Who they are, what triggers the search, what they need to know]

Current website:
[URL, what works, what does not]

Must-have pages/content:
[List]

Must-have functionality:
[Forms, bookings, ecommerce, integrations]

Content available:
[Copy, images, reviews, logos, videos, case studies]

Content still needed:
[What needs writing or creating]

SEO/search requirements:
[Existing rankings, important URLs, target services/locations]

Analytics/tracking:
[GA4, Search Console, call tracking, conversion tracking]

Budget range:
[Range]

Target launch:
[Date and reason]

Decision-maker:
[Name/role]

Ownership requirements:
[Domain, hosting, licences, admin access]

Support after launch:
[What you expect or need priced separately]

Anything still undecided:
[Questions you want the supplier to advise on]

Website brief FAQs

How long should a website brief be?

There is no ideal length. For many small-business projects, one to three clear pages are enough. A larger ecommerce, membership or integration-heavy website may need more detail. Clarity matters more than page count.

Do I need a website brief before asking for a quote?

You can ask for an initial conversation without one, but a useful fixed or detailed quote normally needs enough information to define scope. A brief helps several suppliers price the same job rather than making different assumptions.

Should I tell a web designer my budget?

A realistic range is usually helpful. It allows the designer to recommend an appropriate scope and explain trade-offs. Without a budget, different suppliers may design completely different solutions and the quotes become difficult to compare.

Should SEO be included in the website brief?

Yes if search visibility matters to the business. For an existing website, include current high-value pages, Search Console information and any URLs that already generate traffic or enquiries. SEO migration should be planned before launch, not after rankings disappear.

Do I need to know how many pages the website will have?

No. List the services, products, audiences and information that must be covered. A good designer can recommend the page structure. If you already know certain pages are essential, include them as must-haves.

Should I specify WordPress, Shopify or another platform?

Only when there is a good reason. Existing staff skills, integrations, ecommerce requirements or ownership constraints may make a platform important. Otherwise describe what the website needs to do and let suppliers explain their recommendation.

Can a good website brief prevent extra costs?

It cannot prevent every change, but it makes assumptions and exclusions visible much earlier. That reduces the risk of discovering halfway through the project that copywriting, product imports, redirects, booking setup or licences were never included.

Final takeaway

A useful website brief does not tell a designer how to design the website. It gives them enough commercial and practical context to solve the right problem.

For a small business, the most valuable outcome is simple: several suppliers can understand the same job, price it on the same basis and explain their differences clearly.

Define the business goal, customer, must-have scope, content, functionality, SEO risks, budget, ownership and support. Mark what is known and what still needs advice. Then use the brief as the reference point when proposals arrive.

If you are preparing a new website or redesign and want professional input on scope before you commit, see our web design service for London and UK businesses. For an existing website that may only need targeted repairs rather than a rebuild, start with our website repair service instead.