How to Write a Website Brief That Gets Accurate Quotes
TL;DR
In this guide
- Explain the goal. Say what the website needs to do for the business.
- Include the detail. Pages, functions, content, budget and timing affect the scope.
- Clarify the references. Explain what is useful about the examples you share.
To write a useful website brief, explain the business goal, the intended audience, the pages and functions needed, and who will supply and approve the content. The template and example below help turn those answers into a clearer scope.
The guide at a glance
The three parts of a useful website brief
A quote becomes more useful when the team can see the actual work behind the request.
01
Business goal
Describe the audience, the action the website should support and the problems it needs to solve.
02
Practical requirements
List pages, functions, assets, content responsibilities, timing and the available budget range.
03
Design context
Explain the useful parts of reference websites and identify what is not working on the current site.
Start with the business goal
Before listing pages or features, explain what the website needs to achieve. Do you need more qualified enquiries, better trust, ecommerce sales, a cleaner service presentation, a resource hub, or a site that your team can edit more easily?
The goal helps shape the structure. A lead-generation site, for example, needs strong calls to action and forms. An ecommerce site needs product flow, payment, shipping, customer communication, and stock thinking.
Be clear about what is not working
If you already have a website, the most useful brief often starts with frustrations. Tell us whether the current site is hard to update, slow, visually outdated, confusing on mobile, not generating enquiries, or missing important services.
Add examples, but explain why
Website examples are helpful when they include comments. Instead of only sending links, note what you like about each one: navigation, typography, product pages, form layout, mobile simplicity, visual tone, or animation. Also include examples you dislike if they help define the boundaries.
A website brief template you can copy
Start with these prompts in a shared document. Short, specific answers are more useful than polished language that leaves the actual requirements unclear. Mark an unanswered point as an open question rather than guessing.
- Business and audience: What do you offer, where do you work and who should the website help?
- Purpose: Which action should visitors take? Explain what is wrong with the current experience.
- Page list: Name the essential pages, products or content groups. Note which existing pages should remain.
- Functions: List forms, payments, bookings, memberships, search, downloads and connections to other systems.
- Content: State which copy, photographs, product data and brand assets exist, and who supplies anything missing.
- Editing: Who will update the website, and which parts need to be easy to change?
- Constraints: Give the budget range, the reason for the deadline and any supplier or approval dependencies.
- Review and launch: Name the approval contact and clarify domain, hosting, enquiry delivery and tracking responsibilities.
Attach reference websites with comments about the useful parts. A visual example can help explain tone or layout, but it does not specify integrations, copywriting or ongoing support. Those belong in the written brief.
An example of a clear brief
Fictional example: A local maintenance business wants a WordPress website for property managers. Its current site groups every service on one page, making it difficult to understand what is offered. The first release needs a home page, four service pages, an about page, permitted project examples and a contact page.
The business has an approved logo and service descriptions, but photography still needs selection. Visitors should be able to send a service enquiry from a phone. One manager will approve the content; an administrator needs to edit service information afterwards. Online payment and booking are possible later phases, not assumed requirements for this launch.
This brief gives the team something concrete to assess: content structure, mobile enquiry flow, asset readiness and editing needs. It also makes the later ideas visible without silently including them in the initial scope. No cost, delivery period or business result is implied by the example.
What changes the scope of a website quote
Page count is only one input. A small site with an unusual integration, several approval teams or complex product data may need more planning than a larger site with straightforward content. Mention these requirements early so the proposal can explain its assumptions.
Ask the team to identify dependencies and exclusions in its response. For example, who writes the content, who pays third-party subscriptions, who configures a specialist external system and what happens after launch? This makes quotes easier to compare against the same work.
Use the redesign scope guide for an existing site and the website project planning roadmap to see where the brief fits in the wider process. The onboarding guide explains what to gather before completing the questionnaire.
Put it into practice
Include the practical details
- Business name, website URL, and contact details.
- Whether this is a new site or redesign.
- Target customers and the problems they need solved.
- Pages you already know you need.
- Functionality such as forms, ecommerce, bookings, memberships, downloads, or integrations.
- Brand assets, logos, colour references, and fonts if available.
- Content status: ready, needs editing, or still needs to be written.
- Important deadlines and why they matter.
- Budget range, even if approximate.
Keep in mind
Explain what is not working
Slow pages, confusing navigation, weak enquiries or difficult editing help the team understand why the project is needed.
Mistakes to avoid
- Only saying “modern website” without explaining the business goal.
- Requesting a quote before listing required functionality.
- Leaving out ecommerce, membership, booking, or integration requirements.
- Assuming content writing, image sourcing, SEO, or hosting is automatically included.
- Not mentioning approval layers or deadline pressures.
Useful answers
Common questions
Can I send a rough brief?
Yes. A rough brief is often enough to begin the conversation, especially if you are willing to answer follow-up questions.
Do I need a sitemap before asking for a quote?
You do not need a final sitemap, but a rough page list helps a lot. If the site structure is unclear, discovery may be needed before a fixed scope is possible.
Should I include my budget?
Yes. A budget range helps match recommendations to what is realistic. It also prevents a proposal from being shaped around the wrong level of work.
