How to Handle Objections in Sales Calls

Sean Linehan5 min read • Updated Oct 2, 2025
How to Handle Objections in Sales Calls

Mastering how to handle objections in sales calls makes the difference between average sellers and top performers. Simply put, getting good at handling pushback is one of the best ways to boost your sales success.

Most sales teams practice objection handling in training sessions, but when prospects raise concerns about price, timing, or product fit, unprepared salespeople resort to defensive responses or aggressive pushback.

This disconnect between preparation and performance costs businesses deals, erodes trust and derails conversations with prospects.

This article explores sales objections and how to handle them confidently during real conversations.

What Are Sales Objections?

Sales objections are concerns, questions, or hesitations that prospects express during the sales process that prevent immediate agreement or purchase. Understanding why objections occur helps you respond more effectively rather than defensively.

  • Fear of Loss (Loss Aversion) drives people to work harder avoiding a $100 loss than gaining $100. Your prospects might object because they fear making mistakes or wasting money on the wrong solution.

  • Status Quo Bias is our natural tendency to stick with current systems. When you hear "we're doing fine without it," prospects feel safer maintaining existing processes even when your solution offers clear improvements.

  • Cognitive Dissonance happens when new information conflicts with existing beliefs. Your prospects push back because your pitch challenges their current understanding, creating mental discomfort they resolve through objections.

These psychological factors explain why prospects object, but knowing the psychology won't help your team respond confidently under pressure. The ability to handle disagreements gracefully requires practice in realistic scenarios.

4 Types of Sales Objections

Most objections fall into four buckets. Your team probably recognizes these patterns, but categorizing objections during real conversations requires split-second thinking that comes from experience.

1. Price and Budget Objections

A significant number of objections involve price. When someone says "too expensive" or "not in our budget," they often mean something deeper. Usually, they don't see enough value to justify the price.

Example: "This costs more than we planned to spend this quarter."

What they really mean: They haven't connected your price to enough value, or they're testing whether you'll negotiate.

2. Authority and Decision-Making Objections

These happen when prospects can't make the final decision or need approval from committees or bosses.

Example: "I need to run this by my boss before we can move forward."

What they really mean: You haven't found all the decision-makers, or the prospect needs more confidence to sell this internally.

3. Need and Value Objections

Prospects raise these when they don't see how your solution fixes their specific problems or creates meaningful value.

Example: "We're managing fine with our current approach."

What they really mean: You haven't found pain points big enough to justify change, or you haven't connected features to benefits they care about.

4. Timing and Urgency Objections

These come up when prospects see your solution's value but question whether now is the right time to make changes.

Example: "This sounds good, but let's revisit it next quarter."

What they really mean: Other priorities feel more important, or they don't feel urgent enough to act now.

The LISTEN Framework for Handling Sales Objections

The LISTEN method gives you structure for handling objections, but frameworks only work when responses become automatic. The key is practicing this framework until it becomes second nature, so you can use it confidently even when facing difficult prospects.

Listen Completely Without Interrupting

Let prospects finish expressing their concerns before you jump in. Real listening means focusing on them, taking notes, and watching for what they're not saying through their tone.

Don't plan your response while they're talking. Just listen completely. This shows respect and gives you better information about what's really bothering them.

Investigate with Strategic Questions

Ask questions to understand what's behind their objection. Try asking "why" several times to get to the real issue.

Here's how this sounds:

Prospect: "It seems too expensive."

You: "I understand price concerns. What part of the pricing feels too high?"

Prospect: "Well, it's more than we budgeted this quarter."

You: "What went into setting that budget amount?"

Through questions like these, you might learn the real objection involves timing, other priorities, or perceived value rather than price.

Sympathize and Validate Concerns

Show you understand their position after you get their objection. Validation means acknowledging that their concern makes sense from their perspective. You don't have to agree with their conclusion.

The "Feel, Felt, Found" method works well here:

"I understand how you feel about the timeline. Many current clients felt the same way at first. However, they found that with our support, the process went smoother than they expected."

Transform Objections with Tailored Solutions

Present solutions that address their specific concern. Connect particular features or benefits directly to what they objected to.

"While the upfront cost is $X, compare that to what you're spending on manual processes plus the opportunity cost of delayed market entry. You'd see positive ROI within six months."

Focus on turning objections into chances to highlight value that matters to their situation.

Engage for Commitment or Next Steps

Check whether you've handled their concern completely and ask for commitment to move forward.

"Does that address your concern about the timeline?"

After they confirm, suggest clear next steps instead of leaving things hanging: "Since we've solved that issue, should we schedule a technical review with your IT team next week?"

Note Objection Patterns for Improvement

Write down the objections you hear, how you responded, and what happened. This helps you prepare for similar objections later, spot patterns across prospects, and track how you're improving over time.

