# Brand Messaging

> Develop brand messaging frameworks: value proposition, positioning statement, key messages, tone of voice, and elevator pitch. TRIGGER when: user says /brand-messaging, "brand positioning", "messaging framework", "value proposition", "brand voice", "elevator pitch".

- Skill: `ashutoshsrivastava17/brand-messaging` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ashutoshsrivastava17/brand-messaging`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ashutoshsrivastava17/brand-messaging/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: ashutoshsrivastava17 (https://skillmd.com/u/ashutoshsrivastava17)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ashutoshsrivastava17/brand-messaging

---


# Brand Messaging

Develop a comprehensive brand messaging framework that ensures consistent, compelling communication across all channels and stakeholders. Covers value proposition, positioning, key messages, tone of voice, and ready-to-use elevator pitches.

---

## Process

### Step 1 — Understand the Brand Foundation

Gather the inputs that inform all messaging decisions.

| Input | Question | Why It Matters |
|---|---|---|
| Company / product | What do you sell or do? | Defines the core subject |
| Target customer | Who is the primary buyer? | Messaging must resonate with them specifically |
| Problem solved | What pain does the customer have before you? | Foundation of the value proposition |
| Solution | How do you solve it differently? | Differentiator and positioning anchor |
| Competitors | Who else solves this problem? | Defines the competitive frame of reference |
| Current perception | How do people describe you today? | Gap between current and desired perception |
| Desired perception | How do you want to be known? | The north star for all messaging |
| Proof points | What evidence supports your claims? | Credibility and trust |
| Stage | Startup, growth, mature, repositioning? | Affects messaging confidence and scope |

If the user provides minimal information, ask for at minimum: what they do, who they serve, and what makes them different.

### Step 2 — Craft the Value Proposition

The value proposition is the single most important piece of messaging. It answers: "Why should I choose you?"

Use this formula:

```
For [target customer]
who [situation or need],
[product/brand] is the [category]
that [key benefit].
Unlike [alternative],
we [primary differentiator].
```

Also produce a one-line version (under 15 words) for use in headlines, taglines, and ad copy.

Value proposition strength test:

| Criterion | Strong | Weak |
|---|---|---|
| Specific customer | "Series A SaaS founders" | "Businesses" |
| Clear benefit | "Close deals 40% faster" | "Improve sales" |
| Differentiated | "The only platform that combines X and Y" | "A better way to do Z" |
| Provable | "Used by 500+ teams including Stripe and Notion" | "The best tool available" |
| Memorable | Can be repeated from memory after one reading | Requires re-reading to understand |

### Step 3 — Write the Positioning Statement

The positioning statement is an internal strategic document (not customer-facing) that aligns the team.

```
POSITIONING STATEMENT
=====================
Target audience: [Specific buyer persona]
Market category: [The space you compete in]
Brand promise: [The single most important benefit]
Reason to believe: [Evidence that you deliver on the promise]
Competitive alternatives: [What the customer does if you don't exist]
Primary differentiator: [The one thing competitors cannot easily replicate]
```

Positioning traps to avoid:

| Trap | Example | Fix |
|---|---|---|
| **Category confusion** | Claiming you're "not a CRM" when you clearly are | Own your category or clearly define a new one with context |
| **Feature, not benefit** | "We use AI" (so does everyone) | "We cut analysis time from 3 hours to 10 minutes using AI" |
| **Undifferentiated** | "We're faster, cheaper, better" | Pick one axis and own it with proof |
| **Too broad** | "For everyone who uses the internet" | Narrow to the audience that values you most |
| **Aspirational without proof** | "The #1 platform for..." (says who?) | Use verifiable claims or softer framing |

### Step 4 — Develop Key Messages

Create a message hierarchy — a structured set of messages for different contexts and audiences.

| Level | Purpose | Length | Example Use |
|---|---|---|---|
| **Tagline** | Instant brand recall | 3-7 words | Logo lockup, ads, social bios |
| **Elevator pitch** | Explain what you do in 30 seconds | 2-3 sentences | Networking, investor intros |
| **Boilerplate** | Standard company description | 50-100 words | Press releases, "About" sections |
| **Key message 1** | Primary benefit / differentiator | 1-2 sentences | Homepage hero, sales pitch opening |
| **Key message 2** | Secondary benefit | 1-2 sentences | Feature pages, ad copy |
| **Key message 3** | Proof / trust signal | 1-2 sentences | Case studies, testimonials page |
| **Objection handlers** | Preempt common pushback | 1-2 sentences each | Sales enablement, FAQ |

For each key message, provide:
- The message itself
- Supporting proof point
- Where to use it (channel / context)
- What NOT to say (common missteps)

### Step 5 — Define Tone of Voice

Tone of voice ensures messaging sounds consistent regardless of who writes it.

Define the brand voice using a spectrum for each dimension:

| Dimension | ← One End | Your Position | Other End → |
|---|---|---|---|
| Formality | Casual, conversational | [Place on spectrum] | Formal, corporate |
| Humor | Playful, witty | [Place on spectrum] | Serious, no humor |
| Confidence | Humble, understated | [Place on spectrum] | Bold, assertive |
| Emotion | Warm, empathetic | [Place on spectrum] | Rational, data-driven |
| Complexity | Simple, accessible | [Place on spectrum] | Technical, expert-level |

Then provide concrete guidance:

| We Say | We Don't Say | Why |
|---|---|---|
| "Simple and powerful" | "Easy and basic" | "Basic" implies lack of depth |
| "Built for teams like yours" | "Built for everyone" | Specificity builds trust |
| "Here's what we found" | "Studies have shown" | First-person ownership over vague attribution |
| [Brand-specific examples] | [Brand-specific anti-examples] | [Rationale] |

Provide 3-5 "this, not that" pairs specific to the brand.

### Step 6 — Create the Elevator Pitch

Produce multiple versions for different contexts:

| Version | Audience | Duration | Structure |
|---|---|---|---|
| **Cocktail party** | Anyone, no context | 10 seconds | "We help [audience] do [outcome]." |
| **Investor pitch** | VCs, angels | 30 seconds | Problem → Solution → Traction → Ask |
| **Sales intro** | Prospects | 30 seconds | Pain → Solution → Proof → CTA |
| **Conference bio** | Event organizers | 50 words | What + Who + Why it matters |
| **Press blurb** | Journalists | 100 words | Boilerplate with key stats and quotes |

Each pitch should:
- Open with the audience's problem, not your product
- Include one concrete proof point (number, customer name, result)
- End with a clear next step or memorable takeaway

---

## Output Format

Deliver the messaging framework as a structured document:

```
BRAND MESSAGING FRAMEWORK
==========================
Company / Product: [Name]
Date: [Date]
Version: [1.0]

1. VALUE PROPOSITION
   Full: [Multi-line version]
   One-liner: [Under 15 words]

2. POSITIONING STATEMENT
   [Filled template]

3. KEY MESSAGES
   Tagline: [3-7 words]
   Key Message 1: [Message + proof point]
   Key Message 2: [Message + proof point]
   Key Message 3: [Message + proof point]

4. ELEVATOR PITCHES
   10-second: [Cocktail party version]
   30-second: [Sales / investor version]
   Boilerplate: [50-100 word version]

5. TONE OF VOICE
   Voice spectrum: [Table]
   This, not that: [Examples]
   Writing guidelines: [3-5 rules]

6. OBJECTION HANDLERS
   Objection 1: [Objection] → Response: [Response]
   Objection 2: [Objection] → Response: [Response]
   Objection 3: [Objection] → Response: [Response]

7. USAGE GUIDE
   [Where each message element should be used]
```

---

## Quality Checklist

- [ ] Value proposition answers "why you" in one read — no jargon, no ambiguity
- [ ] Positioning statement is internally consistent (audience, category, benefit, differentiator all align)
- [ ] Key messages are distinct — each one says something different, not the same thing three ways
- [ ] Elevator pitches open with the customer's problem, not the product
- [ ] Tone of voice has concrete "this, not that" examples, not just adjectives
- [ ] Objection handlers are honest — they acknowledge the concern before reframing
- [ ] All claims have supporting proof points
- [ ] Messaging is differentiated from the top 2-3 competitors (not interchangeable)
- [ ] Framework is usable by someone who was not in the room — no tribal knowledge required
- [ ] Tagline is memorable, not just descriptive

---

## Edge Cases

- **Early-stage startup with no customers yet**: Use founder story and problem validation as proof points instead of customer metrics. Frame positioning as a hypothesis to test, not a permanent stake.
- **Repositioning / rebrand**: Capture the "from → to" narrative. Acknowledge the old positioning and clearly articulate why the shift is happening. Provide transition messaging for existing customers.
- **Multiple products or business lines**: Create a master brand framework plus product-level messaging that ladders up. Ensure product messages do not contradict or compete with each other.
- **Technical product for non-technical buyers**: Develop two message tracks — one for technical evaluators (features, architecture, integrations) and one for business buyers (outcomes, ROI, risk reduction).
- **Commodity market** (hard to differentiate): Focus messaging on experience, service, community, or brand values rather than product features. "How" you deliver matters more than "what" you deliver.
- **Regulated industry**: Flag claims that may need legal review (e.g., "guaranteed", "compliant with", performance claims). Recommend legal sign-off before public use.
- **Messaging by committee** (too many stakeholders): Recommend a RACI for messaging decisions. One person approves, others are consulted. Messaging should not be designed by consensus — it becomes bland.
- **International / multi-language**: Note that messaging must be transcreated, not just translated. Cultural context, idioms, and humor do not transfer directly. Recommend local market input for each language version.