25 Common Sales Objections and How to Handle Each

Introduction: Why Objection Handling Separates Top Performers

Every salesperson faces objections. The difference between quota-crushing reps and those who struggle comes down to one skill: the ability to handle objections with confidence and turn resistance into opportunity.

After analyzing thousands of sales conversations, we've identified the 25 most common objections and developed proven response frameworks for each. These aren't theoretical scripts—they're battle-tested responses that top performers use daily.

We've organized these objections into five categories: Price, Timing, Competition, Authority, and Need. For each objection, you'll understand why prospects say it and exactly how to respond.

Price Objections

Price objections are the most common but rarely the real issue. When prospects say "it's too expensive," they're usually saying "I don't see enough value." Your job is to reframe the conversation around ROI and business impact. For a deeper dive on this specific objection, see our guide on "Your Price is Too High" — 7 Responses That Actually Work.

1. "Your price is too high"

Why they say it: They're comparing your price to their budget or a competitor's offering without fully understanding the value differential.

How to respond: "I appreciate you being direct about budget concerns. Help me understand—when you say the price is too high, are you comparing it to what you're currently spending, another solution you're considering, or the budget you had allocated? [Wait for response] What I've found with other [industry] companies is that when we look at the total cost of [problem], including [hidden cost 1], [hidden cost 2], and [opportunity cost], our solution actually reduces overall spend by [X%]. Would it be helpful if I walked through that analysis for your situation?"

2. "We don't have the budget"

Why they say it: Either the budget truly isn't allocated, or they haven't prioritized this initiative highly enough to find the money.

How to respond: "I understand budget constraints are real. Let me ask you this—if solving [their stated problem] could save you [specific amount] or generate [specific revenue], would that change the budget conversation? [If yes] That's exactly what we've helped companies like [similar customer] achieve. What would it take to make this a funded priority for this quarter?"

3. "Your competitor is cheaper"

Why they say it: They want you to justify the price difference or match the competitor's price.

How to respond: "You're right—[Competitor] does come in at a lower price point. Out of curiosity, what made you reach out to us if you already have a more affordable option? [Wait for response] That's exactly why our customers choose us despite the price difference. They've found that [specific differentiator] actually delivers [quantified benefit] that more than makes up the difference. Would you like me to connect you with [similar customer] who evaluated both options?"

4. "Can you give us a discount?"

Why they say it: They're negotiating, testing your flexibility, or trying to get more value for the same price.

How to respond: "I appreciate you asking directly. Our pricing reflects the value we deliver, and we've found that discounting actually does our customers a disservice because it would require us to reduce the support and success resources we provide. That said, I want to make this work. If budget is the constraint, we could look at [phased implementation / different package / extended payment terms]. What would be most helpful for your situation?"

5. "We need to cut costs right now"

Why they say it: The company is under financial pressure and all discretionary spending is being scrutinized.

How to respond: "I completely understand—many of our customers came to us specifically because they needed to reduce costs. Can I share what [similar company] did? They were in a similar situation and found that implementing [your solution] actually reduced their [specific cost category] by [X%] within [timeframe]. The investment paid for itself in [X months]. Would that kind of outcome be relevant to your cost reduction goals?"

Timing Objections

Timing objections often mask other concerns. When someone says "not right now," dig deeper to understand if it's truly a timing issue or something else entirely.

6. "This isn't a priority right now"

Why they say it: They have competing initiatives, or they don't see the urgency in solving this problem.

How to respond: "I hear that—there's always a lot competing for attention. Help me understand what is the top priority right now? [Wait for response] Got it. And how is [their stated problem] affecting your ability to achieve [that priority]? [If connected] That's actually why many of our customers decided to address this now—they found that [problem] was actually slowing down [priority]. [If not connected] Fair enough. When do you think this will move up the priority list, and what would trigger that?"

7. "Call me back next quarter"

Why they say it: They want to end the conversation without saying no, or there's genuinely a reason why next quarter is better.

How to respond: "I'm happy to follow up then. Before I put that on the calendar, help me understand what will be different next quarter? [Wait for response] Okay, so if [their condition] happens, you'd be ready to move forward? What would you need to see from us between now and then to be prepared to make a decision quickly when that time comes?"

8. "We just implemented a new solution"

Why they say it: They've recently invested in something else and aren't ready to consider alternatives.

How to respond: "Congratulations on getting that project done—implementations are a lot of work. I'm curious, how's it going so far? Are you seeing the results you hoped for? [If struggling] That's actually common in the first few months. What would it look like if you could [specific improvement your solution offers]? [If going well] That's great to hear. Many of our customers actually use us alongside [their solution] to [specific complementary benefit]. Would that be worth a quick conversation?"

