The short version
Memorised rebuttals make objection handling sound like a debate the prospect is losing, which breeds resistance instead of resolving it. A better framework has three moves: acknowledge the objection as legitimate (“that’s fair, a lot of teams say that”), clarify what’s actually behind it with one question (is “we have no budget” really about budget, or about not yet seeing enough value?), then respond to the real concern, not the surface one.
“Send me information” is rarely about information. It’s usually a polite no or a stall for internal reasons you haven’t surfaced yet. Handling objections well is 70% diagnosis and 30% response; most reps skip the diagnosis and go straight to rebutting, which is why it feels like arguing.
Mapping surface objections to real concerns
Every surface objection hides one of about five real concerns: budget, timing, authority, trust or the status quo. We have no budget may mean the cost is not justified yet; not now may mean there is no internal owner; send me information often means they cannot say no politely. Build a two-column table and keep it visible during calls.
The clarifying question depends on the column. For timing: What would need to be true for this to become a priority? For authority: Who else would want a say in this? For trust: What would you want to see before taking it further? Each question is open and short, so it gathers information instead of pushing.
Scripts for the five most common stalls
Send me some information: Happy to. So I send the right thing, what would you be hoping it answers? Their reply tells you if there is genuine interest. We’re happy with our provider: Good, then I won’t suggest replacing it. If one thing could be better, what would it be? Call me next quarter: Sure; what happens in the business between now and then that would change things?
Too expensive: Compared with what? Often they are comparing with doing nothing, which is a different conversation. We’ve tried this before: What happened last time? Then stay quiet and listen. In each case, acknowledge first with a short, sincere phrase, because a clarifying question without acknowledgement sounds like cross-examination.
Training the skill with call data
Tag objections in your CRM with a picklist, and review monthly. If 40 percent of lost conversations end at we’re happy with our provider, the issue sits earlier in the call: the problem was never established. Objection handling is often a symptom of weak discovery, so fix the upstream question before adding more rebuttals.
Practise with role-play in 15-minute blocks, twice a week. The person playing the prospect should use real phrases from recorded calls, not textbook ones. Swap roles so the rep learns what a clarifying question feels like from the receiving side; the ones that sound defensive become obvious immediately.
Worked example (illustrative)
Hypothetical: a team of four logs 200 objections over a month, then adopts the acknowledge, clarify, respond sequence and a shared table of real concerns for the next month.
What changed: The change came from asking before answering. More calls continued past the first objection because reps understood the concern, not because they had better rebuttals.
Do it: the steps
Tick them off as you go. Your progress stays on this device.
Traps to avoid
- ×
Using the same clarifying question every time. It turns into a script the prospect recognises within two calls.
- ×
Treating every no as an objection. A clear, reasoned no from a prospect outside your target segment deserves a polite close and a note in the CRM, not a third attempt.
- ×
Answering with a case study immediately. Evidence works only after you know which concern it addresses; otherwise it sounds like deflection.
What to track
- Objection-to-continuation rate
- calls that go on after the first objection divided by calls with an objection; track monthly.
- Objection mix
- share of each objection type in the CRM picklist; a shift shows where discovery needs work.
- Next-step rate
- calls ending with an agreed next step divided by conversations; common range 15% to 30%.
Benchmarks are typical planning ranges, not guarantees. Calibrate to your own data.
Questions people ask
How many clarifying questions are too many?
One per objection is usually enough, and two is the limit before it feels like an interrogation. If you need more, you probably asked a closed or leading question the first time. Follow the answer with a summary sentence, such as, So the real issue is timing with the audit, to show you listened before you respond.
Should I ever argue with an objection?
Rarely. If a prospect states a factual error about your product, correct it gently and briefly. If it is an opinion or a preference, acknowledge it and explore the reason. Winning the argument usually loses the conversation, so measure yourself by whether the call continues and the next step is agreed.