Common objections in B2B sales: How to handle them
Le Anh Nguyen (Content Manager)
The demo went well. Your contact likes the product. Then the proposal reaches finance, and the conversation changes.
“It’s too expensive.”
You explain the benefits again. Offer a smaller package. Perhaps suggest a discount. A week later, the buyer says they need more time.
What happened? The objection you answered may have been only part of the problem. Finance could be questioning the projected return. The implementation team could be fully booked. Your contact might support the purchase without knowing how to secure approval.
Handling B2B sales objections means identifying what prevents the buyer from moving forward, then helping them evaluate or resolve it. That requires useful questions, credible evidence and an understanding of how business purchases actually happen.
This guide covers 20 common objections, practical responses and ways to train your team to handle the conversation that follows.
TL;DR
Clarify the concern before defending the offer. Price, budget and uncertainty about ROI require different responses.
Consider the sales stage. A cold-call dismissal and a procurement concern need different approaches.
Use evidence the buyer can evaluate. Relevant customer results, transparent calculations and implementation plans are more useful than broad promises.
Make the next step address the blocker. A technical concern needs technical validation; an approval concern needs a decision process.
Practise different versions of the same objection. Reps need to adapt when the buyer’s answer changes.
Recognise when the deal should stop. A clear refusal or a requirement you cannot meet deserves an honest response.
What are B2B sales objections, and what do they tell you?
A B2B sales objection is a concern or constraint that prevents a prospect from taking the next step in a buying process.
Objections can relate to the purchase itself: price, capabilities, implementation or expected results. They can also relate to the organisation: budget ownership, competing priorities or disagreement between stakeholders.
An objection doesn’t automatically signal interest. During prospecting, it may simply be a response to an interruption.
In an analysis of more than 300 million cold calls, Gong classified 49.5% of objections as dismissive, including initial expressions of disinterest. That finding applies to cold calls; it shouldn’t be generalised to buyers already evaluating a proposal. Source: Gong’s cold-call objection research.
Before choosing a response, distinguish between three situations:
A concern you can investigate: “I’m unsure the team will use it.”
A condition that must be met: “IT must approve the integration.”
A reason the opportunity cannot proceed: “We require a capability you don’t offer.”
The same phrase can also mean different things at different stages. “Send me information” during a cold call may end the conversation. During procurement, it may identify exactly what is needed to progress.
How do you handle a sales objection without becoming defensive?
A useful starting point is LAER: Listen, Acknowledge, Explore and Respond, a framework developed by Carew International. It gives salespeople a sequence for understanding resistance before answering it. Source: Carew International.
In practice:
Listen: Let the buyer finish, including any explanation that follows the initial objection.
Acknowledge: Reflect the concern specifically: “You’re worried this will add work for managers.”
Explore: Clarify what remains uncertain: “Which responsibilities would be hardest to accommodate?”
Respond: Address that issue with relevant information, an adjustment or a proposed next step.
Then check whether your answer helped.
That final check can be simple: “Does that resolve the reporting concern, or is there another requirement we haven’t covered?”
There is evidence for slowing down. Gong’s analysis of 67,149 sales calls found that successful salespeople paused after objections for five times longer than less successful peers. This is an observed association, but it supports a practical coaching habit: resist the immediate rebuttal. Source: Gong’s objection-handling research.
Use the framework naturally. When a buyer asks whether you support a particular integration, give a clear answer. Making them work through several questions before receiving basic information can create frustration.
The response examples and financial scenarios below are illustrative. Adapt them to your offer and use only claims you can substantiate.
Early objections: How do you earn a relevant conversation?
Early in the relationship, the buyer may know little about your offer and owe you very little attention. Your immediate task is to establish whether discussing the problem would be useful.
1. “We’re not interested” or “We don’t need this”
Avoid assuming the buyer has misunderstood their own business. They may already have the problem under control.
A brief response could be:
“Understood. Is improving new-hire ramp time already covered, or is it outside your priorities?”
Replace “new-hire ramp time” with the specific outcome you support. A concrete question is easier to answer than “Why aren’t you interested?”
If they explain that onboarding is already performing well, investigate only if they welcome the discussion. If they clearly decline, end the conversation.
The useful outcome may be disqualification. Continuing to pitch after a clear refusal doesn’t create a stronger opportunity.
2. “I don’t have time”
First establish whether they lack time for this conversation or for the project itself.
On an unexpected call, keep your response short:
“I caught you at a bad moment. Would a short email about reducing manual reporting be useful?”
If they agree, follow through with a relevant message.
During an active evaluation, the same objection needs a different question:
“Is the difficulty finding time to evaluate the options, or finding people to implement one?”
Evaluation workload might be reduced with a focused demonstration and a concise comparison. Implementation capacity requires a realistic plan. Another meeting won’t solve a shortage of delivery resources.
3. “Send me some information”
Treat this as a request worth clarifying.
“Certainly. Are you mainly looking for pricing, technical details or evidence from a similar organisation?”
Send the material that answers the request. For a finance stakeholder, that might be a cost breakdown. For a sales leader, it might be a relevant training scenario.
If the conversation supports it, ask what happens after the review:
“Will you be assessing this yourself, or sharing it with someone else?”
That helps you make the material useful without forcing a meeting onto every email exchange. Generic brochures leave the buyer to work out the relevance themselves.
Price and value: What is the buyer actually questioning?
Five objections can sound like resistance to price while raising different issues: affordability, funding, comparison, negotiation and confidence in the return. Separating them prevents unnecessary concessions.
4. “It’s too expensive”
Start by identifying the reference point.
“The proposal is above what you expected. What range or alternative were you comparing it with?”
If the buyer expected €15,000 and your proposal is €30,000, explain what drives the difference. Check whether the additional scope is actually necessary.
If they question the value, revisit the outcome and the evidence supporting it. A list of features won’t establish that the investment makes sense.
Before changing the price, determine whether the buyer needs a different scope, a stronger business case or a genuinely cheaper option.
5. “We don’t have the budget”
Clarify whether there is no available funding, no allocated budget or no authority to use it.
“Would this need funding in the next planning cycle, or can projects still be approved if they meet a business-case threshold?”
A confirmed spending freeze may justify postponing the opportunity. An unallocated budget may require a proposal to the person who controls the relevant funds.
For example, a sales director might sponsor a training initiative while learning and development owns the budget. Establish who funds, evaluates and approves the purchase.
A smaller initial scope can help if it delivers a useful outcome. It shouldn’t become a token purchase that cannot solve the buyer’s problem.
6. “Your competitor is cheaper”
Compare the offers against the buyer’s requirements.
“Let’s look at the price difference alongside what each proposal includes. Which requirements matter most in your decision?”
Suppose one supplier quotes €18,000 and another €24,000. Establish whether both include the required users, onboarding, support and integrations.
If the offers are equivalent for the buyer’s needs, acknowledge that the cheaper option may be attractive. If there is a meaningful difference, demonstrate its relevance.
For instance, an additional capability matters only if the buyer will use it and values the result. Avoid turning the conversation into a long comparison of features that won’t affect their decision.
7. “Can you give us a discount?”
A discount request may be routine negotiation. Clarify what the buyer is trying to achieve.
“Are you working towards a fixed total budget, or reviewing the commercial terms across suppliers?”
Then discuss the available options within your pricing policy. These might include a smaller deployment, different payment arrangements or a concession linked to a commitment that has value to your business.
Explain each trade-off clearly. A longer contract, for example, also increases the buyer’s commitment.
Before finalising revised terms, confirm what else remains unresolved:
“If we agree on the commercial terms, which approvals would still be outstanding?”
A price agreement doesn’t establish that security, procurement or the business sponsor has approved the purchase.
8. “I’m not convinced by the ROI”
Build the calculation together and expose the assumptions.
Imagine a workflow tool with €24,000 in annual fees and €6,000 in implementation costs. Twenty employees each spend two hours per week on the process, across 46 working weeks. At €40 per hour, that represents €73,600 of annual staff time.
If the tool removes half the work, the potential capacity released is worth €36,800. At a quarter, it is €18,400. That difference materially changes the case against €30,000 in first-year costs.
Ask:
“Which assumption would you need us to validate before using this in your approval process?”
Include adoption time and internal implementation work. Also distinguish released capacity from cash savings: freeing employee time doesn’t automatically reduce payroll.
A credible business case should survive a conservative scenario.
Existing solutions: Is there a worthwhile reason to change?
An incumbent supplier or internal process has advantages simply because it is already operating. Your proposal needs to justify the effort and risk of changing it.
9. “We already have a supplier”
Explore the current arrangement without criticising a decision the buyer helped make.
“What would you want to preserve from the current service, and what would you review at renewal?”
The answer may reveal a specific gap: reporting delays, limited support coverage or a workflow that still requires manual intervention.
Investigate the gap before proposing a replacement. If it is minor, switching may be disproportionate.
Where there is a credible reason to evaluate alternatives, establish renewal dates, notice periods and migration dependencies. Begin planning early enough for the buyer to make a considered decision.
10. “We can build this internally”
An internal solution may be the right option, particularly when the requirements are highly specific.
Help the buyer compare the complete commitments:
“Who would own the initial build, and who would maintain it when requirements change?”
The comparison should cover delivery time, internal capacity, maintenance, support and the work the team would postpone to build it.
For an internal training tool, for example, someone must maintain scenarios, manage access and keep evaluation criteria consistent. Those responsibilities continue after launch.
Offer a transparent build-versus-buy assessment. Claiming that internal development always costs more weakens your credibility with buyers who have capable technical teams.
Timing and priorities: What would make action worthwhile?
A buyer can believe in your product and still have stronger reasons to invest elsewhere. Understanding those competing demands makes the next conversation more useful.
11. “This isn’t a priority”
Find out what currently receives attention and resources.
“Which outcomes are taking priority this quarter?”
Then assess whether your offer directly supports those outcomes.
If the company is expanding its sales team, consistent onboarding may be relevant. If it is reducing its product range, a project focused on launching additional products may have little urgency.
Any connection should be specific enough to test. Explain which existing initiative the purchase would support, how and at what cost.
If there is no meaningful connection, accept the timing. Claiming every solution supports every strategic objective makes prioritisation harder.
12. “Come back next quarter”
Establish what is expected to change.
“What will be different next quarter that would make this easier to evaluate or approve?”
A budget release, contract renewal or completed migration provides a real trigger. Work backwards from it to identify when evaluation would need to begin.
If the buyer can’t name a change, ask whether another concern remains unresolved.
Where a delay has a measurable consequence, discuss it using figures the buyer accepts. Thirty hours of monthly rework would mean another 90 hours over three months, but the buyer must still weigh that against other demands.
Record the reason for reconnecting alongside the date.
13. “We’re reorganising”
A reorganisation can change the project owner, budget, user population and business case. Reconfirm those foundations before pushing for a decision.
“Which parts of this project remain agreed, and which depend on the new organisation?”
If responsibilities are unsettled, maintaining a short record of the work completed may be more helpful than requesting another demonstration.
If the project remains active, update the stakeholder map and confirm who can approve the next step.
Avoid treating organisational disruption as automatic urgency. A proposal built for a structure that no longer exists needs revisiting.
Internal approval: How do you help a buying group reach a decision?
A supportive contact is valuable, but B2B purchases often depend on several people with different responsibilities.
In a survey of 632 B2B buyers, conducted in August and September 2024, Gartner found that 74% of buyer teams demonstrated unhealthy conflict during the decision process. This included conflicting objectives and disagreement about the course of action. Source: Gartner, May 2025.
The practical implication is to establish how the group will evaluate the purchase, including where its members disagree.
14. “I’m not the decision-maker”
Learn how your contact participates in the purchase.
“What part of the evaluation do you own, and who needs to approve the recommendation?”
They may manage the users, assess technical fit or prepare the recommendation. Each role matters.
Ask how they would prefer to involve the other stakeholders. A joint conversation can help when your contact supports it and its purpose is clear.
Avoid bypassing them to contact a more senior person. You risk losing context and damaging a relationship with someone whose assessment may strongly influence the decision.
15. “I need approval from my manager or the committee”
Help your contact prepare for the decision the group actually needs to make.
“What would cause the committee to reject or postpone this proposal?”
That question can reveal concerns that haven’t appeared in your conversations: unclear ownership, weak economics or insufficient implementation capacity.
Prepare a concise decision brief covering the shared objective, options considered, costs, expected outcomes, delivery responsibilities and remaining uncertainties.
Confirm the review date and what will happen afterwards. “The committee meets on Tuesday and will decide whether to fund a pilot” is useful progress. “They’re discussing it internally” leaves the next step unclear.
Delivery and trust: Can the buyer safely commit?
At this stage, buyers may understand the value while questioning whether the organisation can deliver it. Specific operational evidence becomes essential.
16. “IT or security won’t approve this”
Find out whether this is an anticipated concern or the result of an actual review.
“Has a requirement already been identified that we don’t meet, or do we need to start the assessment?”
Ask for the relevant requirements and bring in the people qualified to answer them. Depending on the product, the discussion may involve access controls, data handling, integration methods or documentation.
Track unanswered questions and owners. Don’t promise a capability or certification based on an assumption.
If a mandatory requirement cannot be met, explain that early. A sales response cannot substitute for technical approval.
17. “Implementation will take too much time”
Make the workload visible.
“Which team would carry most of the implementation work, and where is its capacity constrained?”
Present the tasks, dependencies and responsibilities on both sides. Include work that vendors sometimes omit from the initial conversation, such as data preparation, internal communication and manager training.
A phased deployment may help when it reduces the initial burden while delivering a useful outcome.
For example, starting with one region can simplify coordination. It won’t resolve a company-wide integration dependency. The proposed approach must address the specific source of effort.
18. “Our team won’t use it”
Treat adoption as part of the buying decision.
“What happened with the last tool the team struggled to adopt?”
Perhaps it duplicated existing work, required too much setup or had no manager support. Those causes need different responses.
For sales-training software, agreeing when practice happens and how managers use feedback may matter as much as the product experience.
A pilot can test these conditions. Define participation expectations, ownership and useful success measures in advance.
A few enthusiastic volunteers can reveal usability problems, but they provide limited evidence about adoption across an entire organisation.
19. “We’ve tried something similar, and it didn’t work”
Ask the buyer to describe the failure before presenting your differences.
“Where did the previous approach break down: the product, the rollout or the results?”
If a training programme failed because managers never reinforced the learning, more content may reproduce the same outcome. If the product lacked a required capability, a different implementation plan won’t fix that gap.
Connect your evidence directly to the failure they describe. That might mean demonstrating a workflow, introducing a comparable customer reference or explaining who owns delivery.
If you cannot show why the relevant conditions would be different, acknowledge that uncertainty.
20. “We need to think about it”: How do you handle an unresolved decision?
Give the buyer room to decide while offering to clarify what remains open.
“Of course. Which part still needs consideration: the choice of solution, the business case or the practicalities of getting started?”
If they are comparing options, summarise the trade-offs against their agreed criteria. If they doubt the outcome, identify a proportionate way to test the uncertainty. If stakeholders disagree, help make the disagreement explicit.
Consider a buyer choosing between a regional deployment and a company-wide launch. Another product demonstration may add little. A clear recommendation, with the reasons and limitations explained, could make the decision easier.
End with a next step that has a purpose and an owner. If they prefer to decide without further contact, respect that.
Which mistakes make sales objections harder to resolve?
Even a well-chosen response can fail if the surrounding conversation creates distrust.
Answering before understanding. A buyer mentions price, and the salesperson immediately explains premium features. The real issue is an unapproved budget. One clarifying question could prevent several minutes of irrelevant persuasion.
Turning questions into pressure. Repeatedly asking “If we fix that, will you sign?” can make a complex decision feel like a series of traps. Establish what a resolution would enable without demanding commitments the buyer cannot make.
Using examples that don’t transfer. A result from a large enterprise with dedicated implementation resources may offer little reassurance to a small team. Explain which conditions are comparable and which differ.
Creating artificial urgency. An arbitrary deadline may secure a response while leaving the underlying concern unresolved. Use the buyer’s actual deadlines and dependencies.
Making promises outside the offer. Roadmap features, unsupported integrations and unrealistic deployment dates create problems for both sides. Confirm what is available before relying on it.
Treating every polite answer as progress. “That makes sense” is different from agreeing that a concern has been resolved. Clarify what the buyer is now comfortable doing.
How can you prevent objections from appearing too late?
Bring foreseeable constraints into the evaluation early enough to act on them.
A Gong study of 11,331 sales opportunities, each involving at least three calls, found that discussing pricing on the first call was associated with higher win rates. The research is observational, but it supports addressing commercial fit early. Source: Gong’s pricing and budget research.
Give buyers a realistic view of the likely cost and what affects it. Establish who needs to participate, which requirements are mandatory and what implementation involves.
A useful discovery question is:
“When you’ve bought something like this before, what caused the biggest delay?”
Record the answer in a shared evaluation plan. If security review previously took six weeks, account for that before promising a launch date.
The goal is to surface concerns while there is still time to investigate them.
How should sales teams train for objection handling?
Use recent conversations to build practice scenarios with enough detail to require judgement.
For “It’s too expensive,” create three buyer situations: a strict spending ceiling, a cheaper competing offer and doubt about the projected return. Keep the opening phrase the same and change the underlying concern.
The salesperson should discover which situation they face.
After the exercise, review a small number of observable behaviours:
Did the rep clarify the concern accurately?
Did the response use relevant, credible evidence?
Did the rep check what remained unresolved?
Did the next step address the actual blocker?
Repeat the difficult moment with one improvement. Then introduce a different buyer response so the rep has to adapt.
Soft’s AI sales training platform supports this approach through simulated sales conversations, personalised feedback and targeted exercises. Reps can practise handling objections before facing them in live opportunities, while managers focus coaching on the areas that need attention.
Measure progress in real conversations as well as practice. Look for clearer qualification, fewer unsupported promises and better-defined next steps.
Try an objection-handling scenario with Soft and practise the conversation your team finds hardest.
FAQ: Common objections in B2B sales
What are the main types of B2B sales objections?
Common categories include relevance, price and value, existing solutions, timing, internal approval, implementation and trust. The same wording can belong to different categories, so clarify the situation before choosing a response.
What is the difference between a price objection and a budget objection?
A price objection questions whether the offer is worth its cost. A budget objection concerns whether funding is available or approved. Price concerns require a comparison of value and cost; budget concerns require understanding the funding process and constraints.
What is the LAER method?
LAER stands for Listen, Acknowledge, Explore and Respond. Developed by Carew International, it provides a sequence for understanding a buyer’s concern before addressing it. After responding, check whether anything remains unresolved.
How do you know whether an objection is the real issue?
Ask a neutral question and listen for specifics. A named requirement, approval step or capacity constraint gives you something to investigate. If the explanation remains unclear, summarise what you understand and invite the buyer to correct it.
Should you always try to overcome a sales objection?
No. Some objections reveal that the product, timing or commercial arrangement is unsuitable. A clear refusal, an essential missing capability or an impossible delivery deadline may justify ending or postponing the opportunity.
Can AI roleplay improve objection handling?
AI roleplay gives salespeople opportunities to rehearse varied buyer conversations and receive feedback. Its usefulness depends on realistic scenarios, accurate product information and coaching criteria. Assess whether the behaviours practised also improve in real sales conversations.