FlyingFish Space

One night I couldn't sleep.

I'd spent years building internet products — photography sites, e-commerce experiments, personal tools. Most of them failed. What kept me awake wasn't the failure itself. It was the realization that none of it had been recorded anywhere. The projects just vanished. No post-mortems. No lessons. Just silence.

So I went looking for other people's stories. 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. Somewhere between 80–90% of startups don't survive their first five years. But the evidence for that reality was almost nowhere to be found.

The reason isn't hard to understand. Nobody wants to attach their name to a public account of something that didn't work. The professional risk is real. The shame is real. The path of least resistance is to move on and say nothing.

But the cost of that silence compounds. Each new generation of builders starts from scratch on the question of what failure actually looks like from the inside. The same patterns repeat — cash flow miscalculations, premature scaling, false demand signals — not because they're subtle, but because nobody left a record of having seen them before.

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.

That's what eventually led me to build [Startup Trace](https://trace.flyingfishspace.com/) — an anonymous archive of real startup failure post-mortems. The anonymity is the point: when the story isn't attached to an identity, the professional risk disappears and what remains is the knowledge itself. The pattern. The timeline. The specific decision that turned out to be wrong, and why.

It's early. 18 stories so far, across 9 industries, with 9 failure 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. It's earlier recognition — seeing the shape of what's happening while there's still time to respond, rather than after the runway is gone.

---

Two questions for this community:

1. Have you ever wished you could read an honest, detailed account of a failure in your specific industry or stage — and couldn't find one?

2. If you've been through a startup failure yourself, what made you decide to document it publicly — or not?

The archive is only as useful as the honesty that goes into it. If you've built something that didn't work and you're willing to document what actually happened without your name attached, I'd genuinely love to hear from you.