9. "We're in the middle of [major initiative]"

Why they say it: They're genuinely overwhelmed with another project and can't take on anything else.

How to respond: "I don't want to add to your plate when you're focused on [initiative]. Quick question—is [your solution's problem area] part of that initiative, or separate? [If part of it] Then we should definitely talk, because [your solution] could actually accelerate what you're trying to do. [If separate] Understood. When does [initiative] wrap up? I'd like to reconnect then when you have bandwidth."

10. "We're not ready yet"

Why they say it: They need to complete certain steps before they can evaluate or implement a solution.

How to respond: "I appreciate your honesty. What needs to happen for you to be ready? [Wait for response] That makes sense. Just so I understand—is that a [1 month / 3 month / 6 month] timeline? And is there anything we could do now to help you get ready faster, or to make sure you have all the information you need when that time comes?"

Competition Objections

When prospects mention competitors, resist the urge to bash them. Instead, focus on your unique value and let the prospect draw their own conclusions. For more strategies on this topic, read How to Handle "We're Already Using a Competitor".

11. "We're already using [Competitor]"

Why they say it: They have an existing solution and see no reason to change or evaluate alternatives.

How to respond: "Got it—[Competitor] is a solid choice. Out of curiosity, what made you choose them originally, and how's it been working for you? [Wait for response] Interesting. The reason I'm reaching out is that companies who've been using [Competitor] for a while often tell us they struggle with [specific gap]. Is that something you've experienced? [If yes] That's exactly where we're different. Would it be worth 15 minutes to show you how?"

12. "We're evaluating several vendors"

Why they say it: They want you to know you have competition and may be using it as leverage.

How to respond: "That's smart—it's a significant decision. Who else is in the mix? [Wait for response] Good choices. What criteria are you using to evaluate them? [Wait for response] That's helpful. I want to make sure I'm focusing on what matters most to you. Of those criteria, which 2-3 are absolute must-haves versus nice-to-haves? [Then tailor your conversation to those priorities]"

13. "I've heard [Competitor] is better"

Why they say it: They've done research or heard from peers that a competitor has advantages.

How to respond: "I appreciate you sharing that. What specifically have you heard makes them better? [Wait for response] That's fair feedback. Here's what I'd suggest—[Competitor] is strong in [acknowledge their strength], and we're strong in [your differentiation]. The question is which of those matters more for your specific situation. Based on what you've told me about [their problem], would [your differentiation] be more valuable than [competitor strength]?"

14. "We have an existing contract with [Competitor]"

Why they say it: They're locked in and can't switch even if they wanted to.

How to respond: "Understood—contracts are contracts. When does your current agreement expire? [Wait for response] Okay. Two questions: First, are you happy enough with [Competitor] that you'll definitely renew, or is there a chance you'd look at alternatives? Second, some of our customers have found that the ROI from switching actually justified buying out their existing contract. Would you be open to exploring what that would look like if the numbers made sense?"

15. "We're going to build this in-house"

Why they say it: They believe they can create a better, cheaper, or more customized solution themselves.

How to respond: "That's an option. What's driving that decision—cost, control, customization, or something else? [Wait for response] I ask because we've had several customers who started down that path and ended up choosing us instead. They found that by the time they factored in [development time, opportunity cost, maintenance, and iteration], the build option was actually more expensive and took 3x longer. Would it be helpful to compare a build vs buy analysis for your specific situation?"

Authority Objections

Authority objections help you understand the buying process. Use these moments to identify all stakeholders and build a multi-threaded deal.

16. "I need to talk to my boss"

Why they say it: They don't have final decision authority, or they're not confident enough to champion the solution internally.

How to respond: "Of course—what do you think their main questions or concerns will be? [Wait for response] Those are the same questions I'd have. Would it be helpful if I put together a one-pager that addresses those specific points? Also, when you talk to your boss, what do you want them to come away thinking? And would it make sense for me to join that conversation, even for just 10 minutes, to answer any technical questions directly?"

17. "I'm not the right person"

Why they say it: They genuinely aren't involved in this decision, or they're trying to pass you off.

How to respond: "I appreciate you telling me that. Who would be the right person to talk to about [specific problem your solution solves]? [Get name] Great, and what's the best way to reach them? Also, would you be willing to make a quick intro? Coming from you would carry a lot more weight than a cold outreach from me."

18. "We have a committee that decides"

Why they say it: Large purchases require multiple stakeholders, and they want you to understand the process.

