Objection Handling In Sales: What To Do Instead Of Arguing

Objection handling in sales is usually taught as a set of comebacks. The buyer says it is too expensive, you say let me show you the return. The buyer says send me an email, you say what would make this worth a meeting. The lines are not wrong. They fail because they treat the objection as the problem, when the objection is almost always a summary of something the buyer has not said yet.

Think about what an objection really is. The buyer has a concern they may not have fully worked out, and they compress it into a short sentence that is socially acceptable to say out loud. Too expensive is acceptable. I am not sure this will work for my team, and I will look foolish if it does not, is not. So they give you the acceptable version and you answer the acceptable version, and the real one stays where it is.

I would be careful not to assume every objection hides something. Sometimes the price really is beyond the approved budget. My job is to find out, not to replace the buyer's explanation with a story of my own.

The first thing I would change is your reaction time. When an objection lands, most salespeople respond within a second, because silence feels like weakness. Take the second. Then ask what is behind it. Not defensively, just plainly.

When someone says it is too expensive, ask what they are comparing it with. Sometimes the comparison is a competitor, sometimes it is last year's budget, sometimes it is doing nothing, and each of those needs a completely different conversation.

If a distributor compares your sales software with the spreadsheet they already use, I would not start with a feature comparison. I might say, “What is difficult to manage in the current sheet, if anything?” If the answer is that nothing important is difficult, I have learned something useful. If orders get missed during handovers, I can explore that specific problem before discussing price again.

The second change is to stop trying to win. An objection is not an attack, and treating it as one turns the meeting into a debate where the buyer has to defend a position they may not even hold strongly. If you agree with part of what they said, say so. It is expensive if the team does not use it. That sentence costs you nothing and it moves you to the same side of the table.

I would then ask how the team works today. A regional sales manager may worry that field staff will have to enter the same information on WhatsApp and in a new system. That is a reasonable concern about extra work, not resistance to change. I need to understand what work can stop, and who can approve that change, before saying adoption will be straightforward.

Timing matters more than wording. An objection raised in the first meeting is usually a filter: the buyer wants to know whether to keep spending time on you. An objection raised after the proposal is usually a decision problem: somebody in the room is not convinced, and often it is not the person talking. When a late objection appears, the useful question is who else needs to be comfortable with this, and what would they need to hear.

In an owner-managed business, the person discussing the proposal may still need the owner's approval. In a larger company, finance may be asking about payment terms while operations worries about disruption. I would ask my contact which concern remains unresolved, rather than send another version of the same presentation. I would also ask whether they want help explaining it internally, rather than try to go around them.

There are objections you should not handle at all. If the buyer does not have the problem you solve, or the money, or the authority, the honest response is to say this may not be for you right now and to leave the door open. Indian sales teams are often under pressure to keep every opportunity alive in the pipeline, so nobody wants to be the one who closes a deal out. A pipeline full of opportunities that are being handled rather than progressed is the reason forecasts keep slipping.

I would distinguish a real next step from a polite request to call later. A planned budget review gives us something specific to revisit. Repeatedly hearing “next month” without any change in the situation does not give me a reason to keep forecasting the sale.

Price deserves its own discipline. If you drop the number the moment it is questioned, you have taught the buyer that your first price was not serious, and everything after that is negotiation about how much you were inflating. Hold the price and change the scope instead. A smaller starting engagement at full rate protects the value and still gives the buyer a way in.

I might say, “We can start with one branch rather than all your branches. Would that cover a useful part of the work within your budget?” I would make the exclusions clear, including any training or support that is not included. A smaller engagement only makes sense if it still addresses a real need.

Practice helps, but not the kind where a colleague reads objections off a sheet. Take the last five deals you lost. Write down the exact sentence the buyer used when things turned. Then write down what you now believe they actually meant. That gap is your training material, and it is more accurate than any script.

I would keep those interpretations separate from confirmed facts. Review the call notes with your manager and ask what question might have clarified the concern at the time. The point is to practise listening, not to build a more elaborate comeback.

This week, pick the objection you hear most often and stop answering it. Ask one question about it instead, and write down what you hear. You will find the same objection has three or four different causes, and you have been giving one answer to all of them.