50 Sales Objections: The Complete Field Guide to What B2B Buyers Actually Say (And Why)

When David Sandler taught his first cohort of salespeople in Stevenson, Maryland in the late 1960s, he opened by telling them that the entire industry had been training them to do the wrong thing. Every objection-handling manual on the market in 1967 was based on the same assumption: that an objection was a wall, and the salesperson's job was to push through it. Sandler told his class that an objection was not a wall. An objection was a window. The wall was what came before — the buyer's silence, their politeness, their nod, their non-committal "interesting." The window arrived when the buyer finally said something honest enough to be worth disagreeing with.

He spent the next thirty years building a methodology around that single inversion. Other people did, too. Neil Rackham at Huthwaite, studying thirty-five thousand sales calls in the late 1970s, came to a parallel conclusion: high-performing reps did not have fewer objections raised against them, they had different ones. They went deeper before objections surfaced, which meant the objections that surfaced were more substantive, which meant the conversations that followed were more honest, which meant the deals closed faster. HubSpot's own data, looking at modern SaaS sellers, finds that reps who handle objections well close at rates as high as sixty-four percent — roughly double the field average.

This is the field guide to fifty of those windows. The sales objections below come from the largest aggregated cold-call and discovery-call datasets in modern sales — Gong's three-hundred-million-call corpus, HubSpot's annual buyer report, Salesforce's State of Sales, and Cognism's prospecting research — augmented by the practitioner literature from Sandler, Challenger, MEDDIC, Command of the Message, and the modern coaches now operating on LinkedIn and podcasts. The fifty are arranged into the six categories that recur across every serious analysis of B2B sales objections: budget, need, authority, timing, trust, and the status quo (which is what we used to call "the competition" before everyone realized the competition was rarely another vendor).

Before we get to the fifty, internalize four ideas.

Now the fifty.

Category One: Budget and price (objections 1–10)

Budget objections are the most common single category of sales objections in B2B and have been every year that anyone has bothered to measure them. They are also the most consistently misunderstood. The Sandler methodology has been arguing for half a century that money concerns surface late only because pain was uncovered shallowly; if you have done the discovery properly, money becomes a function of pain, and a quantified pain almost always justifies the price.

Objection 1 — "It's too expensive." The reflex is to defend the price. The instinct is to discount. Both are wrong. The correct move is to ask: "Compared to what?" The buyer is comparing the price to something — a competitor, an internal benchmark, the cost of doing nothing. You cannot defend a price until you know what it is being compared against. Once you know, you can compare it to the right thing yourself.

Objection 2 — "We don't have the budget." The translation is almost never literal. "We don't have the budget" most commonly means "I don't yet believe the return will justify the budget I would have to fight for." The right response: "Totally fair. If the budget did appear, what would have to be true for you to want to spend it on this?" The answer is your business case.

Objection 3 — "Your competitor is cheaper." The classic. The classic response, popularized by Karrass and refined by every enterprise sales coach since, is to acknowledge and reframe: "You're right — and there's a reason for that. May I ask what's included in their price, and what isn't?" The reframe moves the conversation from price to scope, which is where you usually win.

Objection 4 — "Can you offer a discount?" The Sandler answer is almost always "What part of the value would you like me to take out?" This is not snark. It is a genuine question that forces the buyer to acknowledge that a discount is a trade against scope, and that the scope you proposed was a coherent design. Most discount requests evaporate when reframed as "which features should I delete."

Objection 5 — "We need to cut costs this year." The cost-cutting environment is the most expensive environment in which to ignore inefficiency. Your line should be some version of: "That makes this conversation more important, not less. What's the biggest cost line on your team's P&L right now?" The cost-cutting mandate is, properly understood, a buying signal in disguise.

Objection 6 — "It's not in this year's budget." Two responses, deployed in sequence. First: "When does next year's budget get planned?" Then: "Would it help if I put together a one-pager you could plug into the planning cycle?" You have just transitioned from being a vendor they are blowing off to being a vendor doing their planning homework. That position is rare and valuable.

