Objection Handler

---
name: Objection Handler
description: Diagnoses what is actually behind a B2B sales objection - price, timing, authority, need, competitor, or status quo - and supplies a calibrated, non-pushy response for each with reframe patterns and exact language. Use when someone asks "they said it's too expensive, what do I say", "how do I handle 'not right now'", "the buyer says they're fine with their current tool", or a rep needs a response framework mid-deal. Do NOT use for gym or local-fitness lead objections and speed-to-lead cadence - use objection-handling-and-speed-to-lead instead; for writing a full call script, use closer-sales-script.
---

# Objection Handler

An objection is not a rejection - it is information. The costly mistake this prevents is the reflex rebuttal: answering the surface words ("too expensive") instead of the real concern underneath (unclear value, no budget authority, or a polite stall), which burns trust and teaches the buyer to stop sharing objections at all. Diagnose first, respond second, one objection at a time.

## Operating procedure

### Step 1: Gather inputs

Before crafting a response, establish:

1. The objection verbatim - the buyer's exact words, not the rep's paraphrase.
2. Deal stage (discovery, evaluation, negotiation) - the same words mean different things at different stages; "too expensive" in discovery is usually unclear value, in negotiation it is often real.
3. Who raised it and whether they hold budget authority.
4. What quantified pain has already been established. If none, that gap - not the objection - is the real problem.

### Step 2: Run the universal first move

For every objection: pause, acknowledge, and ask one clarifying question before responding. "That makes sense - can you help me understand what's driving that?" This surfaces the real concern. Skip this step and almost every rebuttal lands hollow. Then classify into the taxonomy below and respond to what the diagnosis reveals, not the surface words.

### Step 3: Apply the category playbook

**Price ("too expensive").** Almost always one of three things: (1) value is not clear yet, (2) budget is genuinely constrained, (3) price is a stall. Reframe pattern: move the comparison from price-versus-zero to price-versus-cost-of-the-problem. For (1): "What does the current situation cost you per quarter - in time, lost deals, or rework?" then map the price to that delta. For (2): explore phased rollout, smaller initial scope, or payment structure - never discount before understanding what they can actually do. For (3): ask directly what would need to be true to move forward, then be silent; silence after a price objection outperforms a counter.

**Timing ("not right now").** Reframe pattern: separate constraint from priority - they need opposite responses. Ask: "Is there a specific event or milestone you're waiting for, or is it more that the priority isn't there yet?" Real constraint (budget cycle, reorg, in-flight project): agree a specific reconnect date and send a calendar hold immediately. Priority gap: reconnect to the quantified pain. "Not right now" without a date is not a next step - it is a polite no.

**Authority ("I need to run this by my boss / the team").** Reframe pattern: convert the blocker into a champion. Ask: "What do you expect their main concern will be?" - this reveals the real internal objection. Then equip, don't bypass: offer to join the internal conversation or build a one-page summary the champion can forward. Going over someone's head kills the deal and the relationship; a champion who can't articulate the case loses the internal meeting the rep never sees.

**Need ("I'm not sure we need this" / competitor / status quo).** Two variants:

- Incumbent competitor: never trash the competitor - it looks insecure and buyers hate it. Reframe pattern: "A lot of our customers came from there - what's been working well for you about them?" This surfaces what the buyer values; differentiate only on dimensions that matter to this specific buyer. Generic feature comparisons are noise.
- Status quo ("we're fine with what we have"): the cost of inaction is not yet concrete. Ask: "What would it take for the current approach to stop working well enough to change?" - then be quiet. If they cannot name a trigger, the problem is not painful enough: qualify out gracefully. Manufactured urgency destroys trust.

### Step 4: Confirm and advance

After responding, confirm the objection is resolved before moving on: "Does that address it, or is there something underneath it?" Handle one objection at a time - batching responses signals defensiveness. Every resolved objection should end with a concrete next step on the calendar.

## Worked pairs - one per category

Price
Buyer: "It's 40% more than what we pay now."
Rep: "Fair comparison to make. Before we talk numbers - you mentioned the current tool drops about 15 leads a month. At your close rate, what's a lead worth? [Buyer: ~$800.] So roughly $12k a month leaking. The difference between us and your current spend is $900 a month. Is the gap the price, or whether we'd actually recover those leads?"

Timing
Buyer: "Let's revisit next quarter."
Rep: "Happy to. Is there something specific landing next quarter - budget, the reorg - or is it more that this isn't top-three right now? [Buyer: budget resets in April.] Then let's book April 8th now so you're first in line when it does. Sending the hold today."

Authority
Buyer: "I need to run it by our CFO."
Rep: "Of course. When she looks at this, what's her first pushback likely to be? [Buyer: payback period.] Then let me build you a one-pager showing breakeven at month five from your own numbers - would that make that conversation easier, or would it help if I joined for ten minutes?"

Need / status quo
Buyer: "Honestly, our current process works fine."
Rep: "That's good to hear - most processes do work until something changes. What would have to happen for 'fine' to stop being fine? [Silence.] [Buyer: if we doubled ticket volume, we'd drown.] Is that on the horizon? If not, this may genuinely not be worth your time yet - and I'd rather tell you that than push."

## Deliverable

Produce a response plan for the live objection containing: the diagnosed category and the evidence for it, the clarifying question to ask first, the calibrated response with exact language, and the confirming close plus next step.

## Do NOT

- Do not offer a discount the moment price comes up - it confirms the price was padded and resets the anchor for the whole deal.
- Do not answer the surface words without the clarifying question; the stated objection is wrong often enough to make the reflex response a coin flip.
- Do not promise to "check with the team" unless the follow-up will actually happen within 24 hours - a missed micro-commitment costs more trust than the objection did.
- Do not manufacture urgency against a status quo objection; if there is no trigger, qualify out.
- Do not handle multiple objections in one response; stack answers and the buyer hears defensiveness.

## Quality bar

A finished response passes when: the category diagnosis is stated with its evidence; the first move is a question, not a claim; the reframe ties to this buyer's quantified pain (or the plan says pain must be established first); and the exchange ends with a dated next step or an honest qualify-out. For the discovery groundwork that prevents objections, pair with discovery-call-prep; for structuring the full close, closer-sales-script.