How to Write a Website Brief That Gets Accurate Quotes
A section-by-section guide to writing a website brief, from goals and audience to features, content, integrations and budget, so quotes are accurate.
The quality of the quotes you receive for a website depends almost entirely on the quality of the brief you send. A vague brief produces guesses: some providers quote low and plan to make it up in change requests, others quote high to cover every possibility, and you end up comparing numbers that describe different projects.
A good brief does not need to be long or technical. It needs to answer the questions every developer will ask before they can estimate. Here is what to include, section by section.
1. About your business
Two or three paragraphs: what you do, who your customers are, and what makes you different. Include links to your current site, if you have one, and to your social profiles. This context shapes every design and content decision.
2. Goals
What should the website achieve? Be specific and, where possible, measurable:
- "Generate 30 qualified enquiries per month through the contact form"
- "Let customers book appointments without calling us"
- "Sell our product range online, with stock synced to our warehouse system"
- "Reduce support calls by answering common questions"
If you only include one section, make it this one. Goals tell the developer what matters and what is decoration.
3. Audience
Who will use the site, and what do they need from it? Describe your two or three main types of visitor, what they are trying to do, and what devices they mostly use. A site for busy tradespeople on phones looks different from a site for procurement teams on desktops.
4. Pages and structure
List the pages you expect, even roughly. A simple sitemap is enough:
- Home
- About
- Services, with one page per service (how many?)
- Case studies or portfolio
- Blog
- Pricing
- Contact
Note which pages share a layout. Developers estimate by unique templates, not total pages, so "ten service pages using the same layout" is very different from ten unique pages. Our guide to website development costs explains why.
5. Features and functionality
List anything the site must do beyond displaying content:
- Contact or quote forms, and where submissions should go
- Booking or scheduling
- Search and filtering
- User accounts or a member area
- E-commerce: number of products, payment methods, shipping rules
- Multiple languages
- Calculators, quizzes or other interactive tools
Mark each one as essential for launch or nice to have later. This lets providers quote a core version and the extras separately.
6. Integrations
Which other systems must the site connect to? CRM, email marketing platform, booking system, payment provider, analytics, chat widget, inventory or ERP. Name the actual products you use. "Connect to our CRM" cannot be estimated; "send form submissions to HubSpot as new contacts" can.
7. Content
Who will write the copy and provide images? Is existing content moving from an old site? How many blog posts or products need migrating? Content is the most common cause of delayed launches, so be honest about what exists today.
If you have an existing site with search traffic, mention it. Migrating URLs and setting up redirects properly protects the rankings you already have.
8. Design direction
Share your logo, brand colors, fonts and any brand guidelines. Then list three to five websites you like and say what you like about each, whether the layout, the tone, the photography or the simplicity. Also list one or two you dislike. Specific references are far more useful than adjectives like "modern" or "clean".
9. Content management
Who will update the site after launch, how often, and how technical are they? This decides which CMS or platform makes sense. If your marketing team will publish weekly, the editing experience matters as much as the design.
10. Technical requirements
Include anything you already know: preferred platform, hosting constraints, security or compliance requirements, accessibility standards you must meet, and expected traffic. If you do not know, say so; a good provider will recommend options.
11. Timeline
Give your ideal launch date and explain whether it is fixed, for example tied to a product launch or event, or flexible. Include when you can review designs and give feedback, because review time is part of the timeline.
12. Budget
Many businesses leave this out to avoid anchoring the quotes. In practice, a budget range gets you better proposals: providers can suggest what is achievable within it, rather than guessing at the scale you have in mind. A range is enough.
13. How you will choose
Tell providers what you will base your decision on, when you will decide, and who is involved. Ask for the format you want: a fixed quote, an estimate range, or a proposal with phases. If you are unsure which pricing model fits, see fixed price vs time and materials vs dedicated team.
Keep it short enough to read
A brief of two to five pages is plenty for most business websites. Clear bullet points beat long prose. The aim is not to design the site yourself; it is to give a developer enough information to ask good questions and quote with confidence.
When you bring a brief to Zemenay's tech outsourcing team, the first thing we do is go through it with you, then define deliverables, timelines and milestones in writing, so the quote and the finished site describe the same project.
