Based on Lenny's Podcast data
The ProofYou Don't Need to Code
to Build With Cursor
"I'm a non-technical PM. I now prototype faster than our engineers. That's not a brag — that's a workflow."
- Cursor + Claude = prototype in hours without touching raw code
- The PM superpower: turn user feedback into working demos same day
- Spec quality determines output quality — this IS a PM skill
- Non-technical doesn't mean non-builder anymore
FrameworkThe Non-Technical Cursor Workflow
- Step 1: Write a detailed spec in plain English — be obsessive about edge cases
- Step 2: Give Cursor the spec + context about your stack + target behavior
- Step 3: Test the output against your spec, not just your eyes
- Step 4: Iterate on the spec when output is wrong — don't just re-prompt
The PM edgeYou know what users need better than any engineer. Now you can test your hypotheses without a sprint.
What Actually WorksCursor for PM Workflows
- Best for: Admin dashboards, data views, internal tools, prototype UI
- Best for: Automated reports, script-based workflows, API integrations
- Hard: Complex state management, performance-critical features, novel architecture
- The rule: If a junior dev could build it in a week, Cursor can build it in an afternoon
The spec discipline
The better your spec, the better the output. Writing specs well is the skill Cursor teaches PMs.
Knowing when to stop
Cursor prototypes are for learning. Know when to hand off to engineers for production.
PlaybookPM in Cursor
- Start with the simplest useful version — one page, one workflow
- Use Cursor to build your own sprint review demos — stop waiting for eng
- Build a "spec library" of successful prompts for common patterns
- Show your output to users, not your engineer — validate the problem, not the code
The permission you haveNo one will give you permission to build. Cursor means you can start without waiting for it.
ContrarianWhat Non-Technical PMs Get Wrong
✗I need to understand the codeINSTEAD →✓ You need to understand the output. Cursor insulates you from the code; you own the behavior.
✗Engineers will judge meINSTEAD →✓ Engineers respect PMs who ship fast. Nobody cares how you built the prototype.
✗This is a crutchINSTEAD →✓ This is leverage. A hammer isn't a crutch for a carpenter.
✗I should learn to code firstINSTEAD →✓ You should learn to spec first. Cursor rewards specification skills, not syntax.