A founder story is the short account of why a company exists and who decided to build it. Most are forgettable because they are written to sound impressive rather than true — a problem "discovered," a market "underserved," a mission "to empower." The stories people repeat are usually smaller, stranger and more specific than that. This piece is about how to find the version worth telling and how to write it without slipping into press-release language.

Why most founder stories fail

The failure is rarely a lack of material. It is a decision, usually made early and without much thought, to write the story in the register of a funding announcement.

That register has recognisable symptoms. Everything is framed as inevitable. The founder appears fully formed, already an expert, already certain. The problem is described in the abstract — "inefficiency in the supply chain" — rather than as something that actually happened to somebody on a particular afternoon. Any real hesitation, false start or accident gets edited out, because it looks like weakness.

What gets lost is the only thing that makes a story stick: friction. A narrative without resistance is a list of achievements, and nobody retells a list. We have written before about why the best leaders are great storytellers, and the underlying mechanism is the same here. Listeners hold on to tension and resolution. They discard summary.

There is a second failure, quieter than the first. Many founders write the story they think investors want, then find themselves stuck telling it to customers, to candidates, to journalists and eventually to their own team — audiences with completely different questions. A story built for one room does not travel well.

Start with the moment, not the mission

The most useful writing exercise is also the most restrictive: describe the single moment the problem became personal. Not the market analysis. The moment.

Something specific happened. You watched a colleague spend a full day on a task that should have taken an hour. You tried to buy something and could not find a version that worked. You built a crude internal tool and someone else asked for a copy. Whatever it was, it has a date, a location and other people in it.

Write that scene first, in a few hundred words, before you write anything else. Include what you actually thought at the time, including the unflattering parts — irritation, boredom, the assumption that someone else would fix it. This draft is not the final story. It is the raw material the final story gets carved out of, and it prevents you from starting at the abstraction layer, which is where most founder narratives go to die.

Test for specificity

A useful check: could a competitor publish your founder story with the company name swapped out? If yes, you have written a category description, not a story. Specificity is not decoration. It is the evidence that the story is yours.

The three-part spine

Once you have the moment, most workable founder stories fit a simple structure.

The situation before. What the world looked like, concretely, when you were still living inside the problem. Resist the urge to inflate this into a market thesis. One or two sentences grounded in real experience do more than a paragraph of industry framing.

The decision. Not the vision — the decision. The point at which you stopped treating the problem as background noise and did something about it. This is the hinge of the story and the part most founders skip fastest, usually because the real reason was mundane. Mundane is fine. Mundane is credible.

What changed. What exists now that did not exist before, described in terms a stranger could verify. This is where the temptation to exaggerate is strongest and where exaggeration costs the most, because it is the part people can check.

Three parts, in that order, will carry a story told in sixty seconds or in two thousand words. The length changes; the spine does not.

Write it in your own register

Founder stories are usually read aloud eventually — in a pitch, on a podcast, at an all-hands, in a hiring conversation. Language that looks fine on a website can be unsayable out loud.

The practical fix is to draft by speaking. Record yourself explaining the company to a friend who does not work in your industry, transcribe it, and edit that transcript rather than writing from a blank page. What you get back is imperfect but it is in your actual voice, with your actual emphases, and the parts you naturally lingered on are usually the parts that matter.

This is close to what we mean by finding your voice and helping others find theirs. Voice is not a stylistic flourish added at the end. It is the thing that makes the same facts sound like they came from a person.

Some concrete edits that help:

• Replace abstract nouns with the things they stand for. "Operational complexity" becomes "four spreadsheets and a group chat."

• Cut intensifiers. "Deeply passionate," "incredibly excited," "truly believe" — each one weakens the sentence it is attached to.

• Keep contractions. They are how people talk.

• Name real constraints. Limited money, limited time, a day job — these make the story legible rather than lucky.

Honesty is a practical constraint, not just an ethical one

There is an obvious ethical case for not embellishing a founder story. There is also a purely practical one: an embellished story is expensive to maintain.

Anything you claim gets repeated by other people — employees, partners, press — in rooms you are not in. If the detail is soft, it will eventually be stated by someone who does not know it is soft, to someone who can check. Founder stories that quietly inflate timelines, revenue milestones or the size of an early team tend to be corrected in public, and the correction becomes the more memorable story.

The safer approach is to keep every factual claim to something you could produce evidence for, and to let narrative craft do the rest of the work. Craft is not dishonest. Choosing which true thing to open with, deciding what to leave out, deciding where to slow down — that is editing, and every good story has been edited.

Let the story change as the company does

A founder story written in the first year rarely fits the fifth. The origin does not change, but its relevance does. Early on, the story explains why anyone should take a chance on you. Later, it explains what the company has stayed loyal to while everything else scaled.

Rather than rewriting from scratch, most companies do better by keeping the origin fixed and periodically changing the frame around it — which part is emphasised, where the story ends, what it is being used to explain. A story you revisit once a year stays usable. A story you set in stone becomes a museum piece that everyone internally has quietly stopped believing.

It is worth noticing, too, that the instinct to reach for narrative under pressure is not a marketing trick. It is how people process difficulty in general, something we have explored in why we turn to stories when life gets heavy. Founders are not exempt from that. The story you tell about your company is also, quietly, the story you tell yourself about why the difficult years were worth it — which is part of why an inflated one is so corrosive.

A short working checklist

Before publishing, read the draft against these questions:

• Is there one specific scene in it, with a time and place?

• Would it survive having the company name removed and replaced with a competitor's?

• Can every factual claim be evidenced?

• Does it sound like you when read out loud?

• Is there a decision in it, not just a vision?

• Could someone retell it accurately after hearing it once?

The last question is the real test. A founder story does its work secondhand — repeated by a customer to a colleague, by an employee to a friend. If it survives that retelling with its shape intact, it is finished.

Frequently asked questions

How long should a founder story be? Long enough to contain one scene and one decision. In practice that is usually 150 to 400 words for a website or pitch, with a longer version available for interviews and hiring conversations. The spine stays identical across lengths.

Should a founder story be written in first person? First person is usually the stronger choice because it matches how the story will be told aloud. Third person suits a formal company history or an about page written on behalf of a team, but it adds distance, and distance is the thing most founder stories already have too much of.

What if the origin was not dramatic? Most are not. An undramatic origin told honestly reads better than a dramatic one that feels inflated. Ordinary beginnings — a side project, an annoyance at a previous job, a favour for a friend — are relatable and easy to believe, which is most of what a founder story needs to do.

Can a co-founded company have one story? Yes, and it should. Pick the moment shared by the founding group, or the moment one founder brought to the others. Two competing origin stories told in parallel tend to cancel each other out, because listeners cannot tell which one to repeat.

How often should a founder story be rewritten? Rarely rewritten, regularly reframed. Reviewing it once a year is enough for most companies — the facts stay fixed while the emphasis shifts to match where the business now is.