The Unsexy Middle of Building Something

Every founding story, told after the fact, compresses into two exciting moments: the spark of the idea, and the eventual proof that it worked. What almost never gets told honestly, because it makes for a worse story, is the enormous stretch of time in between, where you are doing real, difficult work with no external confirmation that any of it matters. I've spent time in that middle stretch, both building things of my own and advising founders building theirs, and I think it deserves a more honest accounting than it usually gets.

The beginning of anything new has a kind of borrowed energy to it. People are curious. The idea is still theoretical, which means it's still perfect — untested by contact with reality, so it hasn't yet had the chance to disappoint anyone, including you. That energy is real, but it's also, by nature, temporary. It runs on novelty, and novelty has a short half-life. The hard part starts precisely when that energy runs out and the actual, repetitive, often boring work of building something durable has to continue without it.

I remember advising someone through exactly this stretch — the product was live, the initial curiosity had faded, growth had flattened into something that looked less like a trajectory and more like noise around a flat line, and nothing about the day-to-day work had visibly changed except that the emotional reward for doing it had mostly disappeared. That is, in my experience, the actual test of whether someone can build something real. Not the idea stage, where almost everyone looks capable, but this stretch, where the only fuel available is a decision to keep going that you have to remake, quietly, most days, without much external evidence that it's the right call.

What I've noticed separates the people who make it through that stretch from the people who don't isn't raw talent or even resilience in the abstract sense — it's something closer to a specific kind of patience with ambiguity. The middle of building something doesn't offer clean signals. Is slow growth evidence the idea is wrong, or evidence that this particular kind of growth is naturally slow and compounds later? Is the customer who churned a sign of a real problem, or noise you'd see in any small sample? In the beginning and at the eventual proof point, the signal is loud. In the middle, it is quiet and easy to misread in either direction — false despair or false confidence, both equally common, both equally dangerous.

I think the honest answer is that nobody, including the founder, can fully distinguish "this isn't working" from "this is working but slower than expected" from inside the middle. You're making a judgment call under real uncertainty, and I've watched good people make that call wrong in both directions — quitting something that would have worked, and persisting stubbornly on something that genuinely wouldn't have, no matter how much longer they'd pushed. What helps, as much as anything can, is having a small number of trusted people outside the day-to-day intensity of it who can ask you the harder version of the question you're avoiding asking yourself.

The other thing I wish someone had told me plainly, rather than letting me absorb it the hard way, is that the middle is not a phase you pass through once and are done with. Even after something is working, there is another middle waiting on the other side of the next ambitious thing you try to build within it. The relief of finally having proof doesn't remove the necessity of the unglamorous, uncertain work — it just resets the clock on it. I don't think that's discouraging, once you actually expect it. It's discouraging only if you were, like I once was, expecting the middle to be a temporary inconvenience on the way to some permanent, comfortable plateau where the hard, uncertain part is finally over for good.

If there's a piece of this worth carrying forward, it's simply to expect the middle honestly, rather than being blindsided by it the way most first-time founders are, myself included. The idea stage will feel good. The proof, if it comes, will feel good. Nearly everything in between will feel like work with no clear reward attached, done anyway, on the strength of a judgment call you can't fully verify yet. That's not a flaw in the process. As far as I can tell, that's just what the process actually is.