The Mock Cold Call
Open, discover, handle objections, ask for the meeting - live
Anatomy of a cold call
After this you can break a call into its phases and know your goal in each.
A cold call is not one conversation. It is five short ones stacked back to back and most reps lose at the seam between them - they earn permission and then immediately pitch or they run good discovery and then forget to ask for anything.
In the Cursor mock, a manager or AE plays a skeptical engineering buyer who has likely already heard of the product. The interviewer is watching whether you can move cleanly through the phases under pressure, not whether you have a flashy pitch. Know the goal of each phase cold and the call stops feeling like improv.
- 1Opener / permission. Ten to fifteen seconds. Earn the right to keep talking by being honest it's a cold call and naming a researched reason. Goal: get a "go on," not a hang-up.
- 2Hook / value. One or two sentences. State the specific reason you called this person at this company. Goal: make staying on the line feel worth it.
- 3Discovery. The bulk of the call. Ask open questions about how their team builds and where the friction is. Goal: surface a real problem worth an AE's time.
- 4Objection handling. Whenever resistance shows up. Acknowledge it, ask one question, advance. Goal: keep the conversation alive without arguing.
- 5Meeting ask. The close. Propose a specific time for a specific reason. Goal: a calendar invite, nothing more.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Each phase has one goal; the meeting ask is the gate that turns the whole call into a booked meeting.
You are not on this call to sell Cursor. You are on it to earn a 30-minute meeting with an AE. That single reframe fixes most cold-call mistakes: you stop over-explaining the product, you stop fearing silence and you stop trying to close a deal a Sales Development Representative was never meant to close. Pitch the meeting, not the product.
Talk-time disciplinethe 80/20 rule
The biggest tell of a green rep is talking too much. Aim to let the prospect talk roughly 80% of the call. Your 20% is sharp questions and brief, concrete value. When you finish a question, stop talking and let the silence do its work.
- Phase
- Opener
- Who talks more
- You (briefly)
- Your job
- Be honest, be quick, get a yes to continue
- Phase
- Hook
- Who talks more
- You (briefly)
- Your job
- Land one specific, researched reason
- Phase
- Discovery
- Who talks more
- Them, heavily
- Your job
- Ask, then shut up and listen for the trigger
- Phase
- Objections
- Who talks more
- Them, then you
- Your job
- Acknowledge first, never rebut first
- Phase
- Meeting ask
- Who talks more
- You
- Your job
- Name a real time and a real reason to take it
| Phase | Who talks more | Your job |
|---|---|---|
| Opener | You (briefly) | Be honest, be quick, get a yes to continue |
| Hook | You (briefly) | Land one specific, researched reason |
| Discovery | Them, heavily | Ask, then shut up and listen for the trigger |
| Objections | Them, then you | Acknowledge first, never rebut first |
| Meeting ask | You | Name a real time and a real reason to take it |
Across a 5-minute call, your voice should be the minority for everything except the open, hook and close.
Tone carries the call
Engineers read pacing and tone as a signal of whether you know what you're talking about. A rushed, sing-song script reads as a vendor reading off a card. Calm, curious and unhurried reads as a peer. Slow down by about 20% from your nervous default and you'll already sound more credible.
A generic "Hi, this is Alex from Cursor, how are you today?" opener tells the buyer you could be calling anyone. Have a one-line reason for calling that only makes sense for this person - their team's recent growth, an observed tooling choice or the fact that engineers there already use Cursor. Specificity is the whole game in the first ten seconds.
Takeaway. A cold call is five phases - opener, hook, discovery, objections, ask - and the only goal across all of them is a booked meeting. Let the prospect talk ~80%, keep your tone calm and lead with a reason that only fits this person.
Self-check
QRoughly what share of a good discovery-heavy cold call should the prospect be talking?
The opener that earns the next 30 seconds
After this you can deliver a permission-based opener that survives an engineer's skepticism.
The first ten seconds decide the call. The buyer has already half-decided to hang up and your opener either confirms that instinct or interrupts it.
Two opener styles dominate SDR training. Fake-rapport openers ("How's your day going?") trigger the sales-call reflex immediately. Permission-based openers lower defenses by handing the prospect a little control. With a skeptical engineer, the permission opener wins almost every time.
"Hey Priya, this is a cold call - can I have 27 seconds to tell you why I called and you can decide if it's worth continuing?"
Honest, low-pressure and gives the buyer a sense of control. Engineers respect that you didn't pretend to know them.
"Hi Priya! How are you doing today? Great! So I wanted to reach out because..."
Reads as a script instantly. The forced warmth raises the buyer's guard before you've said anything real.
The pattern interrupt: just be honestdirectness as a tactic
The strongest pattern interrupt with engineers is candor. Naming that it's a cold call - out loud, with a slight smile in your voice - disarms the very objection they were forming. They were about to say "is this a sales call?" and you've already answered it. Directness reads as confidence and confidence buys you the next 30 seconds.
"Hey Marcus - I'll be honest, this is a cold call. I saw your team posted four backend roles last month and I work at Cursor. Can I take 30 seconds on why that made me pick up the phone and then you tell me if it's worth more?"
Lead with a researched reason
The line after the permission ask is your hook and it has to be specific to this person. Generic value props die here. A real observed detail - hiring, a migration, a conference talk or the fact that their devs already use Cursor - proves you did homework and earns the conversation.
- Team growth: "You've opened a bunch of eng roles" implies onboarding pain Cursor can speak to.
- Observed tooling or stack: a public job post, GitHub activity or a tech-stack signal you can reference honestly.
- Existing bottom-up usage: "A few of your engineers are already on Cursor" - a strong, true, Cursor-specific hook.
- A trigger event: a funding round, a new VP Eng or a stated push on AI tooling.
"Revolutionary," "transformative," "state-of-the-art," "synergy" - to a technical buyer these are noise and they flag you as someone who doesn't understand the product. Cursor sells to skeptical engineers who can smell marketing language in one syllable. Describe what the tool does in plain, concrete terms and let the specifics carry the weight.
Have your first ten seconds memorized to the point of muscle memory, so nerves don't leak through in the mock. When the interviewer picks up as a cold, slightly annoyed buyer, your automatic, calm opener is itself a graded signal. Practice it out loud until you can deliver it while distracted - that's the bar for sounding natural under pressure.
Takeaway. Open with a permission-based ask, name that it's a cold call and follow with one researched reason that only fits this person. Cut every hype word and drill the first ten seconds until they're automatic.
Self-check
Discovery that respects a technical buyer
After this you can ask questions that surface a real workflow problem worth a meeting.
Discovery is where the call is won. The rep who pitches features loses the engineer; the rep who gets genuinely curious about how the team ships code earns a meeting.
At Cursor the motion is usually bottom-up, so the buyer often already uses the product. That changes your discovery. You're not asking "do you use AI tools?" - you're asking what happens when good organic adoption meets the realities a leader cares about: standardization, security, admin and billing.
This is the defining feature of selling Cursor outbound. The person on the line may have used the product for six months and have opinions you don't. Pretending to be the expert is fatal. Your edge is honesty and the org-level view they don't have: who else on their team is on it, what standardizing would enable and what an AE can do that a personal Pro plan can't.
Open questions about workflow, not featuresdiscovery toolkit
Ask how the team works today and let them narrate. Feature interrogations ("do you use autocomplete?") get yes/no answers and teach you nothing. Workflow questions surface the friction that justifies an AE conversation.
- Ask this
- How does your team handle onboarding a new engineer today?
- What it surfaces
- Ramp time and codebase-context pain - exactly what Cursor's Agent shortens.
- Ask this
- Who on the team is already using Cursor and who isn't?
- What it surfaces
- The standardization gap: organic love on some teams, none on others.
- Ask this
- How do you think about AI coding tools at the team level versus individuals expensing their own?
- What it surfaces
- The shift from scattered personal plans to a managed, admin-controlled rollout.
- Ask this
- When a dev adopts a new tool, who has to sign off on security and data handling?
- What it surfaces
- The blocker that turns bottom-up usage into a real buying conversation.
| Ask this | What it surfaces |
|---|---|
| How does your team handle onboarding a new engineer today? | Ramp time and codebase-context pain - exactly what Cursor's Agent shortens. |
| Who on the team is already using Cursor and who isn't? | The standardization gap: organic love on some teams, none on others. |
| How do you think about AI coding tools at the team level versus individuals expensing their own? | The shift from scattered personal plans to a managed, admin-controlled rollout. |
| When a dev adopts a new tool, who has to sign off on security and data handling? | The blocker that turns bottom-up usage into a real buying conversation. |
Each question moves from a comfortable yes/no toward a problem only an AE conversation resolves.
Listen for the trigger
Not every account is ready now. Your job in discovery is to hear the trigger that makes an AE conversation timely and to be honest when there isn't one.
A hiring wave makes onboarding and ramp time a live, expensive problem.
Big codebase changes are where AI tooling pays off and budget gets approved.
Leadership pushing "use AI" turns scattered usage into a standardization project.
Quantify lightly, don't force ROI
As a Sales Development Representative you're qualifying, not building the business case - that's the AE's job. So quantify just enough to confirm the problem is real. Get a rough number on time lost or onboarding pain, then hand the deeper sizing to the meeting.
A technical buyer will reject an invented ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. faster than no ROI at all. If they say onboarding takes "a few weeks," don't immediately claim Cursor halves it. Note the pain, agree it's worth a closer look and let the AE run the real analysis. Light quantification builds credibility; manufactured numbers destroy it.
Takeaway. Discovery beats pitching - ask how the team builds, accept that they may know Cursor already and hunt for the standardization, security or admin gap a personal plan can't solve. Listen for a trigger, quantify lightly and never fake the ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in..
Self-check
QWhich is the strongest discovery question on a cold call to an engineering leader?
Objection handling under pressure
After this you can apply a repeatable framework to the objections engineers actually raise.
Objections are not the call going wrong. They're the call getting real - and how you handle one is the single most-graded moment in the mock.
Under pressure, untrained reps either freeze or argue. A simple framework gives you a default move so you never wing it. The most durable one is Acknowledge–Ask–Advance: validate what they said, ask one question to understand or reframe, then advance toward the meeting.
- 1Acknowledge. Genuinely. "That's fair" or "Totally hear you" - show you listened before you respond. This alone defuses most heat.
- 2Ask. One curious question that opens the objection back up. "What are you using today?" or "What would have to be true for it to be worth a look?"
- 3Advance. Move toward the next step, not a rebuttal. "Sounds like it's worth 20 minutes with someone who can go deeper - does Thursday work?"
The instinct is to defend the product the second you hear an objection. Resist it. Acknowledging first signals you're listening, not selling and a technical buyer notices the difference instantly. Curiosity and calm beat a clever rebuttal every time, because you can't argue someone into a meeting - you can only make the meeting feel low-risk and worth their time.
Prep the objections engineers actually raisethe common five
- Objection
- "We already use Copilot / Windsurf."
- Acknowledge + Ask + Advance
- "Makes sense, a lot of teams start there. What's working and what isn't? Most folks who switch tell us it's about the agent and codebase context - worth a side-by-side with our AE?"
- Objection
- "Engineers won't switch tools."
- Acknowledge + Ask + Advance
- "Fair - forced rollouts fail. A lot of your devs may already be on Cursor on their own. Want to see what standardizing the ones who chose it looks like?"
- Objection
- "We don't have budget."
- Acknowledge + Ask + Advance
- "Understood, no ask for budget today. The meeting's just to see if there's a real fit - if there isn't, you've lost 20 minutes. When's good?"
- Objection
- "Just send me an email."
- Acknowledge + Ask + Advance
- "Happy to. So I send something useful and not generic - what's the one thing that'd make this worth your time? I'll put it in the email and grab 15 minutes to walk through it."
- Objection
- "We built our own internal tool."
- Acknowledge + Ask + Advance
- "Impressive - that's a real investment. What's it good at and where does maintaining it cost you? That's usually the conversation worth having with our AE."
| Objection | Acknowledge + Ask + Advance |
|---|---|
| "We already use Copilot / Windsurf." | "Makes sense, a lot of teams start there. What's working and what isn't? Most folks who switch tell us it's about the agent and codebase context - worth a side-by-side with our AE?" |
| "Engineers won't switch tools." | "Fair - forced rollouts fail. A lot of your devs may already be on Cursor on their own. Want to see what standardizing the ones who chose it looks like?" |
| "We don't have budget." | "Understood, no ask for budget today. The meeting's just to see if there's a real fit - if there isn't, you've lost 20 minutes. When's good?" |
| "Just send me an email." | "Happy to. So I send something useful and not generic - what's the one thing that'd make this worth your time? I'll put it in the email and grab 15 minutes to walk through it." |
| "We built our own internal tool." | "Impressive - that's a real investment. What's it good at and where does maintaining it cost you? That's usually the conversation worth having with our AE." |
Notice every response acknowledges first, asks one real question, then advances - without ever calling the buyer wrong.
"Send me an email" is a soft no
It feels polite, so reps accept it and lose the deal. Treat it as a brush-off you can convert. Acknowledge, ask one qualifying question to learn what they'd actually value, then advance to a specific time - with the email as the bridge, not the destination.
"For sure, I'll send something over. Quick thing so it's not the usual generic deck - is the bigger question for you the agent's code quality or the security and admin side of rolling it out to the team? I'll tailor the email to that and hold 15 minutes Thursday in case it's worth going deeper."
Know real differentiators
A tooling objection is a discovery opening if you know what's actually different. You don't need a competitive teardown - you need one or two honest, specific contrasts so "we use Copilot" becomes a question instead of a wall.
Bashing Copilot or Windsurf reads as insecure and disrespects a buyer who chose it deliberately. Acknowledge that the incumbent works, get curious about the gap and let a concrete difference do the persuading. Engineers trust the rep who says "that's a solid tool" far more than the one who calls it garbage.
Takeaway. Run every objection through Acknowledge–Ask–Advance so you never wing it - acknowledge first, never rebut first and treat "send me an email" as a soft no you convert into a specific time. Know one honest differentiator so a tooling objection becomes a discovery opening.
Self-check
QThe buyer says "Just send me an email." What's the best move?
The meeting ask and clean handoff
After this you can close the call for a specific next step and brief the AE well.
Reps run a great call and then fumble the close with "so, would you maybe want to find some time sometime?" The ask should be the most confident sentence on the call.
Vague asks get vague answers. Assume-the-meeting language - proposing a specific day and time as if the meeting is a given - converts far better than asking whether they'd like to meet. You're not being pushy; you're making it easy to say yes.
"Would you maybe want to set up some time next week to chat more?"
Open-ended, low-conviction, easy to defer forever.
"I'd love to get you 20 minutes with our AE who works with teams like yours. Does Thursday at 2 or is Friday morning better?"
Names the time, the length and a real reason - and offers a simple either/or.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
The specific ask wins on every dimension the close is graded on.
Make the meeting valuable to themearn the calendar slot
Don't sell "a meeting." Sell what they get from it. Name the specific thing the AE conversation will answer, tied to the pain you just uncovered in discovery.
- "You'll see exactly how the agent handles a codebase your size, with someone who can answer the security questions."
- "We'll map what standardizing the engineers already on Cursor would actually cost and enable."
- "You'll get a straight answer on whether this beats what you've built internally - and if it doesn't, we'll tell you."
Confirm the right attendees
A meeting with only your champion can stall the moment it needs a budget decision. Without being heavy-handed, try to get a decision-influencer in the room - a lead, an EM or whoever signs off on tooling and security.
"Since rolling this out usually touches security and budget, would it make sense to pull in whoever owns those calls? That way you don't have to relay everything secondhand and we can get you real answers in one session."
Capture notes the AE can actually use
The qualified handoff is the real unit of your job. An AE who walks into a meeting blind because your notes were thin will stop trusting your pipeline. Capture the four things that let them prep in two minutes.
- Trigger
- Why now - the hiring wave, migration or AI mandate that made this timely
- Pain
- The workflow problem you surfaced, with any rough numbers they gave
- Stakeholders
- Who you spoke to, who has budget, who can block on security
- Current tooling
- What they use now (Copilot, internal tool, existing Cursor usage) and the gap
Trigger, pain, stakeholders, tooling - four lines that turn a calendar invite into a meeting an AE can win.
Define what makes a meeting "qualified"
A booked meeting and a qualified meeting are not the same thing. A qualified meeting has a real problem, a relevant stakeholder and a reason to talk now. Showing in the interview that you know this distinction signals you'll generate pipeline an AE actually wants.
When the mock ends, the interviewer may ask "would you forecast that as a qualified meeting?" Have an answer. Say what made it qualified - the trigger, the pain, the stakeholder - or be honest that you booked it but it's thin and you'd flag that to the AE. Truth-seeking on your own pipeline is a Cursor value and naming a weak meeting honestly scores higher than pretending every booking is gold.
Takeaway. Close with a specific time and a reason the prospect cares about, get a decision-influencer in the room and hand the AE a four-line brief: trigger, pain, stakeholders, current tooling. A booked meeting isn't the unit of work - a qualified one is.
Self-check
QWhich meeting ask is most likely to convert at the end of a cold call?
How the mock is scored - and how to self-assess
After this you can perform to the scorecard and debrief like a top rep.
The mock cold call isn't graded on vibes. There's a scorecard and knowing its categories lets you perform to them instead of hoping you came across well.
Most SDR mock scorecards grade the call in the same buckets the call itself has phases. Map your prep to these categories and you stop leaving easy points on the table.
- Scored category
- Opener
- What they're watching for
- Confident, permission-based, honest it's a cold call, with a specific reason
- Scored category
- Discovery
- What they're watching for
- Open questions, ~80% prospect talk-time, listening for the trigger
- Scored category
- Objection handling
- What they're watching for
- Acknowledge first, calm under pressure, advance without arguing
- Scored category
- Close
- What they're watching for
- Specific time, assume-the-meeting language, clear value to the buyer
- Scored category
- Composure & coachability
- What they're watching for
- Staying calm with a hostile buyer and applying mid-call feedback fast
| Scored category | What they're watching for |
|---|---|
| Opener | Confident, permission-based, honest it's a cold call, with a specific reason |
| Discovery | Open questions, ~80% prospect talk-time, listening for the trigger |
| Objection handling | Acknowledge first, calm under pressure, advance without arguing |
| Close | Specific time, assume-the-meeting language, clear value to the buyer |
| Composure & coachability | Staying calm with a hostile buyer and applying mid-call feedback fast |
Four phase-based categories plus a behavioral one - composure and coachability are graded whether or not they're on the sheet.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Perform to the heaviest signals first - composure and objection handling carry the call.
The interviewer will likely play hostile on purpose - curt, dismissive, maybe a little rude. They want to see the job under pressure, because rejection is the daily reality of the role. Staying calm, curious and unbothered when the buyer is cold is a graded outcome on its own. Reacting with frustration or going quiet tells them how you'll handle a Tuesday of no-pickups.
Take mid-call feedback and apply it instantlycoachability live
Sometimes the interviewer breaks character mid-mock: "try opening differently" or "you're talking too much." This is not you failing. It's the highest-value moment in the loop, because coachability is one of the things they screen hardest for. Adjust visibly and immediately.
"Got it - that's good feedback, let me try that again." Then actually change the behavior on the spot. Naming the adjustment out loud and executing it is worth more than a flawless first attempt.
Self-assess before they ask
The strongest move after the mock is to debrief yourself first. Volunteering an honest self-assessment shows the truth-seeking and self-awareness Cursor screens for and it beats waiting to be critiqued.
- 1One thing you did well. Be specific: "I think my permission opener landed and I let you talk through the workflow."
- 2One thing you'd change. Own a real gap: "I jumped to the ask a beat early - I'd have asked one more discovery question first."
- 3What you'd do next. Show iteration: "Next rep I'd tighten the hook so it's one sentence, not two."
Honest self-critique reads as senior. Saying "I rushed the close" before the interviewer points it out demonstrates the exact intellectual honesty Cursor values and it reframes a flaw as evidence you'll coach yourself rep over rep. Don't oversell what went well or pretend the call was perfect - name one genuine strength and one genuine fix.
Practice reps beat the cram session
Cold calling is a motor skill. You can't read your way to a natural opener - you have to say it out loud enough times that nerves stop touching it. Short, frequent reps build the consistency the scorecard rewards.
- Record yourself running a full 3-minute mock, then listen back for talk-time and filler words.
- Drill the first ten seconds daily until they're automatic under distraction.
- Run live reps with a friend playing a hostile engineer and have them throw the five common objections.
- Five short reps across a week beat one long cram the night before - consistency wins.
Can you deliver your opener calmly while someone interrupts you? Do you have an Acknowledge–Ask–Advance response ready for all five common objections? Is your close a specific time, not a vague maybe? Can you name one strength and one fix without being prompted? If yes to all four, you're ready to perform to the scorecard.
Takeaway. The mock grades opener, discovery, objections and close as separate buckets, plus composure and coachability throughout. Stay calm with a hostile buyer, apply mid-call feedback instantly, self-assess honestly before they ask and build it with short daily reps - not one cram.