Some of the smoothest projects I’ve worked on started with a clear brief from the client. A few pages explaining what the business does, who the website is for, what it needs to achieve and what’s important. Questions were few, quotes were accurate and the finished site matched expectations.
Some of the most difficult projects started with a single sentence: “We need a new website, something modern.” Every week brought new requirements nobody had mentioned, and the budget and timeline stretched while everyone grew frustrated.
A website brief doesn’t need to be long or technical. It needs to communicate what you want clearly enough that a developer can understand, quote and plan accurately. Here’s what to include.
Why a brief matters
A good brief:
- Helps you clarify your own thinking before spending money.
- Gets accurate, comparable quotes from different providers.
- Reduces misunderstandings during the project.
- Prevents scope creep, because everyone agreed on what’s included.
- Gives a reference point for decisions and testing.
1. About your business
Start with context:
- What does your business do?
- Who are your customers?
- What makes you different from competitors?
- How long have you been operating, and where?
- Who are your main competitors online?
Developers who understand your business make better suggestions.
2. Why you need a website now
Explain the trigger:
- Starting a new business.
- Replacing an outdated or broken site.
- Rebranding.
- Adding ecommerce or new functionality.
- Improving performance, SEO or conversions.
- Moving away from a website builder.
If you’re redesigning, explain what’s wrong with the current site and what works well. Both matter.
3. Goals and success measures
What should the website achieve? Be as specific as possible:
- Generate a certain number of enquiries per month.
- Sell products online.
- Take bookings.
- Reduce phone calls by answering common questions.
- Build credibility for sales conversations.
- Recruit staff.
How will you measure success? Enquiries, sales, bookings, traffic or time saved. Clear goals help developers prioritise features that matter.
4. Your audience
Describe the people the website is for:
- Who are they, and what do they need?
- What questions do they have before contacting you?
- How do they find businesses like yours?
- Which devices do they use?
- Are there accessibility needs to consider?
- Which languages do they speak?
If you serve several distinct audiences, like customers and partners, describe each.
5. Pages and structure
List the pages you think you need. A rough sitemap helps:
- Home.
- About.
- Services, with individual service pages.
- Case studies or portfolio.
- Blog.
- Contact.
- Legal pages: privacy policy, terms.
Don’t worry about getting it perfect; a good developer will suggest improvements. But a starting list makes scope clear.
6. Features and functionality
Describe what the site needs to do beyond showing content:
- Contact or quote forms.
- Online store, with approximate number of products.
- Booking or appointment system.
- Membership or customer login areas.
- Online courses.
- Event listings.
- Job listings.
- Multilingual content.
- Search.
- Newsletter signup.
- Live chat.
- Calculators or configurators.
Distinguish between must-haves and nice-to-haves. This helps with budgeting and phasing.
7. Integrations
List other systems the website must connect to:
- CRM.
- Email marketing platform.
- Payment gateways.
- Accounting software.
- Inventory or ERP system.
- Booking or scheduling tools.
- Analytics and advertising platforms.
Integrations often have significant effects on cost and complexity, so mention them up front.
8. Content
Content is one of the biggest factors in project timelines:
- Who will write the text?
- Do you have existing content to reuse?
- Do you have professional photos, or will you need photography?
- How much content needs migrating from an existing site?
- Will you need help with copywriting or SEO content?
Be realistic about your capacity to provide content. Projects frequently stall waiting for it.
9. Design preferences
Help developers understand your taste:
- Brand guidelines: logo, colours, fonts.
- Websites you like, and specifically what you like about them.
- Websites you don’t like, and why.
- The impression the site should give: professional, friendly, premium, playful.
Examples are far more useful than adjectives. “Modern and clean” means something different to everyone.
10. Technical requirements
You don’t need to be technical, but mention what you know:
- Preferred platform, like WordPress, and why.
- Existing hosting, domain and email arrangements.
- Who will maintain the site after launch.
- Who will edit content, and their technical comfort level.
- Security, privacy or compliance requirements.
- Performance expectations.
- Accessibility standards you need to meet.
If you’re redesigning, mention SEO concerns, like protecting existing rankings and traffic.
11. Budget
Sharing a budget range is one of the most helpful things you can do. It lets providers propose a solution that fits, rather than guessing. Without it, you may receive quotes that are wildly different in scope.
If you’re unsure what’s realistic, say so, and ask providers to suggest options at different levels.
Also mention ongoing budget for hosting, maintenance and marketing.
12. Timeline
- When do you need the site launched?
- Is the date fixed, like a product launch or event, or flexible?
- Are there periods when you’re unavailable for feedback?
Allow time for your own reviews and content preparation, not just development.
13. Decision-making and contacts
- Who is the main contact for the project?
- Who approves designs and content?
- How many people need to review work?
Projects with many reviewers and unclear decision-makers take longer. Naming a single decision-maker helps a lot.
14. After launch
- Will you need ongoing maintenance and support?
- Do you plan regular updates or new features?
- Will you need help with SEO, content or marketing?
Keep it concise
A brief doesn’t need to be a 40-page document. Two to five pages covering these areas is usually enough. Use bullet points and plain language. If something is undecided, say so; that’s useful information too.
What happens next
Once you send a brief, a good developer will:
- Ask clarifying questions.
- Suggest improvements or alternatives.
- Provide a proposal with scope, timeline and cost.
- Highlight risks or assumptions.
The brief starts a conversation; it doesn’t have to answer every question perfectly.
A short example brief
Here’s what a concise brief might look like for a small business:
Business: Family-run tutoring centre offering maths and English tuition for school students, both in person and online, operating for eight years.
Why now: The current site was built on a website builder years ago, looks dated, isn’t mobile friendly and generates very few enquiries.
Goals: Increase trial lesson bookings, make it easy for parents to understand courses and prices, and reduce phone calls asking basic questions.
Audience: Parents of school students, mostly browsing on phones in the evening; some adult learners for online classes.
Pages: Home, About, Maths tuition, English tuition, Online classes, Pricing, Testimonials, FAQ, Contact, Blog.
Features: Trial lesson booking with calendar, contact form, testimonials, newsletter signup. Nice to have: parent login for resources later.
Integrations: Existing email marketing platform; Google Calendar for bookings.
Content: We’ll write page copy with help on editing. We need professional photos of the centre.
Design: Friendly, trustworthy, not childish. Examples attached with notes.
Budget and timeline: Range provided. Launch before the new school term.
Decision maker: Owner, with input from one senior tutor.
That’s around a page, and it gives a developer almost everything needed to propose a sensible solution.
Even a short brief like this saves weeks of back-and-forth and gets you far more accurate quotes.
Update the brief as you learn
As the project progresses, keep the brief updated with decisions and changes. It becomes a living reference everyone can rely on.
Frequently asked questions
Do I need to be technical to write a brief?
No. Describe your business, goals, audience and needs in plain language. Developers translate those into technical requirements.
Should I share my budget?
Yes, at least a range. It helps providers propose suitable solutions and makes quotes easier to compare.
How detailed should a brief be?
Detailed enough to explain goals, scope and priorities. Usually a few pages. More detail on complex features helps accuracy.
What if I don’t know what features I need?
Describe what you want to achieve, and let developers suggest features. A discovery phase can help clarify requirements for complex projects.
Final thoughts
A website brief is a small investment that pays off throughout a project. Explain your business, why you need a website, your goals and audience, the pages and features you need, integrations, content plans, design preferences, technical requirements, budget, timeline and who makes decisions. Keep it clear and honest. The better developers understand what you need, the more likely you are to get a website that delivers it.




