How to write a website brief: a copyable template and examples
You do not need a 40-page specification. A concise brief can improve estimates and reduce misunderstandings.
Copy a practical 10-question website brief to receive clearer quotes from developers.
Key takeaways
- Describe goals, target audience, services, content, functionality and budget.
- Explain what you like about reference websites.
- You do not need to pick a framework before talking to a developer.
Why a brief matters
A short written brief makes quotes comparable. It reveals whether a “simple site” means a brochure or a multilingual booking platform. You can send the same answers to several suppliers.
Copy this 10-question website brief
Answer as many questions as possible. “To be agreed” is better than guessing.
- 1. Business name, industry and coverage area
- 2. Products/services and audience
- 3. Primary goal: leads, calls, sales or recruitment
- 4. Top three offers
- 5. Required pages
- 6. Existing logo, copy, photos and references
- 7. Forms, CMS, languages, bookings and integrations
- 8. Reference sites and what works about them
- 9. Ideal launch date and budget range
- 10. Decision maker and future content editor
A practical example
“We run a local service business. Our goal is to attract enquiries for three core services. We have a logo and photographs. We need service pages, a mobile-friendly design, an enquiry form and simple content editing.” This is enough to start a useful conversation.
Avoid vague requirements
“Make it premium” does not define a deliverable. Instead explain the user journey and measurable goals. Break “full SEO” into specific tasks such as metadata, indexing and redirects.
What to expect from the proposal
Ask for pages, deliverables, stages, exclusions, ownership and ongoing costs. You do not need to pick WordPress or Next.js before a discovery call.
Frequently asked questions
Is a brief mandatory?
No, but it improves estimate quality and alignment.
Should I include a budget?
It is optional but helps suppliers propose realistic scope.
Can the developer plan the page structure?
Yes. A brief describes needs, while discovery helps define the solution.
Have a brief? Send it to us
Share your answers and we can outline a practical next step for your project.
Send your brief ↗