Section 1
Dig before you draft
Give yourself an afternoon and collect the evidence. The first thing you ever sold and what you charged for it. The email or message where someone first asked you to solve the problem, and their exact words. The first version that did not work, and what specifically broke. The first customer who left, and their stated reason. Whatever you were doing for money at the time, and how much of your week it consumed. Those five artefacts contain your origin story. What they will not contain is a moment of clarity, because there almost never is one. What there usually is instead is a pattern you noticed because of where you were standing: a job that gave you an unusual view of a broken process, a market you belonged to, a constraint you had lived with long enough to know which parts of it were fake. That standpoint is the thing worth telling, and [Why Storytelling Is a Critical Leadership Skill for Founders](/blog/why-storytelling-is-a-critical-leadership-skill-for-founders) explains why it belongs in the founder's hands rather than an agency's.
Section 2
Origin story and founding insight are not the same thing
Separate two claims that founders routinely fuse. The origin story is why you started: circumstance, motive, timing. The founding insight is what you understood that the incumbents did not, and why they could not act on it even if they had. Investors and senior hires are buying the second. Customers mostly care about the second as well, though they will listen politely to the first. The origin story earns its place only where it is the evidence for the insight, which happens when your position gave you access to information other people did not have. If your story is charming but does not explain how you knew something, keep it for the offsite and lead with the insight.
Section 3
Mapping what you found
The table below sorts each artefact you collected into what it proves: motive, insight, credibility or nothing. The last column matters most. Material that proves nothing is not necessarily false, it is simply not load-bearing, and it belongs in an interview rather than on a homepage.
Section 4
Writing the version that holds up
Write two paragraphs and stop. The first paragraph puts you somewhere specific with a date and a problem that was not yours to solve. The second names what you saw that made the standard answer look wrong, and what you did about it in the following ninety days. No epiphany, no destiny, no adjectives about passion. Then pressure-test it. Read it to somebody who was there. If they correct a detail, correct it, because they will not be the last person who was there. Read it to somebody who was not there and ask what they now expect the company to be good at. If their answer is not the thing you are good at, the story is pointing in the wrong direction, however true it is. A visual version of the same exercise is laid out in [Story Mapping: Visualizing Your Company's Narrative](/blog/story-mapping-visualizing-your-company-s-narrative).
Section 5
The retrofit problem
The dominant failure mode is retrofitted destiny. Once a company is working, every earlier decision starts to look like foresight, and the story quietly upgrades luck into judgement. It is a comfortable edit and an expensive one, because the team then treats your instincts as a method they cannot reproduce. The second failure is borrowed shape. Garage, rejection, breakthrough. That arc is so familiar it now reads as a genre rather than a history, and a reader who recognises the genre discounts the content. The third is the story that stops. An origin story with no continuing line into what the company is doing this year is nostalgia, and buyers do not underwrite nostalgia. Keep the through line running to the present, and cut the parts that no longer explain anything. Be precise about what you actually built while you are at it, since [Robotic Process Automation (RPA) vs AI Automation: What's the Difference?](/blog/robotic-process-automation-rpa-vs-ai-automation-whats-the-difference) covers categories founders routinely blur when retelling the early years.