agentleFS
cwhited26cwhited26/pocket-agent-starter-skills/skills/sales/objection-handling/SKILL.md

objection-handling

Skill0 starsChanged 4 months agoMITView on GitHub

Find the actual objection hiding behind the stated one, then address the fear of loss driving it instead of arguing the surface. A prospect pushes back — on price, timing, \"I need to think about it.\" Use before you discount or walk, when there's still a real conversation to have.

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

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    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:

    Don't take the first objection at face value.

    line 20
  2. Distinctive:

    Don't argue. You're not winning a debate.

    line 24

“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

Handle the Real Objection

The first objection is rarely the real one. "Too expensive" usually means "I'm not sure this is worth it" or "I'm scared of getting burned again." Surface the real one, then speak to the loss behind it.

The technique

  • Don't take the first objection at face value. "Too expensive" compared to what? Ask the question that surfaces the real worry.
  • Listen for loss aversion — most objections are fear of making a wrong call, not the price itself. People dread the loss more than they want the gain.
  • Name the fear out loud: "Sounds like you've been burned by a contractor before and you don't want to repeat it." Naming it defuses it.
  • Answer the real objection, not the stated one. If the fear is being abandoned mid-job, talk about how you stay reachable — not about the price.
  • Don't argue. You're not winning a debate; you're removing the reason they're scared to say yes.

Do this, not that

Do: They say "it's a lot of money." You ask, "Is it the number, or is it that the last guy took a deposit and disappeared?" — and now you can actually solve the thing.

Don't: Hear "it's a lot of money" and immediately drop the price 15% — you just discounted to solve a fear that wasn't about money, left margin on the table, and taught them to push.

Why this works

People rarely tell you the real reason they're hesitating on the first try — partly because they haven't named it themselves. If you answer the surface objection, you solve the wrong problem and they still don't buy. Surfacing the real one, usually a fear of loss, lets you address what's actually in the way — and most of the time it costs you nothing, where a reflexive discount costs margin every time.

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.