objection-handling

star 0

Use this skill when teaching, evaluating, or demonstrating objection handling techniques. Invoke when user asks about overcoming objections, dealing with resistance, handling pricing concerns, competitive objections, or when providing feedback on how objections were addressed during roleplay or demo.

hbs-1991 By hbs-1991 schedule Updated 3/4/2026

name: Objection Handling description: Use this skill when teaching, evaluating, or demonstrating objection handling techniques. Invoke when user asks about overcoming objections, dealing with resistance, handling pricing concerns, competitive objections, or when providing feedback on how objections were addressed during roleplay or demo.

Objection Handling

Overview

Objections are buying signals — they mean the prospect is engaged enough to voice concerns. Effective objection handling doesn't "overcome" resistance; it explores the underlying concern and addresses it collaboratively. The best salespeople welcome objections and use them to deepen understanding and build trust.

Response Frameworks

AER: Acknowledge — Explore — Respond

  1. Acknowledge — Show you heard and respect the concern ("That's a fair point...")
  2. Explore — Ask questions to understand the real objection ("Help me understand — when you say too expensive, compared to what?")
  3. Respond — Address the specific, real concern with evidence or reframing

FFF: Feel — Felt — Found

  1. Feel — "I understand how you feel..."
  2. Felt — "Other [role] in [industry] felt the same way..."
  3. Found — "What they found was..."

Best for emotional objections. Use sparingly — can feel formulaic if overused.

Isolate and Address

  1. "Other than [objection], is there anything else holding you back?"
  2. Isolate the real blocker from the list of concerns
  3. Address the isolated objection specifically

Common B2B Objections and Responses

Price Objections

"It's too expensive"

  • Explore: "Compared to what?" / "What's your budget range?" / "What ROI would make this worthwhile?"
  • Respond: Reframe as cost of inaction, break down to per-user/per-day, quantify the problem cost
  • Never: Immediately offer a discount

"We don't have budget"

  • Explore: "Is this a timing issue or a priority issue?" / "If budget weren't a constraint, would this be the right solution?"
  • Respond: Help them build a business case, offer phased implementation, suggest budget reallocation

Competitor Objections

"We're already using [competitor]"

  • Explore: "How's that working for you?" / "What would you change about your current solution?"
  • Respond: Don't bash competitors. Focus on gaps they've identified, share relevant case studies
  • Key: Find the pain they haven't solved yet

"We're evaluating other solutions"

  • Explore: "What criteria are most important to you?" / "What would make one solution stand out?"
  • Respond: Align to their criteria, offer to help define evaluation framework, suggest a pilot

Timing Objections

"Not right now" / "Let's revisit next quarter"

  • Explore: "What changes next quarter?" / "What's the cost of waiting?"
  • Respond: Quantify the cost of delay, connect to upcoming business events, offer a low-commitment next step
  • Key: Create urgency without pressure

"Send me a proposal and I'll review it"

  • Explore: "I'd be happy to — what specifically would you want to see in it?" / "Who else would review it?"
  • Respond: Never send a proposal without a follow-up meeting booked. Proposal = conversation, not document.

Authority Objections

"I need to check with my boss"

  • Explore: "What do you think they'll focus on?" / "Would it help if I joined that conversation?"
  • Respond: Equip your champion with ammunition (ROI summary, case study), offer to present directly

"This is a committee decision"

  • Explore: Map the committee: "Who's involved? What does each person care about?"
  • Respond: Tailor materials for each stakeholder, offer individual meetings

Trust Objections

"We've been burned before by solutions like this"

  • Explore: "What happened? What would be different this time?"
  • Respond: Acknowledge their experience, offer risk mitigation (pilot, guarantee, phased rollout), share relevant references

Common Mistakes

  1. Arguing with the objection — you win the argument, lose the sale
  2. Answering before understanding — the stated objection is rarely the real one
  3. Offering discounts at the first price objection — devalues your product and trains the buyer to negotiate harder
  4. Ignoring objections — hoping they'll go away; they won't
  5. Taking objections personally — they're about the deal, not about you
  6. Over-handling — sometimes a brief acknowledgment is enough

Practice Scenarios

  1. Price negotiation — Prospect says "Your competitor is 40% cheaper." Handle without discounting.
  2. Stall tactic — VP of Sales says "Great demo, send me a proposal and we'll circle back." Prevent the stall.
  3. Hidden objection — Prospect keeps raising minor concerns. Uncover the real blocker.

Evaluation Criteria

Criteria Score Range Description
Active Listening 0-20 Did they fully hear and acknowledge the objection?
Exploration 0-25 Did they uncover the real concern behind the stated objection?
Response Quality 0-25 Was the response specific, evidence-based, and non-argumentative?
Outcome 0-15 Did the conversation move forward after the objection?
Composure 0-15 Did they stay calm, confident, and non-defensive?

Scoring Guide:

  • 0-40: Needs work — arguing, ignoring, or folding on objections
  • 41-70: Developing — acknowledges well but shallow exploration or weak responses
  • 71-90: Proficient — uncovers real objections, responds with confidence and evidence
  • 91-100: Expert — transforms objections into buying momentum
Install via CLI
npx skills add https://github.com/hbs-1991/sales-coach --skill objection-handling
Repository Details
star Stars 0
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator