Handling Objections

Understanding Objections

Wrong Mindset: "Objections are obstacles to overcome" Right Mindset: "Objections are questions that need answers"

Truth: When someone objects, they're still engaged. Silence is worse than objections.

What Objections Really Mean

They SayThey Often Mean
"It's too expensive""I don't see enough value yet"
"I need to think about it""I'm not confident in this decision"
"Let me talk to my team""I'm not the sole decision-maker" or "I need an excuse to delay"
"We're happy with current solution""You haven't shown me why change is worth the hassle"
"I need more time""I'm afraid of making wrong decision" or "Not urgent enough"
"Can you send me information?""I want to get rid of you politely" or "I'm early in research"

Key Insight: Address the underlying concern, not just the surface objection.

The Four Types of Objections

1. Lack of Need

"We don't need this"

Real Issue: They don't see the problem or its impact

Response Strategy:

  • Ask deeper questions about their situation
  • Highlight costs of current approach
  • Show what they're missing
  • Provide industry benchmarks

Example:

Them: "We don't really need this right now."

You:  "I understand. Can I ask - how are you currently handling [process]?"
      [Listen]
      "And how much time does that take?"
      [Listen]
      "What would you do with an extra [X] hours per week?"

2. Lack of Trust

"I'm not sure about this" / "How do I know it works?"

Real Issue: They don't trust you, your company, or the solution

Response Strategy:

  • Provide social proof
  • Offer guarantees or trials
  • Share specific case studies
  • Connect them with reference customers
  • Reduce risk

Example:

Them: "How do I know this will actually work for us?"

You:  "Fair question. Let me share what [similar company] experienced...
      [Tell specific story with metrics]
      Would it help to talk to them directly? I can introduce you."

3. Lack of Urgency

"We'll think about it" / "Let's revisit this next quarter"

Real Issue: Problem isn't painful enough to act now

Response Strategy:

  • Quantify cost of waiting
  • Create honest urgency
  • Highlight opportunity cost
  • Show what happens if they don't act

Example:

Them: "Let's revisit this next quarter."

You:  "Of course. Can I ask - the [problem] we discussed, is that 
      getting better or worse over time?"
      [Listen]
      "So if we wait 3 months, that's [X cost] in continued impact.
      What would make it worth addressing sooner?"

4. Lack of Budget

"We can't afford this"

Real Issue: Usually value hasn't been proven, or budget exists but allocated elsewhere

Response Strategy:

  • Reframe as investment, not cost
  • Show ROI clearly
  • Offer payment options
  • Compare to cost of problem

Example:

Them: "We don't have budget for this."

You:  "I appreciate that. Just to understand - is it that budget 
      doesn't exist at all, or it's allocated to other priorities?"
      
      [If no budget exists]:
      "When does your next budget cycle start? And what would need 
      to be true for this to make it into that budget?"
      
      [If allocated elsewhere]:
      "Given that you're currently spending [X] on [current approach]
      with [results], would it make sense to redirect some of that 
      to something that delivers [better results]?"

The Objection Handling Framework

Step 1: Listen Completely

Don't:

  • Interrupt
  • Jump to response
  • Get defensive
  • Dismiss their concern

Do:

  • Let them finish completely
  • Take notes
  • Show you're listening (nod, "I see")
  • Pause before responding

Step 2: Acknowledge and Validate

Phrases:

  • "That's a fair concern"
  • "I understand why you'd think that"
  • "That makes sense"
  • "I appreciate you bringing that up"
  • "Other clients have felt the same way"

Purpose: Show respect, reduce defensiveness, build rapport

Example:

Them: "This seems too complicated for our team."
You:  "I completely understand that concern. Ease of use is critical, 
      and you know your team best."

Step 3: Clarify

Ask questions to understand the real concern:

  • "Can you tell me more about that?"
  • "What specifically concerns you about [objection]?"
  • "Help me understand - what makes you feel that way?"
  • "Is that the only concern, or are there others?"

Purpose: Uncover the real objection underneath

Example:

Them: "It's too expensive."
You:  "I understand. Can I ask - compared to what are you measuring 
      the price?"
      OR
      "What budget range were you thinking?"
      OR
      "Is it the absolute price, or the value relative to price?"

Step 4: Respond with Evidence

Provide specific answer backed by:

  • Data and statistics
  • Customer stories
  • Demonstrations
  • Guarantees or risk-reversals

Not:

  • Vague claims
  • "Trust me"
  • Attacking their logic
  • Pressure tactics

Step 5: Confirm Resolution

Check if you've addressed it:

  • "Does that address your concern?"
  • "How does that sound?"
  • "Does that make sense?"
  • "What else would you need to know about this?"

Don't move forward until concern is resolved.

Common Objections and Responses

"It's too expensive"

Poor Response:

