Translate a finished positioning document into a messaging system: champion definition, value matrix, messaging house, core narrative, homepage structure, and rollout. Pulls Pierri's 7-step homepage framework, Dunford's Setup / Follow-Through pitch architecture, and Moesta's JTBD interview method for surfacing buyer language.
Run this after positioning is locked. Before any homepage rewrite, sales-deck refresh, or paid-channel push. Re-run after major ICP, product, or competitive shifts.
Inputs required
- Completed positioning document (canvas, statement, messaging house skeleton)
- At least 5 customer interviews
- Competitive analysis with win/loss patterns
- Product demo or docs
- Site analytics (for rollout prioritization)
Steps
01 Lock the champion. Situation, not just job title.
The champion is the person closest to the problem with the motivation to push the decision through. Not the budget holder, who is too far removed from the daily pain to drive urgency. Not the IT buyer, who evaluates fit but does not feel the cost of doing nothing.
Define the champion in three layers:
- Company type. Stage, industry, team size, tech stack.
- Persona. Role, reporting structure, what success looks like in their job.
- JTBD situation. What they are trying to accomplish. What is currently breaking. What trigger makes them start looking.
The situation layer is the one most messaging skips. Two people with the same job title can have completely different buying situations. A sales manager at a 20-person startup who just missed a quarter has different urgency than a sales manager at a 200-person company optimizing an already-working process. Same persona, different situation, different message.
02 Mine customer interviews for the actual language.
Do not write messaging from your own vocabulary. Write it from the buyer's vocabulary. The phrases that land in headlines are almost always phrases buyers said in interviews, not phrases the product team invented.
JTBD switch interviews are the best source. They trace the timeline from trigger through decision. The trigger language ("we had a critical demo and the call quality broke on us") tells you where and how to advertise. The decision language ("we just needed something that worked without us thinking about it") tells you what the headline should say.
"JTBD interviews help you define a customer's language, what they actually mean by 'easy,' the root cause of why they switched, and how their story connects, all of which directly impact your product marketing."
— Bob Moesta, Intercom podcast
JTBD interviews surface the customer's actual language and the switch trigger
After 5 to 10 interviews, look for the phrases that appear across multiple buyers without being prompted. Those are your message candidates. Test them. If you can copy-paste a customer phrase into a headline and it sounds sharper than your current headline, that is not a coincidence.
03 Map the champion's situation. Then narrow to the exact pain.
List the functional activities the champion does day-to-day. Cross out everything the product does not address. What remains is the overlap between the buyer's situation and the product's capability. That overlap is where the message lives.
Most B2B messaging fails because it speaks to too many situations at once. "Streamline your workflow" covers everything and describes nothing. The champion's exact situation, described in behavioral terms, is a much tighter target.
Example: instead of "improve team productivity," the situation is "we have 8 reps calling the same prospect list, no way to see who talked to whom, and we lose deals because we call the same person twice in a day." That situation has a message. The first one does not.
04 Document the old way. This is what the Setup is about.
Before you can sell the new way, the buyer needs to recognize that the current way is failing them. Andy Raskin calls this the "old game to new game" narrative. April Dunford calls it the Setup.
"A live sales pitch is the best way for B2B companies to test their positioning… sales is a back-and-forth with a prospect; sales can and should be asking questions, looking for feedback, and handling objections. Marketing doesn't fully understand the sales team's needs when it comes to a narrative."
— April Dunford, "Sales-First Storytelling"
Test positioning in a live sales pitch, marketing stories are unfalsified theory until then
The Setup has three parts:
- Insight. A non-obvious truth the buyer can agree with. Something they recognize as true from their own experience.
- Alternatives. What buyers currently use or do instead. Including doing nothing.
- Perfect world. What the buyer's situation looks like if the problem is solved. Described in their terms.
Document the Setup before writing any product messaging. If the Setup lands, the product claims follow naturally. If the Setup is weak, no feature list will compensate.
"When you survey buyers who didn't buy, 40–60% say they made no purchase decision at all."
— April Dunford, Lenny's Podcast, 2026-04-28
40–60% of B2B buyers say "no decision", your real competitor is the status quo
The most important alternative to include in the Setup is the status quo. Most deals are lost to inertia, not to named competitors. The Setup must make the cost of inaction concrete.
05 Choose the comparator. This determines the message architecture.
The comparator is the alternative the buyer is most likely to evaluate. It could be a direct competitor, a manual process, or an adjacent tool. Name it explicitly. The message hangs off the comparison.
Emily Kramer's four product types tell you which message architecture fits:
| Product type | Comparator | Message job |
|---|---|---|
| New category | The old way of doing things | Explain the category exists and why it matters |
| 10x better | Direct competitor | Prove superiority on a specific, measurable dimension |
| New way | A manual process | Make the old way feel costly and the new way feel inevitable |
| Incumbent | Price, feature parity, trust | Signal stability and depth |
The comparator also determines the Setup's length. Greenfield comparators need more explanation. Known competitors need less.
06 Build the value matrix. Per persona, not per feature.
For each champion persona, map the full chain from pain to message:
| Pain / Situation | Product Benefit | Feature / Capability | Message |
|---|---|---|---|
| What blocks them | What the product solves | What powers it | How to say it in one line |
The key constraint: the message column must be specific to the persona's situation. If the same message works for two different personas without editing, it is too generic for either.
Features connect to benefits through capabilities. The capability is what the user actually does. The feature is what enables it. The benefit is what changes because of it.
Most messaging jumps from feature to benefit and skips capability, leaving the buyer to make the connection themselves. Do not make them.
Example:
| Pain | Benefit | Capability | Message |
|---|---|---|---|
| Calls go to voicemail after hours | No missed revenue opportunities | AI agent answers and qualifies every call | "Every inbound call gets answered, even at 2am, and the summary is in your CRM by morning" |
07 Write the overall positioning paragraph. One-liner, then expand.
Unique Belief + Value Provided + Who Cares. The one-liner is the test. If it requires more than one sentence to be understood, the positioning is not yet sharp.
Then expand to two to three sentences for the paragraph version used in sales decks and email signatures. The expansion adds context but does not dilute the core claim.
Run the four-question test against the one-liner:
- What is it? (category)
- Who is it for? (champion)
- What does it replace? (comparator)
- Why is it better? (differentiator)
"B2B homepages should lead with the trinity of the specific use case, the alternative the buyer is currently using, and the result the product produces, communicable in roughly five seconds."
— Anthony Pierri, FletchPMM
B2B homepages must communicate use case, alternative, and result in five seconds
08 Map the capability layer. This is where copy hangs.
For each feature you plan to highlight, define what the user does. The capability bridges feature to benefit. Copy hangs off capabilities, not features.
Wrong: "Our AI summarizes meetings." (feature)
Right: "Review the full call in 90 seconds and see which objections came up." (capability)
Better: "Know exactly where every deal stood before you walk into the next call." (capability + emotional frame)
The capability layer also tells you what to demo. Not the feature. What the user does with the feature. Show the user doing something, not the interface existing.
09 Build the messaging house. Exactly three pillars.
[Overall value proposition — one sentence]
/ | \
[Pillar 1] [Pillar 2] [Pillar 3]
| | |
[Feature, proof] [Feature, proof] [Feature, proof]Three pillars. No more. If you have four or five value themes, choose the three that matter most to the champion. The others can live in dedicated landing pages or persona-specific content.
Each pillar needs:
- A pillar name (the value theme, phrased as a benefit)
- A one-line message for that pillar
- Supporting features as evidence
- At least one customer quote or data point
The messaging house is the internal architecture. It is not customer-facing copy. Sales uses it to stay consistent. Marketing uses it to brief content. Copy hangs off it but is not identical to it.
10 Write the core narrative. One paragraph, then adapt per channel.
One paragraph: problem, stakes, solution, outcome. This is the seed. Every channel adaptation starts here and adjusts length, tone, and evidence to fit the context. The paragraph version is for email signatures, about pages, and investor updates. The one-liner is for ads and cold outreach. The three-pillar version is for the homepage.
The company story is the strategy. When sales decks, the homepage, and product release notes start diverging from each other, positioning is drifting.
"The company story is the company strategy."
— Andy Raskin, citing Amplitude, Clearbit, Auvik cases
Run a monthly narrative-drift audit across decks, homepage, and release notes
Set a monthly audit: compare the sales deck, the homepage hero, and the most recent release notes. Do they share the same problem framing and the same differentiator claim? When they diverge, fix before the next campaign launches.
11 Generate 3 or more angles. Evaluate before choosing.
The core narrative has one setup. The angle is how you enter the conversation. Different anchors work for different personas and different awareness levels.
Common anchor types:
- Pain anchor. Lead with the problem: "Missed calls are costing you more than you think."
- Proof anchor. Lead with a result: "Teams like yours close 30% more deals using X."
- Insight anchor. Lead with a non-obvious truth: "Your best lead called. You were on another call."
- Contrast anchor. Lead with the comparison: "Other tools log calls. This one coaches on them."
For each angle, map: anchor type, persona it targets, emotional driver it activates. Evaluate against your ICP before choosing. Do not choose based on what sounds best internally. Choose based on what your champion cares about most.
12 Structure the homepage. Problem-led, not solution-led.
The homepage structure follows Pierri's buyer-journey logic:
| Section | Job | What to include |
|---|---|---|
| Hero | Answer all 4 positioning questions in 5 seconds | H1 (main value), H2 (supporting), CTA |
| Social proof | Build immediate trust | Logo bar, metric-backed quotes |
| Problem section | Establish the cost of inaction | Champion's situation in their language |
| Solution by persona | Show the product as the answer | Persona-specific value props + embedded quotes |
| Capability sections (x3) | Prove each messaging pillar | Feature shown as user action, not product feature |
| Differentiation | Why you vs. the alternative they currently use | Before / After, Us vs. them, old way vs. new way |
| Trust | Handle the remaining objections | Security, integrations, compliance, customer count |
| Closing CTA | Reinforce the hero | Same message, different wording |
Each pain claim should be followed immediately by its solution and a proof point. Not pain for three sections, then solution for three sections, then proof. Interleaved.
"Vision pitches land harder when each pain claim is paired with its own solution claim and a concrete proof point, interleaved per beat, not three sequential acts."
— Mihika Kapoor, Figma, Lenny's Podcast
Pitch a vision as pain → solution → proof, interleaved per beat, not three sequential acts
13 Embed social proof per persona section.
Proof is most effective adjacent to the claim it supports. Not segregated to a testimonials page. Not grouped into a testimonial section at the bottom.
For each capability section: specific metric + named person + named company. "Teams close 30% faster" is weaker than "Acme's 12-person team went from 40 dials per rep per day to 120 in the first week." Specificity is what makes proof credible. Generic proof is just a claim.
If industry or vertical matters to your champion, add panels. Pain + solution + proof per vertical. A real estate team and a dental practice have different objections and different success metrics. The homepage's job is to signal that you understand that.
14 Build the rollout tracker. Phase by business impact.
Every page needs to be updated, but not all at once. Score each page by traffic × conversion rate impact × strategic importance. Update highest-impact pages first.
Build a tracker with four columns: page, current messaging score (1 to 3), new messaging version status, owner + ETA. Review weekly until rollout is complete. This is not a waterfall. Update pages as they are ready, not in a batch.
15 Test in live pitches. Messaging is theory until it survives a real buyer.
Before declaring the messaging done, run it through three to five live discovery calls. Sit alongside a rep or listen to the recording. Watch for:
- Where the buyer interrupts with "wait, what do you mean by..."
- Where the buyer's energy drops
- Where reps deviate from the script (they deviate for a reason)
Those moments are where the messaging broke. Fix them. Then test again.
The sales team will detect messaging failures months before any dashboard does. Build the rep-input loop early: a weekly objection log, a competitive Slack channel, call-shadowing twice a month. Without that loop, messaging drift accumulates silently.
Quality gates
- Every value-matrix message traces to a real interview pain. Not an internal assumption.
- Features are shown through capabilities (verbs), not abstract benefits.
- Social proof is interleaved per capability section, not segregated.
- Core narrative answers the Setup (insight, alternatives, perfect world) before any product claim.
- Status quo is included as an alternative in the comparator analysis.
- Messaging house has exactly 3 pillars with feature-level evidence.
- Three or more angles were generated and evaluated before choosing.
- Live-pitch test completed before publishing.
- Monthly narrative-drift audit is scheduled.
Common failure modes
- Hero leads with aspirational outcomes. "Build pipeline faster" tells buyers nothing about what the product does. Lead with capabilities.
- Targeting the budget holder. The person who signs is not the person who felt the pain. Write for the champion.
- Too many segments on one page. Pick the champion. Persona-specific panels handle the rest.
- Feature overload, no capability bridge. The buyer cannot connect the feature to their job. Show the action.
- Guitar teacher anti-pattern. Too many new concepts in one scroll. Start with what the buyer already knows.
- Treating positioning, messaging, and copy as interchangeable. Positioning is the strategic frame. Messaging is the system built from it. Copy is the words on the page. Each has a different job.
- Skipping the rollout tracker. Messaging gets written but never deployed systematically.
- No narrative-drift audit. Sales decks, the homepage, and product release notes diverge within a quarter. Catch it monthly.
Outputs
- Champion profile (company type, persona, JTBD situation).
- Value matrix per persona (pain, benefit, capability, message).
- Messaging house (3 pillars with feature-level evidence).
- Core narrative (one paragraph, seed for all channels).
- Angle comparison sheet (3+ options evaluated against ICP).
- Homepage wireframe with copy for each section.
- Before / After frames for differentiation section.
- Rollout tracker (page, score, status, owner).