What to include in a website brief (so estimates do not explode)
Must-haves, nice-to-haves, and red flags that turn vague ideas into a priced plan
A brief is not a mood board dump. It is the shared artifact that lets someone price work without inventing your business for you. Thin briefs produce padded quotes or silent assumptions. Good briefs produce ranges you can challenge.
Must-haves in every useful brief
If these are missing, the estimate is partly fiction. Fill them before you ask for a number.
Brief must-haves
- Who it is for and what success looks like in 90 days
- Primary offer and call to action (book, buy, inquire)
- Page inventory or journey map—not “about 10 pages”
- Content readiness: who writes, who approves, what already exists
- Must-have integrations (CRM, booking, payments, analytics)
- Constraints: timeline, languages, brand rules, legal
- Explicit out-of-scope list
- After launch: who hosts, who edits, who measures
Red flags that inflate price
Ambiguity is expensive. Vendors either pad for risk or underbid and change-order later. Both outcomes come from the same thin brief.
How to write the brief without a workshop circus
You do not need a 40-page PDF. You need decisions. A short document or wizard intake beats a long deck that never chooses.
- 1
Name the job
One primary audience, one primary action, one proof story that supports it.
- 2
List surfaces
Pages and states that must exist at launch. Park the rest in a later phase.
- 3
Attach reality
Links to current site, brand files, competitor references, and content owners.
- 4
Mark unknowns
Open questions stay visible. Do not hide them inside a fake fixed price.
Write a brief in one afternoon
Nice-to-haves belong in a phase plan
Animation polish, secondary landing pages, and experimental features can wait. Pricing everything as launch-critical is how budgets die. Separate must-ship from next-sprint.
Safe to phase later
- Secondary market pages once the core offer converts
- Advanced personalization before basic tracking works
- Portal features that are not part of the marketing job
- AI flourishes without a measured workflow behind them
Final thoughts
A brief that names outcomes, inventory, content owners, integrations, and out-of-scope items is the cheapest insurance on a website project. Write it once, keep it alive, and let every estimate point back to the same artifact.
Related Articles
How long a website project really takes (and what slows it down)
Realistic timelines by package—and the content, revision, and integration delays that stretch them
How to choose a web agency: 12 questions that expose vague proposals
Ask these before you sign—scope, hosting, SEO ownership, handoff, and maintenance
Ready to build something this considered?