Objection Handling
Definition
The skill and content used to address concerns a prospect raises during the sales cycle — price, security, integration, vendor risk, switching cost — without weakening the seller's position. The best objection handlers reframe the objection rather than fight it.
Three kinds, and only one is an objection
- A blocker. Something that genuinely disqualifies you if unresolved. Rare, and usually stated plainly.
- A negotiating position. Raised to create room, often on price or terms, sometimes dressed as technical.
- Scar tissue. A previous vendor did this badly and the buyer is checking whether you will too. This is the most common and the most misread — it wants reassurance and evidence, not a rebuttal.
Why rebutting well is the wrong goal
A confident counter to scar tissue reads as dismissal, and the objection goes underground rather than away — it reappears in a room you are not in. The useful first move is almost always to establish which of the three you are hearing, which usually takes one question rather than an answer.
The half that compounds
Record what was raised, what was said, and whether it worked — against a deal that later won or lost. One objection is an anecdote; the same objection across a sector is a product signal, a battlecard line, and a trap question. Almost every team handles objections well in the room and loses the record within a week.
The technical variant
In a technical evaluation the objection is often raised to a colleague rather than to you, in a review you are not part of. Which is why what your champion can say without you present matters more than how well you answer live.
Related terms
Further reading
See how this works on a real deal
WinIQ turns RFPs, competitor data and account research into deal-specific output your SEs can defend.
Request a Demo