How to construct messages for different people at different stages of awareness. Persona-based messaging, awareness stage variations, value prop construction, and brand voice direction. Draws from the Fletch PMM framework (500+ positioning projects). Assumes familiarity with positioning-and-strategy.md – particularly market maturity, ICP segmentation, and the category decision. For sentence-level writing craft, see b2b-copywriting-craft.md.
Positioning determines what to say. Messaging determines how to say it to specific people in specific situations. One feeds the other – messaging without positioning produces vague, unfocused copy that resonates with nobody.
Three positioning decisions directly shape messaging:
-
Market maturity determines competitive framing. In mature markets (M3), messages must differentiate against known alternatives ("why us over Salesforce"). In emerging markets (M1/M2), messages must anchor to the prospect's current workflow ("stop managing your SOC 2 audit in spreadsheets"). Messaging against competitors in a market where prospects don't know the category exists guarantees irrelevance.
-
ICP segmentation determines who receives the message. Use-case-based segments (not firmographics) define the audience. A message to "SaaS companies with 1000 employees" is generic. A message to "teams preparing for SOC 2 audits using spreadsheets and consultants" speaks to a specific situation.
-
Differentiation determines emphasis. The sharpest competitive difference becomes the lead claim – not the broadest capability, not the most aspirational outcome, but the most specific thing that separates the product from alternatives.
These three decisions must be resolved before writing. Without them, teams produce watered-down copy that tries to keep everyone comfortable. Comfort kills clarity.
Fictitious archetypes ("The Wizard," "The Teacher," "The Maverick") don't work. Nobody knows what a "Wizard" sounds like. A "Maverick" could mean "F*ck the old way" or "Welcome to the new era" – totally different tones.
Use four voice quadrants instead:
- Aggressive/Bold
- Friendly/Casual
- Humorous/Cheeky
- Professional/Formal
Pick a quadrant, then add adjectives to narrow further. Professional/Formal can be visionary or technical – very different voices under the same umbrella. Good writing is always clear, concise, and compelling regardless of quadrant. The quadrant choice affects tone, not quality.
How to use it: Before writing, get alignment on the quadrant and 2-3 adjectives that narrow it. "Professional/Formal, technical, understated" gives a copywriter something actionable. "The Maverick" gives them nothing.
A single message aimed at "the company" lands with nobody. Different people in the same buying committee care about fundamentally different things. The sales rep cares about daily experience. The CFO cares about ROI. The IT lead cares about security. Same product – completely different conversations.
Translate the core value proposition into language that maps to each role's concerns:
| Role | What they care about | Lead with |
|---|---|---|
| User | The day-to-day experience | How it makes their work easier |
| Champion | The challenge they're solving | How it addresses their specific problem |
| Decision Maker | Moving the needle | Outcomes and business impact |
| Financial Buyer | ROI | Metrics and cost justification |
| Technical Influencer | Making it work | Integration, security, logistics |
For each persona, map four elements in sequence:
- Context – What occupies their day? What are they responsible for?
- Problem – What challenge do they face that relates to the product's capability?
- Capability – What new thing can they do with the product?
- Benefit – What specific outcome improves, in terms they care about?
Every element must use the role's language and frame around their priorities – not the company's internal terminology.
The construction pattern above captures functional needs – what the business requires. But the person making the decision also has emotional needs: not looking stupid, not getting fired, removing themselves from a process they hate. B2B buying emotion is primarily fear, not aspiration. More money involved, more people involved, more to lose.
Both layers must be addressed. Functional needs alone leave the buyer uninvested emotionally. Emotional needs alone leave them unable to justify the business case internally. The two are connected – solving the functional need (cost reduction) helps solve the emotional need (feeling safe defending the purchase to the board).
In practice: after mapping the four functional elements per persona, ask one more question – what does this person fear if they make the wrong choice? A CRO fears missing targets. A CFO fears wasted budget. A Head of IT fears a security breach. Messages that acknowledge and reduce that fear convert better than messages that only promise upside.
Use case: personalized video messages in a sales process. Target: companies with enterprise sales teams.
| Role | Context | Problem | Capability | Benefit |
|---|---|---|---|---|
| User (Sales Rep) | High volume of customer communications | Emails get ignored by prospects | Create and send personalized videos | Increase response rates |
| Champion (Dir. Sales Enablement) | Trying to optimize the sales experience | Hard to know what's working | Track video performance in the sales cycle | Increase visibility into what works |
| Decision Maker (CRO) | Focused on closing deals and hitting targets | Struggle to move deals through pipeline | Enable reps to create messages that motivate action | Increase engagement % of rep activities |
| Financial Buyer (CFO) | Sales operations costs are high | Every purchase must defend its ROI | Connect sales rep engagement to bottom line | Better defend purchases to the board |
| Technical Influencer (Head of IT) | Must ensure reps don't share sensitive data | Hard to ensure compliance at scale | Encrypt all messages with login credentials | Reduce risk profile |
Diagnostic: Pick the product's primary use case and ICP. Can the team fill in all five rows with specifics? If any row is vague or generic ("improve efficiency"), the messaging is not sharp enough. Each row should contain language that role would actually use.
Prospects exist on a spectrum of awareness. Two macro-modes define the messaging approach:
Creating demand targets prospects who don't know they have a problem – or know the problem but haven't looked for solutions. The message must educate, frame the problem, and create urgency. This path is slower but reaches a much larger audience.
Capturing demand targets prospects who already know what they need and are actively evaluating options. The message must differentiate – show why this product over alternatives. Smaller audience, but faster to convert.
The ratio depends on market maturity: emerging markets (M1/M2) skew heavily toward creating demand. Mature markets (M3) skew toward capturing it. Most startups need both.
The same product needs different messages depending on how aware the prospect is:
| Stage | What they know | Lead with | Goal |
|---|---|---|---|
| Problem Unaware | Only their current way of doing things | Their current alternatives/situation | Convince them they have a problem |
| Problem Aware | They have a problem | The specific problem | Convince them they're missing a key capability |
| Solution Aware | The type of solution they need | Capabilities that match their need | Convince them the product unlocks that capability |
| Product Aware | The product and its competitors | Most differentiated features | Connect features to outcomes |
The goal at each stage is to shift the prospect's thinking one step forward – from "this is how things are done" to "I have a problem," from "I have a problem" to "I need a specific capability," and so on. The lead element earns this shift by demonstrating understanding of where the prospect currently stands. If the lead lands, the prospect grants permission to hear the next piece.
| Stage | Lead message | Goal |
|---|---|---|
| Problem Unaware | "Separate document tools and PowerPoint to create a roadmap" | Convince them they have a fragmentation problem |
| Problem Aware | "Team members struggle to find details of their roadmap plans" | Convince them they're missing centralized product management |
| Solution Aware | "Organize all product work in one place for cross-functional launches" | Convince them Notion unlocks this |
| Product Aware | "Built-in Kanban roadmapping and task tracking" | Convince them Notion delivers on its benefit |
Each lead message demonstrates understanding at that stage. "Separate document tools and PowerPoint" proves familiarity with the prospect's current workflow without pitching anything. "Built-in Kanban roadmapping" speaks to someone who already knows what they want and is evaluating specifics.
The channel determines the likely awareness stage:
- Cold outbound (email, LinkedIn DM) almost always targets Problem Unaware or Problem Aware prospects. Leading with features or product claims to someone who doesn't know they have a problem guarantees irrelevance.
- Inbound from content/SEO typically reaches Problem Aware or Solution Aware prospects – they searched for something related to the problem.
- Comparison/review sites reach Product Aware prospects – they're actively evaluating.
- Homepage must handle a range. The hero should answer "what is this?" for Solution/Product Aware visitors, while the page body can create demand for Problem Aware visitors.
Diagnostic: For each outreach channel, identify the most likely awareness stage of the recipient. Does the current messaging lead with the right element for that stage? If a cold email leads with product features, it's mismatched.
The two frameworks combine into a matrix. A specific message targets a specific role at a specific awareness stage. The Loom example from Section 2 assumes Solution Aware buyers – the Champion already knows they need better sales enablement tools. For a Problem Unaware Champion, the message leads differently: "Sales enablement teams spend 30% of their time on manual reporting" (anchoring to the current situation, not pitching capabilities).
This means a thorough messaging strategy produces multiple message variants – not one universal pitch.
The frameworks from Sections 1-3 combine into a construction sequence:
- Positioning foundation. What is the product, who is it for, how is it different? (Section 1)
- Pick the persona. Which buying committee role is this message for? (Section 2)
- Determine awareness stage. What do they already know? Channel usually indicates this. (Section 3)
- Choose the lead element. Alternatives, problem, capability, or features – based on the stage.
- Frame the benefit in the persona's terms. A CRO hears "pipeline velocity." A CFO hears "cost per acquisition." Same capability, different framing.
- Test specificity. Could a competitor write the same sentence? If yes, the differentiation hasn't made it into the message.
Leading with the wrong element. A cold email that opens with product features to a Problem Unaware prospect. Features are meaningless to someone who doesn't know they have a problem. Fix: rewrite to lead with their current situation or workflow.
Generic persona framing. "Decision makers care about outcomes" is true but useless. WHICH outcomes? Fix: name the specific metric. Name the dashboard they check every Monday. Use the construction pattern from Section 2 to get concrete.
Skipping the awareness stage. Treating all prospects as Product Aware because feature-focused copy is easier to write. Most prospects – especially in emerging markets – aren't there yet. Fix: use the channel mapping from Section 3 to determine the likely stage, then match the lead element.
One message for all roles. Sending the same pitch to the user, the champion, and the CFO. Fix: run the message through the five-role table from Section 2. If the same sentence works for all five roles, it's too generic to work for any of them.
- Positioning precedes messaging. Market maturity, ICP, and differentiation decisions must be resolved before writing. Without them, messaging defaults to vague, comfortable language.
- Universal messages fail. Different buying committee roles need the value prop translated into their language and priorities.
- Awareness stage determines the lead. Match the message's opening element to what the prospect already knows. Channel context usually indicates the stage.
- Creating demand ≠ capturing demand. Emerging markets require problem education. Mature markets require differentiation. The messaging approach differs fundamentally.
- Persona × Awareness Stage = specific message. The combination produces the actual copy brief. One product, many message variants.
- Test for specificity. If a competitor could say the same thing, the differentiation hasn't made it into the message.