Objection Handling Cheat Sheet for New Reps

The 12 objections you'll hear in month one, in the order you're likely to hear them most. For each: what it usually really means, the one-line framework to respond with, and word-for-word language you can use today.

---

1. "Just send me some information."

What it usually means: You haven't earned enough interest yet for them to spend time on a call.

Framework: Agree to send something, but trade it for a question that re-engages them.

Say this: "Happy to — I'll send over something specific rather than a generic deck. Quick question so I send the right thing: what's the main thing you'd want it to address?"

---

2. "We're happy with our current vendor/solution."

What it usually means: They haven't felt enough pain to look for an alternative — or they don't want to admit gaps to a stranger.

Framework: Don't argue against their current vendor. Ask about the edges of "happy."

Say this: "That's good to hear — most people don't switch from something that's working. Out of curiosity, is there anything about it that's a minor annoyance, even if it's not a dealbreaker?"

---

3. "It's not a priority right now."

What it usually means: Either genuinely true, or it's priority-in-theory but nobody's been forced to act yet.

Framework: Find out what would make it a priority, and note the date.

Say this: "Understood — what would need to happen for it to become one? And is there a point on the calendar — end of quarter, a renewal date — where this comes back into view?"

---

4. "I need to check with my manager/team."

What it usually means: Often genuine — but sometimes a polite way to end the call without saying no.

Framework: Support the check-in, but get a specific next step attached to it.

Say this: "Makes sense, that's a good instinct. What information would help you make the case to them? And once you've spoken to them, can we put 15 minutes on the calendar for early next week to hear how it went?"

---

5. "It's too expensive" / "Your price is too high."

What it usually means: The value hasn't been connected to a number yet, or they're comparing to a cheaper, different thing.

Framework: Never argue price. Ask what it's being compared to, and reconnect to impact.

Say this: "Fair to raise — compared to what, specifically? And going back to what you told me about [the impact they named earlier] — how does the cost of that problem compare to the number we're discussing?"

---

6. "We don't have budget."

What it usually means: No budget line exists yet, which is different from "we would never pay for this."

Framework: Separate "no budget line" from "no funds available at all," and find the trigger for a new budget.

Say this: "Is that a case of there's genuinely no funds anywhere, or that there's no budget line for this specific thing yet? If it's the latter, what's the process for creating one when something's worth it?"

---

7. "Call me back next quarter."

What it usually means: A real timing constraint, or a soft no dressed as timing.

Framework: Accept the delay, but lock the follow-up and find out what changes between now and then.

Say this: "Happy to circle back — so I use the time well, what needs to be true by then for this to move forward? I'll put a specific date on the calendar now rather than a vague 'next quarter.'"

---

8. "We tried something like this before and it didn't work."

What it usually means: A real scar. Dismissing it will lose trust instantly.

Framework: Get specific about what went wrong before you say anything about how you're different.

Say this: "That's really useful to know — what specifically didn't work? Was it the tool itself, how it was rolled out, or something else? I want to understand that before I tell you anything about how we're different."

---

9. "I don't have time for a call."

What it usually means: They don't yet believe the call is worth their time — it's a value objection wearing a calendar costume.

Framework: Shrink the ask and name the specific value of the shrunk version.

Say this: "Totally fair — how about 10 minutes, not 30, and I'll come with one specific question about [their situation], not a pitch. If it's not useful after that, you can hang up with zero guilt."

---

10. "Just send me a proposal."

What it usually means: They want to skip discovery — which produces a proposal that misses the mark and dies quietly.

Framework: Agree to send one, but insist on the minimum discovery needed to make it relevant.

Say this: "I can do that — but a generic proposal usually isn't useful to you, and it wastes both our time. Give me 10 minutes first so what I send actually reflects your situation, not a template."

---

11. "We're already talking to a competitor."

What it usually means: Genuine competitive process — don't panic, and don't trash the competitor.

Framework: Get curious about their evaluation criteria, not defensive about the competitor.

Say this: "Good to know — what's most important to you in how you're evaluating options? I'd rather understand your criteria than tell you why we're different in the abstract."

---

12. "I'm not the right person to talk to."

What it usually means: Sometimes genuinely true — but sometimes a way to deflect without doing the work of a warm handoff.

Framework: Get the actual name and ask this person to make the introduction, don't just accept a redirect.

Say this: "Appreciate you saying so — who would be the right person? Would you be open to a quick intro email so I'm not cold-reaching-out to them?"

---

The Underlying Rule Behind All 12

Every objection above follows the same three-step shape:

1. Acknowledge without agreeing or folding ("that's fair," "good to know," "makes sense")
2. Ask one clarifying question before you respond with content
3. Reconnect to their stated impact/timeline, don't argue the objection in isolation

Drill these out loud with a peer or mentor — reading them silently doesn't build the reflex. Say the objection to a partner, then say your response, until it doesn't feel scripted anymore.