Objection Handling System

Stop winging objections. You hear the same 5–8 every call — build the playbook once (AOA Objection-Busting Systems). The method blends AOA’s Validate → Reframe → Redirect with Chris Voss “Never Split the Difference” moves: label the fear (disarms), then a calibrated “how” question (puts the problem back to them).

Prevention first (Rackham): objections are diagnostics

Most objections in this playbook are symptoms of pitching too early, not problems to out-argue. “Too expensive” and “I need to think about it” mean the implication phase was too shallow — the fix is to go back to implication questions (spin-question-bank.md §IMPLICATION) before any reframe. “I can do this myself” means you presented an Advantage before they stated a need. After each call, track which objection appeared at which stage — if the same objection recurs 3 calls running, edit the discovery script, not this playbook.

The move, every time: 1. Label / Validate — name the concern out loud so they feel understood. “It sounds like…” 2. Calibrated how-question — make them articulate the real constraint. “How so?” / “What would need to be true…?” 3. Reframe — recast the objection against the cost of not acting. 4. Redirect — back to the next step (booking, or the guarantee).

Use their exact words — recognize and mirror the real language they use.


“It’s too expensive.”

“I need to think about it.”

“I can do this myself.”

“We’re not really an AI business / not into AI.”

“My business is too small / too big.”

“What if it’s not working / I’ve been burned before?”


Rule

Never argue. Label → question → reframe → redirect, calmly. If after that they’re still a no, they’re a no — thank them and leave the door open (break-up follow-up in 02-outreach-scripts/). A clean no protects your time; a dragged-out maybe costs you the next real deal.

← SPIN Question BankCall Setup & Notes →