Sales objection handling: method, examples and practice

Not every hesitation is an objection in the useful sense. Three cases to separate before answering:

• A real objection: a specific doubt, often a sign of interest. A buyer who debates price or rollout is already picturing themselves using the product.
• An excuse: a surface reason ("I'm busy", "just send me some info") hiding another cause: lack of interest, lack of trust, a contact without authority.
• A refusal: a decision, explained or not. Pushing then only damages the relationship.

To sort them, the test question works well: "If that point were settled, could you move forward?" A "yes" confirms a real objection, a "yes, but" reveals another one behind it, and silence or a dodge often signals an excuse.

Whatever the framework, the logic is the same: do not fight the objection, understand it and then answer it.

1. Welcome it. Let the buyer finish, do not interrupt, do not contradict. A short sentence is enough: "Thanks for telling me."
2. Understand it. Rephrase, then ask an open question to find the real reason and how much weight it carries.
3. Answer it. Address the specific point you identified, with an example, a proof point or an option, not a general speech.
4. Check and move on. Make sure the answer removed the doubt, then propose a concrete next step.

Order matters: answering before understanding means handling an objection the buyer never actually raised.

Several frameworks exist. None is magic, but knowing them gives a team a shared vocabulary.

CRAC: Creuser, Reformuler, Argumenter, Contrôler

A French-origin method, widespread in French sales training. In English: dig into the objection to understand it, rephrase it to show you heard it, argue on the isolated point, then check the buyer is reassured. The last C is sometimes presented as "Conclure" (conclude).

LAER: Listen, Acknowledge, Explore, Respond

A close English-language framework: listen, acknowledge the concern, explore what drives it, then respond. It is associated with the training firm Carew International, which markets its own version under the name "LAER". It stresses the exploration phase before any answer.

SPIN: a questioning framework, to prevent rather than cure

Drawn from Neil Rackham's research (the book SPIN Selling, 1988), it structures discovery into Situation, Problem, Implication and Need-payoff questions. It does not handle objections as such: by getting the buyer to state the cost of their problem, it can head off several of them upstream, price objections above all.

Listen

Leaving two seconds of silence after the buyer's sentence avoids cutting them off and invites more. Write down their exact words: you will use them to rephrase.

Rephrase

"If I understand correctly, what worries you is the time it takes to set up. Is that right?" Rephrasing defuses tension and fixes a misunderstanding before it becomes an obstacle.

Question

Open questions ("What makes you say that?") reveal the criterion behind the sentence. Impact questions ("What happens if nothing changes?") give weight to the problem.

Prove

An example, a reference, a trial, a third-party opinion: proof reassures more than claims. Only offer evidence you can verify, and never an invented number to win agreement.

These are the most frequent and the worst handled, because the usual answer is a discount before anything has been understood.

"It's too expensive"

• What it hides: perceived value that is too low, or a comparison point you do not know about. Rarely a plain lack of money.
• Sample answer: "I understand, it's an investment. To compare like with like: expensive compared to what?"
• Follow-up question: "If price were not an issue, would the solution meet your need?"

"We don't have the budget"

• What it hides: money not allocated this year, another priority, or value judged too low to defend internally.
• Sample answer: "Thanks for being clear. Is it this year's budget that's the problem, or where this project sits in your priorities?"
• Follow-up question: "Who decides on budgets, and on what criteria?"

"Your competitor is cheaper"

• What it hides: a comparison made on price alone for lack of differentiating criteria, or a negotiation lever.
• Sample answer: "That's possible. On which points do the offers look equivalent to you? I'd rather compare the same scope."
• Follow-up question: "Among your selection criteria, which would cost you the most if they weren't met?"

"Can you do better on price?"

• What it hides: a margin test, or a need to show internally that they negotiated. It is not always a blocker.
• Sample answer: "I can look at what is adjustable if we also adjust the scope, the term or the timeline. What matters most to you?"
• Follow-up question: "If we agree on this point, can you sign off this week?"

"We already have a vendor"

• What it hides: real satisfaction, habit, switching costs or fear of risk.
• Sample answer: "That's a good sign, you've structured this need. I'm not asking you to switch: where are you fully satisfied, and where would you like better?"
• Follow-up question: "What would make you consider a trial on a limited scope?"

Here the main competitor is not a vendor, it is the absence of a decision.

"We've always done it this way" (status quo)

• What it hides: change costs more, in effort and perceived risk, than the problem does. Doing nothing is the most common competitor.
• Sample answer: "That has clearly worked so far. What has changed recently in your volumes, team or customers that could make the status quo more costly?"
• Follow-up question: "If nothing changes over the next year, what happens for you?"

