How PMs can improve their technical skills with AI and build a real SaaS

A product manager without a technical background at a grooming session—an eternal story of awkward silence and misplaced nods. A guide on Habr offers a concrete recipe: take AI as a tool and build a real SaaS from scratch—not to launch into production, but to understand how a product works from the inside.

Why Exactly SaaS

With 90% probability, a product manager works or will work specifically with SaaS products. Authentication, payment processing, subscriptions, APIs, dashboards, multi-tenancy—here you find almost the entire spectrum of technical tasks you need to understand to work properly with the development team. This is not a textbook model—it's the living architecture of a real product that a PM encounters every day.

The author sets a hard filter from the first paragraph: if you can't set up a VPN or begrudge $20 for tools—this article is not for you. It's not snobbery, but filtering intentions. The guide is designed for those ready to invest time and dig into details, not simply watch AI magic from the sidelines.

Controlled Vibe Coding

Vibe Coding—programming with an AI assistant, where you describe the task in words and the model generates code. The usual approach: write a prompt, get code, run it. This approach is different. The PM doesn't blindly accept the code—they examine every block. The AI works as a mentor: explains architectural decisions, breaks down errors, suggests alternatives. That's exactly what 'controlled' means:

• Asks questions like 'why this way and not another?'—and gets answers at the concept level, not syntax
• Analyzes every dependency the AI adds to the project
• Understands what technical debt arises with each corner-cut
• Feels the difference between 'do it fast' and 'do it right'
• Sees why today's architectural decision affects development speed three months from now

The goal is not to learn to code like a junior—it's to understand how the things you put in the backlog work. Technical empathy starts right here.

Where This Changes PM Work

At grooming—when a developer says 'we need to rewrite the data access layer,' the PM understands why. They don't just nod and add a task without context; they can substantively discuss priority, timelines, and the real cost of delaying that decision.

In planning—'add OAuth2' stops sounding like 'just a button.' The PM sees the integration with an external service, edge case handling, and documentation updates. Developer estimates stop seeming like random numbers and become understandable trade-offs between speed and quality.

In postmortems—instead of silent sitting in a corner, real participation appears. Understanding what broke and at which level makes the incident review meaningful from both sides.

"Technical empathy is not the ability to write code, but the ability

to understand why something costs exactly what it does"—the essence of the approach in one sentence.

What This Means

AI has lowered the barrier to technical literacy so much that a non-coding PM now needs just one real pet project and a language model as a mentor. Controlled Vibe Coding transforms from a hyped trend into a practical tool for those who want to speak the same language as the development team—without a five-year programming course and without impostor syndrome on tech reviews.