Positioning and messaging
Messaging template: a message house with proof beside every line
A copyable message house template with a proof column, a filled example, the launch brief that carries it, and how to mine competitor reviews for wording.
A messaging template is a message house: one roof sentence that states your core message, two or three pillars that each make one claim, and under every line the proof that makes it true, with its source, the date you checked it and a status. Copy the blank template below, fill it from your positioning decision and your competitor's reviews, and cut any line whose proof you cannot open.
The message house template
Copy this table into a document or a Claude Project file. Each row is one line of the house. The message house templates published by Atlassian and The Starr Conspiracy ask for proof points, but neither asks where each proof point came from, when someone last checked it or whether it still holds. The last two columns here record exactly that, so a seller can tell which lines are safe to say. Every table on this page is in the Markdown version of this page.
| Layer | Your line | Proof | Source and date checked | Status |
|---|---|---|---|---|
| Audience | The buyer and the job they are hiring a product for | |||
| Alternative | What that buyer uses today, including a spreadsheet or doing nothing | |||
| Roof | One sentence a buyer could repeat to a colleague | |||
| Pillar 1 | One claim | The fact that makes it true | Confirmed / Needs verification / Withheld | |
| Pillar 2 | One claim | |||
| Pillar 3 (optional) | One claim | |||
| Pain, in their words | The phrase buyers use for the problem | Review or interview it came from | ||
| Objection 1 | What a buyer says against you | The answer, with its proof | ||
| Objection 2 | ||||
| Owner and version | Name, approver, version, date of last review |
Three rules make the template work:
- The roof is one sentence with no adjective you cannot prove. "The fastest onboarding tool" needs a measurement; "See who must approve every onboarding task" needs only the product.
- A pillar without a confirmed proof point is not in the house. It moves to a "needs evidence" list and goes back to research.
- Proof is a fact someone can open: a product page, a dated document, a customer interview note you have permission to use, a review link. "Customers love it" is not proof.
A filled message house
Acme is a sample competitor, a general project-management tool. The house below belongs to a client-onboarding product for agencies that competes with it; the product and every line are a worked example.
| Layer | Line | Proof | Source and date checked | Status |
|---|---|---|---|---|
| Audience | Agency operations leads who onboard new clients | Discovery notes from five lost and won deals | Interview notes, Sept 2026 | Confirmed |
| Alternative | Acme for tasks, email for client approvals | Same notes; four of five named both | Interview notes, Sept 2026 | Confirmed |
| Roof | See who must approve every onboarding task, and when they did. | Pillars 1 and 2 | Confirmed | |
| Pillar 1 | Every task shows the client contact who approves it. | Approver field on each task | Product docs, 2 Oct 2026 | Confirmed |
| Pillar 2 | The approval is recorded on the task, with a timestamp. | Approval log on each task | Product docs, 2 Oct 2026 | Confirmed |
| Pillar 3 | Onboarding finishes faster. | No measured cycle time | None | Withheld |
| Pain, in their words | "Approvals get lost in email" | Phrase repeated in 6 of 22 Acme reviews (1–3 stars, agency reviewers) | G2, read 10 Oct 2026 | Confirmed |
| Objection 1 | "Acme already has approvals." | Acme's approvals page covers documents; tasks are not mentioned | acme.example/features/approvals, 10 Oct 2026 | Needs verification |
| Objection 2 | "Clients won't make another login." | Clients approve from an email link without an account; ships 4 Nov 2026 | Release record, 13 Oct 2026 | Needs verification |
| Owner and version | Head of PMM owns; VP Marketing approves; v1.2 | Reviewed 14 Oct 2026 |
Pillar 3 is the sentence a team most wants to write, and nothing supports it, so it stays out until someone measures cycle time. Objection 1 stays at Needs verification because a competitor page that does not mention a feature is not proof the competitor lacks it; a seller asks the buyer how they handle task approvals in Acme instead of claiming Acme cannot. Objection 2 answers with a feature that ships on 4 Nov, so sellers hold it until the release record shows general availability and the status moves to Confirmed.
One claim, several audiences
A pillar can have one version per audience. A version can change the emphasis, never the claim. For the operations lead, Pillar 1 becomes "You can see which client contact approves each task without opening the email thread." For the executive sponsor, "Onboarding finishes faster because approvals stop stalling" adds a speed outcome Pillar 1 does not support, so it is withheld. Store each variant beside its pillar, and check every variant for the claim it adds.
The positioning inputs the house needs first
A message house carries a positioning decision; it cannot make one. Before you write the roof, answer five questions from evidence, not from the product roadmap:
- Who is the buyer, and what job are they doing? A role and a situation, not a company size.
- What do they use today? Often a spreadsheet, email or doing nothing, and only sometimes a competitor. April Dunford's method starts from the same place: "the status quo and shortlist competitors", then differentiated capabilities, then the value they create.
- What can you do that the alternative cannot, and how do you know? A product check proves the capability exists. It does not prove a buyer values it.
- What does that difference mean for this buyer? The value line becomes the roof.
- Who is this not for? A buyer who needs single sign-on you do not offer is excluded, and gets no variant in the house.
Positioning and messaging change on different triggers. Rewording the roof is copy work and goes through the house's approver. A new buyer, a new alternative or a difference you can no longer prove reopens the positioning decision, and then every pillar is rechecked.
When the inputs come from buyers you have already sold to or lost, the win-loss analysis guide covers which findings are strong enough to change a message.
Mine competitor reviews for the customer's words
Your buyer's wording for the problem is already published, in your competitor's reviews. A one- to three-star review of Acme from an agency operations lead tells you what the pain sounds like, which pillar matters and which objection your sellers will hear. Four- and five-star reviews tell you what Acme does well, which is where you should not pick a fight.
- Pick the reviews that match your buyer. On G2, Capterra or Trustpilot, filter by role, company size or industry where the site allows it. A complaint from a 5,000-person enterprise does not belong in a house for agencies.
- Read the original, not a snippet. Note the review link, a short ID, its date, the reviewer's stated role and what the passage says, with qualifiers such as "on mobile" or "after setup" kept in. Keep a reviewer's own account apart from a testimonial the vendor chose or a third party's summary.
- Read by hand. G2's terms of use (updated 9 July 2026) prohibit collecting its content "through automated, programmatic, or mechanical means", and section 3 of the same terms restricts copying or reproducing content from the site. Read the reviews yourself, and check each site's terms before you copy review text into a document or paste it into any tool.
- Count each review once. "6 of 22 reviews" describes the reviews you read, not Acme's whole customer base. Reviews you selected for complaints cannot tell you how common a complaint is.
- Keep the opposing reviews. A reviewer who says approvals in Acme work fine goes beside the theme, with their role, because it may show which buyers you should exclude.
Where a site's terms let you keep the passages in a document, Claude can group them. This prompt keeps every theme traceable to a passage:
Group these review passages into themes about the problem my buyer describes. For each theme, quote the exact passages with their review IDs, count the unique reviews behind it, and list any passage that contradicts it. Do not paraphrase inside quotation marks and do not propose product features.
Check every quoted passage against the original before a phrase enters the house. The reviewer's words go into the "Pain, in their words" row and shape the roof. They never appear in public copy as if your own customer said them.
Reviews leave questions open: why the buyer chose Acme, what almost made them leave. Those need a conversation, and the win-loss interview questions are the place to start.
The launch brief: six sections that carry the house into a release
A launch brief is one dated page that turns the message house into a release: what changes, for whom, when, and who owns each piece. Pendo's launch brief template calls it "more tactical and time-bound" than a product requirements document, and that is the right test: if a line has no date or owner, it belongs somewhere else. A packaging, pricing or availability change is a launch too, and gets the same brief. Here are the six sections, filled for the same onboarding product launching client approvals without an account.
| Section | What goes in it | Filled example |
|---|---|---|
| Audience | Buyers, affected customers, internal teams that will be asked about it | Agency operations leads; existing customers on every plan; support and sales |
| Change | Scope, availability by plan, date, any pricing change, each with its source | Clients approve tasks from an email link. All plans. General availability 4 Nov 2026 (release record, 13 Oct) |
| Narrative | The roof and pillars, copied unchanged from the house | Roof and Pillar 2 from house v1.2; Objection 2 moves to Confirmed at general availability |
| Enablement | Each asset, its audience, owner and ready-by date | Objection Handling card update (PMM, 28 Oct); support macro (Support lead, 30 Oct); release email (Lifecycle, 4 Nov) |
| Risks and open decisions | Evidence, consequence, accountable person, next action, date | Acme's approvals page may change before launch; PMM rechecks it on 3 Nov. Open: whether the link expires (Product lead, 21 Oct) |
| Measurement | One metric, defined so someone else can reproduce it | Share of client approvals made through the email link in the 30 days after 4 Nov, read from product analytics on 4 Dec |
Three rules keep the brief honest. Planned availability is not released availability: if the release record says beta, the narrative does not say "available to everyone". A name beside a risk is a proposal until that person confirms it, so unconfirmed rows stay marked open. And the metric describes the launch period without proving the launch caused it; if nobody has instrumented it yet, that goes under Risks and open decisions with an owner and a date. When an enablement row changes a seller card, the Objection Handling template has the fields that card needs.
Keep the house current
Recheck the message house when any of these happens:
- A source in the proof column changes: your product docs, a pricing page, the competitor page an objection answer cites.
- A seller hears an objection the house does not answer. It goes in as an open row with an owner, and sellers ask the buyer rather than improvise an answer.
- A win-loss interview or a new batch of reviews contradicts a pillar.
Test the wording on buyers as well. Before the first version goes out, and after any change to the roof, ask someone in the audience to read the roof and pillars and say what the product does. If they understand it but do not care about the problem, reopen the positioning; if they care but infer a capability you do not offer, rewrite the line.
Write the change rule at the top of the file: the roof and pillar sentences are fixed and change only through the named approver; audience variants are adaptable within their claim; every change bumps the version and the review date; and one named person sends the new version to sellers and writers through the channel they already read. If you keep the house in a Claude Project, replace the Project's copy of the file whenever the shared one changes.
Where Steve fits
Steve keeps the competitor side of your messaging current. It reads competitor websites, news and reviews every day, G2 and Trustpilot among them, and turns them into the battlecards and objection answers your house points to. Its six battlecard templates include Objection Handling, every line on a card shows Confirmed, Needs verification or Unverified with links to its sources, and a person approves each update before reps see it in Slack, Microsoft Teams, Zoom Team Chat or the CRM.
The tradeoff is scope. Steve does not write your roof or your pillars; the positioning decision and the house stay with your team, and a competitor update waits for whoever approves it. See what it covers on the Competitive Intel product page.
Frequently asked
What is a message house?
A message house is a one-page messaging template: a roof sentence that states the core message, two or three pillars that each make one claim, and the proof under each pillar. Writers, sellers and the website all draw their wording from it.
What should a messaging template include?
The audience and the alternative they use today, one roof sentence, two or three pillar claims, the proof for each with its source, date checked and status, the objections buyers raise with their answers, the words customers use, and an owner with a version number.
How many pillars should a message house have?
Two or three. Each pillar needs at least one proof point you can open and confirm. Two pillars with proof are stronger than three where one is padding, because the padded pillar is the line a buyer challenges first.
What is the difference between positioning and messaging?
Positioning is the decision: which buyer, against which alternative, on which difference you can prove. Messaging is the wording that carries that decision. Change the house when the wording improves; reopen positioning only when the buyer, the alternative or the difference changes.
How do I use competitor G2 reviews for messaging?
Read the competitor's one- to three-star reviews from buyers who match yours, and note the phrases they repeat, with the review link and date. Their complaints show which pillar your buyer cares about, and their words belong in your pain line.
What goes in a launch brief?
Six sections: the audience, what changes and when, the narrative copied unchanged from the message house, the enablement assets with an owner each, the risks and open decisions, and one success metric defined so someone else can reproduce it.
Keep reading
All posts- October 14, 2026Sales battlecard templates: 6 formats with filled examples (copy as Markdown)Six sales battlecard templates, each with its fields and a filled example: objection handling, feature comparison, customer stories and three more.
- October 7, 2026"Their price is 30% lower": five talk tracks that do not start with a discountSort a cheaper-competitor objection into one of four kinds with a single question, then answer it with one of five talk tracks. None opens with a discount.
- September 14, 2026How to analyze win-loss interviews with Claude: buyer quotes first, counts with a denominator, then the message changeAnalyze win-loss interviews with Claude: quotes before themes, counts with a denominator, CRM reasons side by side, and which findings change a message.
- September 14, 2026How to do competitor research: a one-page plan, an evidence table and a rule for disagreeing sourcesHow to do competitor research: write a one-page plan, log each fact in an evidence table, and settle disagreeing sources by scope, authority, then date.
Keep the competitor side of your messaging current