Objection 7 — "I need to see the ROI before I commit." Always answer this with a question, never a number. "What ROI hurdle would make this an easy yes?" Forcing the buyer to articulate their hurdle in their own words means the ROI calculation you eventually produce will be measured against a number they themselves named. That is a much stronger frame than handing them a number they did not pre-commit to.

Objection 8 — "I need to compare you to two other vendors." "Smart. What are the three things that are going to matter most in the comparison?" By asking for the criteria, you may be able to influence the criteria. By influencing the criteria, you influence the outcome. Reps who refuse to ask this question and instead just submit to the bake-off lose most of these.

Objection 9 — "The price is fine, but we want net-90 terms." The right answer depends on your contract value, but the principle is to trade rather than concede. "I can probably help with terms. In exchange, would you be open to a two-year commitment?" Never give a concession without a counter-ask. The buyer learns to ask for more if you do.

Objection 10 — "The CFO won't approve this." The CFO is rarely the real obstacle; the real obstacle is that the champion does not yet have the language to sell the deal internally. The right move is to ask: "What does the CFO usually need to see to approve something like this?" Then build that exact artifact, with the champion's name on it. You are not selling around them; you are arming them.

Category Two: Need and fit (objections 11–20)

These sales objections are about whether your solution actually addresses a real problem. They are mostly diagnostic — the buyer is telling you that they do not yet see the connection between what you sell and what they need. The fault is almost always on the seller's side. You did not connect the two clearly enough, soon enough, in their language rather than yours.

Objection 11 — "We don't really need this." The Sandler response is to ask, gently: "May I ask what makes you say that?" The answer is gold, because it reveals the buyer's current mental model of the problem. Sometimes the model is correct and you walk away. More often, the model is missing a piece — and the missing piece is your value proposition.

Objection 12 — "We already do this in-house." The right follow-up: "What's the headcount on the team that runs it?" Internal teams are almost always opportunity-cost questions in disguise. If the team is spending sixty percent of their time on maintenance rather than the work they were hired to do, the in-house solution is far more expensive than it looks.

Objection 13 — "Our problem isn't that big." Quantify. "If I asked you to tell me how much time your team spends on [specific symptom] each week, what's your best guess?" The number they say out loud is almost always larger than the number they had in their head before you asked. The act of estimation does the work for you.

Objection 14 — "This isn't a fit for our industry." "Tell me about that — what's different about your industry that would change how this works?" The buyer's answer either reveals a real, specific gap (in which case you learn something) or, much more commonly, reveals a vague concern that you can address directly with a customer story from their industry.

Objection 15 — "We're too small for this." The right answer is rarely "but we have small-customer plans." The right answer is: "What are you trying to avoid by saying you're too small?" The honest answer is usually "complexity I can't afford to absorb" — and the fix is not pricing, it is implementation. Show them a frictionless onboarding and the size objection often disappears.

Objection 16 — "We're too big for this." The mirror image. The honest answer here is usually "I don't think you can handle our scale," and the fix is reference selling — show them three customers your size doing exactly what they would be doing. Most "too big" objections collapse against named customers of equivalent scale.

Objection 17 — "Our team isn't ready for this." Translation: "I don't believe my team can absorb the change." This is a change-management objection, not a product one. The right response is to ask about prior rollouts that went poorly — and then explain how your implementation directly addresses each failure mode they describe.

Objection 18 — "We don't have the data this needs." Sometimes true. Often a stall. "What data are you worried about specifically?" The conversation almost always reveals that the data exists, just in a form the buyer assumed was unusable. Half your customers said the same thing on the first call.

Objection 19 — "We don't have the technical expertise." The right counter is almost always implementation services, not product features. "What if we handled the heavy lifting for the first thirty days?" Buyers do not buy features; they buy outcomes. The outcome that gets them past this objection is being held by the hand for the first month.

