Framework · 7 min read

StoryBrand SB7 Framework

A story that casts the customer as the hero and the brand as guide.

Donald Miller · View sources ↓

At a glance

Use this when
You need a customer-centred narrative for a homepage, campaign or presentation.
What you will work towards
A story that casts the customer as the hero and the brand as guide.
Bring to the reading
A specific decision from your work and the customer evidence you have so far.

What it is

A seven-part narrative template, developed by Donald Miller in Building a StoryBrand (2017), that casts the customer as the hero of a story and the brand as the guide who helps them win, rather than the brand casting itself as the hero. The seven parts run in sequence: a Character (the customer, defined by what they want), has a Problem (external, internal, and philosophical layers), and meets a Guide (the brand, which earns trust through empathy and authority), who gives them a Plan (a simple, numbered set of steps), and calls them to Action (a direct next step), that helps them avoid Failure (the stakes of doing nothing), and ends in Success (a vivid picture of life after the product has done its job). The insight, borrowed from screenwriting, is that people do not read messaging the way they read a spec sheet; they process it the way they watch a film, scanning for the hero, the stakes, and what happens next. Most company messaging fails this instinct by making the brand the hero ("we are the leading provider of...") when the reader is looking for a guide who understands their problem. The framework sits at a different altitude from Message Architecture (Messaging House), already in this category: the house is a hierarchy of claims built to keep every asset consistent; SB7 is a narrative arc built to make any single asset land the way an audience processes a story. A messaging house's pillars can supply the Plan and the proof beneath Success, while SB7 supplies the sequence and stakes that make claims worth reading.

When to use it

  • A homepage or landing page reads as a list of features and awards rather than a story a visitor wants to follow. If the "About" section and the value proposition read almost identically, both are probably making the brand the hero.
  • You are writing a founder narrative, an "About Us" page, or a company video script. These formats invite brand-as-hero writing by default, and SB7 is built to correct that instinct.
  • A demo script or sales narrative lists capabilities in the order they were built, rather than in an order a buyer would want to hear them. SB7's Plan step forces a simple, numbered sequence.
  • Message testing shows a landing page or ad scores poorly on "clarity" specifically, not on differentiation. A confusing story structure, not a weak value proposition, is often the real cause.
  • You need one company-wide narrative brief that a video production agency, a copywriter, or a new marketing hire can work from, simpler for a non-specialist to apply correctly than a full positioning canvas.

Ownership

At a scaled company, a Head of Product Marketing or brand and content lead owns the finished SB7 brief, typically briefing a copywriter, video agency, or new marketing hire against it rather than writing every asset personally. A solo or founding PMM writes the brief and the resulting copy directly, often pulling the Guide's authority claims straight from the founder's own customer conversations. Sign-off on the brief, not the finished copy, should sit with whoever owns positioning, since arguing over story structure early is cheaper than rewriting finished sentences later.

