I dropped out of a coding class in college.
Not my proudest founder arc.
At the time, coding felt like this giant wall between me and the things I wanted to build.
I had ideas.
I had product instincts.
I could think through users, pain points, GTM, positioning, and workflows.
But when it came to actually building something myself?
I froze.
So I did what a lot of non-technical people do.
I told myself:
“I’m just not technical.”
That sentence is dangerous.
Because it sounds like self-awareness.
But most of the time, it’s just fear wearing a hoodie.
Fast forward to now.
With AI tools, I built a small app in under an hour.
Nothing crazy.
A simple resume vs. job description scoring tool.
But for me, it was a big moment.
Not because the app was perfect.
It wasn’t.
Not because I suddenly became an engineer.
I didn’t.
But because the barrier between idea and prototype collapsed.
That is the part people underestimate about AI.
It doesn’t just make engineers faster.
It makes builders braver.
It lets non-technical PMs move from:
“I have an idea.”
to
“Here’s a working version. Try it.”
That changes everything.
Because in product, the person who can make ideas tangible faster has an unfair advantage.
You don’t need to become a full-stack engineer overnight.
But you do need to become dangerous enough to prototype.
Dangerous enough to test.
Dangerous enough to stop hiding behind docs.
AI won’t replace PMs.
But PMs who can use AI to build, test, and learn faster will absolutely replace PMs who only write requirements and wait.
Lesson learned:
The future PM is not just a strategist.
The future PM is a builder.