How to respond: "That makes sense for a decision like this. Help me understand the committee—who's involved, and what does each person care about most? [Wait for response] That's really helpful. Of those people, who's most likely to champion this, and who's most likely to be skeptical? What can I do to help you make the case to each of them? Would it be useful if I joined one of the committee meetings?"

19. "Our CEO/CFO would never approve this"

Why they say it: They're anticipating pushback from executives who control budget.

How to respond: "What makes you say that? What specifically do you think would concern them? [Wait for response] I hear you. The CFOs we work with typically care about [ROI, payback period, risk]. Would it help if I put together an executive summary that speaks directly to those concerns? Better yet, we could set up a quick call where I can present the business case directly. What would make your CEO/CFO say yes?"

20. "We need to run this by legal/procurement/IT"

Why they say it: There are internal review processes that need to happen before they can move forward.

How to respond: "Absolutely—we deal with [legal/procurement/IT] teams all the time. What are the typical things they look for? [Wait for response] We've put together documentation specifically for [that team] that addresses most of those questions upfront. I can send that over to help speed things up. Also, would it be helpful to set up a quick call between your [legal/procurement/IT] team and ours? We've found that answering questions directly cuts weeks off the process."

Need Objections

Need objections are the most fundamental. If prospects don't believe they have a problem worth solving, no amount of selling will work. Your job is to help them see the true cost of the status quo.

21. "We're fine with what we have"

Why they say it: They're comfortable with the status quo and don't see a compelling reason to change.

How to respond: "I'm glad things are working for you. Can I ask—when you say 'fine,' what does that look like day to day? [Wait for response] Okay, and what would 'great' look like? [Wait for response] What's the gap between fine and great costing you, whether in revenue, time, or opportunity? [If there's a gap] That's exactly what our customers were experiencing before they made a change. Would it be worth exploring if we could close that gap?"

22. "I don't see how this applies to us"

Why they say it: They don't understand how your solution connects to their specific situation or industry.

How to respond: "That's fair—I may not have done a good job connecting the dots. Let me ask you this: what are the biggest challenges you're facing with [relevant area] right now? [Wait for response] How is that impacting [their key metrics]? [Wait for response] That's actually exactly what [similar customer in their industry] was dealing with before they started working with us. They were able to [specific outcome]. Would it be helpful if I walked you through what that looked like?"

23. "Our current process works"

Why they say it: They've built systems and habits around the status quo, even if it's not optimal.

How to respond: "I hear you—if it's not broken, why fix it? Quick question though: when you look at [relevant metric], are you hitting your targets consistently? [If yes] That's great. What would it mean if you could exceed those targets by [X%]? [If no] What's getting in the way? And what would it be worth if you could close that gap?"

24. "This isn't a problem for us"

Why they say it: They genuinely don't experience the problem your solution solves, or they're not aware of it.

How to respond: "That's great if that's truly the case. Just to make sure I understand your situation—how are you currently handling [specific task or challenge]? [Wait for response] And how much time/money does that take? [Wait for response] Interesting. Most companies in your industry tell us that [related challenge] ends up costing them [X]. Is that something you've measured, or is it possible it's happening under the radar?"

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

Why they say it: They had a bad experience with a similar solution and are now skeptical of the entire category.

How to respond: "I appreciate you sharing that—there's nothing worse than investing in something that doesn't deliver. What happened? What went wrong? [Wait for response] That's frustrating. And what would need to be different this time for you to feel confident it would work? [Wait for response] Those are exactly the concerns we've addressed. The way we're different is [specific differentiation]. Would you be open to a pilot or proof of concept that would let you validate this before committing fully?"

Putting It All Together: The Objection Handling Framework

While each objection requires a tailored response, there's a consistent framework that underlies all great objection handling:

• Acknowledge: Show you heard and understood the objection. Never dismiss it.
• Clarify: Ask questions to understand the real concern behind the stated objection.
• Respond: Address the underlying concern with specifics, not generalities.
• Confirm: Check that your response addressed their concern before moving on.

Practice Makes Perfect

Reading about objection handling is one thing—actually handling objections under pressure is another. The best salespeople don't just know these responses; they've practiced them until they're automatic. Understanding the psychology behind objections can also give you an edge.

That's where AI-powered roleplay comes in. With tools like SalePlay, reps can practice handling these exact objections in realistic scenarios, getting instant feedback on their responses. The result? When these objections come up on real calls, your team responds with confidence instead of fumbling for words.

The objection isn't the end of the conversation—it's the beginning of the real selling. Master these responses, and you'll turn more objections into closed deals.