50 Sales Objections + Responses (2026)

Every sales objection is a buying signal in disguise. A prospect who objects is engaged. A prospect who says nothing is the one you should worry about. This guide covers the 50 most common objections across five categories (pricing, competitor, timing, authority, and product), with word-for-word responses your reps can use or adapt. For objections specific to a competitor, generate a battle card with tailored rebuttals at battlecard.northr.ai/generate.

Pricing Objections (1-10)

1. "It's too expensive."

"I understand budget is a factor. Can you help me understand what you're comparing our price to? Often what looks expensive upfront saves money when you factor in implementation time, add-on costs, and productivity gains. Let me walk you through the total cost of ownership comparison."

2. "Your competitor is cheaper."

"Their base price is lower, that's true. But when you add implementation fees, required add-ons, and annual price increases, the total cost over 12 months is often similar or higher. I can put together a side-by-side TCO comparison for your team size if that would help."

3. "We don't have the budget."

"I hear that. Is this a timing issue (budget opens next quarter) or a priority issue (this isn't high enough on the list)? If it's timing, let's map out the cost of waiting: how many competitive deals will your team face between now and then without preparation?"

4. "Can you give us a discount?"

"I can explore options. What would make this work? If it's about the monthly commitment, we offer annual billing at a lower rate. If it's about scope, we can start with a smaller plan and expand. What I can't do is discount without understanding what flexibility you need."

5. "We need to see ROI first."

"Completely fair. Here's how other teams your size measured it: they tracked competitive win rate before and after. The average improvement was 25-30% within 90 days. On your pipeline, that translates to significant recovered revenue per quarter."

6. "The free version of [competitor] is good enough."

"Free tools are a great starting point. The question is how long they stay good enough. Most teams outgrow free tiers within 3-6 months because of specific limitations: no automation, no support, data goes stale. The cost of upgrading later is higher than starting with the right tool now."

7. "We're cutting costs right now."

"I understand. This is actually a tool that helps you cut costs. Every competitive deal you lose because reps aren't prepared is revenue you paid to generate. A battle card that takes 60 seconds to create can save a deal worth 100x the subscription cost."

8. "Your per-user pricing doesn't scale."

"Fair point. Let me show you the pricing at your projected team size. At your user count, the per-user cost drops significantly. And unlike many competitors, there are no add-on fees for core features or mandatory onboarding costs."

9. "We need to get three quotes."

"Absolutely. When you're comparing quotes, here's what to look for beyond the sticker price: implementation fees, required training costs, annual price escalation clauses, and what's included vs add-on. I can prepare a comparison framework that makes evaluation easier."

10. "We already allocated budget to [competitor]."

"That makes sense. Before you finalize, would it be helpful to see a side-by-side comparison? Sometimes the allocation was based on initial research and new information changes the picture. I can have it ready in 24 hours and it takes 15 minutes to review."

Competitor Objections (11-25)

11. "We're going with [competitor]."

"I respect that. Can I ask what tipped the decision? Understanding what mattered most helps me serve teams like yours better. And if anything changes during implementation, I'm here."

12. "[Competitor] has more features."

"They do have more features. The question is whether your team will use them. More features does not mean more value if nobody uses them. Our customers report higher adoption because we focus on the features that actually drive results."

13. "[Competitor] is the industry standard."

"They are the standard for enterprise and large teams. For teams your size, that standard comes with enterprise complexity and enterprise pricing. The standard is shifting, and companies like yours are choosing tools built for their actual needs."

14. "We already use [competitor] and it works fine."

"If it's working, that's great. What I hear from teams that switch is that 'fine' was costing them more than they realized. Would it be worth 15 minutes to see if there's a meaningful difference, or is the current setup genuinely meeting your needs?"

15. "[Competitor] has better reviews."

"They have great reviews from their target customer, which is typically enterprise teams with dedicated admins. Look at the reviews from teams your size. The feedback often changes: complexity, cost, and adoption challenges show up more in small team reviews."

16. "Our team already knows [competitor]."

"Switching costs are real. The question is whether the switching cost is higher or lower than the ongoing cost of the current tool. If your team spends hours per week on workarounds, the math might favor switching. We can quantify that."

17. "[Competitor]'s integration is better."

"Their integration with specific tools is strong. Where we win on integrations is faster setup, no middleware required, and native CRM sync. Which specific integration matters most for your workflow? That's the one worth comparing in detail."

18. "[Competitor] is launching a similar feature."

"Roadmap promises are common. The question is whether you want to buy based on what exists today or what might exist in 6 months. We have this feature live, in production, with customers using it. I'd rather show you something working than promise something coming."

19. "[Competitor] gave us a better deal."

"They may have room to discount because their standard pricing has more margin built in. Our pricing is transparent: what you see is what you pay, no negotiation games. The real comparison is total cost over 12 months including licensing, implementation, support, and add-ons."

20. "We need to check with our team who uses [competitor]."

"Great idea. When they evaluate, here are three questions worth asking: How much time do they spend on workarounds? How often does a specific limitation come up? And if they could change one thing about their current tool, what would it be? Those answers will tell you a lot."

21. "I saw a negative review about your product."

"I appreciate you bringing that up. Can you share which review? I want to address it specifically. Every product has negative reviews. What matters is the pattern: our overall rating is strong, and I can speak to the specific concern directly."

22. "[Competitor] offered a longer trial."

"A longer trial is helpful if the product takes time to evaluate. Ours delivers value in the first session. Try it for our trial period and see results on day one. If you need more time, we can extend."

