For ten years, "non-technical founder" was a polite way of saying dependent.
You had ideas. Someone else had the keys to the kingdom. You waited, negotiated equity, wrote specs that got half-understood, and shipped things that looked nothing like what lived in your head.
That era is over.
Taste is the new moat
When anyone can generate a React component in thirty seconds, the bottleneck stops being "who can build it" and becomes "who knows what's worth building." That's a taste problem. A systems-thinking problem. A customer-empathy problem.
Those are exactly the muscles a good PM has been training for years without realising they were training for this moment.
What I actually do now
I think in flows. I sketch in Figma. I write specs in plain English. Claude turns them into code. I read the code, push back where it feels wrong, and ship.
The work isn't coding. The work is having a clear opinion about what the thing should feel like — and being able to hold that opinion steady through every step of implementation.
The catch
You still have to understand enough to smell when something is off. A URL in a query string. A database without indexes. A component re-rendering on every keystroke. You don't need to write the fix — you need to notice it exists.
That's not technical debt. That's technical literacy. And it's cheap to acquire if you're paying attention.
What this means
If you've been sitting on an idea waiting for a co-founder, stop. The co-founder is already in your laptop. Your job is to bring the taste.