Common sales objections and how to handle them

Price objections are about value against the alternative: the buyer does not yet see why yours costs more, or has a cheaper option in hand. Trust objections are about risk: will you deliver, will it work, what happens if it does not — often disguised as price, because “too expensive” is easier to say than “I do not believe you”. Timing objections are about urgency: nothing is wrong with the offer, but nothing is forcing a decision either. Authority objections are about the person: they cannot say yes, and may not want to say so. Need objections are the deepest: the buyer does not feel the problem you solve, or feels it less than you think.

Classifying matters because the answers differ completely. A price answer given to a trust objection makes it worse; a discount offered to a timing objection teaches the buyer to wait.

The first response to any objection is a question, not an answer. “When you say it is expensive — compared with what?” “What would need to be true for you to be comfortable going ahead?” “What is driving the timing?” “Who else would be involved in deciding?” The question does three things: it tells you which of the five you are dealing with, it shows the buyer you are listening rather than reciting, and it often leads the buyer to answer their own objection. Only then answer, briefly, with evidence — a customer in their situation, a number, a process — and check: “does that address it?”

Never argue. An objection defeated in argument is a buyer who goes quiet and buys elsewhere. Agree with what is true in it — “you are right that we are not the cheapest quote” — and move to what matters — “the difference is the rejections you will not have to deal with, and here is what that cost the last customer who switched to us”.

For each of the ten common objections: the diagnosis question to ask first, the approved answer in the words that have worked, the proof point that supports it, and what not to say. Written in the playbook, rehearsed in a monthly half-hour of role-play, and used on calls — not read aloud, but known well enough to say naturally. The approved answers are not scripts; they are the best thing the team has found to say, until someone finds better.

The learning loop: every month, each salesperson brings one objection they handled well and one they lost a deal to, with what they said. The answers are updated, the new objection is added, and the deal reviews in the pipeline meeting record which objection stalled each lost deal. Over a year the list becomes the most valuable page in the playbook.

The mistakes: answering the stated objection without diagnosing the real one; discounting at the first mention of price; arguing; treating “send me something” as a request rather than a polite exit; having no written answers, so each salesperson improvises and the new one folds; and never recording which objection lost the deal. A safeguard: for a month, log every objection heard and how it was handled — the pattern will surprise you.

Measure it through the pipeline: conversion after the quote stage, the share of deals lost to each objection type, and the discount given per deal. When the answers are diagnosed and approved, price objections fall because trust and need were addressed first, and the discount rate falls with them. This is what objection-handling training is, when we run it — the list from your calls, the classification, the diagnosis questions, the approved answers with proof, role-play with your team, and the monthly loop — and the free audit starts by asking your team the last five objections they heard.