Sales Objection Handling

Objection Handling

Diagnose what a sales objection really means, then produce spoken-language response scripts - or say plainly that the deal should be disqualified. Works for B2B and B2C, from cold call through negotiation, with dedicated price-objection sequencing.

The prevention check (run it first)

The strongest research in this field (Neil Rackham's Huthwaite studies) found that objections are more often created by the seller than the buyer, and that preventing them beats rebutting them. Pitching before the need is developed, or leading with features, manufactures price sensitivity.

1. Once the interview tells you where the objection landed, ask what discovery happened before it.
2. If the honest answer is "we pitched before we understood the problem", say so, and recommend mbfinotti/sales-skills@sales-discovery-questions to fix the upstream gap.
3. Then continue - the rep still has to answer the objection in front of them. One check; don't turn this into a discovery session.

Interview

Ask one question per message. Offer multiple-choice options wherever possible - the user is often answering from a phone between calls. Gather:

1. What are you selling, and to whom? (product, rough price point, buyer persona)
2. B2B, B2C, or consumer high-ticket (auto, solar, home improvement)?
3. Where did the objection land: cold call / discovery / demo / proposal or negotiation / retail or inbound?
4. The prospect's exact words. Verbatim matters - "that's a lot of money" and "we have no budget" are different objections.
5. What has the rep already tried in response?
6. Which proof assets exist: case study, benchmark, reference customer, guarantee, trial? Never invent one.
7. Do you sell in a regulated category - securities, insurance, lending, health/pharma, energy/utilities? (See Ethics and compliance.)
8. By when does this have to land - the call tomorrow, this quarter's pipeline, or next year's team enablement?
9. One-off win or compounding asset: scripts for one rep's live deal, or a framework the whole team adopts and drills?
10. What's the effort ceiling - rehearsal hours available before the next call, and can the rep offer an opt-out, guarantee, or phased start without sign-off?

Re-rank the framework ladder on those answers, and say which answer moved what:

• A call tomorrow promotes the pause, the value/capability split and the ledge, and drops everything costing a quarter of rehearsal.
• A compounding mandate promotes LAARC, the up-front contract and the JOLT play - all three only pay once a team drills them, and all three are wasted on a single deal.
• No authority to offer de-risking deletes the de-risk move from the discount menu below and leaves trading at the top.

Workflow

1. Run the interview, then the prevention check.
2. Diagnose the objection (next section). Never script before diagnosing.
3. Pick the response mode that matches the diagnosis.
4. Draft the rebuttal set in the output shape below. Apply the price sequencing section to any price objection. For competitor objections: if you can browse the web, verify the competitor's current public pricing and packaging before writing a comparison claim; if you can't, mark every competitor claim "verify before use".
5. Apply the ethics and compliance gate.
6. Run every script through your preferred humanizer skill - mandatory, this is language meant to be spoken. If no humanizer skill is available, do a manual pass: read each line aloud, add contractions, cut anything a person wouldn't actually say on a call.
7. Deliver. If the user is building a reusable library, add the maintenance notes below.

Diagnose before you script

The stated objection is often not the real one. The same words need opposite responses depending on what's underneath, and a rebuttal aimed at the surface words wastes the rep's turn. Classify first:

Make the rep ask one diagnostic question before responding. All four cost the same near-zero breath, so the ordering is pure value:

"what's behind that?" > the price triage > the if-solved test > the confidence question

• "Can I ask what's behind that?" - opens up almost any objection, and needs no guess about which arena you're in.
• "Is it that the number doesn't fit the budget, or that you're not sure it's worth it?" - the price triage. Splits the single most common objection into its two opposite responses, but only once you know it's about price.
• "If [stated objection] were solved, would you move forward?" - a "no" exposes a smokescreen. Needs a stated objection specific enough to name back.
• "What would you need to see to feel confident this is the right call?" - a specific answer is a true objection; an endless list signals indecision. Slowest to interpret: the tell is in the shape of the answer, not its content.

Before any of that, the magic quarter of a second (Jeb Blount): pause before reacting. The first instinct is to defend, and defending is almost always wrong.

Response modes

The diagnosis picks the mode, so the four modes are deliberately not ranked against each other - a ranking there would be false precision. The choice of framework _inside_ a mode is ranked, and that ordering is what a rep with limited rehearsal time needs.

Learn the frameworks in this order - value bought per hour of rehearsal:

pause > value/capability split > LAER > ledge == Mr. Miyagi > gap re-anchor > LAARC > up-front contract > JOLT play > tactical empathy

Steps, originators, what each costs to learn and what each buys are in ./references/response-frameworks.md - read it when drafting. Effort there is rehearsal time, live-call composure, and how badly the move fails in unskilled hands; nothing on the ladder is bought, only learned.

What that order starves: tactical empathy and the full JOLT play are the two highest-value entries and lose every round, because each costs a quarter of rehearsal. Promote both when:

• a single deal is worth a large share of the number
• procurement or an adversarial economic buyer is in the room
• no-decision is already the top loss reason

The order is a default, not a law - it shifts with context and with who executes it. Re-rank it against what you already know: