messaging-framework

---
name: messaging-framework
description: "Build layered, modular messaging: category/vision, problem, product value, and competitive differentiation, plus a pain-to-platform map, positioning statement, claims bank, and audience variations. Use when writing or rebuilding messaging, value props, or a positioning statement."
---

# Messaging Framework Builder

> **Part of the [Product Marketing Toolkit](../../README.md).** Before you start, read whatever exists in `context/` (company, positioning, ICP, voice, and proof library). If those files are empty or missing, ask for the essentials instead of guessing. Label anything you infer as an assumption, and never invent statistics, customer names, or quotes: use a bracketed placeholder like `[sourced metric, n, date]` instead.

A systematic approach to building compelling product messaging through layered frameworks, pain-to-platform mapping, and validated claims.

## Overview

This skill helps product marketers create messaging that:
- Starts with customer problems, not product features
- Builds in modular layers that can be mixed and matched
- Maps customer barriers directly to product solutions
- Backs every claim with verifiable proof points
- Adapts to different audiences and selling scenarios

## Core Principles

**Customer-Centricity**
Lead with customer problems and desired outcomes. The best messaging makes customers feel understood before attempting to sell.

**Modular Construction**
Build messaging in distinct layers that work independently but connect powerfully together.

**Evidence-Based**
Every claim must be verifiable. Combine data with storytelling for maximum impact.

**Conversational Tone**
Avoid jargon and corporate speak. Use simple, direct language that sounds natural in conversation.

**Brand-Specific**
Generic messaging doesn't differentiate. Make it unmistakably yours.

## Layered Messaging Framework

Build messaging in four distinct, stackable layers. Each layer serves a specific purpose and can be used independently or combined.

### Layer 1: Vision / Category Creation

**Purpose:** Establish broader market context and why this matters now

**Elements:**
- Market landscape and customer reality
- Why the old way doesn't work anymore
- The future state vision
- Urgency driver (why now)

**When to Use:**
- Opening a pitch to new prospects
- Setting strategic context
- Category education
- Executive-level conversations

**Example Structure:**
```
"[Customer reality today] → [Why this is a problem now] → [The shift that's happening] → [What this means for their business]"
```

**Questions to Answer:**
- What has changed in the market?
- Why can't customers keep doing what they've always done?
- What future are you painting?
- Why is timing critical?

### Layer 2: Problem / Solution (General)

**Purpose:** Define universal customer pain points and introduce the solution category

**Elements:**
- Specific pain points your ICP faces
- Quantified impact of inaction
- Solution category introduction
- General approach (not product-specific yet)

**When to Use:**
- After establishing vision
- When educating on the problem space
- Building urgency and desire
- Creating category awareness

**Example Structure:**
```
"[Specific pain] → [What this costs them] → [Why existing solutions fail] → [What's needed instead]"
```

**Questions to Answer:**
- What specific problems do customers face?
- What's the impact of not solving this?
- Why haven't they solved this already?
- What type of solution do they need?

### Layer 3: Product-Specific Value

**Purpose:** Your unique approach, specific capabilities, and differentiation

**Elements:**
- Your unique solution approach
- Key capabilities and features
- Specific proof points and data
- Customer success stories
- Measurable outcomes

**When to Use:**
- After problem/solution context is set
- Product demos and walkthroughs
- Feature-specific conversations
- Proof of value discussions

**Example Structure:**
```
"[Our approach] → [Key differentiators] → [Proof it works] → [What this means for you]"
```

**Questions to Answer:**
- What makes your approach unique?
- Which specific capabilities deliver the value?
- What proof do you have this works?
- What outcomes can customers expect?

### Layer 4: Competitive Differentiation

**Purpose:** Head-to-head positioning and why choose you vs. alternatives

**Elements:**
- Competitive comparison points
- Unique advantages
- Why switch / why choose you
- Objection pre-emption

