Building a StoryBrand, Applied: The SB7 Framework for Solo Founders

Most solo-founder pages read like a diary entry: our mission, our story, our journey. The visitor skims for themselves in it, doesn't find it, and leaves. Building a StoryBrand applied to your business means running Donald Miller's SB7 framework so the customer becomes the hero of the story and you become the guide who hands them the plan.

Building a StoryBrand, applied, means turning Donald Miller's SB7 framework into a working BrandScript: a one-page document that names your customer's problem, positions you as the guide, lays out a simple plan, and gives a direct call to action. Once written, that BrandScript becomes the spine for your landing page, ads, and emails, not just a slogan.

Here's what actually decides whether this moves revenue: specificity, not creativity. Confused visitors don't buy, and most solo operators write from inside their own head, using the language of what they built instead of the language the customer uses to describe what they're trying to survive. StoryBrand isn't a new idea. Joseph Campbell mapped the hero's journey long before Miller adapted it for business copy, and it sits alongside the other frameworks in the operator's bookshelf for a reason: it's one of the few that turns straight into copy you ship the same day. What separates a BrandScript that changes conversion from one that just sits in a Google Doc is whether you fill each of the seven slots with your customer's actual words instead of a generic category borrowed from a course transcript.

What is the StoryBrand SB7 framework, in plain terms?

SB7 is a seven-part message structure that puts your customer in the hero role and your business in the guide role, the same relationship Yoda has to Luke or a coach has to an athlete.

Miller built it by adapting the hero's journey for business messaging, then compressed it into seven questions any operator can answer on one page:

• A character wants something.
• They have a problem stopping them from getting it.
• They meet a guide (you) who understands the problem and can solve it.
• The guide gives them a plan.
• The guide calls them to action.
• That action helps them avoid failure.
• And it ends in success.

Answer those seven in order and you've written what Miller calls a BrandScript: a one-page brief that every piece of copy your business puts out should trace back to. Skip the framework and default mode kicks in, which for most solo founders is talking about themselves. Your certifications, your backstory, your "why," all interesting to you, mostly irrelevant to someone trying to solve a problem in the next ten minutes.

The fix isn't complicated. It's just uncomfortable, because it means moving your own story out of the spotlight and putting the customer's story in it instead.

How do you identify the character and their problem?

You name one specific customer with one specific goal, then dig for their problem on three levels: external, internal, and philosophical.

Character comes first, and the biggest mistake here is refusing to narrow it. "Small business owners" or "content creators" isn't a character, it's a mailing list. Pick the one person who actually buys: their role, their situation, what they're mid-way through when they find you.

Problem is where most solo founders stop too early. The framework forces three layers:

• External problem: the tangible, practical obstacle. The thing they'd type into Google.
• Internal problem: how the external problem makes them feel, behind, overwhelmed, embarrassed, out of their depth.
• Philosophical problem: why it's just wrong that this problem exists at all, the bigger principle it violates.

Here's a worked, illustrative example: an operator selling an AI-built client-onboarding template pack to freelance consultants.

• External: every new client means rebuilding an intake form, a contract, and a project brief from scratch, most of a day gone before any billable work starts.
• Internal: feels disorganized and a step behind agencies that show up with a slick packet on day one.
• Philosophical: someone who's good at the actual work shouldn't lose credibility over paperwork they were never trained to build.

Most websites talk only to the external problem ("save time on admin"). The internal and philosophical layers are where the buying decision actually happens, because people rarely spend money to fix a logistics problem. They spend money to stop feeling the way the logistics problem makes them feel.

How do you position your business as the guide, not the hero?

You earn guide status with two things, in this order: empathy first, authority second.

Empathy is a line that proves you understand the specific frustration you just named, not a generic "we care about our customers." It should sound like something the customer would say about their own situation, not marketing language layered on top of it.

Authority comes after, and it's proof, not a resume. Years doing the specific thing, number of times you've solved this exact problem, the tools or methods you personally use. The order matters more than people expect: lead with authority and you sound like you're selling. Lead with empathy, then authority, and you sound like you already get it and happen to be qualified to fix it.

Back to the onboarding-pack example. A guide section built the right way might read: "Building the actual client work was never the hard part, it's the hour you lose stitching together an intake form and a contract every time someone new signs. We've built and rebuilt that packet for our own client work more times than we can count, this is the version we finally stopped tweaking." Empathy in the first sentence, authority in the second, no resume required.

This is also where the real narrative craft lives. The same mechanics behind story-driven sales copy apply here: specific, sensory detail beats a broad claim every time.

How do you build the plan that moves the character to act?

The plan is three or four steps that make the next move obvious, not a summary of your entire process.

Two versions matter. A process plan shows the customer literally what happens after they say yes (step 1, step 2, step 3, done). An agreement plan removes risk instead: a guarantee, a specific promise, terms that make saying yes feel safer than saying no.

Keep the process plan short on purpose. Every step you add is a reason to hesitate. If your actual onboarding takes nine steps, that's fine, the customer only needs to see the three that matter to them:

1. Get the pack.
2. Swap in your details using the built-in AI prompts.
3. Send a client-ready packet the same day.

Notice what's missing: no mention of file formats, no mention of the tech stack behind it, no mention of how the templates were built. That's real information, but it belongs in an FAQ, not the plan. The plan section has one job: make the customer believe the path from here to done is short and clear.

How do you write the call to action and the stakes?

You give one direct call to action (the paid offer) and one lower-commitment transitional call to action, then show what's at stake on both sides of that decision.

Direct CTA: buy, book, join, the action that makes you money. Say it plainly. "Get the pack" beats "Learn more" every time, because "learn more" doesn't ask for a decision.

Transitional CTA: a smaller ask for someone not ready yet, a free template, a short guide, an email opt-in. This isn't a consolation prize, it's how you keep someone in your world instead of losing them entirely to a "not right now."

Failure is the cost of doing nothing, stated plainly instead of dramatized. For the onboarding-pack example: another quarter of losing a day per client to paperwork, another new client who quietly compares you to whoever showed up with a slicker packet first. No countdown timers, no manufactured panic, just the real cost of staying put. Overstate it and you're using loss aversion as a threat instead of a fact, and readers can tell the difference.

Success is the specific after-state, not "achieve your goals." For this example: a client-ready packet sent same day, every time, without touching a blank page. Concrete enough that the customer can picture themselves living it, not vague enough to fit any business on earth.

How do you compress all seven elements into a one-liner?

A one-liner is a single sentence built from three of your seven answers, problem, plan, and success, that works as your headline, your elevator pitch, and your bio at the same time.

The shape is simple even when the words are hard to land: name the character and their problem, name what you do about it, name the result. For the onboarding-pack example: "Freelance consultants who land a new client and then lose a day to paperwork use our AI-built onboarding pack to send a client-ready packet the same day, without hiring anyone."

Run it through one test before you ship it anywhere: could you say it out loud to someone at a conference without sounding like you're reading off a brochure? If it needs a slide behind it to make sense, it's not done. If it could describe five other businesses with the nouns swapped out, it's not specific enough yet, go back to the problem section and get sharper.

This is also the sentence that should survive contact with whatever copywriting framework you layer on top of it later, PAS, AIDA, or anything else you use to write the actual page. The BrandScript decides what you say. The framework you pick decides the order you say it in.

How do you apply a finished BrandScript to your funnel and ads?

You map each of the seven elements onto an existing page or ad slot instead of writing new copy from a blank page.

On a landing page, the mapping runs roughly top to bottom:

• Character + external problem: the hero headline and subhead.
• Empathy line: the first sentence under the fold.
• Authority proof: a short proof strip right after it, numbers, logos, credentials.
• Plan: the three-step section, usually with icons or numbers.
• Direct CTA: the button copy, repeated at the top, middle, and bottom of the page.
• Failure: a short paragraph right before pricing, the cost of staying put.
• Success: the testimonials, framed around the after-state, not just "great service."

For ads, the one-liner becomes the hook (first line, first three seconds), the plan becomes the body, and the CTA is the CTA, no translation needed. Email sequences pull one element per send instead of cramming all seven into one message: a whole email on the internal problem, a whole email on the plan, a whole email that's just the failure case stated plainly.

The reason this works better than writing each asset separately is consistency. Every page, every ad, and every email traces back to the same seven answers, so a visitor who sees your ad, lands on your page, and gets your follow-up email hears one consistent story instead of three different pitches from the same business.

Run this as an AI interview instead of a fill-in-the-blank

The fastest way to get a real BrandScript instead of a generic one is to have AI interview you, one question at a time, and push back when your answer is too vague. A fill-in-the-blank template lets you write "better customer service" and move on. An interview format won't let you get away with that.

You are a StoryBrand-trained messaging strategist working with a solo
operator. Be a skeptic, not a cheerleader: push back when my answers are
vague, generic, or self-flattering, and never let me say "everyone" is
my customer.

