sidchaudhary/gtm-skills / skills/account-executive/objection-handling
objection-handling
VerifiedTakes a product description, ICP and target persona and outputs the five most likely objections, each with a specific acknowledgment, a response, and the follow-up question that moves past it. Use when preparing for cold calls, onboarding a new rep, or building objection handling into a sequence before it launches. Boundary: this prepares responses in advance for a persona. `inbox-management` handles an objection that has already arrived in a real reply, and `price-negotiation` handles a live pricing or terms push on one deal.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.1 KB |
| references/house-rules.md | markdown | 13.3 KB |
| references/objection-handling.md | markdown | 6.8 KB |
| references/outbound-copy-standards.md | markdown | 15.5 KB |
references/objection-handling.md
View on GitHub# Objection Handling
Shared reference for any skill that answers buyer pushback: `objection-handling`,
`price-negotiation`, `sales-enablement`, and the sequence skills that build objection
handling into a touch.
The core claim: **objections are not one thing, and the same response shape cannot answer all of
them.** Most objection handling fails not because the answer was wrong but because it was the
wrong *kind* of answer, delivered at a length that signalled defensiveness.
---
## 1. Six types, six different answers
Classify the objection before writing a response. The type determines the mode; the mode
determines the length and the register.
| Type | Sounds like | What it actually is | Answer with | Length |
|---|---|---|---|---|
| **Practical** | "Does it integrate with X?" | A specification question | The spec, plainly. Yes, no, or the workaround. | One or two sentences |
| **Cost** | "It's too expensive" | A value-to-price comparison, or budget timing | Reframe against the cost of the status quo, or name the comparison they are actually making | Short. Long answers read as justification. |
| **Trust** | "How do I know this works?" | Risk of being wrong in front of others | Proof: a named customer, a number, a guarantee, a reversible first step | Medium, proof-dense |
| **Effort** | "We don't have time to implement this" | Fear of hidden work | Friction reduction: what you do, what they do, how long | Medium, concrete |
| **Identity** | "That's not how we do things" / "We're not that kind of team" | A self-image conflict | Autonomy-preserving language and self-consistency. Do not argue. | Shortest of all |
| **Timing** | "Let's revisit next quarter" | Either a real calendar constraint or a soft no | Find out which before answering. One question, not a response. | A question |
**The most common misclassification is treating a cost objection as a value objection.** "Too
expensive" sometimes means "I don't see the value" and sometimes means "I have no budget until
March." These need opposite responses, and guessing wrong wastes the exchange. Ask which it is.
**The second most common is answering an identity objection with evidence.** Evidence does not
move self-image, it entrenches it. When someone says "that's not how we operate," the reply is
about their autonomy and their own precedents, not about your product being good.
---
## 2. Rank by defensiveness, not by frequency
The instinct is to prepare for the objections heard most often. Those are usually the *easiest*
ones, which is exactly why they get voiced: an easy objection is safe to say out loud.
Rank instead by how much defensiveness the objection carries. Identity and trust objections rank
high: they are rarely stated plainly, they end deals quietly, and a rep who has not rehearsed them
will improvise badly under pressure. A practical integration question ranks low no matter how
often it comes up, because any rep can answer it cold.
A useful test: which objection, if handled badly, ends the deal without the prospect ever telling
you why? Prepare that one first.
---
## 3. Over-answering hardens the objection
The strongest predictor of a failed objection response is length. A long, thorough rebuttal reads
as defensiveness, and defensiveness confirms the prospect's suspicion that the concern is
well-founded.
Specific failure shapes:
- **Stacked reasons.** Giving four reasons the concern is unfounded is weaker than giving one. The
reader discounts the whole set and remembers that you had a lot to say.
- **Pre-emptive rebuttal of things they did not raise.** Answering the objection behind the
objection, unasked, tells them you have heard it many times before.
- **Winning the exchange.** A response that leaves the prospect wrong is a response they resent.
The goal is that the concern stops mattering, not that it is defeated.
- **Reassurance without substance.** "Don't worry, that's not an issue for our customers" invites
exactly one reply, and it is not agreement.
- **Mirroring the objection back as a question they must defend.** "Why do you say it's
expensive?" puts them on trial.
Practical ceiling: if a response runs longer than the objection did by more than about three to
one, cut it.
---
## 4. Preempt where the doubt actually appears
A playbook that only fires when an objection is spoken handles the minority of cases. Most
objections are never voiced; they are resolved silently against you.
Preemption means placing the answer at the point in the journey where the doubt naturally forms,
before anyone has to say it:
| Doubt forms at | Preempt in |
|---|---|
| Pricing page | The comparison framing and what the price replaces |
| Security or procurement mention | A trust page, not a sales reply |
| Implementation discussion | An explicit first-30-days breakdown |
| Second call, no champion yet | A reversible first step that does not need buy-in |
Preemption has a limit: **raising an objection nobody had plants it.** Preempt only the objections
that genuinely recur, and only where the doubt already exists at that step. Handling an
unprompted concern in a first cold touch manufactures resistance.
How many to preempt depends on stage: one at first touch, two or three mid-cycle, and at late
stage only the specific barrier left between them and a decision.
---
## 5. Response structure
Three parts, in order, and short:
1. **Acknowledge**, one sentence that shows the concern was heard. It must not agree, and it must
not concede. Banned openers, because they signal a script: "Great question", "I totally
understand", "That's a fair point", "I hear you."
2. **Answer**, in the mode the type calls for, at the length the type calls for.
3. **One question**, moves forward without pressure. Ends the turn on their side of the table,
which is what stops a response reading as a pitch.
Never stack a second ask onto the question. Never end an objection response with a calendar
request.
---
## 6. Check before returning
1. Is every objection classified by type, with the response mode matching that type?
2. Is any cost objection checked for whether it is a value problem or a budget-timing problem,
rather than assumed?
3. Is every identity objection answered with autonomy and precedent rather than with evidence?
4. Is any timing objection answered with a question that finds out whether it is real, rather than
with a rebuttal?
5. Are the objections ranked by defensiveness, with at least one that would end the deal silently,
rather than only the frequently voiced easy ones?
6. Is every response no more than roughly three times the length of the objection?
7. Does every response give one reason rather than a stack of them?
8. Is every banned acknowledgment opener absent?
9. Does each response end with exactly one question, and no calendar ask?
10. For preemption: is every preempted objection one that genuinely recurs at that step, rather
than a doubt the copy would be introducing?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |