How to Write a Website Brief (With a Template)
A good website brief covers your business and audience, what the site must achieve, required pages and functionality, design references, content readiness, budget range and timeline. One to three pages is enough — longer briefs rarely improve the quotes.
The brief determines whether you get comparable quotes or four documents that cannot be compared. Most briefs describe what the client wants the site to look like and omit what it needs to do, which is the part that drives cost.
The steps
- 1
State the business problem, not the solution
Open with what is wrong today. 'Our enquiries come from Instagram DMs and we cannot track them' tells an agency more than 'we need a modern website'. Good vendors will propose solutions you had not considered — but only if they know the problem.
- 2
Define the primary action
Name the single most important thing a visitor should do: enquire, buy, book, download. Sites with one clear priority outperform sites trying to serve five audiences equally. If you cannot pick one, that is a strategy conversation to have before the brief.
- 3
List required pages and functionality separately
Pages are cheap; functionality is not. Separate 'About, Services, Contact' from 'booking system, payment gateway, customer login'. Agencies price these very differently, and mixing them into one list is why quotes diverge.
- 4
Include three reference sites and say why
Not just 'we like this one' — say what specifically. 'The way this site explains a complex product' is useful. 'This looks premium' is not. Include one site you dislike and why; that is often more informative than the ones you like.
- 5
Be honest about content readiness
State whether copy, photography and product data exist. Content readiness is the single biggest cause of delay in Indian web projects. Agencies that know content is not ready can scope and price for it instead of discovering it in week four.
- 6
Give a budget range
Withholding budget does not get you a better price — it gets you quotes across a range so wide they are useless. A range like ₹2–4 lakh lets vendors propose appropriately, and lets unsuitable ones self-select out.
- 7
State constraints and non-negotiables
Existing brand guidelines, a CMS your team must be able to use, hosting requirements, a hard launch date tied to an event. Constraints stated upfront save a revision cycle each.
Common mistakes
Give a range. Vendors price to fit budgets they know about, and guess wildly at ones they do not.
Say what the site must achieve and who for. Let the agency propose how it should look — that is what you are paying for.
Multi-language, GST invoicing, a customer login, WhatsApp integration — write them down. Assumptions become change requests.
One to three pages is enough. Long briefs bury the important constraints and rarely improve the response quality.
Want us to handle this instead?
Tell us where you're stuck. We'll give you a straight answer on scope, cost and whether it's worth outsourcing at all.
Frequently asked questions
Should I include my budget in a website brief?
Yes, as a range. The common fear is that agencies will price to the budget, and some will. The larger cost is receiving quotes from ₹40,000 to ₹8,00,000 that cannot be meaningfully compared, and wasting weeks discovering that most vendors were never a fit.
How long should a website brief be?
One to three pages for most projects. Enough to cover the business, the goal, required pages and functionality, references, content status, budget and timeline. Beyond that, additional detail generally belongs in the discovery phase rather than the brief.
Do I need a brief for a small website?
Even a one-page brief helps. For a ₹50,000 site, half a page covering the goal, the pages and whether content exists will still produce better and more comparable quotes than a phone call describing what you want.
What if I don't know what I need technically?
That is fine and normal. Describe the outcome — 'customers should be able to book a slot and pay a deposit' — and let vendors propose the mechanism. Briefs go wrong when non-technical clients specify technology rather than requirements.