storybrand-messaging

$npx mdskill add wondelai/skills/storybrand-messaging

Clarify brand messaging by positioning the customer as hero.

  • Helps users craft clear messaging that resonates with customers.
  • Depends on narrative structure and StoryBrand framework principles.
  • Scores messaging using a diagnostic and identifies gaps.
  • Delivers a brand script, one-liner, or copy improvements.

SKILL.md

.github/skills/storybrand-messagingView on GitHub ↗
---
name: storybrand-messaging
description: 'Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "brand script", "StoryBrand framework", "customer as hero", or "my messaging isnt resonating". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales and marketing collateral. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.'
license: MIT
metadata:
  author: wondelai
  version: "1.5.0"
---

# StoryBrand Messaging Framework

Clarify your message so customers will listen. Customers don't buy the best products — they buy the ones they can understand the fastest.

## Core Principle

**The customer is the hero, not your brand.** Your brand is the guide who helps the hero win. Position yourself as the hero and you compete with your customer; position yourself as the guide and you serve them.

## Scoring

**Goal: 10/10.** Score any marketing copy or brand messaging by the Quick Diagnostic: 1 point per satisfied row (7 rows) plus up to 3 points for a one-liner that passes the cocktail party test (clear + repeatable in one hearing). Bands: 9-10 = customer is the hero, all three problem levels named, empathy + authority both shown, a 3-step plan, one obvious Direct CTA, and both success and failure stakes painted; 5-6 = SB7 partly applied but the internal problem, stakes, or CTA is missing; <=3 = brand-as-hero, feature-led, or no clear ask. Always state the current score and the specific changes needed to reach 10/10.

## The SB7 Framework

Every compelling story follows the same pattern. Use this structure for all messaging:

### 1. A Character (The Hero)

**Core concept:** The customer is the hero, and your job is to define the ONE thing they want. Be specific about that single desire.

**Why it works:** Naming a desire opens a story gap — the distance between where the customer is and where they want to be. That tension pulls them in because they feel understood and want the gap closed.

**Key insights:**
- Focus on ONE desire per message — multiple desires dilute the story gap
- Tie the desire to survival (physical, financial, relational, or spiritual)
- Aspirational identity is powerful ("become the leader everyone respects")
- Different segments have different desires — write separate messaging per role, stage, and pain intensity

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Homepage headline | Desire as outcome | "You want a beautiful smile" (not "our dentistry is excellent") |
| Landing page | One desire per page | "You want to retire early" |
| Segmentation | Tailor desire per segment | CEO: "Scale without chaos" vs. IC: "Do your best work without friction" |

**Copy patterns:**
- "You want [specific desire]..."
- "Imagine [aspirational identity]..."
- "What if you could [single clear outcome]?"

See: [references/brand-script.md](references/brand-script.md) — fill out the BrandScript worksheet here when you need to draft all seven elements for a client from scratch.

### 2. Has a Problem

**Core concept:** Define the problem at three levels — external (tangible), internal (emotional), philosophical (the injustice) — and personify it with a specific villain.

**Why it works:** Companies sell solutions to external problems, but customers buy solutions to internal ones. Naming how the problem makes them feel — confused, overwhelmed, embarrassed — taps the emotional driver behind purchases.

**Key insights:**
- External: "my investments are scattered"; internal: "I feel overwhelmed"; philosophical: "people shouldn't need to be experts to retire well"
- A good villain is specific and relatable, not abstract — "Wall Street jargon designed to confuse you", not "complexity"
- Most brands stop at external problems, missing the internal ones that drive purchases

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Website problem section | Name all three levels | External: "Scattered tools." Internal: "You feel overwhelmed." Philosophical: "Teams deserve clarity." |
| Email nurture | Lead with internal problem | "Tired of feeling like you're guessing?" |
| Ad copy | Personify the villain | "Stop letting confusing software steal your evenings." |

**Copy patterns:**
- "You're tired of [internal problem]..."
- "[Villain] has been keeping you from [desire]..."
- "It's not right that [philosophical problem]..."

### 3. And Meets a Guide

**Core concept:** Your brand is the guide, expressing empathy AND authority. Empathy shows you understand the pain; authority proves you can solve it.

**Why it works:** Customers are looking for a guide, not another hero — think Yoda, not Luke. Empathy makes them feel seen, authority (testimonials, logos, statistics) makes them feel safe, and together they create trust.

**Key insights:**
- Show empathy with "we understand" language; show authority with testimonials, client logos, statistics, awards
- Never make your origin story the centerpiece — that is hero behavior; brief, relevant credentials suffice

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| About page | Empathy first, then credentials | "We know what it's like to feel lost in financial jargon. That's why 10,000 families trust us." |
| Homepage social proof | Empathy headline + authority logos | "You're not alone. Join 5,000+ teams who found clarity." + client logos |
| Sales call | Open with empathy, close with authority | "I hear you — that sounds frustrating. Here's what we've seen work for teams like yours." |

