objection-handling-playbook

Imported from noahatcheckpoint/gtm-skills (skills/objection-handling-playbook/SKILL.md). Install upstream with npx skills add noahatcheckpoint/gtm-skills --skill objection-handling-playbook. Copyright stays with the author (MIT).

Objection Handling Playbook

Produces a practical playbook covering the objections your buyers actually raise, grouped by type, each with what it usually means, the questions that uncover the real concern, a short talk track, the proof that backs it, and when to walk away. It is built for live calls, not for memorising scripts.

When to use

• Reps hear the same objections and answer them differently, or not at all.
• Deals stall after "we need to think about it" or "it is too expensive."
• A price increase, new packaging, or new competitor is changing the conversation.
• New sellers need to ramp quickly on how buyers push back.
• Win-loss notes keep citing the same reasons.

What you need

Ask for these before writing:

1. Product and offer: what you sell, pricing model, typical deal size.
2. Buyer roles usually involved.
3. The objections themselves, ideally verbatim from calls, emails, or loss notes. If none are available, offer a standard set and ask the user to confirm which ones they really hear.
4. Proof available: customer stories, metrics, references, security documents, guarantees, trial options.
5. Main alternatives buyers consider, including doing nothing.
6. Constraints: discount authority, terms you cannot change.

Process

1. Collect and group objections by root type. Most fall into a handful of families:
   • Value or price ("too expensive," "no budget").
   • Need or priority ("not a priority," "we are fine as is").
   • Timing ("come back next quarter").
   • Trust or risk ("you are too small," "security concerns," "never heard of you").
   • Authority or process ("I need to check with my boss," "procurement takes months").
   • Competition and status quo ("we already use X," "we can build it ourselves").
2. Rank by frequency and deal impact. Write full entries for the top eight to twelve; list the rest briefly.
3. Diagnose what each objection usually means. "Too expensive" may mean the value is unclear, the budget sits elsewhere, the scope is wrong, or the buyer is negotiating. The same words need different responses, so every entry starts with diagnosis.
4. Use a consistent response pattern that reps can apply to any objection:
   • Acknowledge: show you heard it without arguing ("That is fair to raise").
   • Explore: ask one or two questions to find the real concern.
   • Check scope: ask whether this is the only thing standing in the way, so you do not answer one concern only to meet the next.
   • Respond: address the real concern with a specific point and proof.
   • Confirm: ask whether that resolves it, then agree a next step.
5. Write talk tracks short enough to say aloud. Two to four sentences, conversational, in the rep's own voice. Offer one alternative phrasing for different personalities.
6. Attach proof to every response. A relevant customer result, a reference offer, a document, or a low-risk next step such as a scoped pilot. Responses without proof sound like opinion.
7. Add prevention. Many objections can be addressed before they are raised: surface implementation effort in discovery, bring security documents early, quantify the cost of inaction before price comes up. Note for each objection where in the process it is best prevented.
8. Define walk-away signals. If there is genuinely no problem, no budget path, or no fit, the right move is to disqualify gracefully and leave the door open.
9. Add practice drills. For the top objections, include a role-play prompt with buyer variations (polite, hostile, vague) so reps can rehearse.

Output format

# Objection Handling Playbook: [Product]   Updated [date]

## Response pattern
Acknowledge, Explore, Check scope, Respond, Confirm.

## Objection index
| # | Objection | Family | Frequency | Best prevented at |

## Entries
### [Objection, in the buyer's words]
- What it usually means: [2 to 4 possible root causes]
- Diagnostic questions:
  - [ ]
- Talk track (if root cause is A):
  > [2 to 4 sentences]
- Talk track (if root cause is B):
  > [ ]
- Proof: [story, metric, document, offer]
- Prevent it by: [earlier action]
- Walk away if: [condition]

## Quick reference card
| Objection | One question to ask | One line to say | Proof |

## Practice drills
[role-play prompts with buyer variations]

Quality checklist

• Objections come from real buyer language where available.
• Every entry starts with diagnosis, not rebuttal.
• Each response includes a scope check and a confirmation step.
• Talk tracks are short enough to say naturally on a call.
• Every response cites concrete proof or a low-risk next step.
• Prevention points are mapped to the sales process.
• Walk-away conditions are honest and specific.
• Nothing is promised that the user said cannot be offered.

Common mistakes

• Rebutting before understanding. Answering "too expensive" with a discount when the real issue is unclear value trains buyers to push harder on price.
• Long scripted rebuttals. Buyers can hear a script. Short, specific, and conversational wins.
• Arguing with the buyer. "Actually, you are wrong" ends the conversation. Acknowledge first, always.
• Answering an objection the buyer did not raise. Over-explaining introduces doubts that were not there.
• Treating "send me information" as interest. It is often a polite exit. Ask what specifically they want to evaluate.
• Discounting as the default fix. Trade concessions for something (term length, case study, faster signature) or hold value.
• Never updating the playbook. New competitors and price changes create new objections every quarter.

Example prompts

• "Build an objection handling playbook from these 15 objections our reps logged last quarter."
• "Write talk tracks for 'we already use a competitor' and 'we can build this in house.'"
• "Our prices went up 20%. Prepare reps for the pushback."
• "Create a one-page objection quick reference card for new SDRs."
• "Give me role-play drills for handling timing objections with a skeptical CFO."