Objection handling techniques: 9 methods with examples

You ask what exactly is meant before you answer. Many objections are one word for several possible concerns: “too expensive” can mean the budget, a comparison with another offer, or value that isn’t clear yet.

• “Too expensive compared to what?”
• “What exactly do you mean by [word from the objection]?”
• “What makes you say that?”

When it fits: Almost always as the first step, especially with short, vague objections.

How it fails: Three questions back in a row feel like an interrogation. Ask once, then listen and take notes.

You put the objection into your own words, as a question. It shows that you listened, and it often turns a rejection into a question that can be answered.

• “If I understand you correctly, it’s less about the price and more about whether it pays off within [time frame]?”
• “So you want to be sure that [concern] doesn’t happen. Have I got that right?”

When it fits: When the objection sounds sweeping (“That doesn’t fit”) or you’re not sure what is meant.

How it fails: Putting words in the other person’s mouth. Ask rather than assert, and accept a correction.

You check whether this objection is the only one: if the point were solved, would anything else stand in the way?

• “Suppose we find a solution for [point]: would anything else speak against it?”
• “Is [point] the only thing holding you back, or is there something else?”

When it fits: When you suspect an excuse, or sense that a second objection sits behind the one they named.

How it fails: Phrased as a trap (“So you’ll sign today?”), it sounds like pressure. The point is to understand, not to pin someone down.

You raise an objection before the other person voices it. A point you name openly yourself looks less like an obstacle and more like something you have thought about.

• “You’re probably wondering what your works council will say. One sentence on that.”
• “This is where a lot of people ask about the price. I’ll give it to you in a moment; first, one question about [topic].”

When it fits: For objections that come up in almost every conversation, such as price, effort or data protection.

How it fails: Raising a worry the other person didn’t have. Only pre-empt what demonstrably comes up regularly.

You acknowledge the objection and answer it at the point where the answer makes sense, usually after discovery.

• “Good question. I’ll come back to it once we’ve talked about [topic]; then I can answer it properly. Is that all right?”

When it fits: When the price question comes before it is clear what is needed, or when a detail question would derail the call.

How it fails: Not coming back to it. Note the objection and pick it up explicitly later: “You asked earlier about [point].”

You agree with the other person first and then add your view. The classic “Yes, but …” takes the agreement back with the “but”. An “and”, or a question after the agreement, comes across as more honest.

• Instead of “Yes, that’s a lot of money, but …”: “It’s an amount worth checking. That’s why it pays to look at what [problem] costs you today.”
• “I understand, this year’s budget is committed. What would the project have to deliver to get a place in next year’s budget?”

When it fits: When the objection has a true core you don’t want to dispute.

How it fails: The reflexive “Yes, but”. What people hear is “You’re wrong”, which is exactly what you didn’t want to say.

You confirm a drawback openly and set against it an advantage that counts for this particular customer. Which one that is, you know from discovery.

• “That’s true, [drawback]. On the other hand, [advantage that ties in with what you said earlier]. Which weighs more for you?”

When it fits: When the objection is justified and can’t be removed, such as a higher price or a missing feature.

How it fails: An advantage that ties in with nothing they said, or a comparison with a competitor you can’t back up.

You show that the objection is a reason for the conversation, not against it.

• To “We don’t have time”: “Precisely because your team is short on time, [task that costs time today] is worth a look.”
• To “We’re too small for this”: “That’s exactly why [specific reason it fits small teams].”

When it fits: Only when the connection is genuinely true and you can explain it in one sentence.

How it fails: It quickly comes across as quick-witted rather than understanding. Without a real connection it is a trick, and that is how it lands.

You tell how a comparable customer dealt with the same concern. An experience from practice often convinces more than an argument.

• “A customer in [industry] had the same question. What helped there was [specifically what].”
• “If you like, I’ll ask [customer] whether you could speak to someone there briefly.”

When it fits: When there are doubts about whether something works in practice, such as effort, rollout or acceptance in the team.

How it fails: Invented or embellished examples. Only real references, and names only with the customer’s permission.