The Question You Should Ask Before You Answer Any Objection

There's a specific half-second in every sales call where deals are quietly won or lost. It's the instant right after a prospect pushes back — "this is more than we wanted to spend," "we're happy with what we've got," "let's circle back next quarter" — and before you say anything in return.

What you do with that half-second tells you almost everything about how the rest of the call will go.

Most of us were trained to fill it fast. We treat the pushback as a hurdle and reach for the cleared-it-already answer. But the rep who fills that silence with a rehearsed rebuttal and the rep who fills it with a real question are playing two different games — and only one of them is still learning anything about the deal.

An objection is a sentence the prospect hasn't finished

Here's the reframe that changed how I sell: a pushback is almost never the complete thought. It's the visible top of something larger the prospect hasn't said out loud — sometimes because they can't quite articulate it yet, sometimes because they're testing whether it's safe to.

"It's too expensive" might mean I don't trust the return. It might mean I can't sell this to my boss. It might mean your competitor quoted lower and I want to see how you react. Four prospects can say the identical five words and mean four unrelated things.

So when you answer the words instead of the meaning, you're guessing. And when you guess, you're usually defending against a concern the person doesn't even have — which makes you look like you weren't listening, because you weren't.

The whole skill of objection handling is resisting the urge to answer a question you haven't actually heard yet.

The trade at the heart of it

Getting good at this comes down to a single trade: give up the need to be right, and you get the chance to be useful.

When you feel the pull to defend — that little spike of I need to fix this now — treat it as a signal, not an instruction. It's the moment to slow down, not speed up. Instead of supplying an answer, hand the conversation back with a question that helps the prospect say the part they left out.

That's it. There's no clever script underneath it. The move is simply: when you most want to talk, ask instead.

It feels counterintuitive because it feels like losing ground. It isn't. A defended objection ends the topic. An explored one opens it.

What curiosity actually sounds like

Principles are easy to nod along to and hard to do live, so here's what the trade looks like against the three pushbacks you'll hear most.

"It's too expensive."

The reflex is to justify the price. Don't — you don't yet know which kind of expensive they mean. Separate the two:

"When you say it's a lot — is it more than the budget you had set aside, or more than you expected something like this to cost?"

Those are completely different problems. The first is a procurement conversation; the second is a value conversation, and you can't have the right one until you know which you're in. From there, it helps to surface what the status quo already costs them — the hours, the missed conversations, the deals that slip — because most expensive problems are the ones nobody's put a number on yet. Price only looks high next to nothing. Next to the bill they're already paying, it usually looks different.

"We need to think it over."

This isn't a no, but it isn't a yes, and the worst thing you can do is accept it at face value and schedule a polite follow-up into the void. The goal is to find the specific thing that's unfinished:

"Makes sense — if you imagine the version of this where you'd feel good saying yes, what's true in it that isn't true right now?"

That question is hard to answer vaguely. It tends to pull out the real blocker — a missing stakeholder, an unconvinced CFO, one feature they're unsure about — which is the only thing you can actually help with. "Think it over" you can't work with. "I'm not sure my ops lead will go for it" you can.

"Now's not the right time."

Timing is the most courteous way to pass, which is exactly why it's worth gently testing. The question is whether "later" is a real plan or a soft exit:

"Totally fair. Is it a bandwidth thing right now, or is the problem just not loud enough yet to jump the queue?"

If it's bandwidth, you've got a real follow-up with a real trigger. If the problem isn't loud enough, then timing was never the issue — urgency was — and that's a conversation you can have today instead of pretending September will fix it. Either way you leave the call knowing something true instead of something polite.

Notice none of these are comebacks. They're all ways of asking tell me the part you didn't say.

Curiosity is a skill, which means it doesn't scale by itself

Here's the catch that most advice skips right over.

It's one thing for a calm, experienced rep to pull this off on a good Tuesday. It's another for it to happen reliably across a whole floor — the new hire three weeks in, the rep mid-slump after a string of rejections, anyone caught flat-footed by an objection they've genuinely never fielded before. Under pressure, people don't rise to their good intentions; they fall back to their defaults. And the default is to defend.

So the question isn't really "should reps be more curious?" Everyone agrees they should. The question is what catches them in that half-second and points them at the better move before the old reflex fires. Good intentions don't survive a tense call. Something in front of you does.

That something is a battle card.

Battle cards, done the way that actually works

The version of a battle card that fails is the one shaped like a closing argument — a paragraph you read aloud to win the point. It fails because it puts you right back into defend mode, just with better vocabulary.

A battle card that works is shaped like a detective's notes, not a lawyer's. It points you toward the question, not the verdict. The useful ones carry three things and nothing else:

• The tell — the phrasings that signal which objection is really in play, so you stop guessing.
• The opener — the one or two questions that get the prospect to finish the sentence.
• The follow-through — the response you've seen land, kept in your back pocket for after you understand what you're actually dealing with.

A few habits keep a card library alive instead of abandoned:

• One card, one objection. A card that hedges across three situations is useless in all three.
• Pull them from real recordings. Your best questions and responses already happened on real calls. Don't invent them — harvest them.
• Make them glanceable. If it can't be absorbed at a glance, it won't get used at a glance, which is the only kind of use a live call allows.
• Treat them as living documents. Competitors move, pricing shifts, new objections surface. Revisit them or they rot.

The part that's easy to get wrong

Even a perfect card has one failure mode left, and it's the one that sinks most battle-card projects: a card you can't reach in the moment may as well not exist.

Nobody minimizes the call, opens a shared drive, and skims for the right card while a prospect waits on the line. By the time you'd have found it, the half-second is long gone and instinct already answered for you. A card that lives in a folder helps you prep and review. It does nothing for you mid-sentence — which is the only time it actually counts.

That's the gap real-time coaching is built to close. Instead of asking reps to remember the right move, the card surfaces itself the instant the objection is spoken, right there on the call, so the rep can stay in the conversation rather than digging through their notes. The discipline stops living in memory and starts living in the workflow — which is the only place a discipline survives a hard call. (It's the idea behind Funnelfeedr's live coaching, if you want to see one version of it.)

The takeaway

Stop thinking of objections as obstacles to clear and start thinking of them as sentences to finish. The pushback is rarely the real reason; it's the doorway to it. Win the urge to defend, ask the question that gets the rest of the thought, and the right response usually reveals itself — because now you're answering what they actually meant.

The instinct is teachable. The hard part is making it hold up across an entire team, on every call, when the pressure's on. That's not a talent gap — it's a system gap, and systems are something you can build: capture what works from real calls, shape it into cards that point to questions, and put those cards where reps can reach them in the half-second that decides the deal.

Curious what that looks like in practice? Book a demo and see Funnelfeedr's live coaching in action →