laja-wynter-message-testing git:20261002.46ac0a1A

Immutable. This exact content never changes and is served at /api/v1/blob/2c93e1f73a33ecb5.

---
name: laja-wynter-message-testing
description: "Diagnose and improve B2B page messaging with Peep Laja's Wynter method; use for homepage, landing page, product page, or positioning reviews that need feedback from target buyers."
---

# Wynter B2B message testing

Based on Peep Laja's public method. Not affiliated with or endorsed by Peep Laja.

## When to use

Use this skill when a B2B team needs to learn whether a homepage, campaign landing page, product page, or core value proposition makes sense to its intended buyers, and what to change before or after launch. Apply it when stakeholders have competing copy opinions, traffic metrics show a problem without explaining it, or a new position needs buyer validation. Message testing diagnoses interpretation and motivation; it does not by itself establish a conversion lift. [S2][S5][S7]

Use a buyer survey first when the team lacks recent evidence about the segment's pains, triggers, buying process, or competitive alternatives. If credible recent buyer research already exists, begin with a message test. Use a preference test for two or three competing message directions, and a pricing page test when price communication is the actual question. Do not spend a message test on a blog, careers page, or other page outside the persuasion path. [S3][S5]

## Procedure

### 1. Define the buyer and decision

Write a one sentence research question that names the page, buyer segment, and decision the test will inform. Record the intended job title, seniority, industry, company size, buying role, and current alternative. Keep the target narrow enough that a respondent can recognize their own work in the message. A broad panel can average away a real segment's priorities. Record the desired next action and the message hypothesis before collecting reactions, so the team cannot redefine success after seeing comments. [S3][S5][S7]

Make a buyer context brief from recent interviews, sales calls, win and loss notes, or an ICP survey. Capture the buyer's current priority, problem symptoms, value of solving, purchase trigger, success measure, decision process, objections, and named alternatives. Separate observed buyer language from the team's assumptions. If those facts are missing, ask the target buyers about them before drafting a new promise; a message test cannot tell you which unresearched problem deserves the page. [S3][S5]

### 2. Choose the message and the evidence source

Choose one core revenue page or one proposed page draft as the unit of diagnosis. Preserve the actual reading experience by supplying the live URL or a faithful page image, and mark the hero and the few sections where the message does its main persuasive work. For a homepage, test the whole page and inspect the hero separately. For a campaign page, keep the ad or source promise in the brief so feedback can be interpreted in context. Do not turn a question about positioning into a cosmetic design review. [S5][S7][S8]

Recruit people who match the intended market, preferably verified B2B professionals filtered by role, seniority, industry, and company size. Existing customers can supply useful context, but their product knowledge and loyalty can hide first visit confusion. Record exactly who responded and whether they are prospects, customers, or internal reviewers. If no buyer responses can be collected, mark the work as a provisional expert review and specify the buyer test still needed; do not fabricate panel feedback or scores. [S3][S7][S8]

For a qualitative message test, start with the playbook's 15 respondent default and increase only for a concrete reason, such as distinct buyer roles that need separate inspection. Treat small sample scores as directional diagnostics, not population percentages or statistical proof. If the task asks for a percentage, segment estimate, or market trend, use a properly sized quantitative survey instead. [S5]

### 3. Ask questions that expose interpretation

Collect a consistent rating for clarity, relevance, value, and differentiation, with open text explaining each rating. If brand perception is part of the brief, collect that separately. Ask respondents, in their own words, what the offer is, who it is for, what problem it addresses, what result they expect, why they might choose it over their present approach, what they doubt, and what remains unclear. An explanation is more useful than a score because it points to the failed claim or missing information. [S2][S5][S7]

Keep prompts neutral. Do not supply the category, intended benefit, or differentiator inside the question and then count the respondent repeating it as comprehension. Ask for spontaneous paraphrases and concrete objections. Use page section feedback to locate the confusing headline, unsupported promise, or late arriving explanation. Do not reduce the study to a vote on whether people like the copy. [S2][S7][S8]

### 4. Diagnose in Peep's order

First check clarity: can the buyer correctly say what the product is, what category it belongs to, and what it helps them do? Mark failure when people misclassify the offer, need lower page sections to understand it, or repeat vague words without a concrete explanation. Fix the category cue, primary promise, or plain language account before optimizing later persuasion. A poetic headline that hides the offer is not saved by a polished visual. [S2][S6]

Next check relevance: does the buyer recognize a priority they have now and see the message as meant for their role? Look for comments that the problem is real but belongs to another team, is too low priority, or is framed too broadly. Revise the audience cue, use case, and problem statement around the chosen segment. Do not add generic benefits merely to include more people. [S2][S3]

Then check value: can the buyer connect the capability to a concrete outcome worth pursuing? Identify where a feature list leaves the result implicit, a promised result has no scale or time frame, or the tradeoff sounds larger than the gain. Translate the capability into the buyer's work and substantiate the result. Do not treat a more dramatic adjective as evidence of value. [S2][S3]

