Building

Building a product is not a technical problem. It is a decision problem — and the hardest decisions are not about architecture or stack. They are about what to cut, what to delay, when to stop, and whether the thing you are building is worth building at all.

The Solo Founder Problem

Building without a co-founder is not lonely in the way people think. The loneliness is not social. It is epistemic. There is nobody to push back on your reasoning, nobody who has committed their own time and reputation to the same bet. Every decision you make passes through one filter, and that filter is you — which means your blind spots are always unchecked.

The essays in this chapter examine what that actually costs. Not in the abstract sense of “it’s hard,” but in concrete decisions: the product bets that made sense in your head and failed on contact with users, the months spent optimizing the wrong thing because there was nobody to say “why are we doing this?”, the funding conversations you lost because you couldn’t explain the business model to someone who wasn’t already living inside your assumptions.

What Building a SaaS Actually Teaches You

Nobody tells you that building a SaaS product is mostly a lesson in what you do not know yet. The technology part is tractable. The user behavior part is not. The economics part looks tractable until it isn’t. And the gap between “this works” and “this is a business” is wider than most first-time founders expect.

The stories here are not success narratives. They are reconstructions — attempts to understand, after the fact, what was actually happening during the years of building. What the data was telling us that we weren’t reading. What users were saying that we weren’t hearing. What decisions made sense given the information we had, and which of those decisions were wrong anyway.

On Shipping and Deciding

The bottleneck in most building projects is not engineering. It is deciding. What to build next, what to abandon, which user complaint to take seriously and which to deprioritize. These decisions compound — good ones open up options, bad ones close them down — and the compounding is invisible until you are far enough into the consequences to see the pattern.

These essays try to make that pattern visible earlier.