40 at 20 Learn sooner, live lighter.
Failure & Risk Shared by Nathan Realized at 29

The Business That Worked on Paper and Nowhere Else

I had the spreadsheet, the market research, and the investor interest. What I did not have was a real product that real people wanted to use.

Story

What actually happened

I had done everything the startup literature told me to do. I had identified a gap in the market - specifically in B2B document workflow automation for small legal firms in the Pacific Northwest.

I had done customer discovery interviews, or what I thought were customer discovery interviews, with twelve people who had told me the problem I was trying to solve was real. I had built financial models that showed a clear path to profitability.

I had a co-founder with complementary skills, an MVP timeline, and two angel investors who had expressed preliminary interest after seeing the deck. At 26, I quit my job in Seattle and committed fully. The first sign of trouble arrived three months in, during our first real sales cycle.

The problem, which the discovery interviews had failed to surface because I had not asked the right questions, was not that legal firms did not have the workflow problem I had described. They did.

The issue was that the way they had been solving it - however imperfectly - had become so embedded in their operations and their staff habits that switching to a new solution required a change management effort that nobody had the bandwidth for. The value we offered was real.

The switching cost we required was higher than the value justified. We had built the right solution for a problem that was not painful enough to solve. We tried to pivot the product twice over eight months. The first pivot was half-hearted and did not change the fundamental issue.

The second was more significant but required rebuilding enough of the core that we ran out of money before we could complete it. We closed the company after fourteen months, repaid what we could to the investors, and I found a job with a company building enterprise software.

The failure cost me savings, time, and more of my sense of self than I had expected. What it gave me, which took about a year to be able to say honestly, was an education in the specific gap between a real problem and a problem people will actually pay to solve.

These are not the same thing. I ask one question now, before anything else, when I evaluate any product or business idea: not whether the problem is real, but whether the people who have it are in enough pain to change what they are doing to solve it.

That question, which I did not know to ask at 26, is the one everything else depends on.

The lesson

Customer discovery tells you what problems exist. Only sales cycles tell you which ones people will actually pay to fix. Run them earlier than you think you need to.

Actionable takeaway

What to do with this now

A real problem is not enough. The people with the problem must want to solve it badly enough to change. Validate the urgency, not just the existence.
Login to save 82 people resonated