1 min lesson
The competitive landscape
Use "A PMM who can't name the field accurately loses credibility in the first minute of a competitive conversation" to describe the practical rule.
Step 1 of 3
This market moves weekly and engineers follow it closely. A PMM who can't name the field accurately loses credibility in the first minute of a competitive conversation.
Know the real set, including the unbranded one. “Just use the chatbot” is a genuine competitor for a lot of casual AI-coding work and pretending the field is only paid IDE rivals makes your positioning naive.
Learn more
Advanced table
Each row credits a real strength first
- Player
- GitHub Copilot
- Where it's strong
- Ubiquitous, deep GitHub/IDE reach, trusted brand
- Cursor's honest line
- Cursor is built editor-first around repo-aware multi-file flows rather than added onto an existing IDE
- Player
- Windsurf
- Where it's strong
- Also an AI-native editor with coding-agent ambitions
- Cursor's honest line
- Direct overlap; differentiate on specifics you can verify, not on slogans
- Player
- JetBrains AI
- Where it's strong
- Native in a beloved IDE family, strong language tooling
- Cursor's honest line
- Cursor's bet is the AI-native editor experience over an AI layer on a classic IDE
- Player
- Claude Code / CLIs
- Where it's strong
- Powerful terminal-native autonomous coding
- Cursor's honest line
- Different surface; Cursor keeps the human in an editor-native review loop with the diff in front of them
- Player
- Raw chatbot
- Where it's strong
- Free, familiar, zero setup
- Cursor's honest line
- No repo context; the developer is the copy-paste middleman every turn
| Player | Where it's strong | Cursor's honest line |
|---|---|---|
| GitHub Copilot | Ubiquitous, deep GitHub/IDE reach, trusted brand | Cursor is built editor-first around repo-aware multi-file flows rather than added onto an existing IDE |
| Windsurf | Also an AI-native editor with coding-agent ambitions | Direct overlap; differentiate on specifics you can verify, not on slogans |
| JetBrains AI | Native in a beloved IDE family, strong language tooling | Cursor's bet is the AI-native editor experience over an AI layer on a classic IDE |
| Claude Code / CLIs | Powerful terminal-native autonomous coding | Different surface; Cursor keeps the human in an editor-native review loop with the diff in front of them |
| Raw chatbot | Free, familiar, zero setup | No repo context; the developer is the copy-paste middleman every turn |
Each row credits a real strength first - that's what earns the right to state the difference.
Differentiate on substance, not on a tagline. The defensible claims are editor-native multi-file workflows, codebase-aware context across files and the feel of speed in everyday edits. Those are things a developer can check in a session, which is exactly why they're worth claiming.
A comparison that admits where a rival wins reads as trustworthy and trust is the scarce currency with engineers. If your battlecard says Cursor wins every row, no technical reader believes any row. Name the two or three places Cursor genuinely leads, name where the alternative is fine and let the honesty carry the parts that matter.
Learn more
Optional practice
Practice: The competitive landscape
QWhy is an honest competitive comparison - one that admits where rivals win - often more effective with developers than a battlecard where Cursor wins every row?