Every founding team hits a moment where the product is working but the market doesn't get it. Revenue grows slower than it should. Partnerships stall. Investors ask questions that reveal they missed the point entirely.
The instinct is to throw more at it. More content, more ads, more homepage redesigns. But the problem isn't volume. It's story. Or more precisely, the absence of one.
Seth Godin put it simply:
He's right. And he's not being poetic. He's being literal. Before writing, before currency, before agriculture, humans organized knowledge, values, and trust through narrative. It's how we're built. The question isn't whether your company needs a story. The question is whether you have a good one.
The science is settled
Word-of-mouth has an ROI roughly 5x that of paid media. It's responsible for nearly half of all purchasing decisions. And it's 37% more effective at retaining customers than any other form of advertising.
Why? Because people talk about what they think about. And people think about the things that make them feel something.
Neuroscience backs this up. When someone hears a list of features, the language-processing centers of the brain light up. That's it. When someone hears a story, the brain responds as if it's experiencing the events firsthand. Sensory cortex. Motor cortex. Emotional centers. The whole machine fires.
Neuroscientists have a shorthand for this: what fires together, wires together. When a brand's story aligns with someone's values and lived experience, it doesn't just get remembered. It gets wired in. That's not loyalty earned through repetition. That's loyalty earned through resonance.
Facts don't travel. Stories do.
Here's the thing most founders get wrong: they lead with what their product does instead of why anyone should care.
Features are facts. Facts are processed by the logical brain, which is slow, skeptical, and easily distracted. Stories activate emotion, and emotion is what drives memory, empathy, and decisions. It's subjective experience that stimulates action, not objective information.
Think about your own life. You don't remember the PowerPoint from last Tuesday. You remember the story your co-founder told at the offsite about why they quit their last job to build this thing.
Stories also do something facts can't: they provide context. They turn abstract capabilities into something tangible, meaningful, and repeatable. In a story, facts get woven into a structure that gives them relevance. That makes them easier to understand, easier to remember, and far more persuasive.
Start with progress, not with "once upon a time"
Most narrative frameworks start with the story. Character, conflict, resolution. That's fine for screenwriters. It's backwards for founders.
The better question is: who is trying to make progress, and what's in their way?
This is the lens we use at F/AS, and it changes everything. Instead of starting with your company's origin story or your product's feature set, you start with the customer's job. Not their demographics. Not their persona. The actual progress they're trying to make in a specific moment of their life or work.
When you understand the job, the friction becomes obvious. And not just the surface-level friction (the feature gap, the integration headache) but the deeper friction: the frustration, the self-doubt, the fear of making the wrong bet. That emotional layer is where buying decisions actually happen. We tend to sell solutions to external problems, but customers buy solutions to internal ones.
Five bones, every time
After two decades of building, scoring, and rebuilding brand narratives, the pattern is consistent. The stories that compound all share the same bones:
The Customer. Who is trying to make progress, and what does that progress look like? Not a persona deck. A real human in a real situation with a real job to do.
The Friction. What's blocking that progress? And not just the obvious obstacle. The emotional weight of the obstacle. The thing that keeps them up at night.
The Guide. This is where your brand enters the story. Not as the hero. As the guide. The one who's been there, understands the struggle, and has a credible path forward. Empathy plus authority plus a genuine insight the market hasn't caught up to yet.
The Path. The concrete mechanism. What to do, how it works, and why it's not a leap of faith. The plan has to be tangible enough that the customer can see themselves doing it.
The Outcome. What the world looks like on the other side. Not features shipped. Transformation achieved. And, just as importantly, what persists if nothing changes. The cost of standing still.
Miss any one of these and the story leaks. The audience feels it even if they can't name it. Something's off. They nod politely, say "interesting," and never call back.
Your story is infrastructure
This is the shift most teams don't make. They treat their narrative like a marketing asset: something you produce once, hand to the design team, and move on.
Ben Horowitz put it bluntly: the story is the strategy. If you make your story better, you make the strategy better. He's not talking about marketing. He's talking about the operating system of the company.
Your story isn't a deliverable. It's infrastructure. It's the foundation that every website, every deck, every investor conversation, every sales call is built on.
When the infrastructure is solid, everything downstream gets easier. Marketing spend compounds instead of evaporating. Partnerships close on the first call instead of the third. New hires can explain what you do without reading a script.
When it's not, you get activity without progress. Lots of motion. Very little traction.
The best products don't always win. The best stories do. And the best stories aren't accidents. They're built with the same rigor you'd apply to your product, your codebase, or your cap table.
If you can't articulate who you're for, what's in their way, why you're the guide, what the path looks like, and what changes when it works, you don't have a story yet. You have a collection of talking points. And talking points don't compound.