**When to Use:**
- When competitors come up in conversation
- Late-stage deal situations
- Switching/migration scenarios
- Competitive bake-offs

**Example Structure:**
```
"[Unlike competitors who...] → [We uniquely...] → [This means you get...] → [As proven by...]"
```

**Questions to Answer:**
- What do competitors do differently?
- Where are you meaningfully better?
- Why should someone switch to you?
- What unique proof do you have?

## Supporting Elements for Each Layer

Every layer should include:

**Key Message** (1-2 sentences)
The core statement that captures the essence of this layer

**Supporting Data Points**
Verified claims with sources that back up the message

**Customer Proof**
Testimonials, case studies, or success stories that make it real

**Value Propositions**
What this actually means for the customer (outcomes, not features)

**Discovery Questions**
Questions that surface the need for this layer's message

## Pain-to-Platform Framework

Map customer barriers directly to product solutions with clear value propositions.

### Framework Structure

| **Pillar** | **Customer Barrier** | **Product Solution** | **Sales Value Prop** |
|------------|---------------------|---------------------|---------------------|
| [Theme] | What the customer says / thinks | Specific product capability | Outcome in customer language |

### How to Build This

**Step 1: Identify Customer Barriers**
- Listen to sales calls and customer interviews
- Group similar pain points into themes/pillars
- Capture in the customer's actual words
- Focus on barriers that prevent achieving goals

**Step 2: Map to Product Solutions**
- Connect each barrier to specific product capabilities
- Be specific about features, not generic benefits
- Include multiple capabilities if needed
- Focus on what actually solves the barrier

**Step 3: Craft Sales Value Props**
- Translate product solution into customer outcomes
- Use simple, conversational language
- Lead with the benefit, not the feature
- Make it memorable and repeatable

### Example Pain-to-Platform Map

**Pillar: Ease of Workflow**
- **Customer Barrier:** "I don't have time to learn another tool"
- **Product Solution:** Works inside the tools they already use, templates, sensible defaults
- **Sales Value Prop:** "Up and running in an afternoon, not a quarter"

**Pillar: Audience Growth**
- **Customer Barrier:** "We don't have enough volume for this to be worth it yet"
- **Product Solution:** Free tier, starter templates, imports from existing tools
- **Sales Value Prop:** "Start small with what you already have, and grow into it"

**Pillar: Compliance & Risk**
- **Customer Barrier:** "I'm worried about legal issues, spam complaints, and regulatory compliance"
- **Product Solution:** Built-in compliance checks, automated opt-out management, audit trails
- **Sales Value Prop:** "Stay compliant by design with automated safeguards and documentation"

## Claims Development & Validation

Every claim in your messaging must be verifiable and credible.

### Types of Claims

**Performance Claims**
- Engagement rates (click rates, open rates, conversion rates)
- ROI metrics (revenue per campaign, customer lifetime value impact)
- Efficiency gains (time saved, faster implementation, reduced effort)

**Comparison Claims**
- Cross-channel performance (Channel A + B vs. A alone)
- vs. Industry benchmarks or averages
- vs. Competitor performance

**Customer Success Claims**
- Revenue impact ($ recovered, average order value increase, total revenue)
- Growth metrics (list growth rate, opt-in conversion, audience expansion)
- Operational efficiency (campaigns created, time to first send, team productivity)

### Claim Validation Checklist

Before using any claim, verify:
- [ ] Data source is documented and credible
- [ ] Sample size is statistically significant (n>30 minimum for percentages)
- [ ] Time period is specified
- [ ] Methodology is clear and can be explained
- [ ] Legal/compliance has reviewed and approved
- [ ] Customer permission obtained (if using testimonial or case study)
- [ ] Claim can be verified by third party if questioned

### Claim Formats That Work

**The Specific Number**
"Up to [X%] higher [metric]" (not "much higher" or "significantly better")

**The Timeframe**
"[X%] average [metric] within the first 30 days" (not just "[X%] [metric]")