Finally check differentiation: can the buyer explain why this option beats the alternative they would actually use, including doing nothing? Compare with the brands and current methods buyers name, not a straw competitor. Look for claims any vendor could make, an unfamiliar category label, or a claimed difference without a structural reason or proof. State a defensible difference in product, approach, specialization, or business model, with its tradeoff, rather than merely sounding novel. [S2][S4]

Across all four layers, log friction and proof. Capture doubts, anxieties, missing details, and claims buyers do not believe; pair each important claim with the evidence needed to make it credible. Diagnose the earliest layer that fails before debating later scores. A buyer who cannot identify the offer cannot reliably judge its differentiation. Record one primary failure, supporting verbatim feedback, a causal hypothesis, and the revision it implies. [S2][S5]

### 5. Turn findings into a focused revision

Create a claim audit of the current page: category, audience, problem, outcome, difference, proof, and next action. Compare its claims with the homepages of competitors buyers actually consider. Mark repeated promises and words that could be pasted onto any rival's site. Preserve a difference the company can substantiate, even if it requires a narrower audience or an explicit tradeoff. Do not copy a category leader's vocabulary so closely that the brand disappears into the market. [S4]

Rewrite the page around the first failed layer. If clarity failed, make the hero identify the offer before adding narrative. If relevance failed, use the segment's priority and situation. If value failed, show the meaningful result and its evidence. If differentiation failed, name the alternative and give a credible reason to choose this offer. Remove redundant sections, noise, and long intros that delay understanding. Peep's Qualified teardown shows that repeating similar use cases can obscure a useful explanation even when each section is individually relevant. [S2][S6]

Do not implement every respondent suggestion as a feature or sentence. Cluster comments by the underlying buyer question, count recurring patterns, inspect disagreement by segment, and distinguish a real strategic gap from one person's taste. Buyer research can reveal category table stakes while still pushing brands toward sameness if the team follows every request. Choose the message hypothesis using buyer evidence and the company's actual position. [S4][S5]

### 6. Retest and decide

Pretest the substantive rewrite with the same ICP definition, page scope, questions, and rating scale. Compare the original and revised interpretations, not only average scores. Ask whether buyers now describe the category correctly, recognize their priority, want the outcome, can state the difference, and raise fewer serious objections. Ship when the primary failure is resolved and the remaining doubts have a clear answer; otherwise revise the failed layer and test again. Keep the before and after evidence together. [S2][S5]

Skip a new message test for a typo, slight wording polish, or visual only change. Use a preference test when choosing among two or three genuinely different directions, while retaining responsibility for the strategic choice. When a product launch, new segment, competitor move, pricing change, or shift in buyer behavior invalidates the earlier context, refresh the relevant buyer evidence and test the affected message again. AI can help organize results or query completed tests, as in Peep's linked announcement, but a generated summary is not a substitute for the respondents' answers. [S1][S5]

## Finished output

Deliver a brief that states the buyer and decision, page and version tested, evidence source and respondent criteria, test questions, scores if collected, representative paraphrased feedback, and limitations. Include a layer by layer diagnosis with the earliest failed layer clearly identified, plus friction and proof gaps. Show a claim and competitor sameness audit, the proposed revised hero or page outline, and a prioritized change list connecting each change to buyer evidence. End with a retest plan and a decision rule for ship, revise, or gather missing buyer context. Do not present an untested rewrite as validated. [S2][S4][S5][S7]

## Worked example: illustration

An invented payroll software company says on its homepage, "The future of workforce agility." Its ICP is HR operations leads at companies with 500 to 2,000 employees. Fifteen matching prospects see the page. Most call it a staffing platform; several discover payroll automation only halfway down. They rate the future outcome as attractive but cannot name what is being sold. Diagnose clarity first, despite the favorable value comments. [S2][S5]

The agent rewrites the hero to say that the product automates payroll corrections for multi-state teams, then names the manual spreadsheet process it replaces and adds a documented correction time result. Three repeated use case blocks become one short explanation with links to details. The agent retests the same audience and questions, and ships only if prospects can now explain the offer and its difference without prompting. These names, claims, and reactions are illustrative, not research findings. [S2][S4][S6]

## Sources

1. [S1] Peep Laja, "We shipped Wynter MCP connections for Claude and ChatGPT". https://www.linkedin.com/posts/peeplaja_we-shipped-wynter-mcp-connections-for-claude-activity-7490360926102216705-ycgH
2. [S2] Peep Laja, "B2B Message Layers framework". https://wynter.com/post/b2b-message-layers-framework-wynter
3. [S3] Peep Laja, "How to use buyer intelligence to win the market". https://wynter.com/post/buyer-intelligence
4. [S4] Peep Laja, "How to compete and win on messaging". https://wynter.com/post/how-to-compete-and-win-on-messaging
5. [S5] Wynter, "The Wynter Research Playbook". https://wynter.com/research-playbook
6. [S6] Peep Laja, "Qualified", from "Do you even resonate?". https://wynter.com/dyer-recordings/qualified
7. [S7] Kate Meda, "The definitive guide to message testing". https://wynter.com/post/message-testing
8. [S8] Wynter, "Wynter example tests". https://wynter.com/examples