The StoryBrand Website Framework

Updated September 2026 · Written and maintained by the Progression Agency strategy team

StoryBrand is a message-clarity framework that puts the customer in the hero’s position and the business in the guide’s, and its central instruction — stop describing yourself and start describing the customer’s problem — is genuinely good advice that most business websites need. Its weakness is that a framework applied literally by thousands of firms produces thousands of pages with the same shape, and the differentiation the copy is supposed to create is undone by the structure it arrives in.

What is the StoryBrand framework?

A message-clarity framework, published by Donald Miller in Building a StoryBrand, that structures marketing copy as a story in which the customer is the hero and the business is the guide who helps them succeed.

Its practical claim is that visitors leave a website because they cannot quickly work out what you offer, whether it is for them, and what to do next — and that framing the message as a story fixes that. The diagnosis is accurate and describes the majority of business websites we see.

The core instruction is the valuable part

Stop describing your company and start describing your customer’s problem. That single change improves most business websites regardless of whether anything else from the framework is used, because the default failure mode of a company website is to talk about itself.

We are not certified guides

StoryBrand runs a certification program and a network of implementers, and we are not part of it. This page is our own assessment of how the framework performs on real websites, not an official interpretation, and where we disagree with it we say so.

What are the seven elements?

A character with a want, who has a problem, meets a guide, who gives them a plan, calls them to action, helps them avoid failure, and ends in success.

The character is the customer, not you

The most quoted idea in the framework and the one that changes copy fastest. A homepage beginning ‘We are a full-service agency founded in 2011’ has cast the wrong character; one beginning with what the visitor is trying to do has cast the right one.

The three-part problem is the most useful element

External is the practical problem — the website does not generate inquiries. Internal is how it makes them feel — embarrassed to send the link to a prospect. Philosophical is why it ought not to be that way — a good business should not be let down by its website. Naming all three produces copy that resonates in a way naming only the first does not.

The plan should be three steps, and people write seven

The purpose is to reduce perceived risk by making the process look manageable. A seven-step diagram does the opposite. If your process genuinely has seven stages, describe three and let the detail live somewhere the buyer reaches later.

Empathy before authority, in that order

The guide establishes that they understand the problem before establishing that they can solve it. Reversing it — credentials first — is the default instinct of professional firms and reads as being talked at.

Where does it genuinely work?

On service businesses selling to non-specialists, on sites that currently describe themselves rather than the customer, and on teams that cannot agree what the message is.

The last of those is underrated. A framework’s real function in an organization is frequently to force a decision that internal debate has not produced, and StoryBrand is unusually good at that because its structure makes disagreement visible.

It is a strong first framework

For a business that has never articulated its message deliberately, working through the seven elements produces a large improvement quickly. The alternative for most such businesses is not a better framework; it is nothing.

Where does it produce identical websites?

When the sequence is applied as a page layout rather than as a message diagnosis. The visual signature is recognizable: aspirational headline, three problem icons, one-two-three graphic, ‘Schedule a Call’.

This is the framework’s real weakness and it is a weakness of application rather than of theory. Nothing in the seven elements requires three icons or a numbered graphic; those are conventions that spread through the implementer network and became the default.

A framework applied at scale stops differentiating

If several thousand businesses use the same structure, the structure carries no information. In some categories &mdata; particularly professional services and coaching — buyers encounter the same shape repeatedly and it reads as a template rather than as a considered message.

Keep the diagnosis, vary the expression

The test the framework provides — can a visitor tell in seconds what this is, who it is for and what to do — is worth keeping permanently. The particular arrangement of headline, icons and numbered steps is one way of passing that test, not the only one.

Where does it not work at all?

Ecommerce catalogs, technical products sold to experts, multi-audience sites, and any situation where the constraint is traffic rather than messaging.

Ecommerce is the wrong shape

A catalog site’s job is to help somebody find and evaluate a specific product, not to narrate a transformation. The framework’s structure fights the page types ecommerce actually needs, and applying it to a product listing produces a worse listing.

Technical buyers are lost by simplification

An engineer evaluating a component wants specifications, constraints and honest limitations. Copy that removes technical detail in the name of clarity removes exactly what that reader came for, and reads as evasive rather than as clear.

One hero does not fit a multi-audience site

A business selling to three genuinely different buyers cannot cast one hero without excluding two of them. The workable answer is separate paths from the homepage, each with its own hero — which is a departure from the framework’s usual single-narrative homepage.

Messaging cannot fix a traffic problem

If nobody is arriving, clearer copy improves the experience of the few who do and changes nothing else. Establishing whether the problem is traffic or conversion takes one look at analytics and prevents an expensive misdiagnosis.

How does it compare with other frameworks?

It is the easiest to apply and the most likely to produce sameness. Jobs to be Done produces sharper differentiation and is much harder; positioning work produces the most distinctiveness and requires decisions most businesses avoid.

The last row is a real option and it is the one most businesses are actually using. Against that baseline, StoryBrand is a substantial improvement, which explains its adoption and does not make it the right ceiling.

The frameworks are not exclusive

Jobs to be Done research producing the input, and StoryBrand structuring the output, works considerably better than either alone. The research tells you what the customer is actually trying to accomplish; the framework turns it into copy somebody can read.

How do you apply it without producing the template?

Use the seven elements as questions to answer rather than as sections to build, and let the design and structure follow from the answers.

1. Answer all seven questions in writing before anybody designs anything
2. Write the three-part problem properly, in the customer’s own language
3. Test the headline: can a stranger say what you do after reading only it?
4. Choose the call to action the buyer is actually ready for, not ‘Schedule a Call’ by default
5. Design the page from the answers, not from the framework’s usual arrangement
6. Replace the three-icon row with whatever genuinely communicates the problem
7. Check whether your competitors’ sites already have this shape
8. Give the same clarity test to the pages the homepage leads to

Step four matters more than it sounds. ‘Schedule a Call’ is the framework’s default direct call to action and it is a large commitment for somebody two minutes into a website. A lower-friction step that genuinely fits the buyer’s readiness frequently converts better and is rarely considered.

Check what your competitors’ sites look like first

If three of them already use the framework visibly, adopting the same structure makes you the fourth indistinguishable site in the category. That is a reason to keep the clarity discipline and change the expression, not a reason to abandon the diagnosis.

The transitional call to action is the underused element

Something a visitor can take without committing — a guide, a calculator, a checklist — captures people who are not ready for a conversation. It is in the framework, it is frequently skipped, and it is where most of the unconverted traffic actually goes.

Does it actually improve conversion?

Where the previous site was unclear, usually and sometimes substantially. Where the previous site was already clear, the framework adds little, and no honest answer exists without a measured before and after.

Claims about the framework’s conversion effect circulate widely and are almost never accompanied by a controlled comparison. A rebuild changes messaging, design, speed, structure and calls to action simultaneously, which makes attributing the result to the framework specifically an assertion rather than a finding.

Measure before you rebuild

Record conversion rate, bounce behavior and inquiry quality before the change, so the comparison exists afterwards. Almost nobody does this, which is why the evidence for every website framework consists of testimonials.

Inquiry quality matters as much as volume

Clearer messaging frequently reduces inquiry volume and improves fit, because people who were never going to buy now self-select out earlier. A site that produces fewer, better inquiries has improved even though the headline number fell.

What should you take from it if you take nothing else?

The clarity test, the three-part problem, and one unambiguous next step on every page.

• A visitor should be able to say what you do, who it is for and what to do next, within seconds
• Name the external, internal and philosophical problem, not just the practical one
• Lead with what the customer wants, not with your founding date or your team size
• Establish empathy before credentials
• Give a plan short enough to feel manageable
• Put one direct call to action everywhere, unchanged
• Add one transitional offer for people not ready to talk
• Say what happens if nothing changes, without manufacturing fear

Those eight are the framework’s durable contribution, and they survive being separated from its layout conventions entirely. A site that passes all eight while looking nothing like a StoryBrand site has taken the useful part.

How do you know whether your current site has the problem StoryBrand solves?

Four tests, each taking under a minute, and a site failing any of them has the clarity problem the framework is aimed at.

The last row is the test the framework itself does not provide and the one that catches its own weakness. A page can pass every StoryBrand test and still be interchangeable with three competitors, because clarity and distinctiveness are different properties.

Run the competitor swap before and after

If the page fails the swap test both before and after a StoryBrand rewrite, the rewrite has made unclear generic copy into clear generic copy. That is an improvement and it is not positioning, and knowing the difference prevents expecting the wrong outcome.

What does a StoryBrand website look like in practice?

The change is almost always the same: copy that described the company becomes copy that describes what the visitor is trying to do. Here is that rewrite applied to four common business types.

These are illustrative rewrites rather than client work, and the pattern in the fourth column is the entire lesson. Every ‘before’ is accurate and about the business; every ‘after’ is about the reader. That single shift is what the framework is for, and it is achievable without adopting any of its layout conventions.

The rewrite frequently makes the copy shorter

Describing what somebody wants takes fewer words than describing everything you do, which is why StoryBrand rewrites tend to reduce homepage copy substantially. That is usually an improvement and it creates the SEO problem discussed below.

Test the rewrite on somebody outside the business

Show the headline alone to a person who does not know what you do and ask them to say what the company sells and who it is for. If they cannot, the rewrite has become aspirational rather than clear, which is the most common way this exercise goes wrong.

What are the SEO considerations with a StoryBrand website?

The framework optimizes for a visitor who has already arrived. Search requires content that helps them arrive, and applied strictly StoryBrand can strip a site of the language people actually search for.

None of these conflicts is fatal and all of them are resolved the same way: let the homepage do the StoryBrand job of clarifying and converting, and let service pages do the search job of ranking. Trying to make one page do both is what produces either an unclear homepage or an unfindable one.

Your customer’s words are usually the search terms

The framework’s instruction to use the customer’s language and the SEO instruction to use searched language point the same way far more often than they conflict. Where a business says ‘thermal envelope remediation’ and the customer says ‘draughty house’, the customer’s phrase is both clearer and the one being searched.

Keep the plain term in the title tag

An aspirational H1 with a plain, descriptive title tag gives the visitor the message and the search engine the term, and the two do not have to be identical. This resolves most of the tension in a single field.

Do not let ‘one next step’ remove your navigation

The framework’s emphasis on a single call to action is sometimes read as a reason to strip navigation. That harms crawling, harms visitors who want something specific, and is not what the framework asks for — one prominent action does not mean one link.

Frequently asked questions