Most objection handling advice gives reps a comeback for every line. "Too expensive? Show the value." "Too busy? Show the efficiency." The trouble is that the buyer's words are rarely the real problem. "Too expensive" can mean they don't see the return, that they can't get the money approved, or that they want to see if you'll discount. "Too busy" can mean they see the value, but the pain of their current problem doesn't feel sharp enough to disrupt how they work today. The real issue is priorities, not time in the day. Each one needs a different answer, and a good answer to the wrong concern makes things worse.
This guide covers twelve objections B2B sales reps hear all the time. For each one: what the buyer usually means, what a rep could actually say out loud, and the common response to avoid.
How to handle any objection
Use the same four steps every time:
- •Listen. Let the buyer finish. Pause before you answer.
- •Diagnose. Ask one question to find the real concern behind the words.
- •Answer that concern. Briefly, in the buyer's terms.
- •Check. Ask if that settles it, in a way that makes it easy to say no.
Most reps skip the first two steps. Gong Labs analyzed 67,149 recorded demo calls and found that top reps pause longer after an objection and reply with a question, while average reps speed up and launch into a long answer. Diagnose before you defend.
"It's too expensive"
What they mean: A price is only too high compared to something. Usually it's one of three things. They don't see enough return to justify it. They're comparing you to a cheaper quote or to what they spend today. Or they have no real problem with the price and are asking because asking costs nothing. The first one is the most common, and it's a value problem, not a price problem: the buyer is judging you on price because nothing else in the deal is clear enough to judge you on.
Try saying: "That's fair to raise. Too expensive compared to what: another quote, what you spend now, or what you expected to pay?" Then, depending on the answer: "Leaving the price aside for a second, what is this problem costing you each quarter right now?"
Avoid: Offering a discount straight away. It tells the buyer your first number was soft, and if they still don't see the return, a lower price won't change their mind.
"We don't have the budget"
What they mean: There may truly be no money this year. More often, there is money, it's already assigned to other things, and nobody has made the case to move it. Or "no budget" is a polite way to end the conversation because the problem doesn't feel big enough. Budget follows priorities. Companies find money for problems that hurt.
Try saying: "Understood. Is it that nothing new is getting funded this year, or that this just isn't in the plan yet? When something important comes up mid-year, how does it usually get paid for?" The answer tells you whether you're dealing with a hard limit or a priority question, and who controls the money.
Avoid: Taking it at face value and booking a follow-up for next fiscal year. Also avoid the opposite: rushing to a smaller package before you know whether the problem is money or priority.
"Your competitor is cheaper"
What they mean: Either they're using the other quote to negotiate, or they honestly see the two options as the same, so price is the only difference left. If it's the second, you haven't shown what's different in a way that matters to them. Sometimes the quotes aren't even for the same thing.
Try saying: "Good to know, thanks for telling me. When you put the two side by side, what looks the same to you? And what would have to be true for the higher price to be worth it?" If they're unsure what the other quote includes, offer to compare them line by line.
Avoid: Running down the competitor. It makes you look worried, and it questions the buyer's judgment for considering them. Don't match the price either until you know what the other number covers.
"We're happy with what we have"
What they mean: Often it means "switching sounds like work, and I'm not sure it's worth the risk." The real competitor here is the status quo, not the other vendor. Sometimes it's a reflex to end the call. And sometimes they really are fine, which is useful to know early.
Try saying: "Glad it's working. What made you pick them in the first place? If you could change one thing about how it works today, what would it be?" Another option is a label, in the style Chris Voss teaches: "It sounds like it works well enough that changing isn't worth the hassle." People tend to correct a label that's slightly off, and the correction tells you where the gaps are.
Avoid: Listing everything their current tool can't do. You're asking them to admit their last decision was wrong, and they'll defend it.
"Now isn't a good time"
What they mean: It might be true: quarter end, a reorg, a launch, a hiring freeze. Or it's an easier way to say no than saying no. The test is whether there's a specific reason and a specific date.
Try saying: "Makes sense. What's taking up the team's time right now? Once that's done, what would need to be true for this to be worth a look?" If the reason is real, agree on a date tied to it ("after your launch on the 15th"). If the reason is vague, ask directly: "Is it timing, or is this just not something you need?"
Avoid: "No problem, I'll check back in three months." With no reason and no date, that follow-up turns into another cold call.
"It's not a priority"
What they mean: This is different from timing. Timing says "not now." Priority says "the problem isn't big enough compared to everything else on my list." Either they don't feel the cost of the problem, or the person you're talking to feels it but the people who set priorities don't.
Try saying: "That's fair. Everyone has more on the list than they can do. What's at the top of yours this quarter?" Then: "Does this problem touch any of that, or is it really separate?" If it connects to their top priority, that connection is your case. If it doesn't, you've learned the deal isn't real yet.
Avoid: Inventing urgency with a discount that expires at month end. Buyers see it coming, and it doesn't make the problem any bigger. Real urgency comes from what the problem costs them.
"Just send me some info"
What they mean: Often "I want to get off this call politely." Sometimes it's a real request from someone who likes to read before they talk. And sometimes they need something to share with colleagues, which is a good sign.
Try saying: "Happy to. So I don't send you a forty-page deck, what's the one thing you'd want it to answer? And is anyone else going to read it?" The answers tell you which of the three you're dealing with. Then ask for fifteen minutes later in the week to go through it together.
Avoid: Sending the generic brochure and following up with "Did you get a chance to look?" Nobody reads the generic brochure, and that email is easy to ignore.
"I need to talk to my boss"
What they mean: In B2B this is often simply true: one person rarely decides alone. But it can also mean they aren't convinced themselves and the boss is a safe exit. Or they're convinced but don't know how to make the case inside their company.
Try saying: "Of course. When you bring it to them, what do you think they'll ask first? And how do you feel about it yourself?" The second question matters most. Then offer to help: "Would it be useful if I joined that conversation, or wrote a one-page summary in the terms they care about?"
Avoid: Going around your contact to reach the boss. You'll lose the one person inside the company who was on your side. Also avoid just waiting. A contact who isn't prepared will make your case badly.
"I'm not interested"
What they mean: On a cold call, they don't know enough about you to be interested or not. It's a reaction to being interrupted, not a judgment of your product. Sometimes they really aren't a fit, and that's worth finding out in thirty seconds rather than thirty days.
Try saying: "That's fair, I called out of the blue. Can I ask one question, and then you can decide if it's worth another minute?" Then ask about a specific problem people in their role tend to have: "Most [their role]s I talk to are dealing with [specific problem]. Is that true for you too?" If they engage, you have a conversation. If not, thank them and move on.
Avoid: Repeating your pitch faster and louder. They didn't reject the pitch. They rejected the interruption, and more pitch makes it worse.
"We tried this before and it failed"
What they mean: The idea isn't the problem. The last attempt hurt, maybe in front of their boss, and they don't want to repeat it. You need to know what actually failed: the product, the rollout, adoption by the team, or the problem it was meant to solve.
Try saying: "I'd like to hear about that. What happened? Looking back, what would have had to go differently for it to work?" Then answer that specific failure point. Explain how your approach handles it, and say so honestly if it doesn't.
Avoid: "We're different." Every vendor says it, so it means nothing. Don't blame the previous vendor either. The buyer chose them, and you'll be criticizing their call.
"We don't have time to implement it"
What they mean: They're worried about the work on their side: setup, changes to how the team works, and their own hours. Sometimes it really means "I'm not sure it's worth the effort," which is a value concern again.
Try saying: "That's a real concern. What do you picture implementation involving? Who would need to be part of it?" Then lay out what's actually required, in people and hours, and offer a smaller first step, such as one team or one use case.
Avoid: "It's easy, it takes no time." If they've lived through a rollout, they won't believe you. And if it isn't true, you've set up the next problem with the account.
"We can build this ourselves"
What they mean: Someone on their team thinks it's simple. Sometimes they're right. Often they're comparing a quick prototype to a finished product and leaving out maintenance. Sometimes it's a way to push the price down.
Try saying: "You probably could. Has the team scoped it yet? Who keeps it running after launch, and what would they not be working on instead?" Let the questions bring out the full cost. If they've thought it through and still want to build, that's a fair decision and you've saved yourself a long cycle.
Avoid: Telling them they can't do it. Engineers hear that as a challenge, and you've given them a reason to prove you wrong.
Knowing the answer isn't the same as saying it
Reading this guide takes ten minutes. Answering calmly while a buyer waits takes different skills. Most reps know they should ask a question when they hear "too expensive." Under pressure, many still reach for the discount or the long explanation. The fix is to practice out loud before a real buyer says it. Pick the three objections your team hears most, write down what a good answer sounds like for your product, and have reps run them until it feels natural. A manager or peer can play the buyer. Reps can also use AI sales roleplay against a buyer built from your own material, with each attempt graded against a rubric that quotes what the rep said. See how teams use it for objection practice.