Everyone’s taking the wrong lesson from this.
Cursor scaled to $29B without traditional PMs because they’re building a developer tool for developers. Ryo can walk through the entire product with engineers because engineers are the customer, the user, and the builder. The feedback loop is immediate and everyone speaks the same language.
That model breaks the second you’re building for non-technical users. Product decisions require understanding customer jobs, translating between technical constraints and user needs, prioritizing across conflicting stakeholder demands, and maintaining strategic coherence as the team grows past 50 people.
Cursor gets away with fuzzy roadmaps and fluid roles because every person in those concentric circles (staff, beta users, early adopters, enterprises) can evaluate a live prototype and tell you exactly what’s wrong. They’re not guessing about user behavior because the users are technical enough to articulate precise feedback.
Most companies don’t have that luxury. Your users can’t code. Your stakeholders don’t understand API latency. Your go-to-market team needs a roadmap that sales can commit to. Your support team needs documentation. Your compliance team needs audit trails.
The Cursor model works when the product is the development environment. For everything else, you need someone translating between what’s technically possible, what’s commercially viable, and what customers actually want. That’s the PM role.
Copying Cursor’s structure without Cursor’s context is how you end up with features nobody asked for and engineers burned out from scope creep.
Cursor scaled to $29B without any full-time PMs.
Ryo (Cursor's Head of Design) walked me through how they work and it's the opposite of every big tech best practice:
1. Roles are muddy
PM work is spread across designers and engineers. Everyone does what fits their strengths and uses AI to fill the gaps.
2. Most designs start with code directly
Ryo barely uses Figma except for initial exploration. Most features start as live Cursor prototypes because "it feels more real than pictures."
3. No annual roadmap theater
Just a "fuzzy direction" and features shipped to concentric circles (e.g., staff, nightly beta users, consumers, enterprises) to polish.
Ryo also showed me exactly how he designs and codes new features using Cursor and how he avoid creating generic purple AI slop.
📌 Subscribe to watch our full tutorial tmr:
youtube.com/@peteryangyt?sub…