A website brief is the cheapest artifact in the whole engagement — and the most neglected. When it is vague, teams burn budget on subjective redesign loops, late CRM integrations, and SEO bolted on after launch instead of baked into structure and content.
A brief is not “make it modern.” It names the business problem, the primary conversion, and the evidence that the solution works.
What breaks without a solid brief
| Gap in the brief | Typical project impact |
|---|---|
| No KPI / north star | design debates without acceptance criteria — “done” stays undefined |
| Content owner unclear | beautiful templates filled with lorem ipsum — launch slips |
| “CRM integration” mentioned late | forms rebuilt under pressure + fragile field mapping |
| SEO deferred | thin pages, duplicate intent, missing transactional landings |
Seven blocks every useful brief contains
- Business context — what you sell, what is flagship vs experimental.
- Primary goal + one dominant conversion model.
- Audiences and objections — who decides, what they fear, how they search.
- MVP vs phase 2 — written scope; everything else is backlog.
- Integrations — CRM, analytics, compliance, payments as applicable.
- Brand + content ownership — guidelines and who ships final copy.
- Acceptance criteria + timeline — milestones, approvers, UAT format.
Business goal: one north star
Pick a measurable outcome: qualified leads per month, booked demos, ecommerce checkout completion, or bounce reduction on paid landings. Secondary metrics (share of organic traffic, form abandonment) support the north star — they do not replace it.
Supporting metrics
- cost per qualified lead (when baseline exists)
- form completion vs field-level dropout
- sales SLA from submission to first touch
- organic vs paid mix when SEO is in scope
Personas, promises, and mistrust moments
Draft 2–3 decision-maker profiles: role, buying committee, typical objections. For each, specify the one-sentence promise the hero must carry and the proof section that neutralizes doubt. That ordering drives IA and page templates.
If you cannot phrase how customers search, you are not ready to brief SEO — you are ready for a structured discovery workshop.
Information architecture + SEO in the brief
List intended page types: home, services (one primary intent per URL), proof/case studies, content hub, legal. Flag transactional phrases that deserve dedicated landings. A short IA sketch prevents “everything on one scroll” and anchors internal linking.
SEO minimum to specify
- starter keyword list split by intent
- markets/languages + hreflang needs
- performance budgets as acceptance criteria
- ownership of titles/meta at launch
Integrations — MoSCoW matrix
Each integration is mapping, error handling, and often maintenance — not a checkbox. Separate must-haves from phase-two experiments before estimation.
| Band | Examples | Brief note |
|---|---|---|
| Must | forms → CRM, baseline analytics, consent | describe pipeline stages + required fields |
| Should | newsletter, FAQ bot, FAQ schema | define human escalation rules |
| Could | content hub features, light personalization | budget as phase 2 |
| Won’t (now) | SSO, marketplace, multi-currency | explicitly out of MVP — in writing |
Brand, UI references, and copy responsibility
Attach guidelines or state they will be produced inside the project. Provide directional references (not “clone this”) and anti-patterns to avoid. Clarify who owns final copy and how copy deadlines align with UI lock — content delay is the most common schedule killer.
Definition of Done
- staging-tested forms into CRM (or sandbox) with error paths covered
- agreed LCP/CLS thresholds on mobile for hero templates
- accessibility bar met for contracted level
- meta/H1 aligned with keyword map for agreed URLs
- handover docs / CMS training for editors
Roles, decisions, and cadence
Name the product owner, legal/stakeholder reviewers, and how budget changes get approved. Define meeting cadence and what happens when feedback misses a deadline — this prevents conflicting “sources of truth.”
Pre-send checklist
- 5–7 sentence company overview + link to current site if any.
- One sentence: primary conversion + how it is measured.
- Competitors or benchmarks (local or global).
- must-have integrations + test accounts.
- brand assets or explicit plan to create them.
- launch window and immovable external deadlines.
A crisp one-page brief signed by the revenue owner beats a fifty-page doc full of jargon nobody owns.
Related in the websites cluster
FAQ
Frequently Asked Questions
- No — describe workflows and constraints. Engineering proposes stacks that fit maintenance, SEO, and security.
- Often 2–6 pages plus attachments. Clarity beats length — a short brief with KPIs beats a vague encyclopedia.
- When goals, MVP scope, integrations, and acceptance criteria are agreed in writing — later changes are controlled scope change, not assumed tweaks.
- State who produces it, by when, and whether copywriting is budgeted. IA can precede final prose — launch cannot.
- It complements it — workshops surface nuance, but decisions still need a written summary or ambiguity returns.