The Copy Playbook
Message Architecture · what you're saying, before you write a word
Foundation
This is the base layer of the copy system — the copywriting equivalent of the base theme. Fill this before writing anything. A headline, a post, an email, a landing page: they all inherit their message from here. Get the architecture right and the words get easy. Skip it and you polish sentences that were never going to land.
One thing sits above this page: Positioning. It decides what the thing is, what it beats, and who it's for. Job 05 below is inherited from it rather than decided here, and jobs 01, 03 and 06 all draw on it. Read that document first; brief from this one.
01
The reader — one specific person
Write to one person, not an audience. A real reader with a job, a frustration, and their own words for it. The vocabulary they already use is the vocabulary your copy uses — you're joining a conversation already happening in their head, not starting a new one.
Who is the one reader?
SharpA freelance designer who dreads the "just following up" invoice email and lets clients slide for weeks.
VagueSmall businesses who want to get paid.
The reader
One person
Specific beats broad. One reader you can picture, with their real words.
Use the words they already use for the problem. Don't invent vocabulary they'd never say.
Yours: the vocabulary-fight move — enter a conversation already happening, don't start one.
02
The one thing
If the reader remembers nothing else, what do they keep? Every piece of copy has exactly one answer. The failure is trying to land five ideas at once, which lands none. A competing idea isn't another sentence — it's another piece of copy.
The one thing
You never write a follow-up email again.
The one thing
One idea, always
The spine every headline, hook, and subject line expresses.
One per piece. A second competing idea = a second piece of copy.
Test: can the reader repeat it back in one breath?
03
The promise — outcome, not feature
The reader doesn't want your feature; they want what it does for them. "Automatic reminders" is a feature. "You get paid without the awkward chase" is a promise. Lead with the transformation. The mechanism can come later, once they care.
✓ Promise (outcome)
Get paid faster, chase invoices never.
Timing stops being a guess.
Your evenings back.
✕ Feature (mechanism)
Automated reminder scheduling.
Cash-flow forecasting module.
Configurable email templates.
The promise
What's in it for them
The outcome in the reader's terms, not the mechanism in yours.
Formula: [reader] gets [outcome] without [expected pain].
Feature answers "what is it"; promise answers "what do I get".
04
The proof — specifics, not adjectives
A promise without proof is a slogan. Proof is what makes it believable, and specifics always beat adjectives — "11 days faster" lands where "dramatically faster" evaporates. Climb the proof ladder as high as the truth allows, and never one rung higher.
strongestSpecific numbers — "11 days faster, 4,200+ teams"
strongNamed results — "Dana cut her payment time in half"
mediumDemonstration — show it working, live
weakMechanism — "because it sends on a schedule"
weakestBare claim — "the best invoicing tool"
The proof
Climb the ladder
Numbers > named results > demos > mechanism > claims.
Specifics beat adjectives. "11 days" not "much faster".
Yours: honest-by-default — climb as high as the truth allows, never fabricate to climb higher.
05
The position — inherited, not decided here
This job moved. "Instead of what?" turned out not to be one question but a chain of six, so it has its own page upstream. What happens here is simpler: open the captured positioning and copy two lines across. If there isn't one, that's the work to do before this brief — not during it.
Read from the captured positioning
The ShelfThe category the reader will file you under — and the neighbours they'll measure you against.
The InsteadWhat this reader would actually do if you didn't exist. Products, workarounds, people, and nothing.
Still yoursThe vocabulary fight lives one level up now — naming the shelf is the fight.
The position
Read it, don't rewrite it
Two lines lifted from the Positioning page: the Shelf and the Instead.
Deciding position inside a brief means deciding it differently every time. Decide it once, upstream.
No captured positioning? Stop and go do that. This brief will be guesswork otherwise.
Yours: coining the shelf is the vocabulary fight at product level — it just isn't settled here.
06
The stakes — the thing to beat is inertia
Your competition for this decision is mostly not a rival. It's the reader closing the tab and carrying on exactly as before. Between 40% and 60% of considered decisions end in no decision at all — and usually not because people prefer what they have, but because they don't feel confident enough to choose, and doing nothing is the option nobody gets blamed for. So the stakes answer one question: why act, rather than never. The honest answer is nearly always the compounding cost of the status quo.
✓ Real stakes
Every week you wait is another week of unpaid invoices.
The chase doesn't get easier; it compounds.
The ideas you don't write down stay unwritten.
✕ Manufactured
⏰ Offer ends in 4 hours!
Only 3 spots left today!
The stakes
Why act instead of never
The real cost of waiting, not a fake deadline.
Most decisions are lost to inertia, not to a competitor. Write against the reader's default, not against a rival.
Confidence is the blocker. Someone who can't tell how to choose will choose nothing — so clarity is part of the stakes.
Yours: real urgency only. No fake timers, ever. It would fight the whole brand.
07
The assembled brief
Filled in, the six answers are the brief for any piece of copy. Every downstream page — headlines, posts, emails, landing copy — pulls from these lines. This is the foundation the rest of the copy system inherits from, exactly the way every theme inherited from the base tokens.
The Northwind brief, assembled
Reader — the freelancer who dreads the follow-up email
One thing — you never write a follow-up again
Promise — get paid faster, chase never
Proof — 11 days faster, 4,200+ teams
Position ↑ — shelf: chasing tools, not accounting. Instead: doing it yourself, or nothing.
Stakes — the default is another month of not fixing it; the pile compounds
The brief
Six lines, then write
Assembled, the six answers brief any piece of copy.
Every downstream page pulls from these six lines.
Can't fill a line? That's the gap to close before writing, not while writing.