Every sales rep knows the feeling. You’re mid-pitch, the conversation is flowing well, and then it happens \u2014 the prospect pushes back. Maybe they say your product is too expensive, or they’re happy with their current vendor, or they simply don’t have time to talk. These moments can feel like walls, but experienced sellers know they’re actually doorways.<\/p>\n
The difference between a closed deal and a lost opportunity often comes down to one thing: how well you handle objections. Sales objection handling is not about arguing, manipulating, or pressuring prospects into saying yes. It’s about understanding their real concerns, empathizing with their situation, and guiding them toward a decision that genuinely benefits them.<\/p>\n
This guide is built for B2B sales professionals, SDRs, account executives, sales managers, and anyone who picks up the phone or sends cold emails for a living. You’ll find practical frameworks, deep explanations, and ready-to-use sales objection handling scripts<\/strong> for the 20 most common pushbacks you’ll encounter in the field.<\/p>\n A sales objection is any concern, hesitation, or resistance a prospect raises that prevents them from moving forward in the buying process. It’s a signal \u2014 not necessarily a rejection \u2014 that the prospect has unanswered questions or unresolved doubts about your product, pricing, timing, or company.<\/p>\n Objections are a natural, healthy part of any sales conversation. In fact, a prospect who raises objections is often more engaged than one who goes completely silent. They’re thinking critically about your offer, which means they’re at least somewhat interested. The moment you reframe objections as engagement signals rather than rejection signals, your entire approach to sales conversations shifts.<\/p>\n Common objections in B2B sales fall into four broad categories:<\/p>\n Understanding which category an objection falls into is critical because it determines your entire response strategy. A budget objection requires a value conversation. An authority objection requires a stakeholder mapping conversation. Treating every objection with the same response is one of the most common mistakes reps make \u2014 and it costs them deals they could have won.<\/p>\n Before we dive into scripts, it’s important to distinguish between two things that often get confused in the heat of a sales call: objections and obstructions.<\/p>\n Objections<\/strong> are legitimate concerns rooted in the prospect’s business reality. They reflect genuine doubts about budget, fit, timing, or value \u2014 and they can absolutely be addressed with the right information, empathy, and framing. When a prospect raises a real objection, they’re giving you something to work with.<\/p>\n Obstructions<\/strong>, on the other hand, are deflections. They’re surface-level excuses used to end a conversation without real engagement. They’re not necessarily dishonest \u2014 sometimes people genuinely don’t have time \u2014 but they’re not the real issue either. The prospect hasn’t engaged deeply enough to even form a real objection yet.<\/p>\n Here’s a quick way to tell them apart:<\/p>\n Why does this distinction matter so much in practice? Because the wrong response to an obstruction can kill the call entirely. If someone says “I’m busy” and you launch into a detailed ROI breakdown, you’ll lose them immediately. Obstructions need to be acknowledged quickly, met with brevity, and reframed to earn just a bit more of their attention before you can have a real conversation.<\/p>\n Knowing the difference makes you more efficient, more empathetic, and ultimately far more effective \u2014 because you stop fighting battles that aren’t actually there.<\/p>\n Before we get into the specific scripts, here’s a closer look at the four primary objection types and the psychology driving each one. Understanding the why<\/em> behind an objection makes your response feel far more natural and tailored.<\/p>\n This is the single most common objection in B2B sales, and it’s also the most misunderstood. On the surface, it seems like a financial problem. In reality, it’s usually a value problem. If a prospect could see with certainty that your product would generate five times its cost in the first year, the budget conversation would look very different. The price point hasn’t changed \u2014 the perceived value has.<\/p>\n That’s why your first instinct when hearing a budget objection should never be to drop your price. It should be to deepen the value conversation. Help them see the cost of the problem they’re trying to solve, the ROI your existing customers have realized, and the risk of continuing to live with the status quo. When the value is crystal clear, budget finds a way.<\/p>\n Sometimes the person you’re speaking with is genuinely interested but doesn’t have the power to say yes. They might be an influential champion, a mid-level manager, or a well-intentioned gatekeeper \u2014 but none of that matters if they can’t write the check or approve the vendor. This objection requires a particularly delicate touch.<\/p>\n You need to help your contact become an internal advocate without making them feel bypassed, undermined, or set up to fail in front of their leadership. That means arming them with the right information, giving them language they can use in an internal pitch, and \u2014 whenever possible \u2014 securing a direct conversation with the actual decision-maker.<\/p>\n The prospect doesn’t believe your product solves a problem they actually have \u2014 or they don’t believe the problem is significant enough to justify action. This could reflect a genuine product-market mismatch, but more often it reflects a discovery failure earlier in the conversation. The rep either didn’t ask the right questions to uncover real pain, or didn’t connect that pain clearly enough to the solution.<\/p>\n Your job here is to help the prospect see the gap between where they are and where they could be \u2014 not by insisting they have a problem, but by asking thoughtful questions that lead them to recognize it themselves. People are far more persuaded by conclusions they reach on their own than by conclusions someone else hands them.<\/p>\n This is perhaps the most frustrating objection type, because it often comes late in the process. The prospect agrees there’s a problem. They agree your product could help. They’re just not ready to act now. Other priorities are competing for their attention, their budget cycle is off, or they simply haven’t felt the pressure to move.<\/p>\n To create urgency without being pushy, help them understand the cost of inaction. What does it cost them \u2014 in money, time, missed opportunity, or competitive disadvantage \u2014 to delay solving this problem by another six or twelve months? When inaction has a visible price tag attached to it, urgency tends to appear.<\/p>\n Having the right sales objection handling scripts<\/strong> is important, but those scripts are only as effective as the process surrounding them. Here’s the repeatable seven-step framework that top-performing B2B reps use to handle any objection \u2014 regardless of type, industry, or deal size.<\/p>\n Step 1: Prepare.<\/strong> Anticipate the objections you’re likely to face before the call ever starts. Review notes from previous deals, debrief with colleagues, and study what objections come up most often at each stage of your pipeline. The best reps are never caught off guard by pushback \u2014 they’ve already thought through their response before the prospect even raises the concern.<\/p>\n Step 2: Listen.<\/strong> When a prospect raises an objection, resist the very human urge to jump in with a rebuttal. Let them finish. Let them fully articulate their concern. Not only does this show respect \u2014 it often leads to the prospect revealing more detail about the real issue if you give them enough space to speak without interruption.<\/p>\n Step 3: Understand.<\/strong> Before you respond to anything, ask a clarifying question. Make absolutely sure you’re addressing the actual objection, not the surface-level version of it. “Can you tell me more about what you mean by that?” or “Help me understand \u2014 is it more about X or Y?” are two of the most powerful questions in any sales conversation. They demonstrate intelligence, buy you thinking time, and almost always surface a more complete picture of the concern.<\/p>\n Step 4: Validate.<\/strong> Acknowledge the prospect’s concern without agreeing that it’s a dealbreaker. Phrases like “That’s a completely fair point” or “I totally understand where you’re coming from \u2014 a lot of people we speak with feel the same way initially” do something critically important: they lower the prospect’s defensiveness. When someone feels heard and not judged, they become dramatically more open to a different perspective.<\/p>\n Step 5: Act.<\/strong> Now you respond \u2014 with a tailored, thoughtful answer that directly addresses the specific concern. This is where your script comes in. But remember: the script is a framework, not a recitation. Adapt it to the language, context, and emotional tone of the conversation you’re actually having.<\/p>\n Step 6: Plan.<\/strong> After handling the objection, immediately establish a next step. Don’t let the conversation drift to a vague close. Propose something concrete \u2014 a follow-up call, a personalized demo, a proposal meeting, or a stakeholder introduction. Moving from objection to next step signals confidence and keeps momentum alive.<\/p>\n Step 7: Confirm.<\/strong> Before ending the conversation, explicitly confirm that your response actually addressed their concern. “Does that help clarify things?” or “Does that change the picture at all?” or “Are you comfortable moving forward from here?” \u2014 these closing questions aren’t just polite formalities. They close the loop, prevent lingering doubt, and give you real-time feedback on whether you’ve landed the response or whether there’s more work to do.<\/p>\n Here are the 20 most common objections B2B sales reps encounter, paired with detailed context, the psychology behind each one, and practical, real-world scripts you can use \u2014 and adapt \u2014 immediately.<\/p>\n The objection:<\/strong> The prospect is hesitant to commit to an extended agreement \u2014 typically annual or multi-year contracts. They want flexibility, and the idea of being locked in feels risky.<\/p>\n Why they say it:<\/strong> Commitment anxiety in B2B is real and rational. Prospects worry about what happens if the product doesn’t deliver on its promises, if their business needs shift over the contract period, or if the vendor relationship sours after the ink dries. They’ve likely seen colleagues get stuck in contracts with tools they stopped using months ago. This is a risk management objection at its core \u2014 not necessarily a reflection of low interest in your product.<\/p>\n The Script:<\/strong><\/p>\n “That’s completely understandable \u2014 long-term commitments can feel like a significant leap, especially when we’re just getting to know each other and you haven’t yet had a chance to see our product in your actual environment. I wouldn’t expect you to sign something that makes you uncomfortable. What if we explored a shorter pilot period first \u2014 say 90 days \u2014 where you can see real results with your own data and your own team before making any longer-term decisions? That way you’re evaluating us on performance, not on faith. Would starting with a trial give you the confidence you need to move forward?”<\/em><\/p>\n When a prospect raises commitment anxiety, the worst thing you can do is push harder on the long-term contract. That accelerates their resistance. Instead, reduce the perceived risk by offering a lower-commitment entry point \u2014 a pilot, a month-to-month option, or a success-based milestone before the full commitment kicks in. Once they’ve seen results in their own environment, the long-term conversation becomes far easier. You’re not giving up the full deal \u2014 you’re just sequencing it better.<\/p>\n The objection:<\/strong> The prospect has an existing vendor relationship, sunk costs, and the powerful inertia of a familiar tool. They’ve already made a decision \u2014 or so they believe.<\/p>\n Why they say it:<\/strong> Switching vendors in B2B is genuinely costly \u2014 in time, in disruption, in retraining, and often in migration headaches. Prospects who have an existing solution have also already invested emotional energy in that decision. Admitting that they chose the wrong tool is uncomfortable. So the default position is to defend the status quo, even when it’s not fully delivering. In many cases, the “we already use a competitor” objection is less about loyalty and more about the perceived pain of switching.<\/p>\n The Script:<\/strong><\/p>\n “I appreciate you being upfront about that \u2014 it actually helps me tailor this conversation a lot better. A significant portion of our current customer base came from similar platforms because they found they’d outgrown what those tools could offer as their needs scaled. I’m not saying that’s your situation at all \u2014 your setup might be working perfectly. But I’d love to ask: what’s working really well for you with your current tool, and where do you still feel like there are gaps or workarounds you wish you didn’t need? If there are no gaps, I’ll be the first to say this probably isn’t the right conversation. But if there are, it might be worth 20 minutes to see what a different approach looks like.”<\/em><\/p>\n Never badmouth a competitor by name. It’s unprofessional, it makes you look insecure, and experienced buyers see right through it. Instead, ask questions that lead the prospect to identify their own gaps. When they articulate the limitation themselves, it carries far more weight than anything you could say. Your job is to ask the questions that open the door \u2014 then let them walk through it.<\/p>\n The objection:<\/strong> The prospect has a competing quote \u2014 or has done enough research to believe a competitor offers similar functionality at a lower price point \u2014 and they want to understand why they should pay more for you.<\/p>\n Why they say it:<\/strong> In B2B procurement, demonstrating fiscal responsibility is part of the job. Buyers are expected to optimize spend, and a cheaper alternative on paper is a legitimate point of comparison. Sometimes this is genuine due diligence. Sometimes it’s a negotiation tactic. Often it’s both. Either way, what the prospect is really asking is: “Convince me that the extra cost is justified.”<\/em><\/p>\n The Script:<\/strong><\/p>\n “That’s definitely worth exploring together \u2014 price is obviously an important part of any decision, and I wouldn’t expect you to ignore it. Can I ask a couple of things? First, which competitor are you comparing us to? And second, when you’re comparing the two options, which outcomes and capabilities matter most to your team? I ask because what looks like the same product on the surface often delivers very different results in practice \u2014 and the true cost of a solution isn’t always just the license fee. It includes implementation time, support quality, the cost of gaps in functionality, and how much the tool actually moves the metrics you care about. I’d love to walk through that comparison with you properly.”<\/em><\/p>\n Know your top three competitors cold \u2014 their pricing, their limitations, their ideal customer profile, and the specific scenarios where you consistently win against them. When a prospect raises a competitor’s lower price, you should be able to articulate \u2014 with specificity and without arrogance \u2014 exactly where the difference in outcomes lies. Vague claims of being “better” don’t close deals. Concrete, specific differentiators backed by customer examples do.<\/p>\n The objection:<\/strong> The prospect can’t draw a clear, convincing line from your product to measurable business outcomes. In their view, the investment doesn’t have a clear payoff.<\/p>\n Why they say it:<\/strong> This is almost always a failure of earlier messaging rather than a genuine lack of ROI. The rep either pitched features instead of outcomes, used generic value claims without specifics, or failed to connect the solution to the metrics the prospect actually cares about. In B2B, “this will save you time” is not a ROI argument. “Customers like you reduce manual reporting hours by 60%, which translates to approximately X per year in recovered productivity” \u2014 that’s a ROI argument.<\/p>\n The Script:<\/strong><\/p>\n “That’s really valuable feedback, and I want to address it properly rather than just throw more numbers at you. Can you help me understand which outcomes matter most to your team right now \u2014 is it cost reduction, revenue growth, time savings, faster cycle times, or something more specific? Once I know that, I can walk you through exactly how companies in your space have measured their return from solving this problem \u2014 with real numbers, not estimates. The specifics might surprise you. And if after seeing that you still don’t see the ROI case, I’ll tell you honestly whether I think this is the right fit.”<\/em><\/p>\n Pro Tip:<\/strong> Before every sales call, prepare at least three specific, quantified customer outcomes relevant to the prospect’s industry and company size. “Clients see great results” is not a data point \u2014 it’s noise. “Mid-market SaaS companies in your space typically see a 35% reduction in [specific metric] within the first 60 days” is a data point. The more specific and industry-relevant your ROI examples, the more credible and persuasive they become. Generic claims get ignored; precise numbers get remembered.<\/p>\n The objection:<\/strong> The prospect has shut down the conversation \u2014 often within the first minute \u2014 before you’ve had the chance to establish any real relevance.<\/p>\n Why they say it:<\/strong> This is almost always an obstruction, not a true objection. Early in a cold call, the prospect hasn’t heard enough to know whether they’re genuinely interested or not. What they’re really saying is: “You haven’t yet given me a compelling reason to keep listening.”<\/em> It’s a reflexive, conditioned response to outbound outreach \u2014 the conversational equivalent of skipping an ad. It’s not personal, and it doesn’t mean the conversation is over.<\/p>\n The Script:<\/strong><\/p>\n “Fair enough \u2014 and I’ll keep this to 30 seconds, I promise. Most [specific job title] I speak with are dealing with [one very specific, relevant pain point]. If that’s genuinely not on your radar, I completely respect your time and won’t take another second of it. But if it does sound familiar \u2014 even a little \u2014 it might be worth two minutes to hear how we’ve helped [similar company type] tackle it. Which one is it for you?”<\/em><\/p>\n The key to handling “I’m not interested” is specificity. A generic pitch about your product’s benefits will slide right off a resistant prospect. But a sharply articulated, hyper-relevant pain point \u2014 one that makes them think “How do they know that?”<\/em> \u2014 earns a second listen. Before cold calls, research enough to identify the one problem that is most likely keeping that specific prospect up at night. Lead with that problem, not with your product.<\/p>\n The objection:<\/strong> The prospect wants to end the call \u2014 either because they genuinely have something more pressing, or because they haven’t yet seen a reason to make time.<\/p>\n Why they say it:<\/strong> B2B buyers are legitimately time-starved. Inboxes are full, meetings are back-to-back, and unsolicited calls feel like interruptions by default. But “I’m busy right now” is also the path of least resistance for anyone who hasn’t immediately heard something compelling. The real question underneath this objection is: “Is this worth my time?”<\/em> \u2014 and your job is to answer that question in one sentence.<\/p>\n The Script:<\/strong><\/p>\n “I completely respect that \u2014 and I won’t keep you. I’m not calling to run through a full pitch today, I promise. I just have one quick question: is [specific pain point or business challenge] something that’s on your team’s priority list for this quarter? If yes, I’d love to schedule 15 minutes at a time that actually works for you \u2014 I’ll send a calendar link and you can pick whatever slot works. If it’s not a priority right now, I’ll leave you to it and follow up when the timing is better.”<\/em><\/p>\n The counterintuitive move here is to make a smaller ask, not a bigger one. When a prospect says they’re busy and you respond by requesting more of their time, the resistance increases. But when you ask for just one honest answer \u2014 and make it genuinely easy to say no \u2014 the defensiveness drops. Reps who are willing to quickly give prospects an easy out often find that those same prospects become more willing to engage.<\/p>\n The objection:<\/strong> The prospect is questioning the source of their contact details \u2014 expressing privacy concerns, skepticism about your data practices, or simply catching you off guard.<\/p>\n Why they say it:<\/strong> With GDPR, CCPA, and growing awareness around data privacy, this question is increasingly common \u2014 and entirely legitimate. Some prospects ask it out of genuine concern about how their information is being used. Others ask it as a brush-off. Either way, hesitation or evasiveness in your answer is a deal-killer. What the prospect is really asking is: “Can I trust this person and this company?”<\/em><\/p>\n The Script:<\/strong><\/p>\n “Completely fair question \u2014 and I’d rather you ask that upfront than wonder about it. I sourced your contact information from [specific, honest source \u2014 e.g., LinkedIn \/ a professional B2B database \/ your company’s website]. I want to be fully transparent: I can remove you from our outreach list right now if you’d prefer \u2014 no hard feelings whatsoever, and I’ll make sure it doesn’t happen again. That said, the reason I reached out specifically is [one concrete, relevant reason tied to their role or company]. I genuinely think there’s a fit here. Would you be open to hearing why?”<\/em><\/p>\n Pro Tip:<\/strong> Transparency is one of the most disarming tools in sales \u2014 precisely because so few reps use it. Most prospects brace for defensiveness or deflection when they ask about data sourcing. When they get immediate honesty and a genuine offer to opt out instead, it shifts the entire dynamic of the conversation. The offer to remove them from your list, made sincerely, almost always makes them more willing to listen rather than less.<\/p>\n The objection:<\/strong> The prospect is unfamiliar with your brand and is hesitant to engage with an unknown quantity \u2014 especially for a purchase that carries real business risk.<\/p>\n Why they say it:<\/strong> In B2B, brand recognition functions as a proxy for trust and reliability. Larger, more established vendors feel safer \u2014 even if they’re not necessarily better. Prospects who haven’t heard of you are essentially asking: “Why should I take a risk on you when I could go with someone my peers already know?”<\/em> This is especially pronounced in industries where vendor selection is scrutinized internally or where switching costs are high.<\/p>\n The Script:<\/strong><\/p>\n “That’s a fair reaction \u2014 we’re not the biggest name in the space, and I’m not going to pretend otherwise. But here’s what I’ve found: because we’re more focused and specialized than the larger platforms, our customers typically get faster implementation, more responsive support, and a product that’s built specifically around their use case rather than trying to be everything to everyone. Some companies you might recognize that we work with include [two or three relevant, credible reference clients]. Would it be useful if I sent over a couple of case studies from businesses similar to yours so you can see the kind of results people are getting? That’s probably a better proof point than anything I could say right now.”<\/em><\/p>\n Pro Tip:<\/strong> Being lesser-known isn’t inherently a weakness \u2014 it’s only a weakness if you let it become one by apologizing for it. Reframe it as specialization, agility, and customer focus. Large platforms serve everyone, which means they serve no one particularly well. Smaller, focused vendors often deliver faster time-to-value and more personalized support. That’s a genuine differentiator \u2014 lean into it with confidence rather than defensiveness.<\/p>\n The objection:<\/strong> The prospect is worried about adoption \u2014 specifically, the time, effort, and disruption required to get their team actually using a new tool effectively.<\/p>\n Why they say it:<\/strong> Implementation anxiety is one of the most under-appreciated objections in B2B sales. Prospects have been burned before by tools that looked great in a demo but took six months to deploy, required constant IT support, and were ultimately abandoned by the team. They’re not questioning your product’s capabilities \u2014 they’re questioning whether those capabilities will ever be accessible in their specific environment. The hidden cost of complexity \u2014 in training time, productivity loss, and frustration \u2014 is what they’re really worried about.<\/p>\n The Script:<\/strong><\/p>\n “I hear that a lot, and I want to be straight with you about it rather than just say ‘it’s actually really easy’ \u2014 because that’s not a useful answer. What I can tell you is that most teams are fully operational within [specific, realistic timeframe], and we provide [specific support resources \u2014 e.g., a dedicated onboarding specialist, live training sessions, a self-serve help center] throughout the process so your team is never figuring things out alone. The feedback we get most often from new customers is that they were pleasantly surprised by how much simpler it was than they expected \u2014 which I know sounds like marketing, but I can point you to specific customers who said exactly that. The best way for you to judge is to actually see the interface in action. Could we schedule a 30-minute demo where you can see the workflow your team would actually use?”<\/em><\/p>\n Don’t just tell prospects your product is easy to use \u2014 show them. A well-run, focused demo that walks through the exact workflow their team would use does more to dismantle this objection than any verbal reassurance. If you have video walkthroughs, self-serve trial access, or short onboarding timelines backed by real customer examples, lead with those specifics. Evidence beats assertion every time.<\/p>\n The objection:<\/strong> The prospect has allocated their available budget to a competing internal priority, and your solution is effectively competing with another initiative for the same limited pot of money.<\/p>\n Why they say it:<\/strong> Every B2B organization has more problems to solve than budget to solve them with. When someone tells you the budget is going elsewhere, they’re telling you that, in their current view, something else is more important. This is a prioritization problem \u2014 and it can be addressed, but only if you understand what you’re actually competing against internally.<\/p>\n The Script:<\/strong><\/p>\n “I understand \u2014 and budget allocation decisions are genuinely tough, especially when there are competing priorities pulling in different directions. Can I ask what initiative is currently taking priority? I’m not asking to second-guess your decision \u2014 I’m asking because there are situations where what we do and what you’re investing in actually overlap more than it looks on the surface. We might be able to support both goals with a single investment, which could actually strengthen the business case for your existing initiative rather than compete with it. If that’s even a possibility, it seems worth 15 minutes to find out.”<\/em><\/p>\n Pro Tip:<\/strong> When budget is going to a competing internal project, your best move is to look for alignment rather than competition. Can your solution actually support or accelerate the priority they’ve chosen? Can it be framed as a tool that helps them get more out of the investment they’ve already committed to? Reps who reframe their product as a complement to existing priorities \u2014 rather than a competitor for the same budget \u2014 often find entirely new angles into deals that looked dead.<\/p>\n The objection:<\/strong> The prospect is pushing the conversation into the future \u2014 either because the timing genuinely isn’t right, or because they’re hoping you’ll forget to follow up.<\/p>\n Why they say it:<\/strong> Sometimes this is completely genuine. Q4 is brutal. Fiscal year ends create chaos. Reorgs consume everyone’s attention. But “call me next quarter” is also one of the most common soft rejections in outbound sales \u2014 a polite way to end a conversation without saying no. The challenge is figuring out which one you’re dealing with, because the right response is very different depending on the answer.<\/p>\n The Script:<\/strong><\/p>\n “Of course \u2014 I want to connect when the timing actually makes sense for you, not just when it’s convenient for me. Before I let you go though, can I ask one quick thing: what’s changing next quarter that would make this a more relevant conversation then? I want to make sure I come back with something actually useful rather than just re-pitching what you’ve already heard. And if it works for you, could we put a specific date on the calendar now while we’re both here? Even 20 minutes \u2014 that way it doesn’t get lost in the shuffle and we’re not playing phone tag in three months.”<\/em><\/p>\n Pro Tip:<\/strong> “Call me next quarter” without a specific date on the calendar is a deal that will almost certainly die quietly. Your conversion rate on vague future follow-ups is dramatically lower than on calendar-locked ones. The probing question about what’s changing also serves a dual purpose: it reveals whether this is a genuine timing issue or a polite brush-off, and it helps you understand what will make the conversation more relevant when you do reconnect.<\/p>\n The objection:<\/strong> Your price point exceeds what the prospect is willing \u2014 or able \u2014 to pay, whether that’s due to hard budget constraints, sticker shock, or a value gap.<\/p>\n Why they say it:<\/strong> Price objections are almost always value objections wearing a price tag. The prospect is saying that, in their current understanding of what you do and what it delivers, the cost doesn’t feel justified. That’s a different problem than pure budget constraint \u2014 and confusing the two leads reps to make premature concessions they didn’t need to make. Before you negotiate on price, you need to understand whether you’re dealing with a genuine budget ceiling or an unresolved value question.<\/p>\n The Script:<\/strong><\/p>\n “I appreciate you being direct about that \u2014 it’s genuinely useful. When you say it feels too expensive, can I ask you to help me understand that a bit more? Is it that the number itself is outside your budget entirely, or is it more that you’re not yet seeing enough value to justify that level of investment? I ask because those are actually two different problems, and I don’t want to give you the wrong response. If it’s a budget issue, there might be a way to structure this differently \u2014 different payment terms, a phased approach, a smaller starting scope. If it’s a value question, I’d rather spend the next ten minutes making the value case properly than drop the price on something you haven’t fully seen yet.”<\/em><\/p>\n The golden rule of price objections: never drop your price immediately. The moment you do, you’ve told the prospect that your original number was inflated, your confidence in your product is shaky, and they should have pushed back harder from the start. Defend value first, always. If you do need to adjust \u2014 whether through packaging, payment structure, or scope \u2014 make sure every concession is tied to a trade-off that makes commercial sense for both sides.<\/p>\n The objection:<\/strong> The prospect has a specific capability on their must-have list, and they either know or believe your product doesn’t check that box.<\/p>\n Why they say it:<\/strong> B2B buyers often have detailed requirements lists \u2014 sometimes built by committee, sometimes inherited from a previous evaluation, and sometimes anchored to a very specific workflow they’ve built around a competitor’s feature. When they raise a feature gap, they may be doing it because they’ve genuinely researched your product and confirmed the gap exists, or they may be working from an assumption that hasn’t been tested. Either way, your first move is to understand the underlying need before defending or conceding on the feature itself.<\/p>\n The Script:<\/strong><\/p>\n “Thanks for raising that specifically \u2014 it’s an important thing to get right before we go any further. Can you walk me through exactly how you’d use that capability day-to-day? I want to make sure I understand what you’re actually trying to accomplish, because sometimes there’s more than one way to achieve the same outcome. [If the feature exists in a different form:] Actually, we handle that through [specific feature or workflow] \u2014 let me show you how that works in practice, because it might land differently than you’d expect. [If the gap is real:] You’re right that we don’t have that natively \u2014 I won’t pretend otherwise. But here’s how our customers typically work around it, and what they’ve told us about the tradeoff…”<\/em><\/p>\n The worst thing you can do with a feature objection is get defensive or immediately promise it’s on the roadmap. Promising roadmap features you’re uncertain about is one of the fastest ways to destroy trust \u2014 because the moment that feature is late or never arrives, your credibility is gone. Be honest about gaps. If you do have a workaround, show it \u2014 don’t just describe it. And if the gap is genuinely a dealbreaker, it’s better to know now than after six months of a bad-fit customer relationship.<\/p>\n The objection:<\/strong> The prospect wants to run a formal or informal vendor comparison before making any commitment.<\/p>\n Why they say it:<\/strong> In B2B, especially for purchases above a certain threshold, comparative evaluation is standard practice \u2014 and often a procurement requirement. The prospect isn’t necessarily shopping for a cheaper option; they’re managing the risk of making a bad decision. They want validation that they’re making the right choice. This is healthy buying behavior, and the worst thing you can do is try to talk them out of it. Your job is to stay in the conversation and \u2014 where possible \u2014 shape the criteria they use to evaluate.<\/p>\n The Script:<\/strong><\/p>\n “That makes complete sense \u2014 and honestly, I’d encourage it. Comparison shopping is smart for any significant investment, and I wouldn’t want you to commit to us without feeling confident you’ve done your homework. Can I suggest something that might make your evaluation easier? When our customers were going through their selection process, they told us the factors that made the biggest difference weren’t always the most obvious ones. The three things that consistently separated the right choice from the wrong one were [list your genuine, defensible differentiators]. If those matter to your team, I think the comparison will be fairly clear. And I’d love to stay involved as a resource during your evaluation \u2014 sometimes it helps to have someone who knows our product deeply to answer technical questions as they come up. Would that be useful?”<\/em><\/p>\n Giving the prospect an evaluation framework that highlights your genuine strengths isn’t manipulative \u2014 it’s smart selling. Every vendor will look the same if the prospect is evaluating on generic criteria. But if you can shift the conversation to the dimensions where you clearly win, you’ve stacked the deck without being dishonest. The key is that your differentiators need to be real and verifiable \u2014 not marketing language that falls apart the moment they talk to a reference customer.<\/p>\n The objection:<\/strong> The prospect sees no compelling reason to change. Their current situation \u2014 whether it’s a tool, a process, or a manual workaround \u2014 feels good enough.<\/p>\n Why they say it:<\/strong> Status quo bias is one of the most powerful psychological forces in B2B purchasing decisions. Change is inherently risky. It requires effort, disrupts familiar workflows, and could go wrong in ways that are hard to predict. Even when the current state isn’t optimal, the prospect has adapted to it. They’ve built workarounds, lowered their expectations, and stopped imagining what better could look like. Challenging this requires extraordinary care \u2014 because if you come in too aggressively, you’ll trigger defensiveness rather than curiosity.<\/p>\n The Script:<\/strong><\/p>\n “That’s genuinely great to hear \u2014 and I’m not here to fix something that isn’t broken. Can I ask just one question before I let you go? When you think about [the specific area your product addresses], what does ‘performing really well’ look like for your team right now \u2014 in concrete terms? I ask because there’s a big difference between ‘things are fine’ and ‘we’re operating at the level we know is possible.’ A lot of teams we work with felt exactly the same way \u2014 things were working, no major fires \u2014 until they saw a benchmark of what top-performing teams in their space were actually achieving. Sometimes the gap is significant without feeling significant from the inside. Would you be open to a 20-minute conversation just to explore that?”<\/em><\/p>\n The most effective way to create movement from a status quo position is not to argue that things are bad \u2014 it’s to raise the prospect’s sense of what good could look like. Benchmarks, industry data, and peer comparisons are your most powerful tools here. When a prospect sees that their competitors or industry peers are operating at a measurably higher level, the satisfaction with the current state suddenly feels a lot less comfortable.<\/p>\n The objection:<\/strong> The prospect assumes your product is built for larger organizations and won’t be practical \u2014 or justifiable \u2014 for their current team size.<\/p>\n Why they say it:<\/strong> Many B2B tools are perceived as enterprise-only, either because of their pricing, their complexity, or the way they’re marketed. If a prospect has encountered your brand in an enterprise context, they’ll assume you’re not for them. They may also be genuinely worried about the resource commitment required \u2014 onboarding, administration, and ongoing management \u2014 relative to the size of their team. What they’re really asking is: “Is this tool actually going to make our lives easier or just add to our workload?”<\/em><\/p>\n The Script:<\/strong><\/p>\n “I’m really glad you brought that up, because it’s one of the most common assumptions people have about us \u2014 and it’s one we actively work to challenge. Some of our most successful and satisfied customers started with teams of exactly your size or smaller, and what they consistently tell us is that smaller teams often see the fastest and most direct ROI because there’s less organizational complexity in the way. The product is designed to scale with you, which means you don’t need to wait until you’re bigger to get value from it. Can I ask \u2014 how many people are on your team currently, and what’s the core problem you’re trying to solve? That’ll help me figure out whether this is genuinely a good fit for where you are today, or whether you’d be better served by something else.”<\/em><\/p>\n Always close this response by genuinely qualifying. If a prospect’s team is truly too small for your product to deliver meaningful value, it’s in everyone’s interest to acknowledge that now rather than force a bad-fit deal. Reps who are honest about fit \u2014 even when it means walking away \u2014 build a reputation for trustworthiness that generates referrals and future business far beyond any single deal they might have pushed through.<\/p>\n The situation:<\/strong> The call ended before you could establish relevance or rapport. The prospect disconnected \u2014 intentionally or otherwise \u2014 without real engagement.<\/p>\n Why this happens:<\/strong> Cold calling is an inherently interruptive medium. Prospects sometimes hang up out of habit, genuine time pressure, frustration with unsolicited calls, or simply because the opening didn’t land. It happens to every rep, at every level, every single day. The question isn’t how to prevent it \u2014 it’s what to do next.<\/p>\n Follow-up Script (email or LinkedIn):<\/strong><\/p>\n “Hi [Name], I think we got cut off earlier \u2014 or, more likely, I caught you at a genuinely terrible moment, which happens. I’ll keep this brief: I reached out because [one specific, concrete reason directly tied to their role or company situation]. If that’s not relevant to what your team is focused on right now, no problem at all \u2014 I won’t take up any more of your time. But if [specific pain point] is something on your radar this quarter, I genuinely think 15 minutes would be worth it for both of us. Happy to work around your schedule \u2014 here’s my calendar: [link].”<\/em><\/p>\n Pro Tip:<\/strong> Your follow-up message after a disconnected call needs to do one specific job: re-establish relevance without begging for attention. Keep it short, specific, and confident. Never apologize for reaching out. Never lead with “Just following up on my call.” Lead with the one business reason that makes this worth their time \u2014 and give them a clear, frictionless way to respond if they’re interested.<\/p>\n The objection:<\/strong> The prospect is asking for collateral \u2014 a deck, a one-pager, a case study \u2014 as a way to end the live conversation without committing to a next step.<\/p>\n Why they say it:<\/strong> “Send me some information” is one of the most reliable soft exits in the B2B buyer’s toolkit. It’s not rude, it’s not a firm no, and it gives the rep enough hope to stay patient. But the reality is that a PDF sitting in someone’s inbox rarely generates a meaningful follow-up conversation on its own. Without a real hook tied to a specific follow-up commitment, your carefully designed collateral will be opened once, skimmed, and forgotten within 48 hours.<\/p>\n The Script:<\/strong><\/p>\n “Absolutely \u2014 I’ll send something over today. Just so I can make sure I send you something actually useful and not just a generic 20-page overview, can I ask one thing: what’s the main challenge or question you’d want that material to answer for you? That helps me tailor what I send to be genuinely relevant to your situation rather than a standard brochure. And when would be a reasonable time to follow up to see if it sparked any questions \u2014 would [specific day] work for a quick 10-minute call?”<\/em><\/p>\n The magic move here is turning the collateral request into a discovery moment and a follow-up commitment \u2014 all in one response. You’ve agreed to their ask (so there’s no friction), you’ve gathered information that helps you personalize what you send (making the collateral far more likely to land), and you’ve secured a follow-up date before the call ends. That’s three wins from one objection.<\/p>\n The objection:<\/strong> The prospect has done their research and encountered negative feedback \u2014 from a review site, a peer recommendation, or a social media post \u2014 and wants to understand whether it reflects a real problem.<\/p>\n Why they say it:<\/strong> B2B buyers routinely consult G2, Capterra, Trustpilot, LinkedIn, and peer networks before engaging seriously with any vendor. A negative review \u2014 especially one that mirrors the prospect’s own situation or use case \u2014 creates real, legitimate hesitation. What the prospect is actually doing is testing your response. They want to know: will you be defensive and dismissive, or will you engage honestly? Your answer to this objection tells them a great deal about what working with your company would actually look like.<\/p>\n The Script:<\/strong><\/p>\n “I really appreciate you bringing that up directly rather than just going silent \u2014 that’s exactly the kind of thing I’d rather address head-on than have linger in the background. Can you share what the review said specifically? I’d rather engage with the actual feedback than give you a generic ‘we take all feedback seriously’ response \u2014 that doesn’t help you. [After they share it:] I know that one. Here’s the honest context: [explain what happened and what was done to address it]. And I’d actually like to connect you directly with a few reference customers who can speak to their experience \u2014 including some who had concerns similar to yours going in. Would that help you evaluate this more fairly?”<\/em><\/p>\n Transparency in the face of negative feedback is one of the most powerful trust-builders in sales. Most prospects expect defensiveness \u2014 they brace for it. When they get genuine acknowledgment, a real explanation, and an offer to connect with reference customers instead, the dynamic shifts dramatically. The rep who handles this objection with honesty and accountability often ends up with a stronger prospect relationship than they would have had if the review had never come up at all.<\/p>\n The situation:<\/strong> Most outbound calls go to voicemail \u2014 industry averages suggest anywhere from 60% to 80% of cold calls are never answered live. If you don’t have a disciplined voicemail strategy, you’re leaving enormous pipeline on the table.<\/p>\n Why a strategy matters:<\/strong> The goal of a voicemail is not to get a callback. The callback rate on cold voicemails is extremely low. The real goal is to prime the prospect for your follow-up email \u2014 to make your name and company feel familiar and relevant when they see it in their inbox moments later. A voicemail that’s too long, too salesy, or too vague will be deleted before the prospect hears your name twice.<\/p>\n Voicemail Script:<\/strong><\/p>\n “Hi [Name], this is [Your Name] from [Company]. I’ll keep this to 20 seconds. I’m reaching out because [one specific, concrete reason tied to their role, their company, or a challenge you know is relevant]. I think there might be a real fit here, and I’d love to find out. I’m also sending you a quick email right now \u2014 you’ll have my details there. Talk soon.”<\/em><\/p>\n Pro Tip:<\/strong> Record your voicemail script and listen back to it before you start dialing. Does it sound like a human or like a robot reading from a card? Is the reason you’re calling specific enough to be meaningful? Is it short enough to hold attention? The best voicemails are under 20 seconds, include one hyper-relevant hook, and reference the email you’re sending immediately after. The voicemail and the email work as a pair \u2014 together they create two touchpoints that increase the likelihood of getting a response.<\/p>\n Having strong sales objection handling scripts<\/strong> is the foundation \u2014 but how you deploy them in live conversations is what separates good reps from great ones. Here are the practices that consistently make the difference.<\/p>\n Lead with curiosity, not defensiveness.<\/strong> The moment a prospect senses you’re defending your product rather than trying to understand their concern, they disengage. Train yourself to respond to every objection with a question before a statement. Curiosity signals confidence; defensiveness signals insecurity.<\/p>\n Personalize your response every time.<\/strong> Scripts are frameworks, not performances. Before you deliver any response, take two seconds to adapt the language to the specific person, company, and context in front of you. A response that feels tailored will always outperform one that sounds rehearsed.<\/p>\n Validate before you redirect.<\/strong> Every human being wants to feel heard before they’re willing to be influenced. Acknowledge the prospect’s concern genuinely \u2014 not with hollow phrases like “great question!” but with real recognition of why their hesitation is reasonable. Then redirect.<\/p>\n Use social proof strategically.<\/strong> Customer stories and specific outcomes are among the most persuasive tools in sales. When handling objections, lead with a customer who was in the exact same situation \u2014 same concern, same hesitation \u2014 and show what happened when they moved forward.<\/p>\n Build an objection library as a team.<\/strong> Objection handling shouldn’t be an individual skill developed in isolation. The best sales teams maintain a shared, living library of objections and responses \u2014 regularly updated, regularly discussed, and regularly practiced in role-play sessions. What one rep discovers about handling a specific objection becomes an asset for the entire team.<\/p>\n Track your objection patterns.<\/strong> Which objections come up most often? At which stage of the pipeline? In which industries or company sizes? Patterns in objection data reveal upstream problems \u2014 in messaging, targeting, ICP definition, or product positioning \u2014 that, when fixed, reduce the frequency of certain objections before they ever come up.<\/p>\n Always advance to a next step.<\/strong> After handling an objection, never let the conversation drift. The close of every objection response should include a clear, concrete next step \u2014 a follow-up call, a demo, a stakeholder meeting, a proposal. Momentum is fragile; protect it by always having somewhere to go.<\/p>\n Even reps with solid sales objection handling scripts<\/strong> in their toolkit consistently undermine their own performance with avoidable patterns. Here’s what to watch for \u2014 and what to do instead.<\/p>\n Responding too quickly.<\/strong> Jumping to a rebuttal the instant a prospect finishes speaking signals that you were composing your response while they were still talking \u2014 not listening. Take a breath. Pause for two seconds. It signals confidence and genuine consideration, and it makes your response land far more effectively.<\/p>\n Arguing rather than redirecting.<\/strong> The moment a sales conversation becomes an argument, you’ve already lost \u2014 regardless of who is technically right. Prospects who feel challenged or contradicted become defensive and closed. The goal is never to win the argument; it’s to move the conversation forward.<\/p>\n Dropping your price at the first sign of pushback.<\/strong> Immediate price concessions teach prospects that your list price is a bluff, train them to object every time as a negotiation strategy, and destroy the perceived value of your product. Defend value first, always \u2014 and if you do negotiate, make sure every concession comes with a trade-off.<\/p>\n Treating every objection identically.<\/strong> A one-size-fits-all response to objections is one of the clearest signals that a rep is running on autopilot. Prospects can feel when you’re reciting rather than engaging. Tailor your response to the specific person, the specific concern, and the specific context \u2014 every time.<\/p>\n Using scripts word-for-word without adaptation.<\/strong> Scripts are starting points, not scripts in the theatrical sense. If your responses sound like you’re reading from a page, you’ve already lost the prospect’s trust. Internalize the structure and key ideas, then speak in your own natural voice.<\/p>\n Not confirming after handling an objection.<\/strong> Handling an objection and moving on without checking whether it actually landed is like patching a leak without checking if the water stopped. Always confirm: “Does that help clarify things?” or “Are you more comfortable moving forward from here?” These questions close the loop and surface any residual concerns before they become silent deal-killers.<\/p>\n Giving up after one objection.<\/strong> Research consistently shows that most deals require multiple objection-handling cycles before a prospect commits. Reps who treat the first objection as a final answer miss deals they could have won. Handle the objection, confirm your response landed, and keep the conversation moving.<\/p>\n Sales objection handling is one of the most nuanced, high-leverage skills in B2B selling \u2014 and it’s one that never stops requiring attention, practice, and refinement. The difference between a rep who folds under pushback and one who navigates it with confidence and empathy rarely comes down to knowing more. It comes down to having a clear process, a library of tested responses, and the emotional intelligence to apply them in the moment \u2014 when the pressure is real and the stakes are high.<\/p>\n The 20 sales objection handling scripts<\/strong> in this guide aren’t magic words. They’re starting points \u2014 frameworks you can adapt to your product, your industry, your buyer personas, and your own natural communication style. The reps who truly master objection handling don’t treat scripts as crutches. They treat every pushback as useful information, every hesitation as an invitation to build trust, and every hard conversation as a chance to demonstrate that they’re genuinely trying to help their prospect \u2014 not just close a deal.<\/p>\n Use these scripts. Practice them out loud. Role-play them with your team until they feel natural. Review what’s working and refine what isn’t. Build your own objection library over time and keep it alive.<\/p>\n Because here’s the truth that separates great sellers from average ones: the deals that matter most don’t close in the easy conversations. They close in the hard ones \u2014 the ones where the prospect pushed back, the timing was wrong, the price felt high, and a rep with the right mindset and the right words found a way through.<\/p>\n That’s where great B2B selling happens. And that’s where you’ll find your edge.<\/p>\n An objection is a concern or hesitation that can be addressed with the right information, empathy, or reframing. It’s the prospect saying “I’m not sure yet” rather than “definitely not.” A rejection is a definitive decision not to move forward \u2014 and even then, it’s worth understanding why. The important thing to recognize is that the vast majority of early “nos” in a sales conversation are objections masquerading as rejections. Experienced reps learn to tell them apart by asking one more question rather than accepting the first pushback at face value.<\/p>\nWhat Is a Sales Objection?<\/h2>\n
\n\n
\n \nCategory<\/th>\n What It Signals<\/th>\n Example<\/th>\n<\/tr>\n<\/thead>\n \n Lack of Budget<\/td>\n Financial constraints or unclear value<\/td>\n “It’s too expensive.”<\/td>\n<\/tr>\n \n Lack of Authority<\/td>\n Wrong contact or internal complexity<\/td>\n “I’ll need to check with my boss.”<\/td>\n<\/tr>\n \n Lack of Need<\/td>\n Poor fit or unclear relevance<\/td>\n “We’re doing fine as is.”<\/td>\n<\/tr>\n \n Lack of Urgency<\/td>\n Other priorities taking precedence<\/td>\n “Call me back next quarter.”<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n Objections vs. Obstructions: Why the Difference Matters<\/h2>\n
\n
Types of Sales Objections Every B2B Rep Faces<\/h2>\n
1. Lack of Budget<\/h3>\n
2. Lack of Authority<\/h3>\n
3. Lack of Need<\/h3>\n
4. Lack of Urgency<\/h3>\n
How to Handle Sales Objections: A 7-Step Framework<\/h2>\n
Sales Objection Handling Scripts for Common B2B Pushbacks<\/h2>\n
1. “I Don’t Want to Sign a Long-Term Contract.”<\/h3>\n
2. “We’re Already Using One of Your Competitors.”<\/h3>\n
3. “Your Competitor Is Cheaper.”<\/h3>\n
4. “I Don’t See Any ROI Potential.”<\/h3>\n
5. “I’m Not Interested.”<\/h3>\n
6. “I’m Busy Right Now.”<\/h3>\n
7. “How Did You Get My Information?”<\/h3>\n
8. “I’ve Never Heard of Your Company.”<\/h3>\n
9. “This Looks Too Complicated for My Team to Learn.”<\/h3>\n
10. “We’re Using This Budget Somewhere Else.”<\/h3>\n
11. “Can You Call Me Back Next Quarter?”<\/h3>\n
12. “This Is Too Expensive.”<\/h3>\n
13. “You Don’t Have the Feature We Need.”<\/h3>\n
14. “I’m Going to Get Some Quotes for Comparison.”<\/h3>\n
15. “We’re Happy with the Way Things Are.”<\/h4>\n
16. “We Don’t Have a Big Enough Team for This.”<\/h4>\n
17. They Hung Up.<\/h4>\n
18. “Can You Just Email This Over?”<\/h4>\n
19. “I Saw a Bad Review of Your Company.”<\/h4>\n
20. You Got Their Voicemail.<\/h4>\n
Best Practices for Handling Sales Objections<\/h3>\n
Mistakes to Avoid in Sales Objection Handling<\/h3>\n
Conclusion<\/h2>\n
Frequently Asked Questions<\/h2>\n
Q1: What’s the difference between an objection and a rejection?<\/strong><\/h3>\n