Skip to content
Back to skills

Objection Handling

ASecurity

Sales objection scripts, FAQ generation, and trust-building content for common buying hesitations.

  • 61 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 26, 2026
businessrustgo

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add mfwarren/entrepreneur-claude-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/mfwarren-objection-handling/badge)](https://www.skillsdirectory.com/skills/mfwarren-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
version: 1.0.0
category: Sales & Revenue
domain: sales
author: Matt Warren
license: MIT
status: production
updated: 2026-02-07
activation_triggers:
  - "objection handling"
  - "sales objections"
  - "overcome objections"
  - "FAQ for sales"
  - "why people don't buy"
  - "sales script"
  - "handle pushback"
  - "trust building"
tools: []
---

# Objection Handling

Sales objection scripts, FAQ generation, and trust-building content for common buying hesitations.

## Purpose

Every product faces the same core objections: price, timing, trust, need, and authority. This skill maps your specific objections and creates scripts to address each one honestly.

## Workflow

### Step 1: Gather Context
- Product/service and price point
- Sales channel (calls, chat, email, self-serve)
- Most common objections heard (if known)
- Ideal customer profile

### Step 2: Map the Objection Categories
1. **Price:** "It's too expensive" / "I can't afford it"
2. **Timing:** "Not right now" / "Maybe later"
3. **Trust:** "How do I know this works?" / "I've been burned before"
4. **Need:** "I don't think I need this" / "We're fine without it"
5. **Authority:** "I need to check with my partner/boss"
6. **Competition:** "How are you different from X?"

### Step 3: Create Response Scripts
For each objection:
- **Acknowledge** — Validate the concern (never dismiss it)
- **Clarify** — Ask a question to understand the real objection
- **Reframe** — Shift the perspective
- **Proof** — Provide evidence (testimonial, case study, guarantee)
- **Close** — Re-present the offer with the objection addressed

### Step 4: FAQ Page Content
Turn top objections into FAQ entries for the website/sales page. Proactively address concerns before they arise.

### Step 5: Trust-Building Content
Suggest content pieces that preemptively handle objections:
- Case studies for trust
- Comparison pages for competition
- ROI calculators for price
- Free trials/samples for need

## Output Format
```markdown
## Objection Handling: [Product]

### Objection Map
| Objection | Category | Frequency | Response Script |
|-----------|----------|-----------|----------------|
| "Too expensive" | Price | High | [Script] |

### Response Scripts
#### "It's too expensive"
**Acknowledge:** ...
**Clarify:** ...
**Reframe:** ...
**Proof:** ...
**Close:** ...

### FAQ Content
[Ready-to-publish FAQ entries]

### Trust Content Recommendations
[Suggested content pieces]
```

## Constraints
- Never teach manipulation tactics — honest selling only
- Scripts should feel conversational, not rehearsed
- Always respect "no" — provide one reframe, then move on
- Don't create pressure tactics or false scarcity

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.