The Story You Live In First

The story a founder lives in becomes the story their company runs on.

It shapes the team culture, the sales calls, the decisions made at 11pm when no one is watching. Most founders never examine it.

This post explains why that matters, how it breaks down between Series A and Series B, and what a discipline for changing it actually looks like.

There’s a story most founders are living that they haven’t written.

Not the pitch deck version. Not the About page. The one running underneath — the one that decides how they respond when a deal goes cold, what they do the morning after a bad board meeting, whether they can actually let go of the parts of the business that have outgrown them.

That story shapes everything. The team culture. The sales calls. The decisions at 11pm.

Most founders don’t know it’s there.

The story that runs your company started long before your company did.

How does founder narrative break down between Series A and Series B?

I’ve watched this pattern repeat across companies at different stages. The names change. The mechanics don’t.

Legibility failure.

The story lives in the founder’s head. They can tell it brilliantly in a room. But it hasn’t been made legible — documented, tested, and handed over in a form that survives the founder’s absence. The VP improvises. The deck gets rewritten by a junior hire who misses what made it work. The new CMO brings their own framework. The narrative drifts.

Delegation failure.

The founder can’t hand off the story because they’ve never examined it. They know it works when they tell it. They can’t explain why. So every pitch, every hire, every keynote still runs through them. The company scales. The founder doesn’t get to.

Decision leak.

This one is quieter. Without a shared narrative, the company makes hundreds of micro-decisions every week — product, sales, hiring, partnerships — each guided by a slightly different internal story.

The drift is invisible until it’s expensive. You feel it when investors can’t retell your story. You feel it when a hire who seemed perfect pulls in a different direction. The story became incoherent somewhere. Nobody caught it.

The root cause of all three: the founder never built the habit of examining the story they’re actually living — week by week, not just at the big reframe moments.

Series A is about capturing early adopters. Series B is about winning the early majority. Those are different stories. Most founders only have one.

Or as Rick Hammell, CEO of Globalli put it to me last week, “Series-A is a growth story, Series-B demands a hyper-growth story.”

Why should narrative discipline start with the founder?

When I left Microsoft, I thought the move to working with founders was a business decision. I had 20 years of experience in story methodology inside enterprise. I’d measurably improved conversion rates, run company-wide training, figured out what made story land in business contexts versus just in film school.

The corporate world still calls. But I kept noticing something: founders need something more than what senior directors need.

Senior directors need to align. To move a room. To keep a brand coherent.

Founders need the story to survive without them. It has to transfer to a VP of Sales, hold up in a board deck written by someone else, be explained by new hires in their second week. That’s not a communication problem. It’s a narrative architecture problem.

My father worked at Intel during a formative era for Silicon Valley storytelling. Geoffrey Moore’s Crossing the Chasm sat on the shelf at home like a reference text. The idea that how you frame a company determines who buys in — I didn’t encounter that as a concept later. I grew up watching it practiced.

My parents were killed in a car crash in 2015. I’m not raising that for sympathy. I’m raising it because it’s the moment the work changed shape for me. Loss burns off distraction. The question stopped being what could I do and became what am I actually here to do.

The answer: help people see the story running them, and build a better one.

Founders are the people I most want to help. Not because they pay well — though the work is valuable and I price it accordingly. Because the problem is real, the stakes are high, and this is the exact moment the story becomes existential.

What does a founder narrative practice actually look like?

I’ve kept a handwritten journal every day for 35 years. It started as a way to process things I couldn’t talk through with anyone. It became how I think. Writing through something and just living through it are different experiences — I’ve been doing both long enough that I can’t fully separate them.

A year ago I added a faster operational layer: daily rapid logging in a notes app, tagged by theme, reviewed weekly, synthesized monthly with AI. I call it the Story Sidekick — three layers feeding each other: capture, synthesis, intend.

The weekly synthesis.

Three questions. The same three every time. Desire: what were you actually reaching for this week — not the official goals, the real want. Difficulty: what specifically got in the way? Vague answers hide the pattern. Direction: what moved, and what did you learn?

Then a title for the week. Because finding a title forces you to locate the story inside the noise.

Once a week, I feed the raw log to an AI and ask it what patterns it sees. I’ve been a journal-keeper for 35 years. Pattern recognition is a capability I’ve built at depth. AI multiplies it — surfaces in minutes what I might catch in a month of rereading. What I bring is the honesty of the raw material and the judgment to know what matters. What AI brings is speed and distance.

The monthly sprint.

AI can surface patterns. It cannot set direction. The monthly layer is where intention lives. One remarkable moment. One idea to carry forward. One smallest step. That part is mine.

When I ran a full year of data back through AI analysis, two things came back that I couldn’t see from inside the weeks: an avoidance pattern (every time outreach anxiety spiked, I defaulted to tool-building — it felt productive; it wasn’t) and a rhythm (alternating bursts and integration periods; when I fought it, I got ill). You can’t see either of those from inside a single week. You can see them over a year.

AI finds the patterns. I decide what they mean. I set the intention. That distinction matters.

Why do founders still need an outside voice even when they’re doing the work?

Here’s an analogy I know firsthand: HPDE. High-performance driver education. Track days where you take your car to a circuit and learn to actually drive it.

First time out, you feel the power. You’re in the car. You’re turning laps. It’s real, visceral, and it’s yours. Nobody handed you that experience. You earned it by being there.

But if you want to improve, you get a coach in the passenger seat.

Not because you can’t drive. Because the coach sees what you can’t see from inside the car. The way you brake too early into Turn 3. The line you’re carrying that costs you two seconds a lap without you knowing it. The habit that feels right and is actually limiting you.

I relish getting a coach when I do HPDE. Every session compounds on the one before. When you keep coming back, keep turning laps, and keep leveraging coaches to be as sharp as you can be.

Aside: If you are a petrol head or geek for track telemetry, you will get a kick out of this session at Pacific Raceways.

The Story Sidekick gives you your first laps on the circuit. You’ll feel something real. You’ll start seeing patterns you couldn’t see before. And at some point, you’ll hit the limit of what you can find from inside your own head — because the story you’re living in is the hardest one to read clearly.

That’s when an outside voice becomes the thing that actually moves the needle.

Where does a founder start?

Today: capture one thing that happened that’s worth remembering. Don’t polish it. Just log it.

At the end of the week, write three things. What you were actually reaching for. What got in the way. What moved. Give the week a title.

Do it again next week. Feed the accumulated log to an AI and ask it what patterns it sees. Notice what comes back that you couldn’t see from inside.

Then sit with this: what story are you actually living right now?

Can you name it?

What does working with Go Narrative look like?

Narrative Diagnostic. A structured conversation where we map the story currently running your company — the version your team is actually operating from, not the one in your head. Usually surfaces two or three specific places where the narrative has drifted or broken. Not a pitch meeting. I’ll ask questions, name what I’m hearing, and you’ll decide if there’s a problem worth solving. If there isn’t, I’ll tell you that too.

Narrative Accelerator. A four-week engagement where we build the architecture — the shared story your team can use to close deals, onboard people, handle board questions, prep the Series-B pitch, and make decisions when you’re not in the room.

Most founders I talk to already know something is off. They just haven’t given it a name yet.

Matthew Woodget is the founder of Go Narrative. He helps Series A–B founders build the narrative architecture that lets their company scale without them in every room. If something in this post resonated, get in touch directly. No deck required.

→  Book a Narrative Diagnostic: gonarrative.com/book-meeting

‍ ‍