Why Smart People Keep Getting Stuck at the Same Place

Author's note

I've started asking founders a specific question when I meet them.

Not 'why did you stop?' That question gets rationalisations. 'Where did you stop?' gets coordinates.

The answer, almost every time: three months in. After the demo was ready. When it was time to ship.

What I find interesting is who these founders are.

They're not people who lacked intelligence or drive. I'm talking about product managers who understand software deeply. Former consultants who could outthink most people in any room. Doctors. Architects. Teachers. People who have solved genuinely hard problems for years.

The intelligence is not the variable.

Here's the analogy I keep coming back to.

Imagine you've written a brilliant novel. The prose is clean. The story is tight. You've revised it twelve times. It's ready.

Now someone says: 'Great. Now figure out printing, distribution, bookstore negotiations, rights management, ISBN registration, and international licensing.'

That's The Wall. Most great novelists would also stop there. Not because they're not smart. Because that infrastructure requires a completely different skill set that has nothing to do with writing the novel.

The tools we have today collapsed the time it takes to write the novel from months to hours. What they haven't collapsed yet is the publishing infrastructure. The wall still exists. It just arrives sooner now - because the novel arrives sooner.

There's another layer to this that I want to name.

The advice most founders get when they hit The Wall is: find a technical co-founder.

I want to push back on this. Gently, but seriously.

Finding a quality technical co-founder takes, on average, 12 to 18 months. I'm not citing a study — this is what founders tell me when I ask directly. That's 18 months of pitching your idea to developers who have their own vision, their own equity expectations, their own ideas about what to build.

In that time: your market moves. Your conviction wavers. Someone else ships.

The 'find a co-founder' advice made sense in 2012. The infrastructure wasn't there. It doesn't make as much sense in 2026 — because the infrastructure is getting there, faster than most people realise.

I'm not saying you should build alone forever. I'm saying you should build now, with what exists, rather than wait 18 months for someone who may never arrive.

Build the first version. Get real feedback. Then, if you need a technical partner to scale, you'll be recruiting with evidence instead of asking someone to bet on your conviction alone.

That's a much better conversation to walk into.

Next issue, I want to show you something that challenges another assumption. We spent four weeks building the same app on three different platforms. The results were not what I expected — and some of it is genuinely uncomfortable to report.