Brief

A brief is the document a client hands to an agency, freelancer or internal team at the start of a project: a structured summary of goals, target audience, scope, budget, timeline and constraints. It is the foundation for quoting and executing anything from an ad campaign or a rebrand to a new website or application — and, later, the reference point when someone asks "was this actually in scope?".

What a good brief consists of

The heart of a brief is the problem and the goal, not a prescribed solution — the contractor's job is to propose the "how" once the "why" is clear. A complete document answers:

• Who are we? — company, product, positioning, what has been tried before,
• What do we want to achieve? — the business goal expressed as measurable KPIs (leads, conversion rate, signups),
• Who are we talking to? — the audience, ideally sharpened into buyer personas,
• Within what limits? — budget, deadlines, legal requirements, technical constraints and brand guidelines,
• What does success look like? — acceptance criteria and how results will be measured.

Specialized variants exist for each discipline: creative briefs for campaigns, media briefs for buying, content briefs for writers, and technical or web briefs for digital builds.

Practical use

In web projects the brief precedes both the quote and the specification. It should cover the intended site structure, key functionality (forms, e-commerce, integrations), CMS preferences, who supplies content, hosting and domain arrangements, plus visual references — sites the client likes and why. From the brief, the team derives wireframes and estimates; a misunderstanding caught at this stage costs a conversation, the same misunderstanding after launch costs a rebuild.

A habit that pays off is the debrief: the contractor plays the brief back in their own words, surfaces gaps and confirms the goal before work starts. Keep the brief versioned, too — every approved scope change belongs in it, because the brief is what settles later disputes.