"It's not the right time"

• What it hides: competing priorities, polite disinterest, or sometimes a genuine calendar.
• Sample answer: "I understand. What's keeping your teams busy right now, and when could this become a priority?"
• Follow-up question: "What would need to be settled by then for it to be the right time?"

"Call me back in six months"

• What it hides: a polite brush-off, or a real decision cycle. Without a precise next step, nothing will happen.
• Sample answer: "Happy to. So this call is worth it, what would you like to have seen by then?"
• Follow-up question: "Can I book a fifteen-minute slot for that date right now?"

"Just send me some information"

• What it hides: a common way to cut the conversation short, or a genuine need to forward material internally.
• Sample answer: "Gladly. So I send you something useful rather than a brochure: what do you want to check as you read it?"
• Follow-up question: "I'll send it today. Once you've read it, shall we talk for ten minutes on Thursday or Friday?"

These touch the decision process and perceived risk. Proof and trials weigh more than a pitch here.

"I need to talk to my boss" (absent decision-maker)

• What it hides: your contact may not be the decision-maker, or doubts they can defend the case alone.
• Sample answer: "Of course. What do you think will interest them most in what we've covered? And what questions might they ask?"
• Follow-up question: "Would you like me to join the next conversation to answer directly?"

"I need to think about it"

• What it hides: an unspoken doubt, discomfort, or a genuine need for time.
• Sample answer: "Naturally. So your thinking is useful: is there one specific point holding you back?"
• Follow-up question: "On a scale of one to ten, where are you, and what would move you up one point?"

"I'm not convinced it will work for us"

• What it hides: a need for proof that fits their context, and a fear of being exposed if it fails.
• Sample answer: "You're right to ask, your context is your own. What looks most different from what we described?"
• Follow-up question: "Would a trial on a small scope, with a success criterion we define together, reassure you?"

"We tried this before and it didn't work"

• What it hides: a bad experience, often tied to rollout more than to the solution itself.
• Sample answer: "Thanks for telling me, that's valuable. What exactly happened, and what had you expected?"
• Follow-up question: "What would need to be different this time for you to be willing to try again?"

"I don't have time" (cold call)

• What it hides: an ill-timed interruption, or a refusal at this stage of the conversation.
• Sample answer: "I understand, I'm calling out of the blue. May I tell you in one sentence why I'm calling, and you tell me if it deserves fifteen minutes later?"
• Follow-up question: "What would be the best time this week?"

Reading a sample answer is not enough: in a meeting you have three seconds to react. Practice means living the objection, answering aloud or in writing, then replaying. AI roleplay lets you do that without exposing a real customer, as often as needed. The general principle is explained in our guide to AI sales roleplay.

Personas that push back differently

In AI-Coaching, the counterpart is a configurable persona. For objections, a few useful profiles:

• The rushed buyer: cuts in, wants the essentials in two minutes, answers "just send me something".
• The analytical CFO: asks for numbers, compares costs, challenges the return on investment.
• The skeptical director: has been let down before, asks for proof and a trial.
• The negotiator by principle: asks for a concession on price whatever you offer.
• The wary end user: fears change and extra workload.

A typical session

1. Pick an objection and a persona, based on the ones you really hear; your offer documents can enrich the scenario.
2. Play in text first, then by voice once your answers are settled.
3. Read the detailed report and the observer agent's feedback.
4. Replay with the same persona, then with a firmer variant.
5. Group scenarios into a path or playlist, one per objection, and follow progress in the skills map.

You can try a scenario in the online demo, without an account. For the overall picture, see the AI simulator for sales teams.

After each session, score yourself from 0 (absent), 1 (partial) or 2 (mastered) on each criterion. Have a peer or your manager score the same session, then compare.

Out of sixteen points, a low score points to the basics (listening, rephrasing), a high one to harder scenarios. This grid is a practice tool, not a market standard: adapt the criteria to your sales cycle. To connect this progress to activity indicators, read how to measure the impact of AI coaching on sales KPIs.

• Contradicting head-on ("No, it's not expensive").
• Answering before understanding the real reason.
• Dropping the price at the first sign of resistance.
• Promising what you cannot deliver in order to reassure.
• Reciting a memorized answer regardless of what was just said.
• Moving on to another topic without checking that the doubt is gone.

If you are torn between analyzing real calls and practicing, our comparison of AI roleplay vs conversation intelligence helps you choose.