Teams using conversation practice build objection-handling playbooks that evolve based on what works and what doesn't.

17 Common Sales Objections and How to Handle Them

Here are proven responses to common objections. These work best when you practice them enough that they feel natural during real conversations.

1. "Your solution costs too much."

This objection rarely concerns the actual price. Usually, the prospect doesn't see enough value to justify your pricing, or they're testing whether you'll negotiate.

What to say:

"I get that budget matters. Let's look at this as an investment instead of an expense. Our clients typically see returns of [specific ROI] within [timeframe]. What specific concerns do you have about the investment?"

Practice this response until it becomes automatic under pressure. When adrenaline kicks in during hostile procurement reviews, conscious thinking shuts down. Conversation competency requires responses that feel natural even when fight-or-flight response activates.

2. "We don't have a budget for this right now."

The prospect might have genuine budget constraints, or they haven't prioritized your solution highly enough to allocate funds.

What to say:

"Budget timing makes sense. Help me understand your planning cycle. When do you typically look at investments like this? Meanwhile, let me share how delaying has affected similar companies."

Work on this response until it feels conversational. The key is respecting their budget process while gathering timing information and creating urgency around delay costs.

3. "I need to see better ROI before committing."

The prospect needs more concrete proof that your solution will deliver measurable returns on their investment.

What to say:

"ROI verification makes perfect sense. Let's build a custom analysis using your specific numbers. What outcomes would make this investment obviously worthwhile?"

Practice this collaborative approach. The key is showing willingness to prove value while getting them to define their success criteria.

4. "I need to discuss this with my team."

The prospect might need buy-in from others, or they're using this as a stalling tactic because they're not ready to decide.

What to say:

"Team input makes sense for decisions this important. Could you help me understand who else looks at this? Maybe we could address everyone's questions together and save time for everyone."

Master this response until you can naturally ask for inclusion rather than exclusion. Try to get included in the team discussion rather than being sidelined.

5. "My boss makes these decisions."

You're talking to someone without decision-making authority, and you need to connect with the actual decision-maker.

What to say:

"I appreciate you being upfront about the approval process. Would it make sense to include your boss in our next conversation? This way I can address questions directly and respect everyone's time."

Rehearse this until you can confidently ask for access to decision-makers. Always try to reach the real buyer rather than relying on internal selling.

6. "We have a committee that handles vendor selection."

Large organizations often have formal vendor evaluation processes that involve multiple stakeholders.

What to say:

"Committee processes make sure you evaluate things thoroughly. Could you walk me through their typical decision criteria? I'd like to prepare materials that address their specific concerns."

Practice gathering detailed process information. Understanding the committee's requirements helps you navigate their evaluation more effectively.

7. "I don't see how this helps us."

The prospect doesn't understand the value proposition or how your solution applies to their specific situation.

What to say:

"Let me ask about [specific pain point]. When that happens, what's the impact on your team? Our solution addresses that specifically by [detailed benefit with metrics]."

Rehearse this until you can quickly pivot to specific pain points. Make the value concrete and measurable rather than giving generic benefits.

8. "We tried something similar and it didn't work."

Past negative experiences make the prospect skeptical about trying another solution in the same category.

What to say:

"Previous experiences definitely influence decisions. What specifically didn't work about that solution? Our approach differs because [specific differentiator that addresses their past issue]."

Practice this empathetic response until it feels genuine. Acknowledge their experience, learn from it, then clearly differentiate your solution from what failed before.

9. "This isn't a good time."

The prospect might have competing priorities, resource constraints, or other timing issues.

What to say:

"Timing makes sense. What would make this a better time to move forward? I'd also like to share what we've learned about timing from similar companies."

Rehearse this balance between respecting their timing and creating urgency. Understand their constraints while showing the opportunity cost of delay.

10. "We already work with your competitor."

The prospect has an existing relationship with a competitor and might be satisfied with their current solution.

What to say:

"Many current clients previously used [Competitor]. What made them switch was [specific differentiator]. I'm curious what aspects of your current solution work well, and where you see room for improvement."

Rehearse this respectful competitive response. The key is to find gaps or areas for improvement rather than directly attacking the competitor.

11. "We're getting proposals from other vendors."

The prospect is evaluating multiple options and comparing different solutions.

What to say:

"Smart approach for important decisions. What criteria matter most in your evaluation? I'd like to make sure you have complete information about how we address those priorities."

Rehearse this collaborative evaluation approach. Help them compare options fairly while ensuring your solution gets proper consideration.

12. "I need to think about it."

This common stalling tactic often masks other concerns or objections the prospect hasn't expressed.

What to say:

