Product Launch Messaging Brief: One Page Before the Campaign
Who, job, offer, proof, objections, channels, owner. Seven cells on one page that stop a launch from turning into twelve slightly different announcements.
The launch date is set. The designer wants copy, the developer wants a page title, and sales wants a one-liner. If no one has written down who the launch is for and what you may say, each of them will invent it. A one-page brief stops that, and it takes an afternoon.
Print the launch messaging brief and fill it before any campaign work starts. The company-wide version is the brand brief. If you are still choosing a position, start with the brand positioning framework.
Seven cells, one page
| Cell | Good | Fails when |
|---|---|---|
| Who | One primary buyer in a sentence, plus who it is not for | A list of personas or “everyone who needs this” |
| Job | The outcome they hire this for, in their words | A feature list or a mood |
| Offer | What they get, what it costs, what it does not include | Four versions depending on who asks |
| Proof | What you may show on launch day: demo, process, first-party fact | A claim with no source |
| Objections | The three reasons a buyer says no, and the honest answer to each | “There are none” |
| Channels | Where it appears, in order, with one purpose per channel | Every channel, all at once, same text |
| Owner | One name who approves copy and decides when something ships | A group or “marketing” |
flowchart TD
W["Who"] --> J["Job"]
J --> O["Offer"]
O --> P["Proof"]
P --> B["Objections"]
B --> C["Channels"]
C --> N["Owner"]Who and the job
Name one primary buyer. Role, situation, and trigger. “Practice managers at independent clinics who just lost a week to a broken booking form.” Then write who it is not for. That sentence saves you from a launch email stretched to fit a segment you do not want.
The job is a verb phrase in their words. If a sales call note or a support message has a phrase that fits, use it verbatim. If you cannot find one, you have a research gap. Run three short conversations before you write another line.
Offer: say what it is and what it is not
One sentence a stranger can repeat. Then price or price range if you share it. Then what it does not cover. That last line saves more support time than any feature list. A launch offer that is vague about scope will generate the same question in forty inboxes.
- Offer line: what they get, in one sentence, no adjective that needs proof.
- Terms: price, start date, what is included, what is extra.
- Not included: two or three plain limits. Honest boundaries build trust faster than a long “everything” list.
- Call to action (CTA): one next step for the launch window. Book a call, join a waitlist, buy. Not three of them.
Proof you may show on day one
Brand-new offers rarely have a pile of results. That is fine. List what you can show today. A recorded demo. A screenshot of the real product. A process document. Your own use of it. A permissioned client fact, with scope. A hypothetical, labeled as one.
| Stage | Usable proof | Do not use |
|---|---|---|
| Brand-new, no clients yet | Demo, screenshots, process doc, your own use, labeled hypothetical | Invented testimonials, “trusted by,” made-up numbers |
| A few clients, no permission yet | First-party facts about the process; ask permission before naming anyone | Naming clients without written permission |
| Some permissioned clients | Named fact with scope and what it does not prove | Rounding a single result into a general promise |
If a line feels like it is stretching, run it through the Claims, Proof, Risk ladder. A thin proof cell is honest. A fake one ships and stays.
Objections, answered plainly
List the three reasons a good-fit buyer says no or waits. Get them from sales calls, replies to your pre-launch notes, or from the questions people ask when they see the first draft. Then write the honest answer to each, in a sentence.
| Objection | Plain answer | Where it appears |
|---|---|---|
| “We already have someone who does this.” | “Keep them. This covers the part they do not: [specific part].” | Landing page, sales call |
| “It is too early to know if it works.” | “Correct. Here is what you can see today: [demo]. Here is how we will review it at week four.” | Launch email, FAQ |
| “What does this actually cost?” | “[Price], with [included]. Not included: [limits].” | Landing page, proposal |
Do not write “there are no objections.” There always are. If you cannot name them, you have not talked to enough buyers.
Channels in order, one job each
Not every channel, all at once, saying the same thing. Pick an order and give each one a single purpose. The website explains. Email reminds. Social points. Sales answers. When every channel carries the full pitch, the reader hears the same pitch five times and acts on none.
- Home base first: one page that holds the full story and the CTA. Everything else points here.
- Warm audience next: email list or existing clients. Short, specific, one link.
- Public posts: social or articles. One angle per post, not the whole brief.
- Sales conversations: one who-line and one proof item everybody uses.
One owner, written down
One name approves copy and decides if something ships. Commenters are listed. A reviewer who sees a draft the day before launch is not a commenter, they are a risk. Put the sign-off time on the page: “Copy locked by [date and time].”
Hypothetical, labeled
Hypothetical. A small studio launches a fixed-scope website care plan. Who: practice managers at independent clinics who worry the site broke quietly. Not for: large chains with in-house developers. Job: stop worrying the booking form is down. Offer: monthly checks and updates, written scope, monthly price shown on the page, not included: new page design. Proof: the studio’s own monitoring screenshot and a one-page checklist. Objections: “we already have someone,” “is it worth it,” “what if it still breaks.” Channels in order: care plan page, email to past clients, two posts, a one-line version for sales calls. Owner: founder. Copy lock: three working days before launch. That page fits on one sheet. A pile of campaign mockups would not.
What the example does not prove: that care plans are right for any given studio, or that the launch will succeed. It shows the cells can be filled without invented results.
A three-week runway
- Week 3 before: fill who, job, offer. If the team disagrees, that is the work. Gather the three objections.
- Week 2 before: fill proof and channels. Draft the launch page and one email from the brief only.
- Week 1 before: owner reviews, copy locks, sales gets the one-liner and the objection answers.
- Launch week: ship in channel order. Log new objections for the next brief.
- Week 2 after: review the brief against what happened. Update it, do not discard it.
What a good launch brief prevents
- Version drift: the site says one price, the email another, sales a third.
- Proof creep: someone adds “trusted by” because the page looked bare.
- Channel sprawl: five channels, none with a clear job.
- Launch-day surprises: the same objection hits sales and support with no prepared answer.
For the meeting that uses this page, see how we run a branding kickoff. If you want a launch page and brand system that match the brief, that is branding and website work. Contact.
Frequently asked questions
What is a product launch messaging brief?
A one-page document that fixes who the launch is for, the job it helps with, the offer, the proof you may show, the likely objections, the channels in order, and one named owner. Everyone who writes launch copy works from it.
How is this different from a brand brief?
A brand brief covers the whole identity and who it is for over time. A launch brief covers one offer in one window. It borrows from the brand brief and narrows to what must be said, to whom, and where, between now and launch plus a few weeks.
When should I write it?
Before the campaign creative, the landing page, or the announcement email. Ideally two to three weeks out. If the brief is written after the assets, it becomes a description of what you already made and fixes nothing.
Who should approve it?
One person. Others can comment. If three people can each veto a line, you will get a launch that offends nobody and moves nobody. Write the approver’s name on the page.
What if the proof is thin because the product is new?
Say so in the proof cell. Use what you can show: a demo, the process, your own use, a labeled hypothetical example. Do not invent a customer story. A modest honest launch beats a loud one that someone later checks.