Claude Skill

Objection Handler

Responds to common B2B sales objections with a 2-sentence response and 3 follow-up questions.

Download skill (.zip)Or download whole pack

What it does

Given an objection (already using competitor, no budget, send me info, etc.), this skill produces a non-defensive response, diagnostic questions to surface the real concern, and a graceful exit path if the objection is real. Built for thinking on your feet.

When to use

✓You're actively in a sales conversation and need a response in 5 seconds
✓You're prepping for a likely objection before a call
✓You want to practice a counter-response in writing first

When not to use

✗The objection is genuinely a no — sometimes the right answer is to walk away gracefully, and this skill helps you see when

Install

Download the .zip, then unzip into your Claude skills folder.

mkdir -p ~/.claude/skills
unzip ~/Downloads/objection-handler.zip -d ~/.claude/skills/

# Restart Claude Code session.
# Skill is now available — Claude will use it when relevant.

SKILL.md

---
name: objection-handler
description: Generates non-defensive responses to B2B sales objections — 2-sentence acknowledgment plus diagnostic questions to surface the real concern.
---

# Objection Handler

When the user describes a sales objection they've encountered, generate a structured response that surfaces the real concern instead of fighting the objection head-on.

## Required input

- **The objection** (verbatim if possible)
- **Their product** (1 sentence)
- **Deal context** — company size, role of objector, deal size if known

If the objection is vague ("they didn't seem interested"), push back: ask for the actual words.

## Output structure

### 1. The 2-sentence response
- Acknowledges the objection without surrender
- Re-opens the conversation
- No defensive language, no trash-talking competitors

### 2. Three diagnostic questions
Surface the real concern. Each question should:
- Be open-ended
- Avoid leading the witness
- Surface whether the objection is timing-based, priority-based, or genuine non-fit

### 3. The pivot
If the diagnostic surfaces an opening, what's the bridge to your value? Specific to the objection type.

### 4. The graceful exit
If the objection is real and you should walk away, what's the right exit? Don't manufacture deals from non-fits.

### 5. What NOT to say
Common SDR moves that backfire for THIS objection. Be specific to the objection type, not generic.

## Common objection patterns and what they usually mean

- **"We're already using [competitor]"** → either real loyalty or polite brush-off. Diagnose which.
- **"No budget"** → could be timing, could be priority, could be size mismatch
- **"Send me information"** → 80% brush-off, 20% real interest. Test for which.
- **"Not the right time"** → ask "what would have to change to be the right time?"
- **"Can you send a 1-pager?"** → fine to send, but make it conditional on a follow-up
- **"We're not looking right now"** → don't push. Ask when to reconnect, exit warm.

## Constraints

- The response section is ALWAYS exactly 2 sentences. Not "about 2." Two.
- Diagnostic questions are exactly 3. Not 4. Not 2.
- Don't moralize. Don't say "honesty matters." Just give the user the words.

Example prompts

Once installed, try these prompts in Claude:

Prospect said "we're already using Salesforce." We sell pipeline analytics. How do I respond?
They said "no budget this year." It's May, deal is $30k. What do I say?

Related prompts

Don't want to install a skill? These prompts in /prompts cover similar ground for one-shot use:

sales prompts