**Copy patterns:**
- "We understand what it's like to [empathy statement]..."
- "We've helped [number] [customers] achieve [result]..."
- "You don't have to figure this out alone..."

See: [references/sales-conversations.md](references/sales-conversations.md) — open when scripting a sales call or discovery session; covers discovery questions, objection handling, and full SB7 sales scripts.

### 4. Who Gives Them a Plan

**Core concept:** Give two plans: a Process Plan (3-4 steps showing how to work with you) and an Agreement Plan (commitments that remove risk).

**Why it works:** A clear plan acts as stepping stones across a creek — it reduces cognitive load and perceived risk. Without one, the path feels murky and customers stall.

**Key insights:**
- Process Plan: 3-4 numbered steps max, action verbs, memorable names ("1. Schedule a call. 2. Get a custom plan. 3. Start seeing results.")
- Agreement Plan: fear-removing commitments ("100% satisfaction guaranteed", "Cancel anytime")
- More than 4 steps overwhelms; numbering implies order and ease

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Website plan section | 3-step process with icons | "1. Book a demo. 2. Get onboarded. 3. See results in 30 days." |
| Pricing page | Agreement plan reduces anxiety | "No contracts. Cancel anytime. 30-day money-back guarantee." |
| Email CTA | Reference the plan | "Getting started is simple — just three steps." |

**Copy patterns:**
- "Here's how it works: Step 1... Step 2... Step 3..."
- "Getting started is easy. Just [step 1]."
- "We promise [agreement plan commitment]."

### 5. And Calls Them to Action

**Core concept:** If you don't ask, they won't act. Use a Direct CTA (primary conversion action) plus a Transitional CTA (lower-commitment alternative).

**Why it works:** Customers act only when challenged to act. The transitional CTA keeps not-yet-ready people in your story until they are.

**Key insights:**
- Direct: "Buy Now", "Schedule a Call", "Get Started"; Transitional: "Download Free Guide", "Watch Demo", "Take the Quiz"
- Make the Direct CTA a visually prominent button (contrasting color) and repeat it down the page
- Use action language ("Get" not "Submit"); one obvious Direct CTA per page

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Homepage | Direct CTA above the fold, repeated | "Get Started Free" in header and after each section |
| Blog post | Transitional CTA at the end | "Download our free checklist" |
| Email | Single Direct CTA per message | One "Schedule Your Call" button |

**Copy patterns:**
- "Get [desired result] now."
- "Start your free [trial/demo/assessment] today."
- "Download your free [lead magnet]."

**Ethical boundary:** Never label a paid action as "free" or a Transitional CTA — the button text must match what happens on click.

See: [references/website-wireframe.md](references/website-wireframe.md) — open when laying out a homepage or site; gives section-by-section structure and interior page templates.

### 6. That Helps Them Avoid Failure

**Core concept:** Show what happens if the customer does not act. Without stakes, there is no story.

**Why it works:** Humans are loss-averse — fear of losing motivates more than promise of gaining. A taste of what could go wrong moves customers from "interested" to "committed".

**Key insights:**
- A taste of consequence is enough — don't run a scare campaign
- Focus on opportunity cost, not punishment ("another year of feeling stuck")
- Pair failure with success messaging to create contrast

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Landing page stakes section | Brief failure scenario before CTA | "Without a clear message, you'll keep losing customers to competitors they understand faster." |
| Email subject line | Light urgency | "Are you leaving revenue on the table?" |
| Sales conversation | Name cost of inaction | "What happens to your team if nothing changes in 6 months?" |

**Copy patterns:**
- "Don't let [negative outcome] happen when [solution] is this simple."
- "How long will you wait before [addressing the problem]?"
- "Every day without [solution], you're [cost of inaction]."

### 7. And Ends in Success

**Core concept:** Paint a vivid picture of life after working with you — in terms of status, completeness, and self-realization. Success closes the story gap opened in Element 1.

**Why it works:** People need to see the destination before starting the journey. Showing the transformation — not features — lets customers place themselves in that future and feel its pull.

**Key insights:**
- Status: "Become the go-to expert"; completeness: "Finally have financial peace of mind"; self-realization: "Be the leader you were meant to be"
- Show transformation with before/after comparisons and specific numbers
- Keep the success picture tangible, never vague or generic

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Homepage success section | Specific after picture | "Imagine opening your inbox to qualified leads every morning — no cold outreach required." |
| Case study | Before/after with numbers | "Before: 2% conversion rate. After: 11% in 90 days." |
| Testimonials | Customers describe their success | "I finally feel like I know where every dollar is going." |

**Copy patterns:**
- "Imagine [specific success picture]..."
- "Join [number] [customers] who now [success outcome]..."
- "Finally, [completeness outcome] — without [old frustration]."

## The One-Liner

A single sentence that explains what you do. Use it everywhere.

**Formula:** `[Problem] + [Solution] + [Result]`