Objection 20 — "This isn't a priority for us this year." Always ask: "What is the priority?" The answer reveals the executive narrative for the year, which tells you either how to align your pitch to ride that narrative or whether to back off and re-engage in twelve months. Both outcomes are valuable.

Category Three: Authority and decision-making (objections 21–30)

Authority objections are uniquely treacherous because they sound polite. The buyer is not pushing back on the product; they are pushing back on themselves. The seller's job is to map the decision and arm the champion. The mistake is to take "I need to talk to my boss" as a binary signal — it almost never is.

Objection 21 — "I need to run this by my boss." "Of course. What's your boss going to ask you that I should make sure you have an answer to?" You have just turned the prospect into your co-author. The questions they list are the slide deck you are about to build for them.

Objection 22 — "I'm not the decision-maker." "That's fine. May I ask who is, and what role you play in the decision?" Two pieces of information for the price of one. Many "I'm not the decision-maker" buyers are, in fact, the influence broker — and they often hold more sway than the title-bearing decision-maker.

Objection 23 — "We need to involve [other department]." "Smart. Who specifically? I'm happy to set up a separate conversation if that would help." You are offering to do the multi-thread work for them. Multi-threading is the single most underrated predictor of deal close rates in every Gong study that has measured it.

Objection 24 — "Our procurement team handles this." Translation: "You are now in for legal review and finance scrubbing." The right move is to ask: "Can you walk me through how procurement engages?" Reps who treat procurement as a partner rather than an obstacle close measurably faster.

Objection 25 — "I'd need to bring this to the board." Almost never literally true unless the deal is enormous. When it is true, the right response is: "Happy to provide a board-ready summary. What's the format your board prefers?" You have positioned yourself as understanding how their board operates, which builds credibility.

Objection 26 — "Our CEO won't go for this." The most useful follow-up: "What's the kind of thing the CEO typically does go for?" The answer reveals the strategic narrative inside the company — what the CEO is publicly committed to. Your value proposition needs to attach to that narrative, not to operational pain.

Objection 27 — "I don't have signing authority." "Got it. What's your authority threshold, and how do deals above it usually get through?" Mapping the dollar thresholds inside the buyer's organization is one of the most underrated skills in B2B. Once you know that deals above $50K go to the VP and above $250K go to the CFO, your packaging strategy clarifies dramatically.

Objection 28 — "There are too many cooks in the kitchen on this decision." This is your champion telling you the truth. The right response is: "How can I help you simplify the conversation internally?" The honest answer is usually some combination of business case, social proof, and a tight pitch they can repeat verbatim. Build all three.

Objection 29 — "I'm leaving the company / changing roles." Critical to handle. "Congrats — or condolences, depending. Who's taking this on next, and would you be willing to introduce me?" Departing champions can either bequeath a deal or kill it. The introduction is the difference.

Objection 30 — "Our IT/security team has to approve everything." Pre-empt rather than react. "Totally — when's a good time to loop them in? I'd rather get the security review started early than have it become the long pole." Reps who proactively initiate security review shorten their sales cycle by weeks, not days.

High-performing reps do not have fewer objections raised against them. They have different ones.

Category Four: Timing and urgency (objections 31–40)

Timing objections are the most slippery category of sales objections because they sound logistical but are almost always strategic. "Now isn't a good time" is the most common stall in B2B, and the reps who win against it do so by surfacing the real cost of waiting rather than by arguing with the calendar.

Objection 31 — "Now isn't a good time." "I hear that a lot. May I ask — what would make it a good time?" The trigger event they describe is the thing your follow-up sequence should be wrapped around. Vague follow-ups die; trigger-event follow-ups land.

