Objection Handling: 25 Common B2B Sales Objections & How to Respond

Objection Handling: The Complete Guide for B2B Sales Teams

Updated March 2026

Every salesperson remembers the first time a prospect's objection stopped them dead. You had the pitch memorised. You knew the product inside out. Then the prospect said, "We don't have budget for this right now," and your mind went blank.

Here is the uncomfortable truth about B2B sales: objections are not obstacles. They are buying signals. When a prospect raises an objection, they are telling you they have thought about your offer seriously enough to identify concerns. The prospects who are truly uninterested do not object — they simply ghost you.

Research from Gong's analysis of over 2 million sales calls shows that successful deals actually contain more objections than lost deals. Top-performing reps encounter an average of 4-6 objections per deal cycle, and Salesforce's State of Sales research consistently finds that the highest-performing teams treat objections as discovery, not defence. The difference is not that they avoid objections — it is that they handle them with skill, empathy, and preparation.

I have spent years building sales enablement programmes, delivering fractional sales leadership (compared in our fractional VP Sales roundup), and running one of the best outbound sales agencies for B2B technology companies, and the single most requested resource from sales teams is always the same: "Give us the scripts for when prospects push back." This guide is that resource.

We are going to cover 25 real objections, organised into seven categories, with a proven response script and follow-up strategy for each one. We will also cover two frameworks you can use to handle any objection — even ones you have never heard before. And we will talk about something most objection handling guides ignore entirely: how to prevent objections from coming up in the first place.

Let us get into it.

Why Objections Happen (And Why That Is a Good Thing)

Before we dive into the scripts, it is worth understanding why prospects object. Objections are not random. They fall into predictable patterns driven by psychology, organisational dynamics, and where the prospect sits in their buying journey.

There are four fundamental reasons prospects raise objections:

1. Genuine concern. They are interested but have a real question or worry that needs addressing before they can move forward. This is the best-case scenario.
2. Lack of information. They do not yet understand enough about your solution to see how it solves their specific problem. This is a discovery gap — you have not done enough upfront work to connect your solution to their pain.
3. Internal politics. They may personally see value but anticipate resistance from colleagues, leadership, or procurement. The objection they voice is often a proxy for the internal battle they are fighting.
4. Inertia. Change is hard. Even when the status quo is painful, it is familiar. People will tolerate a known pain over an unknown solution almost every time — unless you make the cost of inaction impossible to ignore.

Understanding which of these four drivers is behind a specific objection changes how you respond to it. A genuine concern requires a direct answer. A lack of information requires better discovery. Internal politics require equipping your champion. Inertia requires urgency and a compelling business case.

If your discovery process needs work, our discovery call framework covers exactly how to uncover pain, qualify effectively, and set up the rest of the sales conversation.

Two Objection Handling Frameworks Every Rep Should Know

Before the 25 specific objections, two structural frameworks that work for any pushback. Internalise these and your reps can handle objections they have never encountered before.

Framework 1: Feel-Felt-Found

The classic empathy-based framework, and it has endured because it works.

• Feel: Acknowledge and validate the emotion. "I completely understand why you feel that way."
• Felt: Normalise it by referencing others who reacted the same way. "Many of our current customers felt the same way before they started working with us."
• Found: Share the outcome those others experienced. "What they found was that [specific result] within [timeframe]."

Example. Prospect: "Your pricing is significantly higher than the other options we are looking at." Rep: "I understand — this is a significant investment. Several of our current customers, including [similar company], felt the same way during their evaluation. What they found was that the total cost of ownership was actually 30% lower over three years because of [specific reason], and they saw ROI within six months."

It works because you are not arguing — you are validating their perspective and then offering new evidence. When to use: emotional or instinctive objections like price shock, fear of change, or uncertainty about results.

Framework 2: Acknowledge-Ask-Advocate (AAA)

Better suited to complex B2B sales where the stated objection often masks a deeper concern.

• Acknowledge: Show you heard the concern. Do not dismiss or counter it.
• Ask: Ask a clarifying question. The surface objection is rarely the real one.
• Advocate: Once you understand the true concern, offer evidence that addresses it.

Example. Prospect: "We are not sure this is the right time for us." Rep: "That makes sense — can I ask what specifically about the timing feels challenging? Is it budget cycle, bandwidth, or something else?" Prospect: "We have a major product launch in Q2 and the team is stretched thin." Rep: "Helpful context. A lot of teams we work with specifically start during busy periods because we handle [specific workload], which frees their team to focus on priorities like your launch. Would it help if I showed you how [similar company] ran their implementation alongside a major initiative?"

