Skip to content
Back to skills

Objection Handling

ASecurity

Activate when: deals stall on 'too expensive', 'not now', 'need to think about it', 'send me info'; a founder gets flustered by pushback; improving close rate. Do NOT activate when: the prospect is genuinely unqualified (then disqualify, don't 'handle'). More: deciqai.com/s/objection-handling

  • 10 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 3, 2026
ai-agentsgogit

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add deciqAI/knowledge-skills --skill objection-handling --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Objection Handling?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Objection Handling
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/deciqai-objection-handling/badge)](https://www.skillsdirectory.com/skills/deciqai-objection-handling)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: objection-handling
description: "Activate when: deals stall on 'too expensive', 'not now', 'need to think about it', 'send me info'; a founder gets flustered by pushback; improving close rate. Do NOT activate when: the prospect is genuinely unqualified (then disqualify, don't 'handle'). More: deciqai.com/s/objection-handling"
---

# 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).

## When to Use
- Recurring stalls at the same stage
- Reflex discounting under pushback
- Founder-led sales where composure under objection matters

## Red Flags
- Discounting the moment price is questioned.
- Rebutting instead of understanding.
- Never re-asking for the close after resolving.

## Verification
- [ ] Objections invited before the close
- [ ] Real concern identified behind the stated one
- [ ] Objection isolated/confirmed as the last blocker
- [ ] Resolved with evidence, then advance re-requested

---
*Part of **deciqAI Knowledge Skills** — 237 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/s/objection-handling** · Built by deciqAI · github.com/deciqAI · Contributions welcome.*

*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/objection-handling.json*

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…