The Website Project Brief: What to Decide Before Design Starts

Start with the decision the site must support

A website brief is more useful when it describes a business decision, not just a list of pages. Write down what a visitor should understand, trust, or do after visiting. “Generate qualified consultation requests from commercial property owners” gives a team a direction that “build a modern site” does not.

The five parts of a useful brief

1. Business outcome

   Name the commercial or operational result and how you will recognize progress.

2. Priority audiences

   Describe the people who matter most, their context, and their objections. Rank audiences instead of asking one homepage to speak equally to everyone.

3. Content and proof

   List the services, evidence, credentials, examples, and answers a visitor needs. Mark what exists and what needs writing or approval.

4. Constraints

   Record the launch date, accessibility expectations, languages, integrations, ownership requirements, and reviewers.

5. Success measures

   Choose a small set of observable measures and pair analytics with sales or customer feedback.

Questions that prevent expensive assumptions

• Who owns final content and approvals?
• Which existing systems must the site connect to?
• What must be editable by the team after launch?
• Which pages are essential on day one?

Turn the brief into a working plan

1. Rank the visitor journeys

   Choose the two or three paths that must work at launch, such as understanding a service, finding a location, booking a consultation, or requesting a quote. A website cannot make every page equally important.

2. Audit the source material

   Collect existing copy, photography, case studies, testimonials, brand assets, legal text, and analytics access. Mark each item as ready, needs revision, needs approval, or does not exist.

3. Name decision-makers and deadlines

   Specify who supplies content, consolidates feedback, approves design, signs off on launch, and owns the site afterward. Unassigned decisions are a common cause of delayed projects.

4. Write the first measurement plan

   Decide how a qualified inquiry, booking, download, or other meaningful result is recognized. Pair the measurement with qualitative feedback so a number is not misread in isolation.

Example: focus the homepage before listing every service

A local consultant might choose one priority audience, explain the costly problem it faces, show one relevant proof point, and invite a consultation. That focused route can be more effective than asking the homepage to introduce every service, industry, team member, and future offer with equal emphasis.

A brief is a boundary, not a prison

Good discovery can change the plan when new evidence appears. The brief makes that change visible: the team can agree what moved, what it costs, and which outcome it protects.