**Structure:** "We help [CHARACTER] who struggle with [PROBLEM] to [SOLUTION] so they can [RESULT]."

**Example:** "We help small business owners who feel overwhelmed by marketing create a clear message so they can grow their revenue."

**Test:** Can someone repeat it after hearing it once? (the cocktail party test)

See: [references/one-liners.md](references/one-liners.md) — open when drafting a one-liner; ~20 industry examples plus three alternative formulas (PSR, BAB, "We Exist Because").

## Tone and Voice Guidelines

Keep brand voice consistent across channels while adapting to context.

**Convey guide qualities:** empathy ("We understand..."), authority ("In our experience..."), confidence ("Here's what works..."), helpfulness ("Let us show you...").

**Avoid:** hero language ("We're the best at..."), jargon (use the customer's words), condescension, and tentative weakness.

See: [references/email-sequences.md](references/email-sequences.md) — open when building a nurture or welcome sequence; SB7-mapped templates and subject-line formulas.
See: [references/multi-channel-consistency.md](references/multi-channel-consistency.md) — open when adapting the message to a channel; social, video, podcast, and PR playbooks.

## Common Mistakes

| Mistake | Why It Fails | Fix |
|---------|-------------|-----|
| Being the hero | Competes with customer | Position as guide |
| Multiple messages | Confuses people | One clear message per asset |
| Clever > clear | People don't decode messaging | Choose clarity always |
| Feature-focused | Customers buy transformation | Lead with outcomes |
| No clear CTA | No direction = no action | Ask for the sale |
| No stakes | No urgency = no motivation | Paint failure picture |
| Starting with "We" | Self-focused | Start with customer's problem |

## Quick Diagnostic

| Question | If No | Action |
|----------|-------|--------|
| Can a caveman grasp the offer in 5 seconds? | Message too complex | Simplify to one desire, one outcome |
| Is the customer clearly the hero? | Brand competes with customer | Rewrite from customer's perspective |
| Is the internal problem named, not just external? | Missing the emotional driver | Add "how it feels" language |
| Do you show empathy AND authority? | Trust gap | Add "we understand" + proof points |
| Is there a clear 3-step plan? | Path feels risky | Add Process + Agreement plans |
| Is there one obvious CTA? | Nobody acts | Add prominent, repeated Direct CTA |
| Do you show success AND failure stakes? | No narrative tension | Paint both outcome pictures |

## Further Reading

For the complete methodology and worksheets:

- [*"Building a StoryBrand: Clarify Your Message So Customers Will Listen"*](https://www.amazon.com/Building-StoryBrand-Clarify-Message-Customers/dp/0718033329?tag=wondelai00-20) by Donald Miller

## About the Author

Donald Miller is the CEO of StoryBrand, which has helped over 10,000 businesses clarify their messaging. A New York Times bestselling author of *Building a StoryBrand*, *Marketing Made Simple*, and *Business Made Simple*, he distilled decades of narrative theory into the practical seven-part SB7 framework.

More from wondelai/skills

SkillDescription
37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
blue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
clean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
clean-codeWrite readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.
cold-start-problemStart and scale networked products using Andrew Chen''s "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth at scale. Covers the five stages: cold start, tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.
contagiousEngineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "referral program", "nobody is sharing it", or "make this spread". Also trigger when designing shareable features, crafting social campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.
continuous-discoveryBuild a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.
create-appGuided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way, software-design-philosophy - asking the user questions at every decision point and recording results in the project docs/ folder (PRODUCT.md, ARCHITECTURE.md, EXPERIMENTS.md, CREATE-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a new app, validate an idea before writing code, architect an MVP that will not need a rewrite, or says ''help me build my app the right way''. App already exists: use improve-app or grow-app. Business idea not yet validated: run create-business first. Marketing site only: use create-website. Architecture-only question: design-code-architecture. For one framework in isolation, invoke that skill directly.
create-businessGuided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation, crossing-the-chasm - asking the user questions at every decision point and recording results in the project docs/ folder (CUSTOMER.md, POSITIONING.md, OFFER.md, CREATE-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to start a new business, validate a startup idea, find product-market fit before building, or says ''I have an idea for a company''. Do not use once the business has paying customers: use grow-business to add revenue and customers, or improve-business to fix strategy and operations. For building the product itself use create-app or create-website. For one framework in isolation, invoke that skill directly.
create-websiteGuided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion. Orchestrates ten skills phase by phase - one-page-marketing, storybrand-messaging, made-to-stick, top-design, web-typography, refactoring-ui, ux-heuristics, cro-methodology, scorecard-marketing, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (POSITIONING.md, WEBSITE.md, DESIGN.md, CREATE-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a new website or landing page from scratch, turn a validated idea into a page that converts, or says ''build me a landing page for my SaaS''. Site already exists: use improve-website to fix conversion/UX or grow-website for more traffic; building a software product, not a marketing site: use create-app; no positioning yet: run create-business first or the positioning phase here. For one framework in isolation, invoke that skill directly.