Without the Ask step, the rep might have pitched flexible payment terms — completely missing the real concern (bandwidth, not budget). When to use: complex mid-to-late-stage deals where the stated objection is unlikely to be the real one. With practice, you will blend elements of both frameworks naturally.

The 25 Objections: Scripts, Context, and Follow-Up Strategies

Now let us get into the specifics. Each objection below includes: what the prospect says, why they are really saying it, a response script, and a follow-up strategy for after the call.

---

Category 1: Price Objections

Price objections are the most common category, and they are also the most frequently mishandled. The mistake most reps make is immediately offering a discount — a pattern HubSpot's sales research blog has flagged as one of the top revenue leaks in B2B selling. Discounting trains the prospect to negotiate harder and signals that your original pricing was inflated.

Objection 1: "It's too expensive."

Why they say it: They may genuinely lack budget, but more often they have not yet connected your price to the value they will receive. This is a value gap, not a price problem.

Response script:

"I hear you — and I'd never want you to feel like you're overpaying. Can I ask: when you say it's too expensive, are you comparing us to a specific alternative, or is it the absolute number that feels high relative to your budget?"

[If comparing to an alternative]: "That's helpful. What I'd want to make sure is that we're comparing like for like. A lot of teams we talk to initially see a lower sticker price from [competitor type] but then discover that [specific hidden cost or limitation] ends up costing them more in the long run. Would it be useful if I walked you through a total cost of ownership comparison?"

[If absolute budget concern]: "Understood. Let me ask this — if we could show you that this investment would generate [X return] within [timeframe], would the budget exist? Sometimes it's about building the business case internally, and we've helped other teams do exactly that."

Follow-up strategy: Send a one-page ROI calculator pre-populated with their specific numbers. Include a case study from a similar company showing payback period. If they are comparing to competitors, your battle cards should provide the competitive pricing intelligence your reps need.

Objection 2: "We don't have budget for this."

Why they say it: This is sometimes true, but it is also one of the most common brush-off lines in B2B sales. The question is whether they genuinely cannot afford it or whether they have not prioritised it.

Response script:

"I appreciate you being upfront about that. Can I ask — is this a 'there's no budget at all' situation, or more of a 'this wasn't in our plan for this quarter' situation? The reason I ask is that those are quite different problems, and I want to make sure I'm being helpful rather than pushy."

[If no budget at all]: "That's fair. Would it make sense for me to follow up at the start of your next planning cycle? When does budgeting typically happen for your team?"

[If not planned]: "What we've seen with a lot of teams is that unplanned investments actually get approved more easily when there's a clear, time-sensitive business case. If I could help you build a one-page proposal that shows [specific impact], would that be worth 15 minutes of your time?"

Follow-up strategy: If genuine no-budget, set a calendar reminder for their budget cycle and send a valuable piece of content every 4-6 weeks to stay top of mind. If it is a prioritisation issue, send them a business case template they can use internally.

Objection 3: "Your competitor is cheaper."

Why they say it: Sometimes this is a negotiation tactic. Sometimes it is genuine. Either way, the worst response is to drop your price immediately.

Response script:

"That's not unusual — we're rarely the cheapest option, and that's deliberate. The question I'd ask is: what's included at that price? In our experience, teams often find that the cheaper option requires [additional cost 1], [additional cost 2], and [additional cost 3] on top of the listed price. When you factor all of that in, the gap usually narrows significantly — and sometimes reverses."

"Can I ask which specific capabilities you're comparing? I want to make sure we're having an apples-to-apples conversation."

Follow-up strategy: Send a feature comparison that highlights what is included in your price versus what requires add-ons or additional investment with the competitor. Use specific numbers if possible.

Objection 4: "We need to get more quotes first."

Why they say it: Procurement processes often require multiple quotes. But sometimes this is a polite way of saying "I'm not convinced yet and I want to shop around."

Response script:

"Absolutely — doing your due diligence is important, and I'd encourage it. Out of curiosity, what criteria are you using to evaluate the different options? I'd love to make sure we've given you everything you need to make a fair comparison."

"Also, would it be helpful if I sent you a comparison checklist? We've seen teams waste weeks going back and forth with vendors because they didn't align on evaluation criteria upfront. I can send you a framework that makes the process faster for everyone."

Follow-up strategy: Send the comparison checklist and include your solution's strengths prominently in the evaluation criteria. This subtly anchors the evaluation around your differentiators.

Objection 5: "Can you give us a discount?"

Why they say it: They may genuinely need a better price to get approval, or they may simply be testing whether your pricing has room to move. In B2B, almost everyone asks.

Response script:

"I appreciate you asking. Our pricing reflects the value we deliver, and we're confident in it — but I also want to find a way to make this work. Rather than discounting, can we talk about what flexibility would be most helpful? For example, we could adjust the scope, payment terms, or implementation timeline. What would make the biggest difference for you?"

[If they push harder]: "I can certainly take a conversation about pricing back to my team. But to do that effectively, I'd need to understand: if we found a way to make the numbers work, is this something you're ready to move forward on? I want to make sure we're solving the right problem."

Follow-up strategy: If you must offer a concession, always get something in return — a faster close date, a longer contract term, a case study commitment, or an introduction to another department. Never give something for nothing.

---

Category 2: Timing Objections

Timing objections are tricky because they feel reasonable. "Not right now" is hard to argue with. But the best reps know that timing objections are often the prospect's way of avoiding a decision rather than making one.

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

Why they say it: They have competing priorities and have not yet seen enough urgency to move your solution up the list. This is a failure of your business case, not genuinely bad timing.

Response script:

"That's completely fair — every team has more priorities than bandwidth. Can I ask what is at the top of your list right now?"

[After they share]: "That makes sense. Let me ask this: how much of your team's time is currently being spent on [the problem your solution solves]? The reason I ask is that many of the teams we work with initially saw this as a 'next quarter' priority, but when they quantified how much time and money the current approach was costing them, it jumped up the list. Would it be useful if I helped you put a number on that?"

Follow-up strategy: Send a cost-of-inaction analysis showing the tangible cost of waiting — revenue leakage, opportunity cost, or competitive risk. Quantify the delay in pounds or hours.

Objection 7: "Call me back next quarter."

Why they say it: They want you off the phone. Sometimes there is a genuine reason (budget cycles, reorgs), but often this is the polite equivalent of "I'm not interested enough to deal with this right now."

Response script:

"Happy to do that. So I can be as prepared as possible when we reconnect — what specifically will have changed by next quarter that makes this a better conversation? Is it budget, bandwidth, or something else?"

[If they give a vague answer]: "I ask because what I'd hate is for us to reconnect in three months only to find that the same things are in the way. If there's something specific that needs to happen first, I'd like to understand it so I can be genuinely useful when I call back — rather than just checking a box."

Follow-up strategy: If they give a specific trigger (budget approval, new hire, project completion), set a reminder for that date and send one piece of relevant content between now and then. If the answer was vague, they are likely not a real opportunity — deprioritise and nurture through content.

Objection 8: "We're in the middle of another project right now."

Why they say it: This is usually genuine. Teams do get consumed by major initiatives. The question is whether your solution is complementary to that project or competing for the same resources.

Response script:

"That makes sense — I wouldn't want to add to an already-full plate. What project is the team focused on, if you don't mind me asking?"

[After they share]: "Interesting. We've actually worked with a few teams who were going through something similar. In their case, they found that [your solution] actually accelerated that initiative because [specific connection]. Would it be worth a quick conversation about whether the same could be true for you, or does it genuinely make sense to wait until that wraps up?"

Follow-up strategy: If the project is genuinely a blocker, agree on a specific follow-up date after the project concludes. Send a case study showing how another company implemented your solution alongside a similar initiative.

Objection 9: "We just signed a contract with someone else."

Why they say it: They have literally just committed to a competitor or alternative. This is one of the hardest timing objections because there is a real contractual barrier.

Response script:

"Understood — I appreciate you being transparent about that. How long is the contract? And without asking you to break any commitments, would it make sense for us to have a conversation about three months before that contract comes up for renewal? That way you'd have a clear comparison ready when it's time to evaluate."

"Out of curiosity, what ultimately tipped the decision in their favour? I ask because the feedback helps us, and also because if there's something they're not covering well, that might be worth a separate conversation."

Follow-up strategy: Set a reminder for 90 days before contract renewal. Send quarterly check-ins with relevant content. Track their satisfaction with the competitor through social signals and review sites.

---

Category 3: Authority Objections

Authority objections reveal that the person you are talking to cannot (or believes they cannot) make the decision alone. Forrester's B2B research consistently finds that the average buying committee now includes 6-10 stakeholders, which means single-threading a deal almost guarantees an authority objection later. The mistake most reps make is treating these as dead ends rather than opportunities to expand into the buying committee.

Objection 10: "I need to run this by my boss."

Why they say it: They may genuinely need approval, or they may be using their boss as a shield. The key is to determine which and equip them if they are a real champion.

Response script:

"Of course — this typically involves multiple stakeholders. When you bring this to your boss, what do you think their main questions or concerns will be?"

[After they share]: "Helpful. Would it be useful if I put together a one-page summary covering those specific points — so you have something concrete to share rather than relaying everything from memory? Would it also make sense for me to join that conversation, just to answer any technical or commercial questions directly? That often saves a round of back-and-forth."

Follow-up strategy: Send a one-page executive summary tailored to the boss's likely concerns — business case, ROI, timeline. If you can get a meeting with the decision-maker, prepare for it using our sales playbook template.

Objection 11: "Our procurement team handles this."

Why they say it: In larger organisations, procurement genuinely does handle vendor evaluations. This is not an objection so much as a process reality. But it can kill deals if you do not handle it well.

Response script:

"Understood — and I'm happy to work with your procurement team. Before I do, can I ask: are you personally supportive of moving forward? I want to make sure I'm not wasting procurement's time if this isn't something you'd recommend."

[If yes]: "Great. What I'd suggest is that you and I align on the key requirements and outcomes first, and then bring procurement in with a clear brief. That tends to accelerate the process rather than slowing it down. Does that approach work for you?"

Follow-up strategy: Prepare a procurement-ready package: pricing summary, security documentation, compliance certifications, references, and contract terms. The more prepared you are for procurement's standard questions, the faster this moves.

Objection 12: "I'm not the right person to talk to about this."

Why they say it: They may genuinely be the wrong contact, or they may be trying to get rid of you. The response depends on which it is.

Response script:

"I appreciate you telling me that — the last thing I want to do is waste your time. Can I ask who would be the right person to speak with? And would you be open to making an introduction, or would you prefer I reach out to them directly and mention that we spoke?"

[If they are reluctant to give a name]: "I understand. Even if you can point me in the right direction — is this something that would sit with your [VP of Sales / Head of Marketing / CTO]? That way I can do my own research and reach out without putting you in an awkward position."

Follow-up strategy: If they give you a name, send a warm outreach to that person within 24 hours, referencing the conversation. If they do not, use LinkedIn and your CRM to identify the right contact and reach out using a cold calling script that references the original conversation.

---

Category 4: Need Objections

Need objections suggest the prospect does not see a fit between your solution and their problems. This is almost always a discovery failure — either you are talking to the wrong prospect, or you have not uncovered the right pain.

Objection 13: "We don't have that problem."

Why they say it: They may genuinely not have the problem, or they may not recognise it yet. Many prospects are so accustomed to their current pain that it feels normal.

Response script:

"That's great to hear — genuinely. Can I ask how you're currently handling [the process or outcome your solution addresses]? The reason I'm curious is that many teams we work with didn't initially see it as a problem either, until they realised how much time and money was going into [specific symptom]."

[If they describe their current process]: "It sounds like you've got a solid approach. One thing I've noticed with teams at your stage is that [specific challenge that emerges at their company size or maturity]. Has that come up at all?"

Follow-up strategy: If they genuinely do not have the problem, they are not a prospect — move on. If they have the problem but do not recognise it, send a case study from a similar company that describes the "before" state in detail. Sometimes people need to see their situation described by someone else to recognise it.

Objection 14: "We already have a solution for that."

Why they say it: They have an existing tool, process, or team handling this function. The question is whether they are satisfied with it or merely tolerating it.

Response script:

"That's good — it would be unusual if you weren't doing anything in this area. Can I ask: on a scale of 1 to 10, how happy is your team with the current solution?"

[If they say 7 or below]: "So there's room for improvement. What's the biggest gap or frustration with what you have today?"

[If they say 8 or above]: "That's great. I don't want to fix something that isn't broken. Would you be open to a quick comparison — just to benchmark what you have? If your current solution comes out on top, you'll have confirmed you made the right choice. If there are areas where we could add value, that's worth knowing too."