**The Comparison**
"[Product + add-on] vs. [product] alone" (not just "better together")

**The Customer Voice**
"For every $1 spent, customers earn [$X] back" (outcome, not feature)

## Positioning Statement Template

Distill your messaging into a concise positioning statement.

**Template:**
```
For [target customer]
Who [customer need/pain point]
[Product name] is a [product category]
That [key benefit/value proposition]
Unlike [competitive alternative]
We [unique differentiator]
```

**Example:**
```
(Illustrative, fictional product)
For freelance designers
Who lose hours every month chasing late invoices
Our product is an invoicing tool
That gets clients to pay on time without awkward follow-ups
Unlike generic accounting software
We send reminders in the freelancer's own voice and stop the moment the client pays
```

## Messaging Hierarchy

Organize messages from broadest to most specific.

**Level 1: Company/Platform Level**
- Overarching vision and mission
- Company differentiation
- Platform value proposition

**Level 2: Product Line Level**
- Product category and approach
- Core value propositions
- Primary use cases

**Level 3: Feature/Capability Level**
- Specific features and benefits
- Technical differentiators
- Use case details

**Level 4: Audience-Specific**
- Industry or segment messaging
- Persona-specific pain points
- Vertical use cases

## Adapting Messaging by Scenario

Use different layers and combinations based on the selling scenario.

### New Prospect (No Product Awareness)
**Use:** Layer 1 (Vision) → Layer 2 (Problem/Solution) → Layer 3 (Product Value)
**Goal:** Educate on category, build urgency, introduce solution

### Existing Customer (Upsell/Cross-sell)
**Use:** Layer 2 (Problem/Solution) → Layer 3 (Product Value) → Pain-to-Platform
**Goal:** Connect new capability to existing challenges, show value

### Competitive Situation
**Use:** Layer 3 (Product Value) → Layer 4 (Competitive) → Claims
**Goal:** Differentiate, handle objections, prove superiority

### Executive Conversation
**Use:** Layer 1 (Vision) → High-level Layer 3 (Outcomes) → ROI Claims
**Goal:** Strategic context, business impact, measurable results

### Technical Buyer
**Use:** Layer 3 (Product Value with feature detail) → Technical Claims → Integration approach
**Goal:** Prove capability, explain approach, address technical concerns

## Testing and Refining Messaging

**Test With Sales Teams**
- Do they understand it?
- Can they repeat it back?
- Does it sound natural when they say it?
- Does it help them in real conversations?

**Test With Customers**
- Does it resonate with their pain?
- Do they understand the value?
- Can they explain it to others?
- Does it make them want to learn more?

**Measure What's Working**
- Which messages appear in won deals?
- What language do customers use when they convert?
- Which proof points overcome objections?
- What claims drive urgency?

**Iterate Based on Feedback**
- Update based on what sales teams say works
- Refine based on customer conversations
- Strengthen based on win/loss analysis
- Simplify based on confusion points

## Common Messaging Mistakes to Avoid

**Feature-First Thinking**
❌ "Our platform has AI-powered automation"
✅ "Do the weekly report in ten minutes instead of two hours"

**Generic Claims**
❌ "Best-in-class solution for modern marketers"
✅ "Cuts month-end close from five days to two" (one specific outcome)

**Complexity Creep**
❌ "Leverage synergistic omnichannel orchestration to optimize customer journeys"
✅ "Reach customers on their preferred channel at exactly the right moment"

**Stacked Claims**
❌ "We're 50% faster, 30% cheaper, and have 10x better support with 99% uptime"
✅ Pick one strong claim per message

**Unmemorable**
❌ Long, complex statements that no one can remember
✅ Simple, punchy messages that stick

**Unverified**
❌ "Most businesses see significant improvements"
✅ "[X%] of customers [hit outcome] within 90 days (n=[sample], [quarter/year])"

## Messaging Document Structure

When creating a messaging framework document:

