A lot of early-stage founders may explain their company five different ways, depending on the audience.

They know their product, the market, and the customer they want to reach. They understand what they’re trying to build. But when they describe it to investors, candidates, customers, and reporters, their language keeps shifting. Many have trouble explaining it in 30 seconds or less.

It’s not because they’re confused. It’s because there’s a gap between what they know and what everyone else understands.

I recorded a short Fund/Build/Scale episode about this that’s 16 minutes and 55 seconds, which means you can get through the whole thing on a walk, while folding a load of laundry, or pretending to clean your kitchen.

(It takes longer to read this newsletter, but I’m a good writer, so consider it time well spent. 😉)

The basic idea is simple: narrative is not decorative. Narrative is load-bearing.

Before you can show customers, revenue, market pull, positive media coverage, or hiring momentum, your story does a lot of the work. 

It convinces people to take a meeting with you. It gets someone to quit their job and join you. It helps a customer understand why your pilot is worth the internal risk, and it gives investors a clean way to explain your company to someone else after your meeting.

That last part really matters, because your pitch is not your message. 

The pitch is what you say in the room. The message is what survives after you leave.

That’s the test: can someone else explain it back after one conversation? Can they describe the problem, your customer, and the outcome you’re offering? Can they describe what becomes possible because your company exists? 

Or do they just remember the vibe?

Here are some questions I’d ask any early-stage founder before an investor meeting, customer call, candidate interview, panel, press conversation, or podcast:

Do you describe the company differently depending on who’s in the room?

Investors, customers, hires and reporters need different levels of detail, but the center of the story shouldn’t change with the audience.

When someone repeats your company back to you, do they get it right?

Some founders might think the deck is to blame, and sometimes it is. But more often, the problem is upstream: the company doesn’t have a stable narrative frame, so the deck, website, LinkedIn, sales material, recruiting language, and founder pitch are doing slightly different jobs.

Are you using a comparison because it clarifies your story, or because your first sentence isn’t fully baked?

Comps are useful, e.g., “Plaid for X,” or “Uber for Y.” I told someone Sinners was like Interview with the Vampire meets The Color Purple, and they got it instantly, but only because they were familiar with both movies.

There’s nothing wrong with a comp that orients people quickly, but that’s a bridge, not a destination. It can’t carry the room.

The most useful narrative question is not, “What problem are we solving?”

It’s: “what breaks without us?”

Answering this question forces founders to name the failure condition. 

I’m told that founders hate homework, but here’s another diagnostic: complete this sentence:

It’s crude, but clarifying. Filling in those blanks moves a founder out of feature language and into stakes. A feature set tells me what you made, but a failure condition tells me why it matters.

Share this fragment with your founding team and ask them to complete it. If they don’t all answer in roughly the same way, you have a narrative gap inside your company. That’s an alignment problem.

Example: If I were the CEO of Thermos in 1926, I wouldn’t say, “without us, people can’t eat hot food unless they’re at home or in a restaurant.”

I’d say, “Without Thermos, people away from home have to plan their day around whatever food and drink is nearby, convenient, and affordable.”

This is where the work gets emotionally harder. 

Founders can remain attached to the thing that got them started: their first product, their first wedge, even the original insight that made them want to build the company in the first place.

All of those things still matter, but they probably don’t belong in the first sentence.

History = how you got here

Story = where you’re going

When founders confuse the two, it makes it harder to understand what they’re building and why it matters. 

It’s OK to keep your origin product in your founder story! But it may not belong in the story you tell investors, customers, new hires, or reporters.

The first sentence of your startup’s story doesn’t need to explain everything. All it has to do is prevent confusion.

A useful first sentence will name your category, domain, customer, and the outcome. It will give the listener just enough information to understand what you do and why they should keep listening. Don’t give them a list of features, your roadmap, or the pricing model. 

Just give them enough structure so they know what to do with the rest of the information. When you’re starting out, ask people you talk to repeat it back to you. (People secretly love it when you ask them for feedback.)

If they can’t say it back, it’s because there’s a gap in your narrative.

Take every current version of your story and put them next to each other: the website, pitch deck, LinkedIn, sales materials, recruiting language, your email signature, the way your team describes the company, and feedback you’ve gotten from investors.

Then ask:

Your story isn’t everything you know. Your story is the order in which other people need to understand it.

That’s the work. Not marketing polish or spin. Messaging is not a cosmetic exercise, it’s founder work. Strategy work.

Survival work.

A lot of founders are told to wait for traction before worrying about story. I think that’s backwards.

Before there is proof, your story does the work.

This is a short episode, and I built it around practical diagnostics you can use before the market, an investor, a candidate, a customer, or a reporter pressure-tests your story for you.

Become a paid supporter. It directly buys me time to make more deeply-reported, founder-first conversations like this one.

Thanks for reading,

— Walter.