One night I couldn't sleep.
I'd spent years in the internet industry. Photography websites. Personal blogs. E-commerce experiments. Some projects lasted a few months. Some survived a year or two. Most of them failed — and I knew it, because I'd lived through each one.
What kept me awake wasn't the failures themselves. It was something stranger: the realization that none of it had been recorded anywhere. The projects had simply vanished. No post-mortems. No lessons attached to them. Just silence.
I started scrolling through the internet looking for company. What I found instead was a relentless feed of funding announcements, growth milestones, and unicorn valuations. Everyone, apparently, was winning.
I knew that wasn't true. But the evidence for the other reality — the far more common reality — was almost nowhere to be found.
That question stayed with me for a long time. And eventually, it led me to build something.
The Asymmetry Nobody Talks About
Startup failure rates are not a secret. Depending on the study, somewhere between 80 and 90 percent of new ventures don't survive their first five years. Some estimates put the number higher for technology startups specifically.
That means for every company that makes it, roughly nine others don't.
Yet if you spent a week reading startup content online, you would encounter that ratio almost perfectly inverted. Success gets covered, shared, analyzed, and celebrated. Failure quietly disappears — taken offline, stripped from LinkedIn profiles, rarely discussed in any detail.
This isn't surprising. Nobody wants to broadcast a loss, especially when so much personal identity and financial risk is bound up in the outcome. The shame is real. The career consequences can be real. The path of least resistance is to simply move on and not document what happened.
But the cost of that silence is something worth examining.
What Gets Lost in the Gap
When a startup fails and nobody writes down what happened, a specific kind of knowledge disappears with it.
Not the knowledge that failure is possible — everyone knows that in the abstract. What disappears is the granular, specific, embarrassing truth of how it happened. The moment the founder realized the demand signals were false. The week the supply chain collapsed and there was no backup plan. The quarter they kept hiring because the metrics looked right, even though something felt wrong.
That kind of knowledge is genuinely hard to come by. It doesn't appear in business school case studies, which tend to sanitize failure into lesson-shaped narratives. It doesn't appear in post-funding interviews, because those happen when things are going well. It lives in the heads of founders who have moved on, and it mostly dies there.
The result is that each new generation of builders essentially starts from scratch on the question of what failure actually looks like from the inside. The patterns repeat. The warning signs go unrecognized — not because they're subtle, but because no one left a record of having seen them before.
The Pattern Problem
Look at any honest collection of startup post-mortems and the same categories appear with uncomfortable regularity.
Cash flow miscalculations that looked manageable until they weren't. Products built for a market that turned out to be smaller, or less willing to pay, than early signals suggested. Premature scaling — growing the team and infrastructure before the core model was actually proven. Regulatory blind spots that only became visible once it was too late to course-correct.
These aren't exotic failure modes. They're common enough to have names. And yet founders continue to walk into them, in part because the documentation of previous cases is scattered, anonymized out of existence, or buried in places nobody thinks to look.
I had walked into several of these myself. Looking back, I can trace the shape of each failure clearly. At the time, I hadn't recognized what I was looking at — partly because I'd never read an account of someone else recognizing the same thing, in the same kind of situation, at the same stage.
Why Anonymity Changes the Equation
The obvious objection to documenting failure is the one already mentioned: the professional and personal cost of attaching your name to a public account of something that didn't work.
That cost is legitimate. It explains why most founders, given the choice between saying nothing and putting their name on a loss, choose silence. It's not cowardice — it's a rational calculation given how career reputation actually works in most industries.
But anonymity shifts that calculation. When the failure story isn't attached to an identity, the professional risk disappears. What remains is the knowledge itself — the pattern, the timeline, the specific decision that turned out to be wrong and why. Stripped of the identity, that content becomes something closer to a warning sign database than a confession.
The value isn't in knowing who made a particular mistake. The value is in recognizing the mistake's shape early enough to avoid making it yourself.
What an Archive of Failures Could Actually Do
There's a version of this that's purely therapeutic — a place for founders to process difficult experiences and feel less alone. That's not nothing. Building something and watching it fail is genuinely hard, and the isolation of that experience is made worse by an environment that makes success look universal.
But the more durable value is practical. A growing, searchable record of real failure post-mortems — organized by industry, by failure pattern, by stage — gives future founders something they currently don't have: a way to pattern-match against the past before they're inside the problem.
Not a guarantee. Not a formula for avoiding failure, which isn't actually the goal. The goal is earlier recognition. Seeing the shape of what's happening while there's still time to respond to it, rather than after the runway is gone.
That's the difference between a cautionary tale told after the fact and a warning sign identified while it still matters.
The Archive That's Starting to Exist
That sleepless night eventually turned into something concrete. I built Startup Trace — a living archive of real startup failure stories, submitted anonymously by founders who want the experience to be useful to someone else.
It's early. Eighteen stories at the time of writing, across nine industries, with nine documented patterns already visible in the data. Small enough that the patterns are just beginning to emerge. Large enough that the shape of the thing is already recognizable.
The goal isn't to celebrate failure or to suggest that losing is as good as winning. The goal is simpler: to make the knowledge that currently disappears into silence available to the people who might need it before it's too late.
If you want to see what failure actually looks like from the inside — the patterns, the industries, the decisions that seemed right until they didn't — the archive is at trace.flyingfishspace.com.
And if you've built something that didn't work, and you're willing to document what actually happened without your name attached to it — that record could be the thing that helps someone else recognize a warning sign they would otherwise have missed.
The archive is only as useful as the honesty that goes into it.