Why a Script Won't Save You When a Buyer Pushes Back

Objection handling isn't about having the right answer ready. It's about knowing which question to ask first.

When I was early in sales, I thought the answer to objections was better rebuttals.

I kept lists. If they say X, respond with Y. I memorized the responses. I practiced them. And then the buyer said X, I said Y, and they pushed back harder — because I hadn't actually addressed what they meant. I'd addressed what the words on the page meant.

A rebuttal is a defense. The buyer says something, and you counter it. The implicit message in a rebuttal is: you're wrong. Even a polished one. Even a friendly one. And buyers can feel that, even when they can't name it.

What actually works isn't a better script. It's a different model of what an objection is.

What an objection actually is

An objection is not a rejection. It's a question the buyer hasn't found a satisfying answer to yet.

When someone says "that's too expensive," they're not telling you to go away. They're telling you that they haven't yet seen the value clearly enough to justify the cost. That's useful information. It tells you exactly where the conversation needs to go next.

When someone says "I need to think about it," they're usually not lying — they genuinely haven't resolved something. Maybe the value isn't clear. Maybe they need cover from someone above them. Maybe there's a risk they haven't voiced. Any of those is workable. But you can't work on what you don't understand.

This reframe changes everything about how you approach pushback. Instead of defending your position, you're gathering information so you can actually help. That's a different posture — and buyers feel that difference too.

Four frameworks, four situations

There's no single best way to handle an objection. What works depends on the type of resistance. I use four different frameworks, and the choice between them comes down to what the buyer is actually expressing.

LAER — Listen, Acknowledge, Explore, Respond. Use this for direct pushback, especially price objections and mid-deal resistance. The key is the Explore step — asking a question before you respond. "Can I ask what's driving the concern about price?" What comes back tells you what your response actually needs to address. Skip Explore, go straight to your prepared answer, and you're probably answering a different objection than the one they were raising.

Feel-Felt-Found. Use this when the buyer has genuine doubt — they're not sure the product will work for them, or they've been burned before by something similar. "I understand how you feel. Other operations managers I've worked with have felt the same way. What they found, after six months, was..." This framework works because it validates the doubt (they're not wrong to feel it) and offers evidence from peers who had the same doubt and resolved it.

ARC — Acknowledge, Respond, Confirm. Your everyday objection framework. Fast, clean, and includes a step most people skip: confirming that your answer actually landed. "That's a fair concern. [Answer.] Does that address what you were thinking about?" Without Confirm, you're guessing whether your response helped. With it, you know.

The Boomerang. Use this when an objection contains a hidden opening — when the thing the buyer is raising actually points toward the value of your product. "You mentioned our price is 20% higher. Can I ask what that comparison includes? Because our onboarding and migration are built in. When you add those to the competitor's base price, the all-in number is usually comparable or lower." The Boomerang doesn't counter the objection. It reframes the question.

The Explore step is the one you're skipping

Of everything above, the Explore step in LAER is the one I see salespeople skip most consistently — and it's the one that makes the biggest difference.

Here's why it gets skipped: when a buyer raises an objection, the instinct is to respond. You know your product. You've heard this objection before. You have a good answer. So you give the answer.

The problem is that the same words often mean different things. "Too expensive" from a buyer who genuinely can't afford it is different from "too expensive" from a buyer who hasn't yet seen the ROI clearly. "Not the right time" from a buyer with a locked annual budget is different from "not the right time" from a buyer who's just uncertain.

The Explore question — what's behind that? or can you help me understand what's driving that concern? — takes about five seconds to ask. What comes back tells you whether your answer will work, before you give it.

Practicing with AI

The frameworks work. But they only work automatically — under pressure, in a live negotiation — if you've practiced them until the responses are instinctive.

AI makes a useful practice partner. Tell it to act as a skeptical buyer with a specific title and situation, give you a realistic objection, and respond to what you say the way a real buyer would. After three or four exchanges, ask it to score your response on Clarity, Confidence, and Empathy and tell you one thing to do differently.

This is uncomfortable the first few times. Do it anyway. The objection you've handled fifty times in practice is a different conversation than the objection you're handling for the fifth time in real life.

The honest caveat

Frameworks are a structure for thinking, not a substitute for it.

The LAER Explore step works because it gets you to the actual concern behind the objection. But if you ask the Explore question and then don't actually listen to the answer — if you've already decided which response you're going to give — you've just added an extra step to the same rebuttal. The question is only useful if you're willing to change your response based on what you hear.

That sounds obvious. It's harder than it sounds when you're in a live conversation and you're confident you know the answer. The instinct to respond to what you expected rather than what you heard is persistent. The frameworks give you the structure. What you do inside that structure is still judgment, not procedure.