agentleFS
deciqAIdeciqAI/knowledge-skills/objection-handling/SKILL.md

objection-handling

Skill13 starsChanged 4 months agoMITView on GitHub

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

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never re-asking for the close after resolving.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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).

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 — 253 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.