"This decision deserves careful thought. To make sure I've given you complete information, what specific aspects would you like to think about further?"

Practice this probing response until you can uncover hidden objections naturally. The key is finding out what they're really concerned about rather than accepting the stall.

13. "We're not ready to make a decision."

The prospect acknowledges interest but isn't prepared to move forward immediately.

What to say:

"Decision timing makes sense. Help me understand what needs to happen before you're ready. Maybe I can provide resources that support your preparation process."

Practice understanding their decision process and finding ways to stay involved. The key is supporting their preparation rather than pushing for premature decisions.

14. "The economy is uncertain right now."

Economic concerns make the prospect hesitant to make new investments or commitments.

What to say:

"Economic uncertainty affects everyone's planning. Companies that invest strategically during uncertain times often gain competitive advantages. How might our solution help you navigate these challenges better?"

Rehearse positioning your solution as helping them succeed despite challenges. The key is addressing their concern while showing how you can help them through uncertainty.

15. "I don't have time to evaluate this properly."

The prospect feels too busy to give your solution the attention it deserves.

What to say:

"Time constraints are real. What would make evaluation easier for you? We can structure this process to minimize your time investment while ensuring you get the information you need."

Rehearse making the evaluation process feel manageable. The key is respecting their time while creating a path forward that works for their schedule.

16. "This seems too complicated for our team."

The prospect worries about complexity, training requirements, or user adoption challenges.

What to say:

"Complexity concerns make sense. Let me show you how simple the daily experience is for users. Most teams are productive within [specific timeframe] because [specific reason]."

Practice addressing complexity with specific examples of simplicity and quick adoption. The key is making implementation and daily use feel straightforward.

17. "We've had bad experiences with vendors like you."

Past negative vendor relationships create skepticism about working with new providers.

What to say:

"Bad vendor experiences definitely create hesitation. What specifically went wrong before? Here's how we ensure those issues don't happen, and here's what our clients say about working with us."

Rehearse this empathetic differentiation until it feels genuine. The key is acknowledging their concern, learning from their experience, then proving you're different with social proof.

Why Knowing What To Say Isn’t Enough

Here's why traditional objection-handling knowledge fails under pressure.

  • Real Objections Come With Unpredictable Variables. Prospects don't follow your scripts. They add tone, timing, and context that generic responses don't address. A simple "too expensive" objection might come from an angry procurement manager with budget constraints, a skeptical CEO comparing multiple options, or a friendly buyer testing your flexibility.

  • Stress Blocks Access to Memorized Information. I once watched a sales rep who knew fifteen different price objection responses freeze completely when a prospect said, "too expensive." In that moment, none of the memorized responses felt right. The rep knew what to say but couldn't access it under pressure.

  • Knowledge and Performance Require Different Brain Systems. Think about learning to drive. You can memorize traffic rules, but that won't help you react quickly when someone cuts you off. Conscious knowledge gets overwhelmed during high-stakes moments.

Objection handling requires split-second decision-making under pressure. Confidence comes from muscle memory, not memorized responses.

What Builds Objection Handling Skills

Here's what your team needs to develop confident objection handling under pressure:

  1. Realistic Practice Scenarios That Mirror Actual Sales Situations: Your reps need to practice with prospects who sound angry, impatient, or skeptical. They require scenarios with tight timelines, complex stakeholder dynamics, and unexpected combinations of objections.

  2. Unlimited Repetition Without Social Pressure: Traditional roleplay requires scheduling with colleagues who might judge poor performance. Teams need the ability to practice the same objection scenario multiple times until responses feel natural.

  3. Immediate Feedback on Performance: Reps need to know what worked and what didn't right after each practice session. This immediate feedback enables faster improvement cycles compared to waiting for manager coaching sessions.

  4. Safe Environment for Making Mistakes: Teams learn best when they can stumble through difficult objections without real business consequences. Making mistakes with prospects costs deals. Making mistakes during practice builds skills.

Master Objections Through Realistic Practice

Objection handling frameworks provide structure, but execution under pressure requires automatic responses built through realistic practice. 

Here's the test. If your reps can't handle the objection in casual conversation with a friend, they won't handle it with a prospect either. The solution is practice that feels as real as the actual conversation.

Ready to transform your team's objection handling from knowledge to confident execution? Book a demo to see how realistic roleplay builds the muscle memory necessary for consistent objection handling success.

Sean is the CEO of Exec. Prior to founding Exec, Sean was the VP of Product at the international logistics company Flexport where he helped it grow from $1M to $500M in revenue. Sean's experience spans software engineering, product management, and design.

Launch training programs that actually stick

AI Roleplays. Vetted Coaches. Comprehensive Program Management. All in a single platform.
©2025 Exec Holdings, Inc. All rights reserved.