objection-handling

Installation
SKILL.md

Objection Handling — Surface, Understand, Resolve

Overview

Objections are information, not rejection. Most lost deals die not from the stated objection but from an unsurfaced real one (budget authority, risk, status quo). The discipline: draw objections out early, understand the true concern behind the script, and resolve it with evidence — rather than arguing or discounting reflexively.

The Process

  1. Invite objections early — "what would stop this from being a fit?" Better surfaced in discovery than at close.
  2. Acknowledge, don't argue — lower defenses first; "makes sense" beats a rebuttal.
  3. Find the real objection — the stated one is often a proxy. "Too expensive" may mean unclear ROI, wrong authority, or fear of switching. Gate: resolving the surface objection without the real one = the deal still stalls.
  4. Isolate & confirm — "if we solved that, is there anything else?" so you're not fighting a moving target.
  5. Resolve with evidence — proof, references, a trial, risk-reversal — matched to the real concern (money, risk, timing, authority).
  6. Ask for the advance again. Gate: no re-ask = the handled objection is wasted.

Common objections → real concern

  • "Too expensive" → ROI not proven / budget elsewhere.
  • "Need to think about it" → unspoken risk or missing stakeholder.
  • "Send me info" → soft no / not enough urgency (built in discovery).
Installs
1
GitHub Stars
10
First Seen
5 days ago
objection-handling — deciqai/knowledge-skills