Most startup websites are written like the founder is the main character. Here's our mission. Here's our journey. Here's the problem we personally got fed up with. It's understandable — it's your company, and the story is genuinely yours. But it's the wrong story to put on the homepage, because the person reading it isn't there to learn about you yet. They're there because they have a problem.
Make the Customer the Hero
This idea isn't new, and I won't pretend I invented it. Donald Miller's StoryBrand framework built an entire methodology around one insight: in every good story, the customer is the hero, not the company. The company is the guide. Think Yoda, not Luke. The guide's job is to show up, understand the hero's problem, and hand them a plan — not to make the story about the guide's own backstory.
What I'd add to that, from working with a lot of early-stage companies: founders resist this instinctively, because it feels like it diminishes the company's role. It doesn't. Being the guide is a position of authority, not a lesser one. Yoda isn't a minor character. He's just not the one the story is about.
State the Problem Before You Say Anything Else
The practical version of this: before your homepage says anything about your product, it should say something true about your visitor's problem, in language they'd use themselves. Not "businesses struggle with inefficient workflows" — nobody talks like that about their own week. Something closer to how they'd actually complain about it out loud.
Then, and only then, introduce yourself as the one who can help. Not with a paragraph about your founding story. With a plan. Three steps, usually. Here's what happens when you work with us: step one, step two, step three. Simple enough that someone could repeat it back five minutes later.
A useful gut check for any page on your site: if you removed your logo, could a stranger tell this is about them, or does it read like it's about you? If it's about you, move the customer back to the center.
Where I'd Push Past the Framework
StoryBrand is a great starting structure, and if you've never written customer-centered copy before, it's worth learning properly — I've linked to a fuller breakdown of the underlying brand messaging script below. But frameworks can become a crutch. I've seen founders follow the seven-part structure so rigidly that the copy starts to sound templated, like every other company that read the same book.
My take: use the structure to get the bones right — customer as hero, problem stated plainly, company as guide with a plan — then let your actual voice back into the sentences. The framework should be invisible to the reader. If someone can tell you followed a formula, the formula won, and the story lost.
Where This Shows Up Beyond the Homepage
Once you see this pattern, you'll notice it's missing almost everywhere founders write: pitch decks that open with the founding story instead of the market problem, "why us" pages that read like a resume, sales emails that lead with product features instead of the prospect's actual week. Same fix everywhere. State their problem first, in their words. Then show up as the guide with a plan.
Frequently Asked Questions
Isn't it a little manipulative to frame the customer as the 'hero'?
No — it's just accurate. They're the one taking the risk, spending the money, and living with the outcome. Framing them as the hero isn't a manipulation tactic, it's writing copy that reflects who the story is actually about.
Do I have to follow every part of the StoryBrand framework exactly?
No. Treat it as a starting structure, not a rulebook. The core idea — customer as hero, plain problem statement, company as guide with a clear plan — matters more than following every labeled step in order.
How do I know if my homepage is still too founder-centered?
Read the first three sentences out loud. If they're about your mission, your background, or when you launched, they're about you. Rewrite the opening to name the visitor's problem instead, and push your story to a secondary page.
What's the difference between a plan and a list of features?
A plan is sequential and outcome-focused: step one, step two, step three, here's what's different after. A feature list is just an inventory. Plans are easier to remember and easier to say yes to, because they show the customer exactly what happens next.
Is Your Startup's Messaging Working?
Take the free Mission & Marketing Scorecard — 5 minutes to find out exactly where your messaging is strong and where it's costing you conversions.
Take the Free Scorecard →Need Help With Your Startup's Messaging?
If your website or pitch isn't landing the way it should, I can help you figure out why. Let's take a look.
Work With JT →