---
name: objection-handling-playbook
description: Build an objection handling playbook that turns common pushbacks into confident, non-defensive responses. Use this skill whenever a user wants help handling sales objections, needs rebuttals for price or timing or competitor concerns, wants an objection playbook or battle-tested responses, or says 'they said it is too expensive', 'how do I handle this objection', or 'prospects keep stalling'. Trigger whenever recurring objections are costing deals.
---

# Objection Handling Playbook

## What this does and why it matters
Objections are not rejections; they are requests for information or reassurance. Reps lose deals by getting defensive or discounting reflexively. This skill builds calm, structured responses that acknowledge the concern, reframe it, and advance the conversation, so the same objection stops killing deals.

## Inputs to gather
1. The objections that keep coming up (or the product and buyer, so common ones can be anticipated).
2. The real differentiators and proof points available.
3. Pricing flexibility and any hard lines.

## Method
For each objection, use the acknowledge, explore, reframe, advance pattern:
- **Acknowledge** the concern genuinely so the buyer feels heard, never argue.
- **Explore** to find the real objection underneath. "Too expensive" often means "I do not see the value yet" or "I cannot get budget approved", which need different responses.
- **Reframe** around value, risk, or cost of inaction, using a proof point.
- **Advance** with a question that moves forward.

Cover the recurring categories: price, timing ("not now"), authority ("I need to check with"), competition, status quo ("we do it in-house"), and trust ("how do I know this works"). For each, write the surface objection, the likely real concern, and a response that is confident without being pushy.

## Output format
ALWAYS use:

# Objection Playbook: [Product / Buyer]
For each objection:
### Objection: "[what they say]"
- Likely real concern: [...]
- Response (acknowledge / explore / reframe / advance): [...]
- Proof point to deploy: [...]
- Question to advance: [...]
## Price objection deep dive (isolate, value-anchor, cost-of-inaction)
## When to walk away

## Anti-patterns to avoid
- Discounting the moment price comes up. It trains buyers to push and destroys margin.
- Arguing with the objection instead of exploring it.
- Canned rebuttals that ignore the specific buyer.
- Talking past the concern to relaunch the pitch.

## Example
For "we already do this in-house", the playbook identifies the real concern (sunk cost and change risk), reframes around the opportunity cost of tying up internal staff, and advances with "what would have to be true for it to be worth handing this off?"