MY BUSINESS: [ONE-SENTENCE DESCRIPTION OF WHAT YOU SELL]
MY CUSTOMER: [WHO SPECIFICALLY BUYS THIS, ONE ROLE OR PERSON, NOT A
DEMOGRAPHIC]
WHAT I KNOW ABOUT THEIR SITUATION RIGHT NOW: [2-3 SENTENCES ON WHAT
THEY'RE DEALING WITH]

Interview me one question at a time, waiting for my answer before moving
to the next, to build a StoryBrand SB7 BrandScript:

1. CHARACTER: What does my customer want, in one sentence, framed as
their goal, not my product?

2. PROBLEM: Push me past the surface answer. Ask for the external
problem (the tangible obstacle), the internal problem (how it makes them
feel), and the philosophical problem (why it's unfair or just wrong that
this problem exists). If my answer is generic, ask a follow-up before
accepting it.

3. GUIDE: Ask me for one line of empathy (proof I understand the
problem) and one line of authority (proof I can solve it), both specific
to me, not generic claims.

4. PLAN: Ask me to list 3 to 4 steps a customer takes from "just found
me" to "got the result." Push me to cut any step that isn't necessary
for the customer to see.

5. CALL TO ACTION: Ask me for one direct call to action (the paid offer)
and one transitional call to action (a lower-commitment first step).

6. FAILURE: Ask me what it costs my customer, in time, money, or
reputation, if they never solve this problem.

7. SUCCESS: Ask me to describe the specific after-state, what changes
in their day-to-day once this is solved.

When we finish all seven, compile my answers into:
A) A full BrandScript with all seven elements labeled.
B) A one-liner (1 to 2 sentences) combining the problem, the plan, and
the success.
C) A 3-sentence version I could say out loud when someone asks what I do.

Ask me the first question now.

Run it in a fresh chat, answer honestly instead of aspirationally, and expect the internal and philosophical problem questions to take the longest. That's normal. It's also usually where the real copy improvement comes from.

Honest limits: where this breaks down

A clean BrandScript doesn't fix a weak offer. If the plan you're promising doesn't actually deliver what the success section describes, clearer messaging just gets more people to notice the gap faster, and refund requests instead of just bounces.

It also isn't an awareness-stage tool. SB7 assumes the customer already knows they have the problem you're naming, which is true for plenty of buyers and false for plenty of others. Someone who's never considered that their onboarding process is costing them clients needs a different opening than someone actively comparing five template packs right now. Pair it with a look at where your traffic actually sits before it arrives: a cold audience and a ready-to-buy audience need different entry points even when they end up reading the same BrandScript further down the page.

There's also a formula risk. Seven businesses that all fill in the same seven slots without real specificity in the problem section end up sounding like seven versions of the same page. The framework doesn't protect you from being generic, only your answers do. If your one-liner could describe a competitor with the nouns swapped, the work isn't finished, it's just organized.

And it's a message framework, not a full marketing system. It tells you what to say. It doesn't tell you what to test, how much to spend, or which channel to run it on. Treat the BrandScript as the input every other piece of your funnel pulls from, not the finished funnel itself.

Frequently Asked Questions

What's the difference between StoryBrand and PAS (Problem-Agitate-Solve)?

PAS is a structure for a single piece of writing, an email, an ad, one page. StoryBrand is a positioning framework for your whole business that feeds into whatever copy structure you use afterward. Once you have a BrandScript, PAS becomes straightforward: agitate pulls from your internal and philosophical problem, solve pulls from your plan and guide.

Do I need to redesign my whole website to use StoryBrand?

No. Start with the hero section, the first sentence under the fold, and your CTA buttons, that's where most of the conversion lift shows up first. Everything else, emails, ads, the About page, can follow once the BrandScript exists to pull from.

How is a BrandScript different from a value proposition statement?

A value prop is usually one sentence describing what you do and for whom. A BrandScript is the full seven-part document underneath that sentence. The one-liner or value prop is the compressed output of the work, not a substitute for doing it.

Does StoryBrand work for high-ticket or B2B offers?

Yes, the seven elements don't change, only their weight does. B2B buyers lean harder on the authority proof (track record, credentials, case history), and the philosophical problem often turns into a business-risk argument instead of a personal one.

How long does it take to write a working BrandScript?

A working draft takes about an hour if you already know your customer well, and most of that hour goes into the problem section, not the plan or the CTA. Running it as an interview instead of writing alone in a document catches vague answers faster.

Can I use this for a personal brand instead of a product?

Yes, same seven slots. The guide section carries more weight since your personal story becomes part of the authority proof, and the success section needs extra specificity: a coach's page that says "grow your brand" fails the same test a template pack would.

Where to take this next

None of this needs to be perfect before you use it. A rough BrandScript that's actually specific beats a polished one full of vague, safe language every time. Ship the rough version, watch what happens to your reply rate or your landing page, then tighten the parts that don't land.

If you want to run this alongside people building digital assets with AI the same way, week over week, pressure-test your BrandScript inside the Asset Academy community on Skool.