Learn how to write a clear website brief covering audience, goals, pages, features, content, accessibility, SEO, responsibilities and launch scope.


A website brief turns a loose idea into a practical plan. It explains who the website is for, what visitors should be able to do, which pages and features belong in the first version, what content already exists and what still needs to be prepared.
Without that shared plan, a website project can begin with colours, layouts and feature requests before anyone has agreed what success means. That often creates extra revisions, unclear quotes and a site that looks finished but does not support the customer journey.
This guide explains how to write a website brief for a small business or ecommerce store. You can also use our free Website Brief Builder to organise your answers and download a structured three-page PDF.
Clarify your audience, offer, pages, features, content and launch priorities, then download a brief you can review or share.
A website brief is a short project document that connects business goals with user needs and delivery requirements. It gives an owner, designer, developer or agency a common reference point before detailed design and development begin.
A useful brief does not need to specify every button or predict every future requirement. It should define the first version clearly enough for someone to understand the problem, estimate the work, identify missing inputs and ask better questions.
The strongest briefs usually cover seven areas:
A brief reduces ambiguity. If you ask three suppliers to quote for “a modern ecommerce website”, each may imagine a different number of products, pages, integrations and content tasks. Their prices will not be directly comparable because the underlying assumptions are different.
A clear brief makes those assumptions visible. It also separates a genuine launch requirement from an attractive future idea. That distinction helps protect the budget and makes it easier to reach a usable first release.
User needs should come before a preferred solution. The GOV.UK Service Manual recommends understanding the full context of the problem and testing assumptions early, rather than starting with a particular solution. Although a small business website is not a government service, the planning principle is valuable: first understand what people need to accomplish, then choose the content and features that help them do it.

Start with one primary outcome. A website can support several tasks, but the first version needs a clear centre of gravity. Is it mainly expected to sell products, generate enquiries, take bookings, deliver digital products or explain a business and build trust?
Write the goal as an action, not an adjective. “Create a premium website” describes a feeling. “Help UK customers compare and buy our twelve handmade tableware products on mobile” describes a useful outcome.
Add one measure that would show progress after launch. Depending on the goal, that might be completed orders, qualified enquiries, booked consultations, email sign-ups or downloads. Avoid turning the brief into a long analytics plan. One primary measure and two supporting measures are usually enough to guide early decisions.
“Everyone” is not a useful audience. Describe the person most likely to need the first version, the problem or desire that brings them to the site and anything that affects their decision.
For example: “UK parents looking for durable personalised lunch bags, usually shopping on a phone and comparing delivery dates before a school term starts.” That description immediately raises practical questions about product photography, personalisation, delivery information, mobile usability and order cut-off dates.
Use evidence where possible. Customer conversations, support questions, search terms, sales enquiries and analytics are stronger than an invented persona. The GOV.UK guidance on learning user needs suggests treating suggestions that do not come from users as assumptions to be tested. For a small business, even five short customer conversations can reveal language and concerns that improve the brief.
State what the website will offer at launch. For ecommerce, include the approximate number of products, categories, variants, price range and any important fulfilment model such as made to order, subscription, digital delivery or print on demand. For a service business, list the core services, typical customer decision and intended contact or booking route.
This is where scope often expands quietly. “Sell candles online” might mean eight fixed products, or it might include subscriptions, gift messages, bundles, wholesale pricing, customer accounts and international tax. Those are materially different projects.
Separate launch requirements from later options. If a feature is not required to serve the first customer or operate the first month, put it in a later list. You are not rejecting the idea. You are sequencing it.
| Brief area | Too vague | Useful first-version detail |
|---|---|---|
| Goal | Grow the business | Generate qualified enquiries for three core services |
| Audience | Anyone who needs us | Independent UK retailers preparing their first online shop |
| Products | Our full range | Twenty products across four categories, with colour variants |
| Features | Everything a modern site needs | Payments, delivery rules, contact form and email sign-up |
| Timing | As soon as possible | Target six weeks, subject to photography by 15 October |
Do not begin with a standard menu and assume every project needs the same structure. Map the questions a visitor needs answered from arrival to action, then create the smallest page set that supports that journey.
An ecommerce first version commonly needs a home page, shop or category pages, individual product pages, about information, contact details and policy pages. Frequently asked questions can be a separate page or placed where the questions arise. A blog is useful only when there is a realistic plan to publish helpful content.
Product pages need enough information for a buying decision. This can include price, availability, variants, dimensions, materials, delivery, returns and care instructions. Google also documents how Product structured data can communicate details such as price, availability, reviews, shipping and returns to search systems. Technical SEO does not replace clear page content, but the brief should make both responsibilities visible.

