The Timing Paradox

I’ve said for years that a mediocre idea at the perfect time beats a perfect idea at the wrong time. I still believe it. The problem is what it implies: the most important variable in a startup’s outcome is the one the founder controls least, and most of what gets narrated afterward as vision was somebody standing in the right spot when the wave came.

My own companies are the specimen set, which is the only reason I get to write this. Intridea caught the Rails wave within a couple of years of DHH releasing the framework, and the surfing metaphor is doing real work there: we didn’t create the demand, we were paddling in the right place when it rose. Remixd hit audio at the moment publishers were desperate for new revenue and voice platforms were making text-to-audio legible to buyers. VideoByte caught the CTV explosion, and the honest version of that story includes the part where the category was growing so fast that execution mattered less than position. Three companies, three timing stories. The uncomfortable audit is asking how much of each outcome was us and how much was the wave.

Too early is the crueler failure, and it deserves its own section, because the market punishes it identically to being wrong. Being early means paying to educate a market that someone later harvests at a discount. My failed social network in 2003, launched after Myspace and just before Facebook, sits somewhere in the too-early-or-too-weak quadrant, and I still can’t fully separate the two. That’s the point. From inside, “the market isn’t ready” and “the product isn’t good” produce the same signal: silence. Every founder in the silence is running the same test with no control group.

So can timing be read, or only survived? The signals I’ve learned to watch are indirect. Infrastructure maturing faster than attention, which is what made CTV obvious in hindsight and invisible in the moment. Complaints getting louder in an industry that has money, which was publishers before Remixd. Toolchains suddenly collapsing the cost of something, which was Rails then and is AI now. None of it is a formula, and it can’t be: timing readable in advance would be arbitraged away instantly. What remains is judgment under fog, plus the discipline of cheap bets so that being wrong about the clock doesn’t kill you. That’s the real link to how I work now. A portfolio of small products is partly a timing strategy: many clocks instead of one, so no single misread is fatal.

The steelman I owe the vision crowd: some founders demonstrably created their timing rather than caught it. The iPhone didn’t ride a wave, it started one. Maybe the great ones make the market ready. My honest response is that for every market-maker there are a thousand founders who thought they were one, and the base rate should terrify anyone betting on being the exception. I’ve never made a market. I’ve caught three waves and missed at least one, and I’d rather build strategy on the record than the exception.

Which leaves the paradox where I found it, unresolved: timing is everything, and timing can’t be controlled, so founders live on luck they’re required to pretend is skill. Investors demand the pretense, employees need it, sometimes the founder needs it most of all. The only honest posture I’ve found is to hold the conviction and admit the dice, at the same time, all the way through. Most people find that combination unbearable. It might be the actual job description.