objection-handler

What it does and when to use it

Build and use objection response playbooks - price, security, integration, competition, status quo. Use to prepare answers and battlecards for sales conversations.

How it works

1. Overview
2. Response framework (AER)
3. Objection families
4. Battlecards
5. Workflow
6. Rules

---
name: objection-handler
description: Build and use objection response playbooks - price, security, integration, competition, status quo. Use to prepare answers and battlecards for sales conversations.
metadata: {"navin":{"emoji":"🛡️","category":"sales"}}
---

# Objection Handler

## Overview

Objections are requests for reassurance, rarely rejections. Prepare structured responses per objection family, grounded in real proof.

## Response framework (AER)

**Acknowledge** (never argue) → **Explore** ("qu'est-ce qui vous fait dire ça ?") → **Respond** with proof → confirm.

## Objection families

| Family | Real question | Response assets |
|--------|---------------|-----------------|
| Price ("trop cher") | "quelle valeur pour ce prix ?" | ROI calc, cost-of-inaction, options (`pricing-assistant`) |
| Security/data | "puis-je vous faire confiance ?" | architecture note, hosting location, compliance, références |
| Integration | "ça va casser mon existant ?" | integration map, phased plan, pilot offer |
| Competition ("X fait pareil") | "pourquoi vous ?" | battlecard: honest diff, where we win, where they win |
| Status quo ("on gère en interne") | "le changement vaut-il l'effort ?" | cost of current state chiffré, migration path |
| Timing ("plus tard") | "pas prioritaire" | trigger tie-back, cost of delay, low-commitment first step |

## Battlecards

Per competitor, kept in `sales/battlecards/<name>.md` (fed by `competitor-intelligence`): their pitch, real strengths, weaknesses (from reviews), landmine questions to plant, our winning story.

## Workflow

1. Collect objections actually heard (`discovery-call-assistant` notes) - build the playbook from reality.
2. Draft AER responses with the user; attach proof per response.
3. Before key meetings: brief with the 3 most likely objections + responses.
4. After losses: log which objection killed it → strengthen that response or the product story.

## Rules

- Honesty wins: concede real limitations and reframe - bullshit detected = deal dead.
- Price objections are never answered with an instant discount.

Versions

Database snapshot: 13.11.2026 · package version a4d07f78c0f3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100objection-handling
  Use when the user wants to handle sales objections or build objection and competitor battlecards — structured responses to the pushback that stalls deals. Also use when the user mentions objections, objection handling, "it's too expensive," competitor comparison, battlecards,…
• 100objection-handling
  Build comprehensive objection handling playbooks — 6-category taxonomy, AER framework, battlecards per competitor, pre-handling in outreach. Use when creating objection responses, building an objection playbook, or preparing reps for tough conversations. Triggers on: "objection…
• 100sales-objection-handling
  Diagnoses what a sales objection really means and writes rebuttal scripts a rep can say out loud, or calls the deal dead when the objection is a real constraint. Covers price/budget, timing, competitor/incumbent, authority, status-quo, and trust objections for B2B and B2C, with…
• 100pm-objection-handler
  Objection handling playbook organized by category. Teaches reps to diagnose the real concern behind the stated objection and respond with evidence, not clever comebacks. Use when someone says "objection handling", "how do we respond when they say", "too expensive", "competitor…
• 100objection-handling
  Handles B2B sales objections with the acknowledge, clarify, respond, confirm method and ready-made responses for price, timing, competitors, no budget, building in-house, status quo and brush-offs, live or in email replies. Use when the user asks "how do I respond to this…
• 100objection-handling
  Handle sales objections using tactical empathy. Use when the user says "how do I handle this objection", "prospect said [X]", "they pushed back on price", "they said they're not ready", "how to respond to 'we already have a solution'", "they said 'send me more information'",…