Handling Sales Objections by Showing, Not Telling

Many reps were taught to handle objections with a quick, confident rebuttal. The buyer says "It is too expensive," and the rep replies with a speech about return on investment. The buyer says "We are worried about adoption," and the rep lists the training resources. It feels like progress. Usually it is not.

When a buyer raises an objection, they are taking a small risk. They are saying, in effect, "Here is something that worries me." An instant rebuttal tells them their worry was not heard, only countered. Most people respond to that by defending their position, or by going quiet and deciding privately that the deal is not for them.

Call data points the same way. Gong's 2025 analysis of 326,000 recorded sales calls found that lost deals often featured long seller monologues, and that sellers talked more in lost deals than in won ones. An objection is exactly the moment when reps are most tempted to give a long answer, and exactly the moment when listening matters most.

This article sets out a different approach in three steps: acknowledge, understand, then show.

Chris Voss, a former FBI hostage negotiator, describes in Never Split the Difference, written with Tahl Raz and published in 2016, a set of skills he calls tactical empathy: understanding the other side's feelings and perspective and saying that understanding out loud. Empathy here does not mean agreeing. It means showing that you understand.

One of the simplest of these skills is the label. The Black Swan Group, Voss's company, describes labeling as making a verbal observation of the emotions and circumstances implied by the other person, usually starting with phrases such as "It seems like", "It sounds like" or "It looks like". These phrases make the observation easy to correct if you got it wrong.

In a sales call, labels might sound like this:

• "It sounds like you have been burned by a rollout like this before."
• "It seems like the price is not the only thing bothering you."
• "It looks like the timing is difficult with everything else your team has going on."

After the label, stop talking. Voss's company calls this dynamic silence. Most buyers will fill the silence with the real story behind the objection, which is far more useful than anything you could have said.

Why might this work? A 2007 study published in Psychological Science by Matthew Lieberman and colleagues at UCLA found that putting feelings into words, which they called affect labeling, reduced the response of the amygdala and other emotion-related brain regions to negative emotional images. It is a laboratory study of images, not sales calls, so treat it as a plausible explanation rather than proof. But anyone who has calmed down after a colleague said "That sounds frustrating" will recognize the effect.

Voss also describes what he calls an accusation audit: listing the negative things the other side may be thinking about you, and saying them out loud before they do. It sounds risky. In practice, it often takes the sting out of objections, because the buyer no longer needs to raise them.

In sales, you usually know the common objections before the call. Use that. For example, at the start of a pricing conversation:

• "You are probably thinking this costs more than the tool you have now."
• "You might be wondering whether your team will actually use it, given how the last rollout went."
• "It may feel like we are asking for a big commitment for a product you have only seen in a demo."

Then pause. Often the buyer will say "Yes, exactly" and explain which concern matters most. Sometimes they will say "Actually, price is fine; the real issue is IT." Either way, you now know where to focus.

The first version of an objection is rarely the full story. "It is too expensive" can mean many different things: the budget is already spent, the buyer does not see enough value yet, a competitor quoted less, or the buyer simply needs a better story for their boss. Each needs a different answer.

Questions that start with "what" or "how" are usually best here. The Black Swan Group calls them calibrated questions: open questions that cannot be answered with a simple yes or no, and that ask the other person to think through the problem.

• "What would need to be true for this price to make sense?"
• "How are you comparing it? What are you measuring it against?"
• "What would your finance lead need to see to approve it?"
• "What happened last time that makes you worried about adoption?"

Another useful tool is the mirror: repeating the last one to three words the buyer said, with a questioning tone. Buyer: "We have tried this kind of tool before and it did not stick." Rep: "It did not stick?" Then wait. The buyer will usually explain exactly what went wrong.

Finish this step with a summary in the buyer's words. Voss suggests aiming for the response "That's right", which signals that the buyer feels understood. "So the price itself is acceptable, but you need to show finance that the team will actually use it, because the last tool was abandoned after three months. Is that right?"

Once you know the real concern, answer it. Where possible, answer it by showing something rather than by making another claim. Claims are cheap; buyers have heard "It is easy to use" from every vendor. Evidence on screen is much harder to dismiss.

Here is how that works for common SaaS objections:

• "It looks complicated." Do the task they are worried about, live, with their own example. Count the clicks out loud. Better still, let them do it themselves in a trial account while you watch.
• "Our team will not adopt it." Show what a new user sees on day one, and how a manager sees who is actually using it. If you have anonymized adoption data from similar customers, show that.
• "It will not work with our systems." Open the integration settings and connect a test account, or show the documentation for their exact system. If it does not integrate, say so.
• "It is too expensive." Build a simple cost model with their numbers on screen, and let them change the inputs. Peter Cohan's advice in Great Demo! to "do the last thing first" applies here too: start with the answer, then show how you got there.
• "We need to think about it." Ask what specifically they need to think about, then put that list on screen and work through it together.

Showing also makes it obvious when you cannot address a concern. That is a good thing. If your product genuinely cannot do something the buyer needs, it is better for both of you to find out now.

Price is the objection reps fear most, and the one most often handled badly. Two mistakes are common: discounting immediately, and defending the price with a long speech about value.

Daniel Kahneman, summarizing decades of research in Thinking, Fast and Slow, explains that losses loom larger than equivalent gains. For a buyer, the price is a certain loss, while the benefits are uncertain gains in the future. That imbalance is why price feels heavier than it should, and why vague promises about value rarely shift it.

So make the benefits more certain and the loss feel smaller:

• Use the buyer's own numbers. A saving they calculated themselves is much more believable than one you claim.
• Show the cost of not acting, if it is real: the hours spent on the current process, the cost of the problem you discussed in discovery.
• Reduce the risk instead of the price: a smaller starting package, a short pilot with clear success criteria, or monthly terms at first.
• If you do discount, trade it for something, such as a longer term, a faster decision or a case study, so it does not look like the price was never real.

Matthew Dixon and Ted McKenna's research on indecision suggests that the third point often matters most: many buyers who say "too expensive" are really saying "too risky". See losing deals to no decision.

Some of the hardest objections arrive second-hand. "Our IT team is worried about security." "My boss thinks it is too expensive." You cannot label the feelings of someone who is not there, and your champion may not fully understand the concern.

Ask your champion to describe the concern in as much detail as they can, then offer to address it directly: "Would it help if I spent 20 minutes with your IT lead? I can walk through exactly how sign-in and data storage work, and answer their questions on the spot." Meeting the person with the objection is almost always better than sending a document through your champion.

If a direct meeting is not possible, give your champion something they can show, not just repeat: a one-page summary, a short recorded walkthrough, or the exact page of the documentation. The buying committee article covers equipping your champion in more detail.

Here is a condensed example from a SaaS call. The buyer is a support manager evaluating a new help-desk tool.

• Buyer: "Honestly, I am not sure we can justify the cost right now."
• Rep (label): "It sounds like there is a lot of pressure on the budget this year." (Pause.)
• Buyer: "There is. And the last tool we bought, nobody used. My director still reminds me about it."
• Rep (mirror): "Nobody used it?"
• Buyer: "The agents found it slower than email, so they went back to their inboxes."
• Rep (calibrated question): "What would you need to see to be confident this time would be different?"
• Buyer: "That the agents would actually prefer it. And something I could show my director."
• Rep (summary): "So the real question is not just the price. It is whether your agents will use it, and having proof for your director. Is that right?"
• Buyer: "That's right."
• Rep (show): "Could we try something? Pick a real email from this morning, and let us handle it in both tools while I time it. Then let us talk about a two-week pilot with three of your agents, with a usage report you can take to your director."

Notice that the rep never argued about price. They found the real concern, which was adoption and credibility with a director, and addressed it with evidence and a lower-risk way to start.

Not every objection should be overcome. Sometimes the buyer is right: the product does not fit their process, the price is genuinely too high for the value they would get, or the timing really is wrong.

In those cases, the most useful thing you can do is say so. "From what you have told me, I do not think we are the right fit for this, because [reason]. If that changes, I would be glad to talk again." It is uncomfortable, but it saves both sides time, and it often earns a level of trust that leads to referrals or a deal later.

Being honest about a poor fit also makes your other answers more believable. A buyer who has seen you admit a limitation is more likely to believe you when you say something will work.

These skills feel awkward at first. Labels can sound scripted, and silence feels uncomfortable. A few ways to practise:

• Collect your team's ten most common objections and write the real concerns that usually sit behind each one.
• For each, write two labels, two calibrated questions and one thing you could show on screen.
• Role-play with a colleague, with the "buyer" scoring whether they felt heard before they heard an answer.
• Listen to recordings of your own calls and count how many seconds pass between an objection and your first rebuttal. Try to make it longer.

The goal is not to win the argument. It is to understand what is really worrying the buyer and help them resolve it, even when the honest answer is that your product is not the right fit. For more on structuring the demo that comes before this, see demos without the product tour.