Objection 32 — "Call me back in six months." Always re-anchor the call-back to a specific event, not a calendar slot. "Got it. What's happening in six months that makes this worth talking about then but not now?" If they cannot articulate the change, the call-back is a brush-off. If they can, you have a concrete reason to re-engage.

Objection 33 — "We're too busy right now." The most useful reframe: "That's the exact reason most of our customers buy. They started with us because they were already underwater. What's eating the most time?" Buyer busyness is not a contraindication; it is, frequently, the diagnosis.

Objection 34 — "We're in the middle of [other initiative]." "How's it going so far?" The follow-up question always opens the door. Most other initiatives are running into snags you do not yet know about, and those snags are often where your product fits. The right play is empathy, not displacement.

Objection 35 — "Let's revisit this next quarter." The Sandler response: "Of course. So I can be useful between now and then — what's the question we'd need to answer for next quarter to feel different than this quarter?" If they cannot name the question, "next quarter" is the buyer's version of "I'd rather not say no out loud."

Objection 36 — "We're going to wait until after [event]." "Makes sense. Out of curiosity — what's at stake at the event that this depends on?" Sometimes the event is real and load-bearing. Sometimes it is anchor decoy. The question reveals which one you are dealing with.

Objection 37 — "It's not the right time in our budget cycle." "What does the next budget cycle look like? I'd rather get on your timeline than push against it." Aligning to the budget cycle is the dignified version of patience, and prospects respect dignified patience far more than they respect pressure tactics.

Objection 38 — "We just signed a contract with someone else." Document the renewal date and treat it as the new opportunity. "Congrats. When does that renewal come up? I'd love to be on your shortlist when you re-evaluate." Many of these accounts return — but only if you are professional in this moment, not bitter.

Objection 39 — "We're considering, but no decision until Q4." Use the time to multi-thread. "Sounds good. Between now and Q4, would it be useful for me to brief other folks on your team so the Q4 conversation moves faster?" The time between now and the decision is the most valuable time you have; do not waste it waiting.

Objection 40 — "I need more time to think about this." The single most important objection in the entire field guide, because it is almost always a polite refusal. The right response: "Of course. What's the part you want to think about most — the fit, the price, or the implementation?" Forcing the buyer to name the concern is what re-opens the conversation. The reps who do this convert at roughly double the rate of reps who let "let me think" close the call.

Category Five: Trust and credibility (objections 41–46)

Trust objections come at every stage of the funnel, but they cluster at the moment of commitment. The buyer is about to put their name on a decision, and the part of them that fears being wrong starts whispering. The right response is rarely a stronger pitch. It is almost always more evidence, more references, and more transparency about the failure modes you have already navigated.

Objection 41 — "I've never heard of your company." The reflex is to over-explain who you are. The better move: "Fair. I'd rather show than tell — who's the most skeptical person on your team I could spend twenty minutes with?" Confidence about your obscurity is more trust-building than defensiveness.

Objection 42 — "Do you have customers in our industry?" If yes, name them. If no, the right response is honest: "Not yet — but here's the closest analog we work with, and here's why I think it transfers. Would it be useful to talk to them?" Buyers prefer "no, but here's why it still works" over a stretched claim.

Objection 43 — "What if it doesn't work?" Address the failure mode head-on. "Honestly, the times it hasn't worked were usually about [specific failure mode]. Here's how we mitigate that now." Buyers buy from sellers who can describe their own failure modes credibly. It signals that you have seen the messy version, not just the demo version.

Objection 44 — "Our last vendor over-promised and under-delivered." "That's incredibly common, and I'm sorry you went through it. What did they promise that didn't materialize? I want to make sure I'm not setting you up for the same thing." Honesty about your industry's failures is one of the cleanest trust signals available.

Objection 45 — "How do I know you'll still be around in three years?" Especially common for startups. The right move is to share the substance — funding stage, revenue, retention, customer growth — without bragging. "Here's the relevant set of numbers. I'll share whatever you want." Transparency about company health builds far more credibility than corporate-speak.

