A web design brief is a short document that tells a designer or agency what your website must achieve, who it is for, what it needs to do, and the constraints on budget and time. A good brief gets you accurate quotes, fewer surprises and a better site. In 2027 it also needs to cover how AI search and AI agents will read your site.
The short answer
A good web design brief covers ten things: your business, the goal of the site, your audience, what is wrong with the current site, the pages and features you need, integrations, content and who supplies it, design direction, budget range and deadline, and who owns and maintains the site after launch. In 2027, add requirements for accessibility, structured content and AI visibility. Keep it to a few pages. Clarity beats length.
I have read a great many website briefs and enquiries over 20 years. The projects that go well almost always start with a clear brief. The ones that go badly usually started with “we need a new website” and a deadline. A brief does not need to be technical. It needs to be specific about what success looks like.
The cheapest week on any website project is the one spent agreeing what it is for. A while ago my team was asked to rebuild the site for a member-based organisation with a big launch event already booked. The vision was clear. The requirements weren’t: several stakeholders each had a different list, and the old site leaned on a stack of plugins that fought each other. Before anyone wrote code, we ran a short discovery to agree the must-haves, cut the nice-to-haves to fit the budget and wrote it all down. The site launched in time for the event, and that written agreement did the job a brief should have done on day one.
What should a web design brief include?
A web design brief should include your business overview, the website’s goals and how you will measure them, your target audience, problems with the current site, required pages and features, integrations, content responsibilities, design preferences, budget range, timeline, and plans for hosting and maintenance. Each section should be short and specific.
| Section | What to include | Example |
|---|---|---|
| Business overview | What you do, who for, where, team size | “Accounting firm, 12 staff, small businesses in Sydney” |
| Goals and measures | What the site must achieve, how you will know | “Double consultation requests from organic search” |
| Audience | Who visits, what they need, what devices | “Business owners, mostly on mobile” |
| Current site problems | What is not working today | “Slow, hard to update, no tracking on forms” |
| Pages and features | Key pages, forms, bookings, search, store | “Service pages, booking, client portal link” |
| Integrations | CRM, email, payments, booking, analytics | “HubSpot forms, Google Analytics 4, Calendly” |
| Content | Who writes, who supplies photos, how many pages | “We supply copy for 15 pages, need photography” |
| Design direction | Brand assets, sites you like and why | “Clean, trustworthy, like these three sites” |
| Budget and timeline | A realistic range and any fixed dates | “Launch before end of financial year” |
| Ownership and care | Hosting, maintenance, who edits after launch | “We own all accounts; need monthly support” |
Why does a web design brief matter?
A web design brief matters because it turns a vague request into a scope that can be quoted, designed and tested. Without it, agencies guess, quotes vary wildly and projects drift. With it, you can compare proposals fairly, keep decisions consistent and judge the finished site against the goals you set at the start.
Copy-ready brief starter: Our audience is __; their three must-work tasks are __. Today we receive __ confirmed enquiries or sales per month, measured by __. The problem to solve is __. In scope: __; out of scope: __. We supply __ content by __. Budget range: __; fixed date and reason: __. Approval owner: __. Before launch, prove __ tasks, preserve the agreed URLs and tracking, test __ integrations and document rollback. After launch, __ owns access, licences, maintenance and measurement.
Should you share your budget in a web design brief?
Yes. Share a realistic budget range, even a broad one. It lets a designer recommend what is achievable instead of guessing, and it saves everyone time on proposals that do not fit. Without a range, you often get quotes that are either far too basic or far too ambitious for your needs.
If you are unsure what a sensible range is, my guide to what drives website design cost explains the factors that move the price.
What should a brief say about AI search and AI agents?
For a site planned for 2027, specify the human journeys and the AI-assisted tasks that matter to your business. Ask for useful service pages, crawlable text, accessible forms and buttons, and relevant structured data matching the visible page. Scope and price the implementation and testing; planning early does not make every requirement free or prove universal AI visibility.
Add these lines to your brief:
- Give each distinct service or customer need a useful page where it deserves a separate answer; avoid splitting near-identical offers into thin pages.
- A location page only where you genuinely serve that area and have something specific to say about it, such as local projects, staff, service limits or conditions. A copy of the same page with the suburb swapped helps nobody, and Google’s spam policies can treat substantially similar pages like that as doorway abuse.
- Key facts (services, areas, contact details, pricing approach, hours) appear as text, not only in images or PDFs.
- The site meets WCAG 2.2 AA accessibility, including labelled forms and keyboard navigation.
- Use relevant structured data supported by the page and the intended search feature; validate it against visible facts.
- Core Web Vitals targets for key templates.
For an agent task, add a test such as: “In the agreed browser and test account, find the correct service and prepare an enquiry. Show the user the details before submission; retain the same permissions and confirmation as the human journey.” Record the test and its limits rather than promising compatibility with every assistant.
I expect AI-assisted research to matter to more buying journeys. That is my planning view, rather than a forecast of your traffic. My guide to an agent-ready website explains how to define and test a named task.
Can you use AI to write a web design brief?
Yes, as a starting point. An AI assistant can turn your notes into a structured brief, suggest questions you missed and tidy the language. It cannot know your business goals, customers or constraints. Check every line, add real numbers and examples, and make sure the brief says what you actually need rather than a generic wish list.
How do you use the brief to choose a designer?
Use the brief to compare designers on the same terms. Send the same brief to two or three, ask each how they would approach it, what they would change and what they need from you. Good designers ask questions and challenge parts of the brief. Weak ones simply send a price.
My list of questions to ask a web design company helps you compare their answers. If you are not sure whether you need a full redesign at all, read my guide on when to redesign a website.
What changes for website briefs in 2027?
A privacy requirement starts on 10 December 2026 for entities covered by the Australian Privacy Principles. It concerns computer programs using personal information to make decisions, or do something substantially and directly related to making decisions, reasonably expected to significantly affect an individual’s rights or interests. Flag relevant workflows in the brief; adding human review does not automatically put them outside the requirement.
The OAIC’s APP 1 guidelines explain the policy information: kinds of personal information used and kinds of solely automated or computer-assisted decisions. Coverage and exceptions matter. Add this brief question: “Which decisions use personal information, what does the system contribute, who reviews them and could they significantly affect a person?” Have the responsible privacy adviser assess the actual workflow.
What to do next
- Copy the ten sections from the table into a document.
- Write two or three lines for each, using real numbers where you have them.
- Add the AI search and accessibility requirements.
- Share it with two or three designers and compare how they respond.
- If you want a second opinion on your brief, book a free call with my team.
Frequently asked questions
How long should a web design brief be?
Two to five pages is usually enough. The brief should be long enough to cover goals, audience, features, content, budget and timeline clearly, and short enough that everyone reads it. Attach supporting material, such as brand guidelines or analytics reports, separately.
What is the difference between a web design brief and a scope of work?
A brief is written by the client and explains what they need and why. A scope of work is usually written by the designer or agency in response, and defines exactly what will be delivered, how and when. A good brief makes the scope of work faster and more accurate.
Who should write the website brief?
The person who owns the website’s results, usually the marketing lead or business owner, with input from sales, operations and anyone who edits the site. Involve the people who will use the site daily, so their needs are not discovered after launch.
What if I do not know what features I need?
Describe the problems you want to solve and what your customers need to do on the site. A good designer will recommend features to meet those needs. It is better to explain the outcome you want than to list features you are not sure about.
Should the brief include examples of websites I like?
Yes. Include three to five sites and say specifically what you like about each, such as the navigation, the tone or the way services are explained. Examples without explanation can be misread. Mention what you do not like as well.