Follow-up strategy: For dissatisfied prospects, send a feature comparison focused on their specific pain points. For satisfied prospects, add them to a long-term nurture sequence — satisfaction can change quickly when contracts renew, leadership changes, or the existing vendor makes a misstep.

Objection 15: "We can handle this in-house."

Why they say it: They believe their internal team can achieve the same outcome without external help. Sometimes they are right. Often they are underestimating the cost and opportunity cost of doing it internally.

Response script:

"That's an option, and some teams do it successfully. Have you costed it out — not just direct costs (salaries, tools, training) but the time to build that capability and the opportunity cost of pulling your team away from other priorities? Many of the companies we work with started with an in-house approach and found it took [X months] longer and cost [Y%] more than budgeted — not because their team wasn't capable, but because [specific reason]."

Follow-up strategy: Send a build-versus-buy analysis showing true cost comparison, including hidden costs like management overhead, recruitment, ramp time, and attrition risk.

Objection 16: "We tried something like this before and it didn't work."

Why they say it: They have been burned. This is an emotional objection rooted in a bad past experience — and one of the strongest because it comes with their own evidence.

Response script:

"I appreciate you sharing that — and I'm sorry it happened. Can I ask what specifically went wrong? Was it the approach, the execution, the vendor, or something else?"

[After they share]: "Useful context. What I can tell you is that [specific differentiator]. [Customer name] had a very similar experience with [previous vendor] before working with us, and the key differences that led to a different outcome were [1, 2, 3]. Would it be worth looking at what made that situation different from yours?"

Follow-up strategy: Send the case study from a customer who had a similar bad experience before switching to you. Emphasise what was different about your approach.

---

Category 5: Competition Objections

Competition objections mean you are in a deal — which is better than not being considered at all. The goal is not to trash your competitor but to position your strengths against their specific weaknesses.

Objection 17: "We're already talking to [Competitor]."

Why they say it: They want you to know you are not the only option — often a negotiation tactic to create urgency or extract better terms.

Response script:

"Makes sense — [Competitor] is a solid company. Where are you in that conversation? Have you seen a demo, or are you early? I'd rather complement your evaluation than duplicate it. There are specific areas where we differ significantly from [Competitor], and I'd like to focus our conversation on those so you get the most useful comparison."

Follow-up strategy: Send competitive positioning materials focused on your genuine differentiators — strategic differences in approach and outcomes, not feature-by-feature comparisons. Your battle cards should give your reps everything they need here.

Objection 18: "We've heard [Competitor] is better at [specific thing]."

Why they say it: They have done research or heard from a peer — an opportunity to either acknowledge a genuine gap or correct a misconception.

Response script:

"I've heard that too, and I'd want to be honest with you. [Competitor] is strong at [specific thing] — I won't pretend otherwise. The question is whether [specific thing] is the most important factor for what you're trying to achieve. Teams that prioritise [specific thing] often find [your differentiator] has a bigger impact on [business outcome]. For example, [customer name] initially leaned towards [Competitor] for that reason but ultimately chose us because [specific reason]. Six months in, they told us [result]."

Follow-up strategy: Send a comparison that honestly acknowledges the competitor's strength but reframes the evaluation around the criteria that matter most for the prospect.

Objection 19: "We're leaning towards [Competitor] right now."

Why they say it: You are losing. They may be creating urgency, or they may genuinely prefer the other option. Either way, you need to act fast.

Response script:

"I appreciate the transparency. Can I ask what's driving that preference — specific capabilities, pricing, the relationship, or something else?"

[After they share]: "Got it. Before you make a final decision, would you be open to one more conversation focused on [that area]? If [Competitor] is still the better fit after that, I'll respect the decision completely. What I'd hate is for you to choose them and then discover three months in that [specific risk] is an issue — because that's a story we hear regularly from teams who switch to us after trying them first."

Follow-up strategy: Request one final meeting focused on the area where you are perceived as weaker. Bring your strongest proof points — references, data, a tailored demo. This is your last shot.

Objection 20: "We built something internally that does this."

Why they say it: They have invested time and resources into a homegrown solution and are understandably reluctant to abandon it.

Response script:

"That shows real initiative. Can I ask: how long ago was it built, and how much of your team's time goes into maintaining and improving it? Internal solutions are great at solving the initial problem, but they often struggle to scale. As requirements grow, the person who built it becomes the bottleneck, maintenance costs creep up, and the gap between what it does and what you need it to do keeps widening. Is any of that resonating?"

Follow-up strategy: Send a build-versus-buy comparison covering total cost of ownership over 3 years, including engineering time, maintenance, and opportunity cost. Include a case study from a company that transitioned away from an internal solution.

---

Category 6: Trust Objections

Trust objections are deeply personal. The prospect does not yet believe you, your company, or your claims. These require patience, proof, and sometimes the willingness to let someone else make the case for you.

Objection 21: "I've never heard of your company."

Why they say it: They are risk-averse and unfamiliar with you. In B2B, buyers often prefer the "safe" known brand — even if it is not the best option.

Response script:

"Fair — we're not the biggest name in the space, and I'd rather be honest about that. What I can tell you is that we work with [notable customer names in their industry], and the reason they chose us over [bigger competitors] was [specific differentiator]. Reputation matters, especially when you're putting your name behind a recommendation internally. Would it help to speak directly with one of our customers in [their industry]? I can arrange a 15-minute reference call with someone in your exact position."

Follow-up strategy: Send a package of social proof — customer logos, case studies, review site ratings, analyst mentions, awards. Make it easy for them to validate you independently.

Objection 22: "How do I know this will actually work?"

Why they say it: They need proof. Claims without evidence are just marketing — this prospect wants data, references, or guarantees.

Response script:

"That's the most important question you could ask, and I wouldn't want you to take my word for it. Let me offer three things. First, a case study from [similar company] showing [specific metric] in [timeframe]. Second, a direct reference call with their [role]. Third, [specific risk reduction mechanism — pilot programme, money-back guarantee, phased implementation, performance-based pricing]. Which would be most useful?"

Follow-up strategy: Send the case study, arrange the reference call, and detail the risk reduction mechanism in writing.

Objection 23: "Your company seems too small/new to handle our needs."

Why they say it: They are worried about reliability, scalability, and the risk of working with a vendor that might not be around in two years.

Response script:

"I understand — working with a smaller company is a different bet. But there are real advantages: you'll get senior attention rather than a junior account manager, we're more agile, and your business matters more to us than it does to a company with ten thousand customers. To address reliability directly: we've been in business for [X years], we work with [Y customers], and here are three references you can contact who have been with us for [Z years]."

Follow-up strategy: Provide references from long-standing customers, share financial stability indicators if appropriate, and offer contractual protections (SLAs, escrow, exit clauses) that reduce their risk.

---

Category 7: Status Quo Objections

Status quo objections are the hardest category. The prospect is not saying "no" — they are saying "I'd rather do nothing." Fighting inertia requires making the cost of inaction vivid and specific.

Objection 24: "Things are fine the way they are."

Why they say it: Change is painful and risky. The current state may not be perfect, but it is predictable. This prospect needs a reason to move that outweighs the discomfort of change.

Response script:

"I'm glad things are working. When you say 'fine,' do you mean optimal, or good enough? In my experience, 'fine' usually means 'we've accepted the current limitations because fixing them feels like too much effort.' What I've seen with teams at your stage is that 'fine' today becomes a real bottleneck in 6-12 months when [industry trend or competitive pressure]. Would it be worth exploring what 'great' looks like — even just as a benchmark?"

Follow-up strategy: Send a cost-of-inaction analysis quantifying what "fine" is costing them in lost revenue, wasted time, or competitive disadvantage. Use industry benchmarks to show where they sit relative to peers.

Objection 25: "We don't want to disrupt what's working."

Why they say it: Fear of disruption is one of the most powerful forces in B2B buying. Even when the prospect sees value, the risk of breaking something that currently works feels too high.

Response script:

"Smart instinct — disruption for its own sake is never a good idea. What if the implementation was designed specifically to avoid disrupting your current operations? [Customer name] had the same concern — they were running [current process] and couldn't afford any downtime. We implemented alongside their existing system, ran both in parallel for [timeframe], and only switched over when they were 100% confident. Zero disruption. Would a similar phased approach address your concern?"

Follow-up strategy: Send a detailed implementation plan that explicitly addresses disruption risk. Include the parallel-run approach, rollback procedures, and testimonials from customers who transitioned without disruption.

---

Prevention vs Response: The Best Objection Is the One That Never Comes Up

Most sales training focuses on response. The best teams also focus on prevention — uncovering concerns early, addressing them proactively, and tailoring the presentation to what the prospect actually cares about. Five prevention strategies stand out:

• Do deeper discovery. Generic pitches generate objections. Use our discovery call framework to uncover real pain, priorities, and decision-making process before you pitch.
• Pre-empt common objections. If 80% of prospects raise pricing, address it before they do. "Let me address pricing upfront" signals confidence and removes the elephant from the room.
• Align your process to theirs. Pushing for a close when the buyer is still in evaluation mode generates objections. Map your sales playbook to their buying journey.
• Involve stakeholders early. Authority objections almost always happen because the right people were not involved early enough. Ask about the decision process in your first call.
• Use social proof proactively. The LinkedIn Sales Blog routinely points out that buyers trust peer evidence over vendor claims, so make proof a constant undercurrent — not a reactive measure.

Building Objection Handling Into Your Sales Process

Knowing how to handle objections is one thing. Building that capability across your team is another. Operationalise it with four habits:

• Maintain an objection library. Document every objection your team encounters with the response that works best. Review and update it quarterly.
• Role-play weekly. Have managers or peers play the prospect and push back hard. Uncomfortable, but the most reliable way to build the muscle.
• Record and review calls. Use Gong, Chorus, or Clari to spot which objections reps struggle with and which responses convert.
• Embed it in enablement. Your battle cards and sales playbook should both include objection-specific guidance, and your onboarding should include certification.

If you are building or overhauling your sales enablement programme, objection handling should be one of the first capabilities you develop.

Common Mistakes in Objection Handling

Before we wrap up, here are six mistakes that undermine even the best objection handling scripts:

1. Arguing with the prospect. The moment you argue, you lose. Acknowledge, empathise, then redirect. Never tell a prospect they are wrong.
2. Answering too quickly. Pausing before you respond shows you are thinking, not reacting. A two-second pause signals confidence. Blurting out a response signals desperation.
3. Treating every objection the same. A genuine budget constraint is not the same as a negotiation tactic. Diagnose before you prescribe.
4. Offering discounts at the first sign of price resistance. This trains prospects to push back every time. Defend your value before you discuss concessions.
5. Giving up after one objection. Research compiled by ZoomInfo shows that 44% of salespeople give up after one rejection — yet 80% of sales require five or more follow-ups. Persistence (not pushiness) is a skill.
6. Not asking clarifying questions. The stated objection is rarely the real one. Always ask "Can I ask what's behind that concern?" before jumping to a response.

Frequently Asked Questions

What is objection handling in sales?

Objection handling is the process of responding to a prospect's concerns, hesitations, or pushback during a sales conversation. It involves understanding the real concern behind the objection and providing a response that addresses it while moving the conversation forward. The best reps treat objections as engagement signals, not roadblocks.

What are the most common B2B sales objections?

They fall into seven categories: price, timing, authority, need, competition, trust, and status quo. Price and timing objections are the most frequent, accounting for roughly 50-60% of all objections in B2B sales conversations.

What is the best framework for handling sales objections?

Feel-Felt-Found suits straightforward, emotional objections — you empathise, normalise, and share what others found. Acknowledge-Ask-Advocate works better for complex objections — acknowledge the concern, ask a clarifying question, then advocate your position with evidence. Most experienced reps blend elements of both.

How do you handle the "it's too expensive" objection?

Avoid immediately offering a discount. Ask whether they are comparing you to a specific alternative or the absolute number feels high. For value problems, present a total cost of ownership comparison and ROI analysis. For budget problems, explore deal structures or help them build an internal business case.

How do you handle objections on a cold call?

Keep responses brief (under 30 seconds), acknowledge without being defensive, pivot to a question that re-engages them, and always have a clear ask. Our guide to cold calling scripts covers this in more detail.

How many times should you follow up after an objection?

Aim for 5-7 touches over 2-3 weeks for mid-funnel objections and 8-12 touches over 4-8 weeks for early-stage objections. Each follow-up should add new value rather than simply asking "Have you had a chance to think about it?"

What is the difference between an objection and a rejection?

An objection is a concern that, if addressed, could allow the conversation to continue. A rejection is a final decision against moving forward. Objections should be handled and explored; rejections should be respected.

How can I train my sales team to handle objections better?

Combine four elements: an objection library of proven responses, weekly role-play sessions, call review using tools like Gong or Chorus, and dedicated training inside your sales enablement programme. Teams that do all four consistently see measurable improvements within 60-90 days.