How to apply it

  1. Define the Character. Name a single primary customer archetype and, crucially, what they want in one plain sentence ("a finance leader who wants to close the books without a fire drill every month"), not a demographic description. A job title with no want attached is a persona, not a character; rewrite until it names a want.
  2. Diagnose all three layers of the Problem. Write the external problem (the practical obstacle), the internal problem (how it makes the character feel; frustrated, anxious, embarrassed), and the philosophical problem (why it is simply wrong that this problem exists). Most messaging stops at the external layer; the internal and philosophical layers are usually where a reader feels understood.
  3. Position the brand as the Guide, not the hero. Write two sentences: one demonstrating empathy (ideally in the character's own words, from support tickets or sales-call notes) and one demonstrating authority (a credential, a customer count, a named client). Cut any sentence describing the brand's own achievements without tying them back to the customer's problem.
  4. Write the Plan as three or four numbered steps. Buyers hesitate when the next step is unclear; a short, numbered plan ("1. Book a 20-minute call. 2. We map your current close process. 3. Go live in two weeks.") removes that ambiguity far more effectively than prose making the same promise.
  5. Write one explicit Call to Action. Every asset should have exactly one primary action, stated as an imperative, not buried among competing links of similar visual weight; a lower-commitment secondary action can exist alongside it but should stay visually subordinate.
  6. Name the stakes of Failure. State briefly what happens if the problem goes unaddressed: a missed deadline, a lost customer, a compliance fine. This is not a scare tactic when specific and true; it gives the Plan and Call to Action their urgency.
  7. Paint a vivid picture of Success. Describe the character's life after the product has worked, in sensory or emotional terms tied back to the internal and philosophical problems named in step 2. Proof points from an existing Message Architecture pillar fit naturally here as evidence.
  8. Assemble the seven parts into a one-page brief. Hand copywriters, agencies, or new hires the finished brief as the source document; the brief, not the finished copy, is what should get sign-off, since arguing over structure is cheaper than arguing over finished sentences.

Example

Ledgerly, a fictional mid-market accounts-reconciliation SaaS company, had a homepage that opened with "Ledgerly is the industry-leading reconciliation platform trusted by 400+ finance teams," followed by a feature grid and three calls to action of equal visual weight (Start Trial, Book Demo, Download Guide). Bounce rate sat at 68%, and sales reported inbound leads frequently could not explain what the product did in a first call. Running SB7, the team defined the Character as "a controller who wants to close the books without weekend work," the external Problem as "reconciliation is done manually across six spreadsheets," the internal Problem as "dread every month-end close," and the philosophical Problem as "finance teams shouldn't have to sacrifice their weekends to make numbers match." The Guide position paired empathy ("we've sat in that Sunday-night spreadsheet, too") with authority (the same 400+ customer figure, reframed as evidence). The Plan became three steps: "1. Connect your existing accounting system. 2. We auto-match 85% of transactions in week one. 3. Close the books by day 3, every month." A single Call to Action, "Start your free reconciliation," replaced the three competing links. Failure was named directly ("unreconciled accounts mean late board reporting and, eventually, a failed audit"), and Success was pictured concretely ("close on day 3 instead of day 12, with your weekends back"). After the rewrite, bounce rate fell to 49% within six weeks, homepage-to-trial conversion rose from 2.1% to 3.8%, and inbound leads could describe the product correctly in the first discovery-call minute in roughly 70% of calls, up from an estimated 30% before.

Pitfalls

  • Making the brand the hero out of habit. Sentences like "we are the leading provider of..." or "our award-winning platform..." creep back in during review, because they feel like the confident, professional way to open. A reader scanning for a guide who understands their problem disengages the moment the brand starts describing its own greatness instead. Recovery: read the draft aloud and flag every sentence whose subject is the company rather than the customer; rewrite each one so the customer is the subject.
  • Writing a Plan that is really a feature list with numbers added. Numbering three product capabilities ("1. Automation. 2. Reporting. 3. Integrations.") is not a Plan; a Plan describes what the customer experiences in sequence, not what the product contains, and a numbered feature list still leaves the buyer unsure what happens after they say yes. Recovery: rewrite each step as an action taken by or for the customer ("we map your process," "you go live"), not a noun naming a product area.
  • Naming Failure so vaguely it reads as generic scare tactics, or so aggressively it reads as manipulative. "Don't get left behind" names no real stakes and persuades nobody; an overwrought doomsday scenario undermines trust instead of building urgency. Recovery: tie the Failure stakes to a specific, evidenced consequence a real customer has experienced (a missed deadline, a real cost figure), sourced from win/loss interviews or support tickets, not an invented worst case.

How the ideas connect

Choose where to go next

Make it useful

Bring it back to your work.

Name one decision this guide could help you make. Write down the evidence you need, the output you would produce, and how you would know it was useful.

Check your understanding

Practise applying StoryBrand SB7 Framework in five short scenarios.

5 practical scenarios. Choose an answer, explore the reasoning, and revisit the guide whenever you need.

Sources

← All entries in Positioning & Messaging · Try the category quiz