skills/by-role/sales/objection-handling/SKILL.md
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'", "objection response", "they went dark after the proposal", "how to handle 'we don't have budget'", or wants to craft a response to a specific sales objection.
npx skillsauth add qa-aman/claude-skills objection-handlingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Based on "Never Split the Difference" by Chris Voss. Voss, former FBI lead hostage negotiator, argues that rational argument rarely moves people in high-stakes conversations - emotional acknowledgment does. His Tactical Empathy framework - labeling emotions, using calibrated questions, and getting the prospect to say "that's right" - is directly applicable to sales objections. The goal is not to counter the objection. The goal is to make the prospect feel heard, then redirect.
Before responding, classify the objection. Different types require different responses.
| Type | What it sounds like | What it usually means | |---|---|---| | Smokescreen | "Send me more info" / "We'll revisit next quarter" | They don't see enough value yet or don't want to say no | | Genuine concern | "We're worried about integration complexity" | A real blocker that needs a real answer | | Stall | "We're not ready to make a decision right now" | Stakeholder alignment is incomplete internally | | Price | "This is more than we expected / budgeted" | Value hasn't been established relative to cost | | Competitor | "We're also looking at [competitor]" | You haven't differentiated clearly enough |
Responding to a smokescreen with a feature argument makes it worse. Classify first.
Voss's core move: name what you think the prospect is feeling. This is a "label." It starts with "It seems like..." or "It sounds like..." - never "I feel like you..."
A label does two things: it makes the prospect feel understood, and it invites them to correct you if you're wrong. Either way, you learn more.
Examples:
Pause after the label. Do not fill the silence. Let them respond.
After the label, ask an open-ended question that starts with "What" or "How." Avoid "Why" - it sounds accusatory.
Examples by objection type:
Do not answer your own calibrated question. Ask it and stop.
"We don't have budget." "It sounds like budget is a real constraint right now. What would the ROI need to look like for this to be justifiable to your finance team?" - then build the business case together.
"We already have a solution." "It sounds like you've invested in this area before. What's working well with what you have, and where does it still fall short?" - this reveals the gap your product fills without attacking their current choice.
"Send me more information." "It sounds like there's something specific that's still unclear. What would be most useful for me to address?" - never send a generic one-pager in response to this.
"We're not ready yet." "It sounds like the timing isn't quite right. What needs to happen internally before this becomes a priority?" - surfaces the real blocker and gives you a re-engagement trigger.
"Your price is too high." "It seems like the investment is higher than you expected. How far apart are we?" - get the number. Then: "What would you need to see to make the difference feel justified?"
Voss's key indicator that you've succeeded: when the prospect says "that's right" - not "you're right." "You're right" means they're placating you. "That's right" means they feel understood.
Before moving forward, summarize their position back to them completely and accurately. Include their concerns, their constraints, and their goals.
"So if I'm hearing you correctly - the value is there, but the timing is the issue because [X] is happening this quarter, and you'd want to revisit in [month] once [condition]. Is that right?"
Wait for their confirmation before advancing.
1. Immediately counter-arguing Bad: "I understand budget is tight, but if you look at the ROI..." Good: Label the emotion first. "It sounds like budget is a real constraint right now." Then pause.
2. Sending more material in response to "send me more info" Bad: Sending a 20-page deck in response to "send me more information." Good: Ask what specifically is unclear. The request for info is almost always a soft no in disguise.
3. Accepting the stated objection at face value Bad: Taking "we already have a solution" as a closed door. Good: "It sounds like you've invested in this area before. What's working well, and where does it still fall short?"
4. Pushing for a close during the objection conversation Bad: "So based on all that, are you ready to move forward?" Good: Get to "that's right" first. Confirm next steps only after full acknowledgment.
development
Plan a webinar end-to-end using April Dunford's Obviously Awesome positioning framework to find the topic angle that makes the webinar obviously valuable to the right audience. Produces topic positioning, abstract, speaker brief, registration page, promotion sequence, day-of run-of-show, and post-webinar follow-up. Use when the user asks to plan a webinar, virtual event, online workshop, "we need a webinar on X", host a webinar, online masterclass, or any live virtual event with promotion and follow-up. Reads ICP, services, and brand voice from knowledge/.
development
Write long-form thought leadership articles, opinion pieces, industry POV essays, and CEO/founder bylines using the Made to Stick SUCCESs framework (Chip and Dan Heath). Use when the user asks for a long-form article, executive byline, opinion piece, industry POV, manifesto, "explain our point of view on X", or wants to publish an authority-building piece (1200-2500 words). Reads brand voice and positioning from knowledge/.
development
Plan a monthly content calendar across channels using the Content Marketing Matrix (Dave Chaffey, Smart Insights) - Entertain/Inspire/Educate/Convince. Every post gets a quadrant label. The monthly calendar must hit 40% Educate, 40% Inspire+Convince, 20% Entertain. Produces a week-by-week posting schedule with topics, formats, channels, and asset links. Use when the user says "content calendar", "social calendar", "plan next month's content", "what should we post", "content plan", "editorial calendar", "schedule posts for the month", or wants a structured posting plan for LinkedIn, Twitter, email, or blog. Reads brand voice, ICP, and past learnings from knowledge/.
development
Write SEO-optimized long-form articles targeting specific keywords using the They Ask You Answer Big 5 framework (Marcus Sheridan). Articles are categorized by Big 5 type (Cost, Problems, Versus, Best/Reviews, How-To) and structured accordingly. The "answer first" rule applies to every article. Use when the user asks for an SEO article, blog post for ranking, "rank for keyword X", organic content, search-optimized post, pillar page, or content for organic traffic. Includes keyword targeting, search intent matching, internal linking suggestions, and meta tags.