Messaging Framework SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as messaging-framework/SKILL.md.

---
name: messaging-framework
description: "Build messaging frameworks from positioning and customer language: a tested value proposition, three or four outcome pillars with proof and supporting features, objection responses, persona and buying-stage variations, channel adaptations for homepage, ads, deck and email, message testing methods and a messaging house that keeps every team on one story. Use whenever someone asks for a messaging framework, value proposition, messaging house, key messages, persona messaging, a clearer pitch or why the website, ads and sales tell different stories."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/product-marketing/messaging-framework/
  category: marketing
  subcategory: product-marketing
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Messaging Framework

Messaging turns positioning into words people understand and remember. A messaging framework gives every team the same core story: a value proposition, three or four pillars, proof for each, and adapted versions for different personas, channels and stages. Without one, the homepage says one thing, ads another, sales a third, and buyers piece together a confusing picture.

This skill builds messaging frameworks from positioning and customer language, adapts them for personas and channels, and tests them before rollout.

## Operating principles
1. **Positioning first.** Messaging expresses positioning; it can't replace it.
2. **Customer language over company language.** Use the words customers use in interviews, reviews and sales calls.
3. **Outcomes before features.** Lead with what changes for the customer; features support the claim.
4. **Every claim needs proof.** Numbers, customer stories, demos or third-party validation.
5. **One story, many versions.** Adapt depth and emphasis by persona and channel without changing the core.

## Framework structure
| Layer | Content | Example (finance reporting tool) |
|---|---|---|
| Value proposition | One sentence: who, what outcome, how it's different | Month-end reporting in hours for mid-market finance teams, built on your ERP |
| Pillar 1 | Key value theme | Close faster |
| Pillar 2 | Key value theme | Trust every number |
| Pillar 3 | Key value theme | Works with your ERP from day one |
| Proof per pillar | Evidence | "Cut close from 6 days to 2" (customer), audit trail demo, ERP connector list |
| Feature support | Capabilities behind each pillar | Templates, reconciliation, connectors |
| Objection responses | Answers to common doubts | "We already have BI": we automate the finance workflow BI doesn't cover |

## When to use, and when not to
Use it after positioning work, when channels tell different stories, before website redesigns, before launches, when entering new segments and when sales asks for a clearer pitch.

Don't use it to decide positioning (`positioning`) or to write long-form content (the Content SEO skills).

## Inputs to ask for, in one message
1. Positioning document.
2. Personas and ICP.
3. Customer language: interview quotes, reviews, sales call notes.
4. Proof available: results, case studies, data, awards, reviews.
5. Current messaging across website, ads, deck and emails.
6. Brand voice guidelines.

## Workflow

### Step 1. Extract customer language
Pull phrases customers use to describe the problem, the outcome and why they chose you.

### Step 2. Write the value proposition
Draft five versions; test clarity with people outside the company; pick one.

### Step 3. Define three or four pillars
Themes that together explain the value. Each must connect to a unique attribute in the positioning.

### Step 4. Attach proof
For every pillar, list the strongest proof: customer numbers, case studies, demos, certifications, review quotes.

### Step 5. Map features to pillars
So product, sales and marketing know which capabilities support which message.

### Step 6. Write objection responses
The top five objections from win-loss and sales calls, with honest, evidence-based answers.

### Step 7. Adapt by persona and stage
What each persona cares about (economic buyer, user, technical evaluator) and what each stage needs (awareness, consideration, decision).

### Step 8. Adapt by channel
Homepage, ads, sales deck, email, social: length and emphasis change, the story doesn't.

### Step 9. Test and roll out
Test with landing pages, ads, sales calls and customer reviews of the message; then train teams and update assets.

## Persona adaptation example
| Persona | Cares about | Lead message | Proof |
|---|---|---|---|
| CFO (economic buyer) | Speed, accuracy, cost of errors | Close faster with numbers you can trust | Time saved, audit outcomes |
| Finance manager (user) | Less manual work, fewer late nights | Templates do the repetitive work | Demo of reconciliation |
| IT (evaluator) | Security, integration effort | Native ERP connectors, SSO, audit logs | Security docs, connector list |

