storybrand-messaging
This Claude Code skill applies the StoryBrand framework to clarify brand messaging by positioning customers as heroes rather than brands. Use it when developing website copy, elevator pitches, email sequences, landing pages, or marketing collateral that needs stronger narrative structure and customer resonance. The skill guides users through the seven-element StoryBrand structure to score and improve messaging clarity, ensuring each communication focuses on customer desires and removes competing narratives that confuse purchasing decisions.
git clone --depth 1 https://github.com/wondelai/skills /tmp/storybrand-messaging && cp -r /tmp/storybrand-messaging/storybrand-messaging ~/.claude/skills/storybrand-messagingSKILL.md
# 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.** Rate any marketing copy or brand messaging 0-10 against the principles below. 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]?"
**Ethical boundary:** Ground desires in real research or observed behavior — never fabricate aspirations the customer does not hold.
See: [references/brand-script.md](references/brand-script.md) for the complete BrandScript worksheet covering all seven elements.
### 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]..."
**Ethical boundary:** Name real frustrations honestly — never exaggerate problems or invent suffering to create fear.
### 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:**
- Empathy without authority seems weak; authority without empathy seems arrogant
- 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..."
**Ethical boundary:** Claim only earned authority — real testimonials, accurate statistics, verifiable credentials.
See: [references/sales-conversations.md](references/sales-conversations.md) for discovery questions, objection handling, and 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 commitmentsBuild 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", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
Create 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", "eliminate-reduce-raise-create", or "uncontested market". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
Structure 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 architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.
Engineer 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", "viral loop", "referral program", or "organic growth". Also trigger when designing shareable features, crafting social media 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.
Build 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", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting 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.
Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", or "conversion funnel". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", or "pragmatist buyers". Also trigger when a startup has early traction but struggles to grow beyond initial users, or when planning go-to-market for technical products. Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.