# 30 Common Sales Objections and How to Respond > 30 common sales objections about price, timing, authority, need, competitors and trust, with what each really means and a response you can use on your next call. - **Author**: Sami AZ - **Published**: 2026-10-27 - **Category**: Objection Handling - **URL**: https://klu.so/blog/common-sales-objections --- The most common sales objections fall into six groups: price, timing, authority, need, competition or the status quo, and trust. For each one, the best response is rarely a counterargument. It's a short acknowledgment, then a question that finds out what's really behind the objection, then an answer to that real concern. Below are 30 objections you'll hear on real calls, grouped by type. For each: what it usually means, a response you can adapt, and a follow-up question. For the underlying method, see our [objection handling guide](https://klu.so/blog/objection-handling). ## What are sales objections? A sales objection is a concern a buyer raises that stands between them and a yes: about price, timing, who decides, whether they need it, what they use today, or whether they trust you. An objection is different from a brush-off ("just send me an email"), which is a reflex to end the call before the buyer has heard enough to object to anything. ## What is the quickest way to respond to any objection? Use this table when you need a first move fast. | Objection type | What they're really asking | Your first move | |---|---|---| | Price | "Is this worth it?" | Ask what they're comparing it to | | Timing | "Why now?" | Ask what would make it a priority | | Authority | "Can I sell this internally?" | Ask what the decision maker will want to know | | Need | "Is this my problem?" | Ask how they handle it today | | Competition / status quo | "Is switching worth the risk?" | Ask what they'd change about the current setup | | Trust | "Can I believe you?" | Offer proof that's specific and checkable | ## How do you respond to price objections? ### 1. What do you say to "It's too expensive"? **Usually means:** they don't see enough value yet, they're comparing you to something cheaper, or they're negotiating. > "I hear you. **Too expensive compared to what?**" **Follow up:** "If price weren't a factor, would this be the right fit?" ### 2. How do you respond to "We don't have the budget"? **Usually means:** the money is allocated elsewhere, or the problem isn't a priority yet. > "Totally fair. **What would need to happen for this to get budget?**" **Follow up:** "When does your budget planning for next year start?" ### 3. How do you handle "Your competitor is cheaper"? **Usually means:** they're comparing on price because they can't see a difference in value. > "They might well be. **What's driving the comparison, is it the price alone or are the two options doing the same job for you?**" **Follow up:** "What would make the difference in price worth it?" ### 4. What do you say to "Can you do a discount?" **Usually means:** they want to buy, and they're testing your price. > "Possibly. **If we could adjust the price, would you be ready to move forward this month?**" **Follow up:** if you give something, get something: a longer term, a faster signature, a case study. ### 5. How do you respond to "We need to see the ROI first"? **Usually means:** they need to justify the spend to someone else. > "Makes sense. **What numbers would your team need to see to call this a good investment?**" **Follow up:** "Can we build that estimate together, using your numbers?" ## How do you respond to timing objections? ### 6. How do you handle "Now isn't a good time"? **Usually means:** other priorities, or a polite no. > "Understood. **Is it the timing of the project, or whether this is a priority at all?**" **Follow up:** "What's on your plate right now that comes first?" ### 7. What do you say to "Call me next quarter"? **Usually means:** maybe a real event, maybe a brush-off. > "Happy to. **What changes between now and next quarter that makes it better timing?**" **Follow up:** book the call now: "Let's put 15 minutes on the calendar for the second week of January." ### 8. How do you respond to "We're in the middle of a big project"? **Usually means:** they're stretched and worried about adding work. > "That's real. **When does that project wrap up, and would this make that easier or harder?**" **Follow up:** "What would a light-touch start look like for you?" ### 9. How do you handle "We don't have time to implement anything new"? **Usually means:** they've been burned by a long rollout before. > "Fair, nobody wants another six-month rollout. **How much time would you realistically have each week?**" **Follow up:** show what the first week actually involves, specifically. ### 10. What do you say to "Let me think about it"? **Usually means:** there's a specific concern they haven't said out loud. > "Of course. **What part are you still weighing?**" **Follow up:** "Is it something about the price, the timing or how it'd work for your team?" ## How do you respond to authority objections? ### 11. How do you respond to "I need to talk to my boss"? **Usually means:** they can't decide alone, or they're unsure how to pitch it. > "Makes sense. **What do you think they'll ask first?**" **Follow up:** "Would it help if I joined for ten minutes to answer the hard questions?" ### 12. How do you handle "I'm not the decision maker"? **Usually means:** you're talking to an influencer, not the buyer. > "Thanks for telling me. **Who would make the call, and how do they usually decide on something like this?**" **Follow up:** "Would you be comfortable introducing us, or should I prepare something you can share?" ### 13. What do you say to "Procurement handles this"? **Usually means:** there's a formal process you need to understand early. > "Good to know. **What does procurement usually need from a vendor, and how long does it take?**" **Follow up:** ask for the checklist now so it doesn't surprise you later. ### 14. How do you respond to "I need to run it by the team"? **Usually means:** they want buy-in, or they're stalling. > "Smart. **Who on the team will have the most questions, and what will they be?**" **Follow up:** "Would a short session with the team help?" ## How do you respond to need objections? ### 15. How do you handle "We don't need this"? **Usually means:** they don't see the problem, or don't see it as theirs. > "Could be. **How are you handling [the problem] today?**" **Follow up:** "What would make you revisit it?" ### 16. What do you say to "We're too small for this"? **Usually means:** they think it's built for bigger companies, or they're worried about cost. > "**What size would you need to be before it made sense?**" **Follow up:** share a relevant example from a company their size, if you have a real one. ### 17. How do you respond to "We do this in-house"? **Usually means:** someone internal owns this and may feel threatened. > "Got it. **How's that working, and how much of someone's time does it take?**" **Follow up:** "What would that person rather be spending their time on?" ### 18. How do you handle "It's not a priority"? **Usually means:** the cost of the problem is invisible to them. > "Fair. **What's at the top of the list right now?**" **Follow up:** connect your problem to their top priority, or accept it's not a fit for now. ### 19. What do you say to "I don't see how this helps us"? **Usually means:** you pitched before you understood their situation. > "That's on me. **Can I ask a couple of questions about how you work, so I'm not guessing?**" **Follow up:** go back to discovery. Our [discovery call guide](https://klu.so/blog/discovery-call) has questions for this. ## How do you respond to competitor and status quo objections? ### 20. How do you respond to "We already use [competitor]"? **Usually means:** switching feels risky, and they don't know if they're unhappy. > "Makes sense. **What do you like most about it, and what would you change if you could?**" **Follow up:** talk only about the gap they name. Don't pitch a comparison they didn't ask for. ### 21. How do you handle "We're locked into a contract"? **Usually means:** a real constraint, and a timeline you can plan around. > "Understood. **When does it renew, and when do you usually start evaluating before that?**" **Follow up:** "Would it be useful to talk a couple of months before then?" ### 22. What do you say to "We're happy with what we have"? **Usually means:** not unhappy enough to change. > "Good to hear. **If you could fix one thing about it, what would it be?**" **Follow up:** "How does your team feel about it day to day?" ### 23. How do you respond to "We tried something like this before and it didn't work"? **Usually means:** a past failure is shaping this decision. > "Thanks for telling me. **What went wrong last time?**" **Follow up:** address that specific failure honestly, including whether it could happen again. ### 24. How do you handle "Switching would be too much work"? **Usually means:** they're picturing a painful migration. > "Fair concern. **What would switching involve on your side, in your view?**" **Follow up:** walk through the real steps, and be honest about the effort. ## How do you respond to trust objections? ### 25. What do you say to "I've never heard of you"? **Usually means:** they're wary of a vendor they can't vouch for. > "That's fair, we're not a household name. **What would you want to know about us to feel comfortable?**" **Follow up:** offer something checkable: a trial, a reference, a short pilot. ### 26. How do you respond to "How do I know it'll work for us?" **Usually means:** they need evidence that fits their situation. > "Good question. **What would 'working' look like for you in the first month?**" **Follow up:** propose a small test against that definition. ### 27. How do you handle "It sounds too risky"? **Usually means:** they're worried about what happens if it fails, often personally. > "**What's the risk you're most worried about?**" **Follow up:** reduce that specific risk: a pilot, a cancellation term, a phased rollout. ### 28. What do you say to "Send me some case studies"? **Usually means:** genuine interest, or a polite exit. > "Happy to. **Which kind of company would be most useful to see, one your size, or in your industry?**" **Follow up:** send exactly that, then book a follow-up to discuss it. ### 29. How do you respond to "Just send me an email"? **Usually means:** a brush-off, especially early in a cold call. > "Sure. **So it's not a generic deck, what's the one thing you'd want to know?**" **Follow up:** if they name something, send only that and ask for 15 minutes to walk through it. ### 30. How do you handle "I need references"? **Usually means:** they're close to deciding and want reassurance. > "Of course. **What would you want to ask a reference?**" **Follow up:** pick references who match those questions, and brief them. ## How do you practice handling objections? Reading 30 responses doesn't mean you'll say them under pressure. Pick the five objections you hear most and drill those: 1. **Write your first line** for each, in your own words. 2. **Say each one out loud** until it comes out without thinking. 3. **Practice with someone who pushes back** and throws objections in random order. Or use an AI buyer: competitor objections are one of the scenarios on [Klu](https://klu.so), and every take ends with coaching on the exact line that lost the buyer. 4. **Log the objections you fumble** on real calls, and add them to your drill list. If you need opening lines to get to the objection in the first place, our [cold calling scripts](https://klu.so/blog/cold-calling-scripts) and [sales techniques](https://klu.so/blog/sales-techniques) are a good next read. ## FAQ ### What are the 5 most common sales objections? The five most common objections are "It's too expensive," "We don't have the budget," "Now isn't a good time," "We already use another provider," and "I need to talk to my boss." On cold calls, "Just send me an email" is just as common. ### What is the best way to handle sales objections? Acknowledge the concern without arguing, ask a question to find out what's behind it, then answer the real concern and check whether your answer landed. Avoid discounting or defending straight away. ### Are objections a bad sign in sales? No. Objections usually mean the buyer is engaged enough to tell you what's in the way. Silence or polite agreement without a next step is a worse sign. ### How do you handle "we already use a competitor"? Ask what they like about their current tool and what they would change. Then talk only about the gap they describe, rather than launching into a feature comparison. ### How many objections should you prepare for? Prepare first lines for the 5 to 10 objections you hear most in your market. Most reps hear the same handful over and over, so drilling those gives you the most return. ## Practice your top five objections Pick the objections that cost you deals and rehearse them before the next call. [Try an objection on Klu](https://klu.so), get coached on the line that lost the buyer, and run it again until it's easy. --- - [More Objection Handling articles](https://klu.so/blog/category/objection-handling) - [All articles](https://klu.so/blog)