Eight MídiaEight MídiaBlog
PT
An Objection Isn't a No. It's a Request for More Information in Disguise

Photo: Radission US / Unsplash

Sales

An Objection Isn't a No. It's a Request for More Information in Disguise

Pedro Toledo · August 1, 2026 · 6 min read

Most salespeople treat an objection as an obstacle to overcome with a stronger argument, when in reality it's a specific request for information the person still needs to decide. How to decode what each common objection is really asking for, why pushing back head-on almost always makes the conversation worse, and the technique of answering a question with a question before arguing.

The most common reaction to an objection is to prepare a stronger counter-argument, as if a sale were a debate to be won. That rarely works, because an objection is almost never a hard wall — it's a request for specific information the person still needs before deciding.

Treating an objection as an obstacle to knock down, instead of a question to answer, is the most common reason a sales conversation cools off right after it appears.

What each common objection is really asking for

"It's expensive" is rarely just about the number. It usually means the perceived value hasn't yet justified that price in the person's mind — the problem isn't the price, it's the connection between price and result that still isn't clear.

"I need to think about it" almost always hides a specific, unspoken doubt. The person hasn't decided they don't want it — they've decided they don't yet have enough confidence to decide now, and "thinking about it" is the polite way of not revealing what that doubt is.

"It's not the right time" can be real, but it can also be a soft way of avoiding saying their priority is elsewhere, or that there's a constraint — budget, internal approval — they don't want to share yet.

Why pushing back directly makes the conversation worse

Responding to an objection with an immediate argument, without first understanding what's behind it, puts salesperson and customer in opposing positions — as if it were a contest over who convinces whom. That triggers a defensive instinct, not openness to reconsider.

The effect is subtle but real: the person feels they need to "win" the conversation by holding their original position, even if the argument presented makes sense, just because giving in quickly feels like losing the point.

Question before argument

A simple technique changes this dynamic: before responding to the objection with an argument, ask a question that helps you understand what's behind it. "When you say it's expensive, expensive compared to what specifically?" opens space for the person to articulate the real doubt, instead of you guessing and answering the wrong thing.

This also takes the conversation out of debate mode and puts it into collaborative mode — the two of you investigating together what the real obstacle is, instead of one trying to convince the other of a position.

How to tell a real objection from a polite excuse

Not every objection hides a solvable doubt — some are real and final, and pushing in those cases just wears down the relationship. A direct way to find out the difference: ask "if we solve that specific point, would you move forward?"

If the answer comes with hesitation, or opens a different objection than the original one, that signals the first objection wasn't the real reason — just the easiest one to put into words. In that case, it's worth digging deeper, or accepting that it might not be the right time, without pushing further than that.

The mistake of having a ready-made answer for every objection

A memorized script for common objections seems efficient, but it tends to sound too automatic to whoever's on the other end — the person feels like they're hearing a rehearsed speech, not a response thought through for their specific situation.

A response that starts by genuinely acknowledging what the person said, before arguing, has a much better chance of being heard than a canned response that ignores that conversation's specific context.

An example of how this changes the outcome

A customer says "let me think about it" at the end of a sales conversation. The automatic response would be to push the product's benefits again, or offer a discount to speed up the decision.

A better response: "That makes sense. Just so I understand better — is there a specific part that's still unclear, or is it more a timing question?" That simple question usually reveals the real objection behind the "let me think about it" — sometimes it's price, sometimes it's insecurity about the result, sometimes it's really just timing. Each of those answers calls for a completely different follow-up, which only becomes clear after asking.

An objection that shows up too early is a sign of something else

If a price objection comes up before you've even explained the full value of what you're offering, that's usually not about price — it's a sign the person hasn't yet understood enough to evaluate whether the price makes sense. Answering a price objection at that point, before finishing the value presentation, tends to reinforce the objection instead of resolving it.

In those cases, it's worth acknowledging the question and asking for space to finish explaining the context before coming back to it: "good question, I'll get to that — let me just finish one point first that will help answer it better."

Recording recurring objections helps improve the offer

If the same objection keeps coming up across different conversations, that's not just an individual conversation problem — it's a signal about the offer or the communication used before the sales conversation even starts. A recurring objection about a specific point can indicate that point should be addressed earlier, in the offer presentation itself, not only when the objection comes up.

Keeping a simple record of which objections come up most often, and reviewing it periodically, turns each individual objection into a source of improvement for the whole offer, not just a one-off situation to work around.

Tone matters as much as the content of the response

Responding to an objection with a defensive tone, even if the content of the response is correct, communicates that you took the objection as a personal attack. A curious, calm tone, genuinely interested in understanding what's behind it, completely changes how the response is received — even when the argument itself is similar.

This is especially important with a repeated objection in the same conversation: if the person insists on the same point after a response, raising your tone or repeating the same argument louder rarely helps. It usually means the previous response didn't address the real concern, and it's worth asking again instead of repeating the same explanation.

The bottom line

An objection isn't the end of the conversation, it's the customer giving you information about what they still need to decide — just rarely in a direct way. Responding with an argument before understanding what's behind it solves the wrong problem most of the time. Asking first costs a few extra seconds and greatly increases the chance of solving the right one.

Frequently Asked Questions