Objection 46 — "Your reviews online aren't great." Always address it directly. "Yeah — here's what happened, here's what we changed, and here's what the most recent cohort of customers says." Acknowledging negative reviews builds trust faster than pretending they do not exist.

Category Six: Competition and the status quo (objections 47–50)

The last category of sales objections is the one that masquerades as the others. Most "we have no budget" and "now isn't a good time" objections are, beneath the surface, "we are not yet convinced that the cost of changing is less than the cost of staying." The status quo is the strongest competitor in B2B sales, and beating it requires making the cost of doing nothing concrete.

Objection 47 — "We're already using [competitor]." The mistake is to attack the competitor. The right move is to agree: "Great tool. Quick question — when [scenario where you are meaningfully better] comes up, how do they handle it?" The specificity of the trap question is the entire move.

Objection 48 — "We're happy with our current solution." The Gong dataset is unambiguous: criticizing the incumbent makes prospects defensive. Instead, ask: "What do you like most about it?" Praising forces evaluation. The follow-up — "If you could improve one thing about it, what would it be?" — almost always produces the gap you sell into.

Objection 49 — "We're going to keep doing it the way we've always done it." The status quo objection in its purest form. The right response, which traces back to the Challenger Sale: "Out of curiosity — when's the last time you measured the actual cost of doing it that way?" The cost of the status quo is almost never measured. The act of measuring it is, often, the first step in selling against it.

Objection 50 — "Nothing is broken — why change?" The hardest objection of all, because the buyer is operating from a position of relative comfort. The Challenger move is to reframe: "What's broken usually shows up later than you'd want. The customers I work with bought before something broke because they saw the signal early. Here's the signal I'm seeing in your space." If you can credibly name a leading indicator the buyer has not yet noticed, you have created urgency.

The pattern underneath the fifty

If you read the fifty closely, you noticed that the same handful of moves recur. Agreement before address. Question before pitch. Specific before general. Cost of inaction before cost of action. Champion-arming before champion-bypassing. The fifty sales objections are not fifty different techniques; they are fifty different surface manifestations of perhaps five underlying ones.

This is good news. It means you do not have to memorize fifty scripts. You have to internalize five moves and deploy them in the surface form the buyer's specific objection demands. The reps who do this without thinking about it are the reps who close at sixty-plus percent. The reps who are still flipping mental flashcards in the moment are not yet there.

The fastest way to get to "without thinking about it" is recorded role-play. Take a partner, throw thirty objections at each other in random order over a thirty-minute block, record the audio, and listen back together. Within four sessions, your responses will collapse from over-rehearsed paragraphs into clean, confident two-sentence moves. That collapse is what mastery actually feels like.

Practice the 50 against an AI buyer

SalesArmor lets you roleplay objection handling against an AI prospect modeled on a real LinkedIn profile — one who pushes back the way real CFOs, procurement leads, and skeptical VPs do. You get scored on whether you agreed before you addressed, asked before you pitched, and surfaced the layer beneath the objection. Free to try.

Try SalesArmor free →

The objection behind the objection

It is worth slowing down on the most consistently misunderstood pattern in B2B sales: the objection you hear is rarely the objection that is actually stopping the deal.

The buyer who says "the price is too high" is, eighty percent of the time, telling you something else. They are telling you they do not yet believe the return justifies the price. They are telling you they have not yet built the internal political case. They are telling you they are worried about being blamed if the project fails. They are telling you their CFO will push back, and they have not yet found the language to push back at the CFO. The surface objection is a cover for the deeper concern. The cover exists because the deeper concern is, in the buyer's own internal narrative, embarrassing to name out loud.