## Message testing methods
| Method | What it shows |
|---|---|
| Five-second tests | Whether the value proposition is understood quickly |
| Customer read-backs | Whether best customers recognise why they bought |
| Landing page or ad tests | Which framing drives qualified conversions |
| Sales call trials | Whether prospects engage faster |
| Message surveys (preference and clarity) | Which pillars resonate with each persona |

## Messaging house template
```
Value proposition: ...
Pillar 1: ... | Proof: ... | Features: ...
Pillar 2: ... | Proof: ... | Features: ...
Pillar 3: ... | Proof: ... | Features: ...
Objections and responses: ...
Persona variations: ...
Channel variations (homepage, ads, deck, email): ...
Words to use / avoid: ...
```

## Value proposition formulas
| Formula | Example |
|---|---|
| [Outcome] for [audience], [without pain] | Pass SOC 2 in weeks, without a security team |
| [Audience] use [product] to [outcome] | Mid-market finance teams use Acme to close in hours |
| The [category] for [audience] who [need] | The reporting tool for finance teams who live in NetSuite |
Write several versions with each formula and test them with people who match the ICP, not colleagues.

## Language rules
| Prefer | Instead of |
|---|---|
| Specific outcomes (hours saved, errors cut) | Vague superlatives about being the best |
| Customer terms (month-end close) | Internal names for features |
| Concrete proof (customer, number, date) | Unsupported claims of transformation |
| Plain verbs (cut, pass, close) | Business jargon |

## Rollout checklist
- Homepage, product pages and pricing page updated.
- Sales deck, demo script and email templates aligned.
- Ads and social profiles refreshed.
- Onboarding and in-product copy checked for consistency.
- Teams trained, with a one-page summary and a recorded walkthrough.
- Review date set (usually every six to twelve months, or after major launches).

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Little proof yet | Use demos, early customer quotes and specific product facts; avoid vague claims |
| Several products | A company story plus product-level frameworks that roll up |
| Technical buyers | More specifics and documentation; fewer adjectives |
| Regulated industries | Check claims with legal and compliance |
| Brand team wants clever taglines | Keep clarity first; taglines can sit alongside a clear value proposition |

## Handoffs to related skills
- Positioning: `positioning`
- Personas: `ideal-customer-profile`
- Customer language: `customer-research-interviews`
- Objections from losses: `win-loss-analysis`
- Sales assets: `sales-enablement`
- Proof: `case-studies-customer-proof`
- Website conversion: the Conversion Rate Optimization skills

## Worked example
A cybersecurity startup's homepage led with "AI-powered unified security platform". Interviews showed customers bought because they could pass SOC 2 audits without hiring a security team. The new framework's value proposition became "Pass your SOC 2 audit in weeks, without a security team", with pillars on automated evidence collection, continuous monitoring and auditor-ready reports, each backed by customer timelines. A landing page test against the old message raised qualified demo requests, and sales adopted the same story in the deck.

## Output format
```
# Messaging framework: <product>, <date>
## Value proposition
## Pillars with proof and features
## Objection responses
## Persona and stage variations
## Channel variations
## Testing results and rollout plan
```

## Common mistakes
- Writing messaging without positioning.
- Company jargon instead of customer language.
- Pillars that are features, not outcomes.
- Claims without proof.
- Different stories on different channels.

## Questions to ask before you write
- How do best customers describe the value in their own words?
- What proof exists for each claim?
- Which personas are involved in buying, and what does each care about?

## Self-check before you answer
- Does messaging follow the positioning?
- Is customer language used?
- Does every pillar have proof?
- Are persona and channel versions consistent with the core?

## Further reading
- April Dunford, Sales Pitch (2023)
- Donald Miller, Building a StoryBrand (2017)

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/product-marketing/messaging-framework/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.