1 min lesson
The Cursor buying committee
Show why this lesson detail matters: "An enterprise Cursor deal is won or lost across roughly six stakeholder groups and the wedge is unusual."
Step 1 of 3
An enterprise Cursor deal is won or lost across roughly six stakeholder groups and the wedge is unusual: the developers already love the product. Your job is to convert that grassroots love into a governed contract while clearing the people whose job is to say no.
Each group cares about something different and the language that wins one can spook another. Promise a CTO “developer velocity” and you're credible; lead with “velocity” to Security and you sound like you're skipping their review. Know what each person buys before you walk in.
Learn more
Full explanation
Who Can Stall the Deal
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Ranked by how hard each group can gate the contract - only developers start on your side.
Notice that only one of those six is rooting for you by default. The economic buyer can be sold, but Security, Legal and Procurement are paid to find reasons to slow down. Multi-threading is not a nicety here; it is the mechanism that keeps a deal alive when any single contact goes quiet or leaves.
Learn more
Advanced table
Six groups, six different purchases. Speak to the one in front of you
- Stakeholder
- Developer / power user
- What they buy
- A tool that keeps them in flow
- The question they ask you
- “Will this still feel like my Cursor?”
- Stakeholder
- Platform / DevEx
- What they buy
- A standardized, manageable rollout
- The question they ask you
- “How do we provision, govern and offboard seats?”
- Stakeholder
- VP Eng / CTO
- What they buy
- Org-wide productivity and AI strategy
- The question they ask you
- “What does this do to throughput and retention?”
- Stakeholder
- Security / IT
- What they buy
- Defensible risk posture
- The question they ask you
- “Is our proprietary code ever exposed or trained on?”
- Stakeholder
- Procurement
- What they buy
- The best commercial terms
- The question they ask you
- “Why this price and what's the multi-year look like?”
- Stakeholder
- Legal
- What they buy
- Acceptable contract risk
- The question they ask you
- “What's the IP indemnity and data-processing language?”
| Stakeholder | What they buy | The question they ask you |
|---|---|---|
| Developer / power user | A tool that keeps them in flow | “Will this still feel like my Cursor?” |
| Platform / DevEx | A standardized, manageable rollout | “How do we provision, govern and offboard seats?” |
| VP Eng / CTO | Org-wide productivity and AI strategy | “What does this do to throughput and retention?” |
| Security / IT | Defensible risk posture | “Is our proprietary code ever exposed or trained on?” |
| Procurement | The best commercial terms | “Why this price and what's the multi-year look like?” |
| Legal | Acceptable contract risk | “What's the IP indemnity and data-processing language?” |
Six groups, six different purchases. Speak to the one in front of you.
Single-threaded deals through one happy champion are the classic enterprise death. If your only relationship is the lead developer who loves Cursor, the deal dies the moment Security raises a code-privacy flag or your champion changes teams. Map all six groups early and name the gaps out loud.
In the mock discovery or panel, proactively map the committee without being asked. “The developers are my entry point, but I'd want to identify the DevEx owner for rollout, the security reviewer early and the VP Eng who owns the budget - and I'd ask my champion who else has to bless this.” That shows you sell the org, not a single contact.
Learn more
Optional practice
Practice: The Cursor buying committee
QYour strongest relationship is the lead developer who adores Cursor. Why is that not enough to win the enterprise deal and what would you do?