**Executive Summary**
- Purpose and how to use this document
- Target audience
- Key takeaways

**Market Context**
- Customer reality and pain points
- Market trends and dynamics
- Competitive landscape overview

**Messaging Layers**
- Layer 1: Vision / Category
- Layer 2: Problem / Solution
- Layer 3: Product Value
- Layer 4: Competitive Differentiation

**Pain-to-Platform Map**
- Customer barriers by pillar
- Product solutions
- Value propositions

**Claims Bank**
- All approved claims with sources
- Organized by category (performance, comparison, customer success)
- Usage guidelines

**Use Cases**
- Primary use cases by industry or persona
- Supporting proof points for each

**Discovery Questions**
- Questions to uncover each pain point
- Organized by messaging layer

**Competitive Positioning**
- vs. each major competitor
- Differentiation points
- Trap-setting questions

## Integration with Other GTM Activities

**Sales Enablement**
Messaging feeds into pitch decks, one-pagers, battlecards, and training

**Marketing Campaigns**
Messaging drives website copy, email sequences, ad creative, and content

**Product Roadmap**
Customer pain points inform product prioritization and feature development

**Competitive Intelligence**
Messaging adapts based on competitive moves and market shifts

**Customer Success**
Messaging helps CSMs articulate value and drive adoption

## Best Practices

**Start With Research**
- Customer interviews
- Win/loss analysis
- Sales call reviews
- Support ticket themes
- Competitive intelligence

**Collaborate Cross-Functionally**
- Product for roadmap and capabilities
- Sales for what's landing in market
- Customer Success for adoption challenges
- Marketing for campaign performance
- Support for common questions

**Keep It Simple**
- Conversational language
- Short sentences
- Active voice
- One idea per message

**Make It Modular**
- Build in layers that work independently
- Create mix-and-match flexibility
- Enable customization by scenario
- Support different formats (pitch, email, web, etc.)

**Validate Everything**
- Every claim has a source
- Every pain point is real (not assumed)
- Every value prop is measurable
- Every message is tested

**Iterate Continuously**
- Update based on market feedback
- Refine based on competitive changes
- Improve based on what wins
- Simplify based on confusion

## Using This Framework

### To Build New Messaging:

1. Research customer pain points and language
2. Build Layer 1 (Vision/Category context)
3. Build Layer 2 (Problem/Solution general)
4. Build Layer 3 (Product-specific value)
5. Build Layer 4 (Competitive differentiation)
6. Create Pain-to-Platform map
7. Develop and validate claims
8. Test with sales teams
9. Refine based on feedback
10. Document and distribute

### To Refine Existing Messaging:

1. Audit current messaging against this framework
2. Identify gaps (missing layers, weak claims, etc.)
3. Test current messaging with sales and customers
4. Strengthen weakest elements first
5. Validate all claims are current and accurate
6. Simplify complex or jargon-heavy language
7. Make more modular if currently monolithic
8. Retest and iterate

### To Adapt for New Audience:

1. Start with core framework (don't rebuild)
2. Adjust Layer 1 for their market reality
3. Customize Layer 2 for their specific pains
4. Highlight most relevant Layer 3 capabilities
5. Update proof points to similar customers
6. Modify language to match their terminology
7. Test with target audience
8. Refine based on feedback

## Deliverable Checklist

A complete messaging framework should include:
- [ ] Layered messaging (all 4 layers)
- [ ] Pain-to-Platform mapping
- [ ] Claims bank with sources
- [ ] Positioning statement
- [ ] Discovery questions by layer
- [ ] Use cases with proof points
- [ ] Competitive differentiation
- [ ] Messaging hierarchy (company → product → feature)
- [ ] Audience-specific variations (if applicable)
- [ ] Usage guidelines

---

This framework provides structure and process for building compelling messaging. The goal is customer-centric communication that drives understanding, builds urgency, and enables sales teams to articulate value clearly in any scenario.