How to handle sales objections: prevent them, then run one process
Stop memorizing comebacks. Prevent most objections in discovery, run the LAER process on the rest, and coach from recorded calls. Scripts and data inside.
Updated June 12, 2026
Most advice on handling sales objections is wrong. It treats an objection as a rebuttal problem: keep a clever line ready, fire it back, win the moment. The sellers who actually close more deals do the opposite. They treat objections as a discovery and prevention problem. The strongest move happens before the objection ever surfaces (deep discovery, raising budget and decision process early, talking less and listening more), and when one does surface, they run one universal process instead of reciting twenty memorized comebacks. This guide gives you that process, the scripts that show it in action, and the reason a recorded call is what makes any of it learnable.
The real problem with "objection handling"
An objection is not a rejection to defeat. It is one of two things: a request for more information, or a signal that you missed something earlier in the conversation. When a prospect says "it's too expensive," they are rarely telling you your price is wrong. They are usually telling you that you never established enough value to justify it, or that you raised price before you earned the right to.
That reframe matters because it changes what you do next. If you believe an objection is a debate to win, you do one of two losing things. You argue back, which means you talk more and listen less, and you push the prospect into defending their position harder. Or you cave, drop the price, and teach the buyer that your number was never real. Both come from the same mistake: reacting to the objection as a live confrontation instead of treating it as data.
You will hear that "60% of customers say no four times before they say yes." It is a tidy stat, and it has no traceable primary source. It circulates through marketing roundups and a popular sales book, but no original research backs it up. Skip it. The numbers worth building a method on are the ones below, and they all point the same direction: the work that wins deals happens in discovery, not in the comeback.
If you sell solo or run a small team, this is also why a conversation intelligence habit beats raw talent over time. You can read more about the broader case in our piece on improving sales productivity, but the short version is: objections are a coaching surface, and you can only coach what you can review.
Prevent the objection before it happens
This is the part nobody teaches, because it is not glamorous. The single most effective objection-handling technique is a good discovery call. Here is what the data says good looks like.
Ask the right number of real questions. Gong's analysis of more than 519,000 calls found a sweet spot of roughly 11 to 14 problem-focused questions on a discovery call. Beyond that, win rates fall back toward average. Quality beats quantity: questions about the prospect's business problems, challenges, and goals do the work, not rapid-fire qualifying. Top reps also spread questions across the call rather than front-loading an intake form. For the questions worth asking on a first call, see our first client meeting objectives guide.
Talk less than half the time. Top B2B sellers land near a 43% talk, 57% listen ratio. Talking more than about 65% of the call correlates with lower win rates. A 2025 look at 326,000 calls found the bigger separator is consistency: high performers keep the same ratio in deals they win and deals they lose, while weaker reps talk more when a deal is going badly, jumping from around 54% talk time in won deals to 64% in lost ones. The lesson: when you feel a deal slipping, the instinct to talk more is exactly backwards.
Raise budget and price early. This one surprises people. In Gong's analysis of 11,331 opportunities, discussing price on the first call correlated with a 42% win rate versus 5% when price never came up. Discussing budget on the first call correlated with a 49% win rate versus 7% when it was skipped. This is not "open with your price." Top reps tend to bring up price after they have built value, often in the 38 to 46 minute window of a call. But they do bring it up, on the first call, instead of leaving budget as a landmine that detonates as an "it's too expensive" objection three weeks later.
Put the deck away. Using slides on a first or discovery call correlated with 17% lower success in Gong's review of 803,402 recorded meetings, along with 21% fewer questions asked and 25% longer seller monologues. A presentation turns a dialogue into a lecture, and a lecture generates the exact objections you could have prevented by listening.
Do these four things and a large share of your "objections" simply never appear. The price objection dissolves because you sequenced value before price. The timing objection shrinks because you surfaced the decision process up front. What is left is the smaller set of genuine concerns, and for those you need a process.
The LAER process: one method for every objection
When an objection does surface, you do not reach for a script matched to that specific objection. You run the same four-step process every time. It comes from Jack Carew, founder of Carew International, who introduced it in his 1987 book You'll Never Get No For An Answer and whose firm still teaches it today as "LAER: The Bonding Process." The four steps are Listen, Acknowledge, Explore, Respond.
- 1
Listen
Give the objection your full attention. Do not interrupt and do not pre-load a rebuttal while they talk. Read tone and emotion, not just words. Let them finish completely.
- 2
Acknowledge
Validate the concern and show you understand it, without agreeing it is a dealbreaker and without arguing. This is the step everyone skips. It defuses the reflex to defend.
- 3
Explore
Ask open-ended questions to find the root. 'Too expensive' and 'no budget this quarter' look the same and need opposite responses. Diagnose before you treat.
- 4
Respond
Now answer the actual concern you uncovered, using what you learned. Then confirm it is resolved: 'Does that address what you were worried about?' Some teach this as a fifth step, Confirm.
The order is the whole point. Most reps jump straight from hearing an objection to responding, skipping Acknowledge and Explore entirely. That is how you end up answering the wrong question. The prospect says "I need to think about it," you launch into an ROI defense, and it turns out their real concern was an implementation risk you never asked about. Explore first. You almost always find that the stated objection is not the real one.
Scripts for the objections you'll actually hear
Below are the most common objections mapped to the Explore questions that diagnose them and a value-led response approach. Treat these as illustrations of LAER in motion, not lines to memorize. The questions matter more than the responses, because the questions are what surface the real concern.
- It's too expensive
- I need to talk to my team / my boss
- We're happy with our current vendor
- Let's reconnect next quarter
- We have an in-house team for this
- Ask: 'Expensive compared to what?' Isolate whether it is a value gap or a real budget cap, then reframe to ROI. Sequence value before any discount.
- Ask: 'Who else weighs in, and what would they need to see?' Equip your champion with a one-pager and aim to get the decision-maker on a call.
- Ask: 'What's working well, and where does it fall short?' Shift from attacking the competitor to consulting on the gap. Probe for the unmet need.
- Ask: 'What changes next quarter that doesn't apply today?' Test for a real timing trigger versus a polite brush-off. No trigger means it is a stall.
- Ask: 'Where does the in-house team get stretched?' Find the gap you fill rather than challenging the team. Position as a force multiplier, not a replacement.
Here is "it's too expensive" run all the way through LAER, so you can see the shape of a real exchange:
Prospect: Honestly, this is more than we were planning to spend.
You: [Acknowledge] That's fair, and I'd rather know that now than later.
[Explore] Help me understand the comparison. Is it more than other
options you're looking at, or more than the budget you have set
aside for this?
Prospect: More than we budgeted. We allocated about half this.
You: [Explore] Got it. When you set that number, was it based on a
specific quote, or more of a placeholder before you'd seen
what's involved?
Prospect: Pretty much a placeholder.
You: [Respond] Then let's make sure the number reflects the actual
problem. You told me the manual process is costing your team
roughly ten hours a week. At a loaded rate, that's the gap we'd
close in the first month. [Confirm] If we can show that math
clearly, is budget something you can revisit, or is the cap firm?
Notice that no "comeback" appears anywhere in that exchange. The prospect did most of the talking, and the price objection turned into a budget-revisiting conversation because you explored instead of defending. That is the entire method.
Real objection or smokescreen: how to tell
Not every objection is a concern you can resolve. Some are brush-offs: vague, low-commitment ways of avoiding a no. "Send me some information." "Let's circle back next quarter." "I'll run it by the team." A true objection is specific and resolvable. A brush-off is general and evasive. Treating a smokescreen like a real objection means you spend a week sending a deck to a deal that was already dead.
The way you tell them apart is, again, Explore. A real objection survives a clarifying question and gets more specific. A smokescreen evaporates or stays vague. The isolate-and-test move works on both:
You: If [the price / the timeline / your team's sign-off] weren't an
issue at all, is this something you'd want to move forward on?
If "yes, definitely" -> it's a real, isolated objection. Solve that one thing.
If "well, also..." -> there's a deeper concern. Keep exploring.
If vague or evasive -> it's a brush-off. Test for a real reason to engage,
and be willing to walk if there isn't one.
Then there is the silence. You respond to an objection, and the prospect goes quiet. The instinct is to fill the gap with more talking. Resist it. Silence after you respond is an invitation for the prospect to reveal the real concern. Ask one short question ("What's your reaction to that?") and then stop. The first person to talk usually loses the thread.
Build a playbook your whole team can use, from real calls
Relying on each rep's instinct means objections never get prevented and coaching never compounds. A documented, living playbook fixes that. Group recurring pushback into a handful of categories (price, timing, trust, fit, authority), record the best Explore questions and responses for each, and update it as you learn. New reps onboard from it. Veterans pattern-match against it.
But a playbook written from memory is fiction. People misremember what they said and why a deal turned. The only reliable source is the recording. This is where the method becomes real: every objection traces back to a moment on the call, and almost always to a discovery step you rushed or skipped. You cannot see that moment from notes scribbled after the fact. You can see it on a transcript.
Summary
Discovery skipped budget question. Price raised at 6:40 (early). Prospect objected on cost; root cause was no value established first.
Transcript · 24:12
Prospect: This is more than we were planning to spend.
Objection flagged: price · value not yet established
Action items
Send ROI one-pager · Get CFO on next call · Lead value before price next time
Scribbl records, transcribes, and summarizes your Google Meet calls with no bot in the meeting (it runs in your browser, so prospects do not see a stranger join), and it covers Zoom and Microsoft Teams on the Team plan. Because the transcript is searchable, a sales leader can find every call where a price objection came up and review exactly how the top rep handled it, then build a "winning calls" collection for onboarding. The summary and action items can flow into your CRM so the objection and outcome are logged against the deal. This is the difference between a team that argues about objections and one that improves on them. If you run a team, Scribbl for teams and our sales workflow page show how this fits a shared playbook; for the broader recording question, our roundup of the best meeting recording software compares the options honestly.
The point is not the tool. The point is that objection handling is a skill, skills improve with review, and review needs a recording. However you capture your calls, capture them.
Frequently asked questions
What is the single best objection-handling technique?
Acknowledge, then explore, before you respond. Most reps skip straight to responding, which means they answer the stated objection instead of the real one. Validating the concern (without agreeing it is a dealbreaker) and then asking open-ended questions to find the root resolves more objections than any clever line, because it surfaces what the prospect is actually worried about.
How do I train new reps to handle objections?
Two things together. First, a written playbook that groups recurring objections by category and records the best Explore questions and responses for each. Second, and more important, regular review of real recorded calls, so reps see how your top performers actually handled an objection rather than how they remember handling it. Build a small library of strong calls and have new reps study them in their first week. See our notes on taking better meeting notes for the capture side of this.
How do I tell a real objection from a brush-off?
A real objection is specific and gets more specific when you ask a clarifying question. A brush-off is vague and stays vague or evaporates. Use the isolate-and-test question: "If [that] weren't an issue, would you move forward?" A real, isolated concern gets a confident yes. A deeper concern surfaces more detail. A brush-off stays evasive, and that tells you to either find a real reason to engage or move on.
What do I do when the prospect goes silent after I respond?
Stay silent too. The urge to fill the gap with more talking is the wrong move; you end up talking yourself out of the deal. Silence after a response invites the prospect to think and reveal their real concern. Ask one short question like "What's your reaction to that?" and then wait. Let them break the silence.
Should I ever just discount to close a price objection?
Almost never as a first move. A price objection usually means value was not established, or you raised price before earning it. The fix is sequencing: establish value, then price. If you discount immediately, you teach the buyer your number was inflated and you train them to push every time. Reframe to ROI first. A discount, if it ever comes, is a deliberate trade for something (a longer term, a case study, a faster close), not a reflex.
Try Scribbl
Let your meetings take their own notes.
Scribbl records, transcribes, and summarizes your Google Meet calls from your browser. No bot joins the call. Free forever for individuals.
Add to Chrome · It's free