This pattern is the structural reason that handling the literal objection so often fails to move the deal. The rep addresses the literal price concern, the buyer nods, and the deal stalls anyway. The rep is, in effect, answering a question the buyer was not really asking. The fix is the layered probe — three or four follow-up questions that move from surface to substance. "When you say the price is too high, is the bigger issue the absolute number, the comparison to alternatives, or the ROI math?" Each layer surfaces a different deeper concern, and the deeper concern is where the deal actually lives.

The buyer who says "we have no budget" is, in many cases, telling you the same thing. They are not literally without funds; they are telling you they have not yet decided this is worth diverting funds toward. The layered probe surfaces the real issue. "When you say no budget, do you mean no allocated budget for this fiscal year, or no internal will to find budget for this specific problem?" The first is a timing problem you can navigate around. The second is a desire problem you have to solve directly.

The buyer who says "I need to think about it" is almost always telling you that there is a specific concern they have not yet articulated. The Sandler answer — "what's the part you want to think about most?" — surfaces it. Reps who let "let me think" close the call are, in the published data, converting at about half the rate of reps who push for the specific concern.

The discipline that all of this requires is a small amount of comfort with productive discomfort. The buyer's surface objection is the polite version. The deeper one is rarely polite. Asking for the deeper version requires you to be willing to be in a slightly uncomfortable conversation for the thirty seconds it takes to surface it. Reps who can hold that discomfort, gently, get to the truth. Reps who flinch — and most reps flinch — accept the surface objection at face value and lose deals that could have closed.

The private objection library you build for yourself

The fifty sales objections in this manual are the public corpus. The objection library that actually wins your deals is the private one you build for your specific market.

The drill is straightforward. Every week, write down the specific objections you heard, in the buyer's own words. Not paraphrased — verbatim, as you remember them. Within four weeks you will have a corpus of fifty to a hundred phrasings that are unique to your industry, your buyer personas, and your product. Within twelve weeks the corpus will be rich enough that you can begin to see patterns — the recurring objection structures, the words that signal stalling versus disqualifying, the rhetorical moves your competitors are training your buyers to make.

The corpus then becomes a coaching artifact. Run it past your sales engineering team, your customer success team, and your senior reps. Each will see angles you did not see. The collective wisdom assembled from the corpus is, over the course of a year, more valuable than any externally published objection library — because it is calibrated to your specific reality.

The same corpus becomes a hiring artifact. New reps onboarded with your private objection library ramp in months rather than quarters. They walk into their first calls already prepared for the specific phrasings they will hear, in the specific cadence they will hear them, from buyers who match the specific profiles of your existing accounts. That ramp acceleration is worth, in aggregate, more than most companies' formal sales-enablement budgets.

Objections as buyer engagement

The hardest thing to internalize about sales objections is that they are, almost always, signals of engagement rather than signs of rejection. The buyer who pushes back is the buyer who is processing your offering seriously enough to articulate concerns. The buyer who nods politely and says "interesting" without pushing back is, more often than not, the buyer who is not engaging and will not close.

This inverts the rep's natural emotional response. The objection feels, in the moment, like a setback. It is, in fact, an invitation to a deeper conversation. The reps who hold this frame — who hear an objection and think "good, we are now actually talking" rather than "shit, the deal is in trouble" — handle objections measurably better than reps who hear objections as threats.

The fifty objections in this manual are not obstacles you must defeat. They are doors the buyer is opening into their own decision-making process. The reps who walk through those doors with calm curiosity, rather than with defensive rebuttals, are the reps who close.

A note on sources

This field guide synthesizes research across the largest public corpora on sales conversations: Gong's analyses of 300M cold calls, HubSpot's annual buyer reports, Cognism's prospecting research, Salesforce's State of Sales, and the practitioner literature from Sandler, Challenger, MEDDIC, and Command of the Message. The fifty objections are the public consensus pattern; the deeper structure beneath each one — the agree-before-address move, the layered probe, the cost-of-inaction reframe — comes from decades of patient reverse-engineering by people who took the time to listen to thousands of recorded calls and ask, honestly, what the good reps did differently.