Tweeted this earlier in the week. Technical gap closing fast, idea guys must be hyped.
Three days into being self-employed and I want to push it harder. The gap isn't closing. It's closed.
A solo founder with Claude Code ships what a five-person team shipped two years ago. PRs a day, migrations a day, full features in an afternoon. The part that used to filter out 90% of would-be founders, the part where you actually had to know how to build the thing, that filter is gone. Anyone can ship. Most do.
So what's left as the differentiator.
Marketing. Sales. Picking the right idea in the first place.
Not in the corporate sense of those words. In the founder sense: can you write one paragraph that makes a stranger pay attention. Can you sit across from someone and ask the question that surfaces what they actually buy on. Can you tell, before you build the thing, whether anyone wants it.
Those used to be skills you grew into after shipping product. The order has flipped. Now they're the prerequisite. Building is the easy half. The hard half is figuring out what to build and getting one person to care.
The category of "technical founder who can't sell" used to be viable because the technical work was hard enough to be its own moat. It isn't anymore. The technical founder who can't sell is going to ship beautiful products into a void. The technical founder who can sell, even badly, ships ugly products that get bought.
Idea guys are about to have a moment. Not because ideas were ever the thing, they weren't. Because the work between idea and shipped product collapsed to almost nothing, and so the ratio of "what to build" to "how to build it" tilted heavily toward the first.
If you're a technical person who quit a job this month, the work isn't to ship faster. You already ship faster than anyone needs you to. The work is to read more, to write in public, to talk to ten strangers a week, and to be willing to look stupid in front of an audience while you find the thing.
I tweeted "ideas and products and pinching the technical gap, what are you doing about it." The honest answer is: I'm not pinching the technical gap, the gap pinched itself. What I'm doing is unlearning ten years of treating writing as a thing you do after the code is done.
— Simon