23. "Our investors recommended [competitor]."

"Investor recommendations carry weight. They typically recommend what they know, which is often the enterprise option. The best decision is based on your team's actual needs, not a portfolio company's stack. Let me show you the comparison and you can make an informed recommendation back."

24. "[Competitor] has a bigger team."

"Bigger team means slower product decisions and more layers between you and support. A smaller team means you talk directly to the people building the product. That access matters more than headcount."

25. "We're locked into a contract with [competitor]."

"When does the contract end? Let's plan for that date. In the meantime, I can set up a pilot so your team is ready to switch when the time comes. Some teams also find that the cost of breaking the contract is lower than the ongoing cost of staying."

Timing Objections (26-35)

26. "Not right now, maybe next quarter."

"I understand. What changes next quarter that makes this a better time? If it's budget, let's plan for that. If it's bandwidth, the setup takes minutes, not weeks."

27. "We just signed with another vendor."

"Congratulations on making a decision. How long is the contract? Let me check back at a specific date so we can be part of your next evaluation."

28. "We're in the middle of another project."

"Makes sense. This doesn't require a separate project. It takes 60 seconds to generate a battle card and your reps can use it immediately. No implementation, no IT involvement, no project plan."

29. "We need to do more research first."

"Absolutely. What specific questions do you need answered? I can either answer them now or send you a comparison document that covers the main evaluation criteria."

30. "Our fiscal year starts in [month]."

"Got it. Let's plan for that. I'll send you a summary now so it's in your evaluation materials. Would it help to do a pilot before the fiscal year starts so you have data to support the budget request?"

31. "We're too busy to evaluate new tools."

"I hear that a lot. The irony is that the busiest teams are usually the ones losing the most competitive deals because nobody has time to prepare. This takes 60 seconds, not 60 hours."

32. "Call me back in 6 months."

"Happy to. What should I bring when I call back that would make the conversation worth your time?"

33. "We just went through a big change."

"Change fatigue is real. This isn't a change, it's a tool. Your reps can use it in 60 seconds without changing any of their existing workflow."

34. "The timing isn't right."

"When would the timing be right? And what would change between now and then? Sometimes the timing issue is actually a priority issue in disguise."

35. "We have other priorities."

"Completely understand. Where does competitive win rate rank on the priority list? If you're losing deals to competitors right now, waiting moves this from a priority to an emergency."

Authority Objections (36-42)

36. "I need to run this by my boss."

"Of course. What does your boss care about most: the cost, the competitive impact, or the implementation effort? I can put together a one-page summary focused on what matters to them."

37. "This isn't my decision."

"Who else is involved in the decision? I'd love to understand what each person cares about so we can address their questions proactively."

38. "Our VP of Sales would need to approve this."

"Makes sense. VPs of Sales typically want to know two things: will this improve win rates, and what does it cost? I can prepare a brief that answers both with specific numbers."

39. "We need buy-in from IT."

"What would IT need to know? We're cloud-based, no installation required. I can provide a technical overview for their review with security and compliance details."

40. "The whole team needs to agree."

"Group decisions take time. Would it help to start with a small pilot, 2-3 reps using it for 30 days? Real results from their peers are more convincing than any sales pitch."

41. "Legal needs to review the contract."

"Happy to get that started now. Our terms are straightforward: monthly or annual billing, cancel anytime, standard DPA. I'll send the agreement so legal can review in parallel."

42. "We have a procurement process."

"Understood. What does the procurement process look like and what documentation do you need from us? I'll prepare everything upfront to keep the timeline moving."

Product Objections (43-50)

43. "It doesn't integrate with our CRM."

"Which CRM do you use? We integrate with major CRMs, and for others, our PDF exports and API cover most workflows. What specific integration would be most valuable?"

44. "We need more customization."

"Tell me what you'd customize. Often what feels like a customization need is actually a workflow issue we can solve differently."

45. "Is your data accurate?"

"We recommend verifying pricing (the most frequently changing data) on the competitor's website before any major deal. For positioning, strengths, and weaknesses, our AI pulls from verified sources. You can supplement with your own deal experience."

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

"What did you try, and what went wrong? The reason matters. If adoption was the issue, our tool takes 60 seconds (not 60 hours of setup). If quality was the issue, I'd like to show you the difference."

47. "Your product is too simple."

"Simple is intentional. Your reps need a battle card they can use in 30 seconds mid-call, not a 20-page analysis. Simple is what gets used. Complex is what gets ignored."

48. "We need enterprise features."

"Which specific enterprise features? Often that means SSO, advanced permissions, and dedicated support. Our Team plan includes those at $149/month, not $15,000+/year."

49. "We can do this ourselves with ChatGPT."

"You can. Most teams try and stop after a week because the prompts need constant refinement, the output is inconsistent, and there's no scoring or practice capability. We've built that infrastructure so you don't have to."

50. "Your company is too small/new."

"We are newer. That means we're faster, more responsive, and more motivated to earn your business. Our product works right now: generate a battle card and see for yourself in 60 seconds. The proof is in the output, not the company size."

Practice These Objections

Reading responses is not the same as delivering them under pressure. Practice the objection handlers that matter most for your deals using AI sales simulations at battlecard.northr.ai/generate. The AI buyer will throw these objections at you in realistic conversation, and you'll get scored on how you handle them. For the complete competitive practice framework, see our AI Sales Simulations Guide at /blog/ai-sales-simulations-guide.

Frequently Asked Questions