Lenny's Podcast
The non-technical PM’s guide to building with Cursor | Zevi Arnovitz (Meta)
with Zevi Arnovitz
18 Jan 2026
20 min read
1h 2m
TL;DR
Non-technical PMs can now build serious production apps using Cursor and Claude Code by following a structured workflow: create Linear issues, explore the problem space, plan the implementation, execute with multiple AI models, peer review the code, and document everything as a learning opportunity. The key insight is that code is just words—files on your computer—and the right prompts and workflow beat technical knowledge.
Zevi is a Product Manager at Meta with zero technical background who taught himself to build serious, revenue-generating products using AI tools like Cursor and Claude Code. He previously worked as a PM at Wix and has created a systematic workflow that non-technical product managers can use to build apps without writing code. His side project StudyMate, an AI-powered study platform, demonstrates that the tools and processes he's developed actually work for real-world applications.
Takeaways
1
**The /command workflow replaces learning to code** Zevi has systematized the entire product development process into reusable prompts (/create issue, /explore, /create plan, /execute, /review, /peer review, /update docs) that run inside Cursor. Each command primes Claude with the exact context and output format needed for that phase. Non-technical PMs can copy these prompts directly and apply them to their own projects without understanding the underlying code.
2
**Cursor + Claude Code beats no-code platforms for serious apps** Bolt and Lovable excel at rapid prototyping because they aggressively write code, but they fail when implementing complex features like payments or database changes. Cursor gives you architectural control—you can split work between multiple models (Composer for speed, Gemini 3 for UI), review code across models, and maintain full project context as your app scales. The tradeoff is exposure to the code itself, which Zevi frames as healthy 'exposure therapy.'
3
**Planning before coding prevents compounding bugs** The exploration phase—where Claude asks clarifying questions about scope, data models, validation, and grading—prevents the gnarly bugs that come from rushing into implementation. This structured approach to discovery mirrors how experienced technical PMs work, proving that good product thinking matters more than code literacy. Zevi spends significant time in the exploration and planning phases before executing any code.