What a brief is doing before a word gets written
A website brief is the document that tells whoever writes the page, a copywriter, a founder doing it themselves, or an AI tool given a prompt, what that page needs to achieve before any copy exists. It states who the page is for, what it has to say, and what the reader should do once they have read it. Skip this stage and every later decision, from the headline down to the wording of the call to action (CTA), gets made by guesswork.
A brief written properly saves a round of rewriting later, because the disagreements that usually surface at review stage, wrong tone, wrong emphasis, a benefit left out, get settled before the page is drafted.
The five things a brief needs to state
Most briefs fail not because they are too short but because they are vague in specific places. The parts worth getting right are these:
- Page purpose: what this particular page is for, stated as an outcome. "A product page for a subscription box" is a category. "A product page that gets an existing newsletter subscriber to start a free trial" is a purpose.
- Audience: who is actually reading, described by their situation. "Someone comparing three suppliers before lunch" tells a writer more than "decision-makers aged 35 to 55".
- Tone of voice: how the brand sounds. A brief that says "not too corporate" has told the writer nothing; one that names the register (see our note on tone of voice) gives them something to match.
- Constraints: anything the copy cannot claim, cannot say, or must include for legal or brand reasons, stated up front.
- Goal: the single action the page is built around, worded as the actual action. "Get the reader to book a call" is a goal. "Build trust" is not, because nobody can tell from that instruction what the page should do differently.
Where briefs fall short
The most common gap is an audience described so broadly it covers everyone who might conceivably buy, which in practice tells the writer nothing about any one of them. A brief that names a specific reader in a specific moment gives the writer something to aim the sentence at; a brief that names a market segment gives them a demographic to describe, which is a different job entirely.
The second common gap is a goal stated as a feeling. "We want the page to feel more premium" describes a mood. A brief that instead states the action, and leaves tone as a separate line, gives the writer two clear jobs. Our guide on how to brief a copywriter goes through this in more detail, including the specificity a good brief needs on format and constraint as well as goal.
How a stated brief becomes page structure
Once purpose, audience, tone, constraints and goal are written down, they map fairly directly onto the sections of the page itself. The stated audience shapes what goes above the fold, the part of the page visible before scrolling, because that is where the reader decides whether to keep reading at all. The stated goal shapes the CTA, because a CTA that promises an action the brief never named is a CTA nobody briefed for. Structures such as AIDA (Attention, Interest, Desire, Action), covered in our piece on copywriting formulas, are easier to apply once the brief has already answered who the reader is and what they are meant to do.
Checking a brief against a tool
The Website Brief Starter takes the same five elements, purpose, audience, tone, constraints, goal, and turns them into a working document a writer can start from. It can suggest structure and prompt for the gaps a brief commonly leaves open, but it cannot know your product, your audience's actual objections, or the constraints your legal team would insist on, so treat what it returns as a first draft to check line by line. It can produce an answer that is confidently wrong in a specific detail, and the person who knows the product is still the one who has to catch that.
A brief is worth the time it takes to write because it is cheaper to argue about a goal on paper than to argue about a finished page. Set out the five elements plainly, run them through the tool if that is useful as a starting structure, and check the result against what you actually know about the reader before anyone calls it done.