Why the established-product statement does not transfer to a launch
The framework page rewrites a statement for a product that already has users. Its recognition test reads the target aloud to real customers, its reason to believe can point at results, and the alternative is known because buyers have described it in interviews. A product that has not shipped has none of this. The people it is for have never used it, so the target is a hypothesis about who will care most. The proof is borrowed from whatever exists before the first sale. And the category is genuinely open, because buyers have no prior picture of where the product belongs.
A launch also changes the cost of being wrong. On an established product, a weak statement is revised quietly and the next campaign uses the new version. At launch, the statement flows into a press release, a newsroom page, sales training, paid search and packaging within the same few weeks, and the first description journalists print tends to stick. The product launches hub treats launches as a repeatable process with tiers and readiness gates; the positioning statement is the earliest item in that process to lock, so the decisions below are made under more uncertainty and with less room to correct them.
Decisions that change for launch
| Template step | In the generic statement | In a launch statement | Decision it forces |
|---|---|---|---|
| Category | The frame buyers already use for the product | Open: join a shelf buyers know, or try to create one | Existing category, new category, or a narrowed sub-category |
| Target | Recognised by current customers in interviews | Inferred from waitlists, pre-launch research and beta users | Which early segment leads, knowing it may not be the long-term buyer |
| Reason to believe | Track record, customer outcomes, reviews | Trials, specifications, certifications, founders, mechanism | Which pre-launch evidence is strong enough to print |
| Testing | Landing page variants after the statement is in use | Message tests and unbranded search ads before launch day | What result would change the statement before assets lock |
| Reach of the statement | Messaging hierarchy feeds every channel | Launch tier sets how far it goes into press and paid media | How loudly to make a claim that has thin proof |
| Revision | When the market or evidence moves | On a dated review once paying customers exist | When provisional proof is replaced and by whom |
Frame of reference: enter an existing category or claim a new one
The frame decides almost everything downstream. Entering an existing category gives buyers a shelf, a comparison set and search demand that already exists, but it places the product beside incumbents and invites a direct comparison on their terms. Claiming a new category frees the claim from those comparisons, yet buyers have no budget line for it, nobody searches for it, and every channel has to explain the category before it can sell the product. A middle route is a narrowed sub-category, a familiar noun with a qualifier that signals the difference.
Choose the existing category when the product is better on a dimension buyers already rank. Choose a new category only when the product does a job that nothing in the existing frame does, the launch tier funds the education, and the team accepts a slower start. The segmentation work in STP and the job evidence behind the value proposition canvas should settle this before anyone drafts copy, and the positioning guide covers how the frame of reference shapes the rest of the statement.
Reason to believe from pre-launch evidence
Before launch the usual proof, customers who got the benefit, does not exist, so the reason to believe is assembled from what does: results from a beta groupSelected customers use a working product or feature before general release, so the business learns whether it works for them and what the launch needs. or tasting panel, specifications and independent tests, certifications, the mechanism that explains why the benefit happens, and the experience of the founders or makers. Rank these by how hard a sceptical buyer or journalist could check them. A mechanism plus an independent test usually outranks a founder biography, which persuades the press far more than shoppers.
The trade-off is between narrow, strong proof and broad, soft proof. A claim backed by a single verifiable result is safer than a sweeping claim backed by enthusiasm. The messaging hierarchy and proof points guide explains how to attach substantiation to each claim; for a launch, add a column marking each proof point as provisional so that it is visibly temporary.
Test the statement with message tests and search ads before launch
Two kinds of test fit the pre-launch window. A message test shows recruited prospects the external version of each candidate statement, without the brand, and asks which describes them and which they would choose over what they use today. Search ads run unbranded headlines derived from each candidate to a holding page or waitlist, which shows which claim earns clicks and sign-ups from people already searching. The responsive search ads guide explains how headline combinations are served, which matters because a clean A/B TestControlled comparison of two variants. needs the competing claims kept apart, for example in separate ad groups or with pinned headlines.
Choose message tests when the categories being compared have little search demand, and search ads when they have plenty. In both cases write down, before the test starts, the result that would change the statement. Search tests have a built-in bias towards the existing category, because only existing language has volume, so a new-category candidate should not be rejected on search evidence alone.
Launch tier decides how far the statement is pushed into press and paid media
The tier from launch planning and launch tiers sets the volume. A flagship launch pushes the statement into a press release, an online newsroom, paid media and sales enablement at once, which means the claim must survive journalists testing it. A smaller launch keeps the statement on product pages and in messages to existing customers, where it can be adjusted more cheaply. The press releases and online newsroom guide covers how the headline and boilerplate carry the position into coverage.
The trade-off is reach against reversibility. The louder the launch, the more conservative the proof should be, and the more the new-category version of the claim should wait for evidence.
A review date for when real customer proof replaces the placeholders
Every provisional proof point should have a date or a milestone attached: a set number of weeks after launch, or the first batch of reviews, or the first renewal cycle. On that date the team reruns the recognition test with actual buyers, checks whether the target who bought matches the target who was predicted, and replaces borrowed proof with customer outcomes. Too early, and the review reacts to launch noise; too late, and founder claims keep carrying weight they were never meant to carry. Name an owner for the review, usually product marketing, so it is not left to whoever notices.
Decision points in a worked launch statement
Moorvale Kitchen chooses between two statements for a plant-based cheese
Moorvale Kitchen makes a cashew-based cheese that browns and stretches when heated, launching into supermarkets in eight weeks. The team drafts two statements.
| Template part | Statement A: new category | Statement B: better option | Evidence available |
|---|---|---|---|
| Target | Home cooks curious about cultured foods | Households cutting dairy who still cook cheese dishes | Waitlist survey of 1,150 sign-ups |
| Category | Cultured plant cheese, a new kind of food | Plant-based cheese | Search data: category terms have volume, new term has none |
| Key benefit | A fermented food with real character | Melts and browns like dairy cheese | Panel of 120 testers |
| Alternative | Artisan dairy cheese | Plant-based slices that stay rubbery | Panel interviews |
| Reason to believe | Fermented for ten days by a former cheesemaker | 71% of testers could not tell its melt from dairy in a blind grill test | Panel results, founder record |
Message test: 400 recruited prospects saw both external versions without the brand. 58% chose B as the one that described them; A drew stronger interest among a small group of food enthusiasts. Search test: three weeks and £1,800 on unbranded ads to a waitlist page. Headlines from B reached a 4.6% click-through rate and a 12% sign-up rate on the page; headlines from A reached 2.1% and 7%, on far fewer impressions because few people search for the new term.
Decision: B becomes the statement, with "fermented by a former cheesemaker" kept as a supporting message. The launch is a mid tier, so the press release leads with the melt claim and the panel result; the new-category idea is held back. Review date: twelve weeks after launch, when the first 300 product reviews and retailer sell-through data replace the panel figure.
The example shows why the order matters. Had the team written the press release first, the more exciting new-category idea would have been printed before anyone checked whether buyers looked for it. The search test was useful but biased, which is why the message test carried equal weight, and the review date stops a tasting panel from standing in for customers indefinitely.
Measuring a launch statement: KPIs before and after launch day
Before launch the measures are about reaction to words: preference and recognition in message tests, click-through and sign-up rates for each headline in search, and the size and make-up of the waitlist. In launch week the useful measure is pull-through, how many pieces of coverage, reviews and social posts repeat the core benefit in roughly the statement's terms, alongside branded search and Share of VoiceYour share of market visibility. for the category terms the statement claims. After launch, recognition is retested with buyers, the launch page is judged on conversion to the next step, and sales teams are asked which message they actually use. Each KPIA metric tied directly to an objective. should be agreed before the launch, with the measuring launch success guide supplying the wider launch scorecard. Read pre-launch tests weekly while they run, pull-through daily in launch week, and the rest monthly until the review date.
Where a launch statement misleads
Pre-launch tests measure response to a sentence, not to the product, so a statement can win every test and still fail when the product does not deliver the benefit. Waitlists over-represent enthusiasts, whose reasons for interest may differ from the mainstream buyer's. Search tests reward language people already use, quietly favouring the existing category. And founder-led proof is persuasive to journalists, which can make coverage look like validation when buyers have not yet been asked anything.
Common mistakes
- Writing the press release first. The release fixes the frame in public; settle the statement before it.
- Claiming a new category by default. It sounds bold and usually means nobody is searching for you.
- Treating panel results as customer proof. They are provisional and should be labelled that way.
- Testing with the brand name visible. Prospects react to the name rather than the claim.
- No decision rule before the test. Without one, every result gets read as support.
- Never holding the review. Placeholders that outlive their date become the permanent position.
