1 min lesson
Mock 2 - the live cold call
Put this idea into your own words: "Your edge is composure and talk-time discipline."
Step 1 of 4
This is the job, live, under pressure. The mock cold call is the stage where most candidates either pitch over the buyer or fold at the first "we already use Copilot." Your edge is composure and talk-time discipline.
Have your partner play a skeptical engineer who may already know Cursor better than you do. One take, no restart. Your job is a permission-based opener, real discovery, calm objection handling and a specific meeting ask - while the buyer talks roughly 80% of the time.
Learn more
Full explanation
The Cold Call, Move by Move
Interactive diagram. Step through it with the Next and Previous controls below, or Tab to a region to read its detail.
The meeting ask is the gate - everything before it exists to earn the right to ask.
Learn more
Advanced table
The hard objections your partner must throw
The hard objections your partner must throw
- Objection
- "We already use Copilot."
- Weak response
- "Cursor is way better than Copilot."
- Acknowledge–Ask–Advance
- "Makes sense - a lot of teams start there. What's the one thing you wish it did that it doesn't? That gap is usually why folks take a look."
- Objection
- "We're not switching tools."
- Weak response
- "You really should, it's worth it."
- Acknowledge–Ask–Advance
- "Totally fair, switching is a pain. Most teams don't switch - they try it on one repo first. Curious what would even make a new editor worth the friction for you?"
- Objection
- "Just send me an email."
- Weak response
- "Sure, what's your email?"
- Acknowledge–Ask–Advance
- "Happy to - so I send something actually useful and not noise, what's the workflow that eats the most time right now? I'll point the email at that."
- Objection
- "No budget for this."
- Weak response
- "It's not that expensive."
- Acknowledge–Ask–Advance
- "Got it, budget's tight everywhere. A lot of teams start free, bottom-up - if a few engineers loved it, who'd even be in the room for a budget conversation later?"
| Objection | Weak response | Acknowledge–Ask–Advance |
|---|---|---|
| "We already use Copilot." | "Cursor is way better than Copilot." | "Makes sense - a lot of teams start there. What's the one thing you wish it did that it doesn't? That gap is usually why folks take a look." |
| "We're not switching tools." | "You really should, it's worth it." | "Totally fair, switching is a pain. Most teams don't switch - they try it on one repo first. Curious what would even make a new editor worth the friction for you?" |
| "Just send me an email." | "Sure, what's your email?" | "Happy to - so I send something actually useful and not noise, what's the workflow that eats the most time right now? I'll point the email at that." |
| "No budget for this." | "It's not that expensive." | "Got it, budget's tight everywhere. A lot of teams start free, bottom-up - if a few engineers loved it, who'd even be in the room for a budget conversation later?" |
The pattern: validate, ask a question that re-opens, then advance - never defend.
Mid-call, ask your partner for one piece of feedback and apply it on the spot - "too much talking? let me hand it back to you" - then visibly change behavior. Coachability is a stated thing Cursor wants and showing you can take a note in real time beats running a clean call that never adjusts.
The fastest way to fail the call is to win the argument. If an engineer says Copilot is fine, do not correct them - an engineer may know Cursor better than you do and arguing torches credibility. Your honest edge is curiosity about their workflow, not a feature-by-feature takedown.
Before you debrief with your partner, write down one strength and one fix from your own read. Truth-seeking is a Cursor value and an honest self-assessment of a call you just ran is exactly the muscle the values round will test later. Then compare your read to your partner's - the gap between them is your blind spot.
Learn more
Optional practice
Practice: Mock 2 - the live cold call
QThe engineer says, "We already use Copilot and it's fine." Which response best fits a skeptical-engineer cold call?