A feature list becomes more useful when each item names the task, user and expected outcome. Instead of writing “filters”, write “help shoppers narrow forty products by size, colour and price”. Instead of “booking system”, write “let customers choose a service, see available times, pay a deposit and receive confirmation”.
Also note what staff need after launch. Who will add products, update prices, fulfil orders, reply to enquiries and publish content? A feature that is simple for a visitor may create an ongoing administrative task. The brief should identify that operational owner.
Common ecommerce functions include payments, delivery rules, product variants, discount codes, stock management, reviews, search, filters, email sign-up, customer accounts and digital delivery. Select only what supports the agreed journey. Each extra integration adds configuration, testing and maintenance.
The Website Brief Builder organises your goal, audience, pages, features and missing content into a clear PDF with practical next actions.
Many website delays are content delays. A design can use temporary text and images, but a site cannot be properly reviewed when the final product names, prices, photography, policies and contact details are still unknown.
Create two lists: ready and still to prepare. Check the logo, brand colours, product or service images, page copy, prices, policies, testimonials, domain name, legal business details and any files customers need to download.
For every missing asset, assign an owner and date. “Photography required” is a warning. “Sahil will deliver twelve edited product images by 15 October” is a plan.
Accessibility should be part of the brief, not a final check. The W3C Web Accessibility Initiative planning guidance recommends setting goals, assigning responsibilities, securing resources and evaluating throughout a project. For a small website, practical requirements can include keyboard access, visible focus states, useful alternative text, readable contrast, clear labels and testing at mobile sizes.
SEO requirements should connect to page purpose and content. Identify the main search intent for important pages, the product information available, internal links, page titles, descriptions and any structured data responsibilities. Avoid promising rankings. The brief should define the work that makes pages understandable to people and search systems.
Measurement requirements should state which actions matter and which tools will record them. Typical events include completed orders, enquiry submissions, booked calls, email sign-ups and important downloads. Include consent and privacy requirements for analytics and marketing tools.
A date without dependencies is not a plan. State the preferred launch window, why it matters and what must be delivered before it can be met. Product photography, policy approval, payment accounts and domain access are common dependencies.
If you have a budget range, include it. A supplier can then recommend a realistic scope instead of designing a proposal around assumptions. If the budget is not fixed, identify the commercial constraint, such as keeping recurring costs below a certain amount or launching with the smallest workable product range.
Name the decision maker and the people responsible for content, technical access and final approval. Too many unranked opinions can stall a project. A clear approval route protects both speed and accountability.

A brief should guide decisions without pretending every detail is already known. Avoid filling it with copied competitor features, untested assumptions or subjective instructions that cannot be evaluated.
If you prefer to draft manually, use the following headings:
Read the brief as if you knew nothing about the business. Could you identify the audience, the first customer journey, the content owner and the launch boundary? Are the must-have features linked to real tasks? Can a supplier see which information is confirmed and which is still an assumption?
Then ask three final questions:
A brief is ready to discuss when those answers are clear enough to support a productive conversation. It does not need to be perfect. A good supplier should challenge assumptions, identify risks and help turn the first draft into a delivery plan.
The brief gives the project structure, but a small evidence pack helps a supplier understand the details without adding assumptions. Share the material you already have and label unfinished items clearly. Do not wait for every asset to be perfect before starting a conversation.
This evidence lets a supplier distinguish content work from design and development work. It also helps expose dependencies early. For example, a payment account may need identity checks, a domain may be controlled by a former supplier or product data may require cleaning before it can be imported.
Ask the supplier to reflect the final decisions back in a proposal or specification. Check that the page scope, functional scope, content responsibilities, acceptance testing and recurring costs all match the brief. If something important is absent, resolve it before work begins.
Create a structured brief for free, or see how MLFG can turn your plan into a complete ecommerce store with hosting, domain, business email, AI tools and training in one £99/year plan.
For a small business website, three to six focused pages are often enough. Clarity matters more than length. Add supporting inventories or technical notes only when they help someone estimate or deliver the work.
The business owner or project lead should own the brief because they understand the goals, customers and constraints. A designer, developer or agency can then challenge and refine it during discovery.
Yes. A smaller budget makes scope clarity more important. A brief helps distinguish the product, payment, delivery and content requirements needed for launch from features that can wait.
No. A brief explains the problem, audience, goals, scope and constraints. A detailed specification records how agreed requirements will be implemented. The brief usually comes first.
Yes, when new evidence justifies a change. Record what changed, why it changed and what it affects in cost, timing or scope. Uncontrolled changes create confusion; documented decisions support iteration.
PREFERRED SOURCE
Like what you’re reading? Add Make Local for Global as a preferred source on Google to see more of our articles when you search.
Build your online presence without having to figure out everything yourself.