"But think of all the money you'll save!"
[Defensive, generic, unpersuasive]

Better Response:

"I understand price is a consideration. Can I ask - what are you 
comparing this to?"

[Listen]

"Based on what you shared earlier, you're currently spending 
[X hours/dollars] on [current approach]. Over a year, this actually 
costs less than continuing the current way, plus you get [specific 
benefits].

Does that way of looking at it make sense?"

Framework:

  1. Acknowledge
  2. Clarify what "expensive" means to them
  3. Reframe as investment with ROI
  4. Show cost comparison
  5. Confirm understanding

"I need to think about it"

Poor Response:

"What's there to think about? Let's just do it!"
[Pushy, dismissive of their process]

Better Response:

"Absolutely, this is an important decision. Can I ask - what 
specifically would you like to think about?"

[Listen - they'll usually tell you the real objection]

"Those are great points to consider. To help you think through 
it, what information would be most useful?"

[Provide that information]

"When would make sense to reconnect after you've had time to 
think?"

[Schedule specific follow-up]

Framework:

  1. Acknowledge their need for time
  2. Uncover what they're really uncertain about
  3. Address those specific concerns
  4. Set concrete next step

"We're happy with our current solution"

Poor Response:

"But ours is so much better!"
[Forces them to defend their choice]

Better Response:

"That's great to hear - having a solution that works is important.
Can I ask what you like most about it?"

[Listen]

"Those are good points. Out of curiosity, is there anything about 
it that could be better?"

[Listen - they'll often reveal pain points]

"I see. The reason I ask is that many of our customers were in 
similar situations - satisfied but not delighted. When they saw 
[specific advantage], they realized what they were leaving on the 
table.

Would it be worth 15 minutes to see if there's opportunity for 
improvement?"

Framework:

  1. Respect their current choice
  2. Find what they value
  3. Identify gaps or frustrations
  4. Show what better looks like
  5. Low-commitment next step

"Send me some information"

Poor Response:

"Sure, I'll email you our brochure!"
[Dead end, they'll never respond]

Better Response:

"I'd be happy to send relevant information. To make sure I send 
you what's most useful, can I ask a few quick questions?"

[Ask 2-3 qualifying questions]

"Based on that, I'll send you [specific information]. Can we 
schedule 15 minutes next week to discuss after you've had a chance 
to review it?"

[Schedule the call before sending anything]

Framework:

  1. Use it as opportunity to qualify
  2. Send only relevant information
  3. Schedule follow-up BEFORE sending
  4. Make information specific to them

"I need to talk to my team/boss/partner"

Poor Response:

"Well, can't you just decide?"
[Dismisses their organizational reality]

Better Response:

"That makes complete sense - this affects more than just you. 
A few questions to help with that conversation:

1. Who specifically needs to be involved in the decision?
2. What concerns will they likely have?
3. What information would be most helpful for them?

Would it make sense for me to join that conversation, or would 
you prefer to discuss it internally first?"

Framework:

  1. Acknowledge their decision process
  2. Identify all decision-makers
  3. Anticipate their concerns
  4. Provide materials for them to share
  5. Offer to present to group

"We don't have time to implement this"

Poor Response:

"It's really quick and easy!"
[Dismisses their legitimate concern]

Better Response:

"I appreciate that concern - your time is valuable. Can I ask 
how much time you're currently spending on [problem]?"

[Listen]

"So [X hours] per week. Our implementation typically takes 
[Y hours] total, which means you break even in [timeframe], then 
save [Z hours] every week after that.

Would it make sense to invest [Y hours] once to save [Z hours] 
permanently?"

Framework:

  1. Acknowledge time constraints
  2. Quantify current time spent on problem
  3. Show implementation time is investment
  4. Calculate break-even and ongoing savings
  5. Reframe as time-saver, not time-drain

"We've tried something like this before and it didn't work"

Poor Response:

"Well, ours is different!"
[Vague and unconvincing]

Better Response:

"I'm sorry to hear that - failed implementations are frustrating 
and expensive. Can you tell me more about what you tried and why 
it didn't work?"

[Listen carefully]

"I understand why you'd be hesitant. The reason that failed was 
likely [specific reason]. We've seen that too, which is why we 
[specific difference in approach].

Would you be open to seeing how we avoid that issue?"

Framework:

  1. Empathize with past failure
  2. Understand what went wrong
  3. Explain specific differences
  4. Show how you prevent those issues
  5. Offer proof (case study of similar situation)

Advanced Objection Techniques

The Boomerang Technique

Turn objection into a reason to buy

Example:

Them: "This seems too advanced for our needs."
You:  "That's actually exactly why it makes sense - you can start 
      simple with just the features you need now, but you won't 
      outgrow it as you scale. Many customers wish they'd chosen 
      something that could grow with them."

The Question Technique

Respond to objection with a question

Example:

Them: "We need something cheaper."
You:  "I understand budget is important. Can I ask - if price 
      weren't a factor, would this solve your problem?"
      
      [If yes]: Now we're talking about value, not just price
      [If no]: We discovered the real objection

The Feel-Felt-Found Method

Empathize, normalize, provide evidence

Structure:

"I understand how you FEEL.

Other customers FELT the same way.

What they FOUND was [positive outcome]."

Example:

Them: "I'm worried this will be too complicated to use."

You:  "I understand how you feel - nobody wants to struggle with 
      new software.
      
      Many of our customers felt exactly the same way before they 
      started.
      
      What they found was that most people are productive within 
      the first hour, and our support team is there to help whenever 
      needed. Would you like to try it yourself for 10 minutes right 
      now to see?"

The Isolation Technique

Confirm this is the only objection

Example:

Them: "I'm concerned about implementation time."

You:  "I understand. If I can show you how implementation takes 
      less time than you think, is there anything else that would 
      prevent you from moving forward?"

[If yes]: Now you know all objections
[If no]: You can focus on this one issue

The Reframe Technique

Change the perspective on the objection

Example:

Them: "This is a big investment."

You:  "You're right, it is. Let me reframe that - it's actually 
      a bigger investment to continue with the current approach.
      You're spending [X] per month in [time/cost/lost opportunity].
      Over a year, that's [Y], which is [Z times] more than this 
      solution costs.
      
      The real question is: can you afford NOT to invest in solving 
      this?"

When to Walk Away

Red Flags

Some objections indicate you should walk away:

1. Values Misalignment

  • Want you to lie or mislead
  • Asking for unethical practices
  • Treating you disrespectfully

2. Unrealistic Expectations

  • Want guarantees you can't provide
  • Expecting results that aren't possible
  • Won't listen to expert guidance

3. Chronic Objections

  • New objection every time you address one
  • Moving goalposts constantly
  • Using objections to avoid decision

4. Bad Fit

  • Genuinely not right for your solution
  • Better served by competitor
  • Can't actually help them succeed

How to Walk Away Gracefully:

"Based on our conversation, I don't think we're the right fit for 
your situation. Here's why: [specific reason].

I'd recommend [alternative solution/competitor] instead - they 
specialize in [what you need].

If your situation changes to [what would make them a fit], I'd 
love to reconnect. In the meantime, I wish you the best."

Benefits:

  • Preserves your reputation
  • Saves both parties' time
  • They might refer right-fit customers
  • Might come back when situation changes

Practice Exercises

Exercise 1: Objection Bank

Create a document with:

  • 10 most common objections you hear
  • Your response for each using the 5-step framework
  • Evidence/stories to support each response

Exercise 2: Role Play

With a colleague, practice handling objections:

  • They throw objections at you
  • You use the framework to respond
  • They give feedback on what felt natural vs. scripted

Exercise 3: Record and Review

Record your next 5 sales calls (with permission). Note:

  • What objections came up
  • How you handled them
  • What worked and what didn't
  • What you'd do differently

Exercise 4: Clarifying Questions

For each common objection, write 3 clarifying questions that uncover the real concern.

Example: Objection: "It's too expensive" Questions:

  1. "Compared to what?"
  2. "Is it the total price or the pricing model that concerns you?"
  3. "If we could show ROI in [timeframe], would that change things?"

Summary

Key Takeaways:

  1. Objections are buying signals - they're still engaged
  2. Most objections are really questions in disguise
  3. Listen, acknowledge, clarify, respond, confirm
  4. Address the underlying concern, not just surface objection
  5. Some objections mean you should walk away

Objection Handling Checklist:

  • [ ] Let them finish speaking completely
  • [ ] Acknowledge and validate concern
  • [ ] Ask clarifying questions
  • [ ] Identify objection type (need/trust/urgency/budget)
  • [ ] Respond with specific evidence
  • [ ] Confirm resolution before moving on
  • [ ] Use feel-felt-found for emotional concerns
  • [ ] Isolate to find all objections
  • [ ] Know when to walk away

Common Mistakes:

  • ❌ Interrupting or getting defensive
  • ❌ Dismissing their concern
  • ❌ Generic, vague responses
  • ❌ Applying pressure instead of providing information
  • ❌ Not confirming resolution
  • ❌ Creating objections by talking too much

Response Framework:

1. LISTEN (fully, without interrupting)
2. ACKNOWLEDGE ("That's a fair concern...")
3. CLARIFY ("Tell me more about...")
4. RESPOND (with evidence)
5. CONFIRM ("Does that address your concern?")

Next Steps:

  • Build your objection response bank
  • Practice the 5-step framework
  • Record yourself handling objections
  • Move to Chapter 07 to learn closing techniques