Sales Objection Handling Framework for Every Scenario

What sales objection handling actually is

Most "objection handling" training is script drills. Memorize 25 rebuttals, rehearse them to a roleplay partner, deploy them on calls. It looks professional. It rarely moves deals.

The reason is simple. A sales objection is rarely a question about what the rep said — it's a signal about what the buyer hasn't told you yet. "It's too expensive" might be a budget problem. It might be a procurement timeline problem. It might be a champion-is-nervous problem. Three different objections wearing the same sentence. A script treats them as one. A framework doesn't.

The framework doesn't replace product knowledge. A rep still needs to know the price, the competitive landscape, and the proof points. But without a framework, that knowledge fires at the wrong time — and the rep spends the whole call defending a number the buyer wasn't really objecting to.

The 4 root causes behind every B2B sales objection

Every objection you hear on a B2B call traces back to one of four root causes. Name the cause and the response follows. Skip the diagnosis and you close the surface objection while the real one is still on the table.

1. Price. "It's too expensive." Underneath that sentence lives three different problems: no clear ROI model, wrong anchor (they're comparing your enterprise tier to a free tool), or the status quo feels free because the cost of inaction was never quantified. You don't answer price with price. You answer price with the cost of doing nothing.

2. Timing. "Not right now." Real timing objections have a forcing function the rep can surface — fiscal year end, contract renewal, team reorg. Fake timing objections are polite brush-offs. The diagnostic question is the same: "What would need to be true for this to be a Q3 priority?" If they can answer, it's real. If they can't, it's a brush-off, and the sale is actually stuck on authority or fit.

3. Authority. "I need to check with the team." Translation: you're not talking to the economic buyer. This is a discovery failure, not an objection. The fix happened two calls ago — the rep should have mapped the buying committee and the decision process before demo day. In-call, the best you can do is ask what the approval process looks like and how you can help your champion push internally.

4. Fit. "This isn't what we need." If the rep hears this at demo, discovery broke down. Sometimes the ICP was wrong to begin with. Sometimes the rep missed a feature gap. Sometimes a competitor is locked in and the prospect just didn't tell you. Fit objections at demo are rarely recoverable in the same call — but they are preventable in the call before.

The LAER framework — 4 steps every rep runs on every objection

LAER stands for Listen, Acknowledge, Explore, Respond. Multiple variants exist (LAARC adds a confirming "Answer and Confirm"), but the four-step core is the version most AEs actually use on a live call. It works because it forces the rep to slow down in the two places where deals get lost: the first five seconds after the objection lands, and the question that follows the acknowledgment.

1. Listen — don't interrupt. Don't rebut in your head.

The average B2B seller interrupts a buyer inside 7 seconds of an objection landing (Gong, 2022). The rep is already assembling their rebuttal before the buyer finishes the sentence. They hear the first three words — "It's too expensive…" — and miss the next seven, which usually contain the actual concern: "…for this quarter, because we already committed to X." Capture the exact phrasing, not your interpretation of it.

2. Acknowledge — confirm the concern so the buyer keeps talking

One sentence. "That's a fair concern." "I hear that a lot from VPs in your stage." "Makes sense — let me understand what's driving that." The goal isn't agreement. The goal is to drop the rep's defensiveness and keep the buyer in the conversation. If you skip this step, every response that follows reads as dismissal — and the buyer stops volunteering information.

3. Explore — one diagnostic question

This is where deals are won. One open-ended question, aimed at surfacing which of the four root causes is actually live. "What's driving that for you right now?" "Is the concern the total cost, or the fit inside this quarter's plan?" "What would need to change for this to be a priority?" Resist the urge to ask two questions. Reps who stack questions lose the thread and end up defending whichever one the buyer picks up.

4. Respond — reframe with proof, then move to the next step

Now — and only now — you respond. One specific proof point tied to the root cause you just surfaced. A benchmark, a peer case study, a quantified cost of inaction. Then close with the next step, not the objection: "Given that, does it make sense to loop in your CFO on Thursday?" The response is a bridge, not a wall. The goal isn't to "win" the objection — it's to move the deal forward.

8 common B2B sales objections, with rep-ready responses

A library of responses is useful — as long as it sits underneath a framework, not on top of it. The sentences below are starting points you run through LAER. They are not scripts to read.

Notice what's missing from the right column: any closing language. Objection handling doesn't end with a tight one-liner — it ends with a question that advances the deal. If your response can be delivered without waiting for a reply, you're monologuing, not handling.

How to handle the price objection specifically

Price is the most common B2B objection (~35%, per Gong Labs) and the one reps are most likely to answer wrong. The default instinct — defend the number, or discount to make the concern disappear — trains the buyer to push harder on the next call. Neither moves the deal.

The LAER version of the price objection runs like this:

1. Listen to the end of the sentence. "It's too expensive" is a headline. "For our current phase" or "for what I can get approved this quarter" is the story.
2. Acknowledge without agreeing. "That's fair — enterprise tools are a real commitment." You haven't conceded the price. You've let them keep talking.
3. Explore the anchor. "When you say expensive, what are you comparing it to?" Half the time the prospect is benchmarking against a point solution that does 30% of what you do. The comparison is the objection.
4. Respond with the cost of doing nothing. Not "here's our ROI." The cost of not solving the problem — hours lost, pipeline leaked, quota missed. Make the status quo expensive, not your software cheap.

The deeper pattern: discounting is the seller's answer to a problem the buyer hasn't fully expressed. Diagnose the root cause (is it budget cycle, ROI model, or anchor?) and the right response picks itself. For a full breakdown with real dollar numbers, see how to handle the price objection in B2B sales.

Objection handling in real time — what to do on the call

Here's the part most objection-handling guides skip. Frameworks work in training. Scripts work in roleplays. Live calls don't wait for the rep to remember which cause maps to which response. The prospect says "it's too expensive" and the rep has seven seconds before the silence gets weird.

This is the gap Gangly's Live Call Coach fills. On a connected Zoom or Google Meet call, the coach listens, detects objection keywords, tags the root cause, and surfaces the right diagnostic question, proof point, and reframe — on screen, while the rep is still on the call. The rep runs the conversation. The coach runs the lookup.

What live coaching actually gives you, once you've run it on 50+ calls:

• Reaction time. The right Explore question appears within 2 seconds of the objection landing. The rep doesn't have to rummage through memory.
• Tailored proof. The coach pulls the case study that matches the prospect's ICP, not the default one. Enterprise call gets Linear; SMB call gets a Series B reference.
• Category tagging. The objection type (price / timing / authority / fit) is tagged automatically, so the post-call note and pipeline pattern work don't depend on rep memory.

The post-call loop — capture, pattern, kill at the source

The most expensive objection isn't the one you lose a deal on. It's the one you lose three deals on — because nobody logged the first two. Pattern capture turns objection handling from a calls-are-hard story into a pipeline-level one.

The loop is short. Every objection heard on a call gets tagged by type, resolved (or not), and logged against the deal in the CRM. After 20 calls, patterns emerge: the demo consistently breaks down on pricing when finance hasn't seen the ROI model beforehand; the "we already have a tool" objection shows up three times more often with a specific competitor in the stack; reps under 18 months of tenure lose to timing objections at double the rate of senior AEs.

Post-Call Notes captures this automatically. The objection and its resolution land in the deal record without the rep writing it from memory on Friday afternoon. Sales managers get a live view of which objections keep killing deals — and the cluster-level fix (a stronger ROI calculator, a better competitive battlecard, a discovery tweak) gets prioritized instead of being guessed at in a QBR.

5 mistakes that turn an objection into a lost deal

1. Interrupting the objection. You lose the half of the sentence that contains the actual concern. The rest of the call is about the wrong thing.
2. Skipping Acknowledge. Every response after lands as dismissal. The buyer stops volunteering anything real and the call becomes a wall.
3. Answering the wrong root cause. Treating a timing objection as a price one means discounting a deal that wasn't about money. You lose margin and still lose the deal.
4. Discounting instead of diagnosing. Cuts train the buyer to push harder. The next call opens with "what can you do on price?" before you've said anything.
5. Never logging the objection. The same pushback costs the same team another three deals next quarter. Pattern loss compounds faster than any single lost call.

How Gangly handles objections automatically

Gangly is built around the rep's actual sales workflow — signal to close, in one connected sequence — not as a sidecar to it. The objection-handling part of that workflow spans three of the six stages, and each one reinforces the next.

Call Prep Engine pulls likely objections based on company profile and prior call history into a pre-call brief, so the rep walks in knowing which of the four root causes is most likely to land. Live Call Coach listens on Zoom or Google Meet, detects the objection keyword, and surfaces the LAER diagnostic question plus tailored proof points during the call. Post-Call Notes tags the objection type, the resolution, and pushes both into the CRM — with the rep's approval — so the pattern compounds across the pipeline.

The Workflow Sequencer keeps all three stages connected. Reps don't switch between coaching tools, note apps, and Salesforce — the framework runs across a single workflow, which is how it actually gets used on Friday afternoon instead of forgotten by Monday.

For a broader take on the call, see the 5-minute sales call prep workflow or the discovery-stage sister piece, the discovery call framework that wins deals. If the price objection is where your team keeps losing, the deep dive is how to handle the price objection in B2B sales.

Frequently asked questions