100 Sales Objections and How to Respond: The Field Guide

Every sales objection you will ever hear is one of four sentences wearing different clothes: “I don’t want to change,” “I don’t want to pay,” “I don’t believe you,” or “not now.” That is the entire genre. The 100 objections below are organized by those four buckets, each with a response you can actually say, because knowing the category tells you how to respond before you finish hearing the sentence.

Two rules before the list. First, clarify before you counter: most objections are compressed, and “too expensive” can mean three different things. Second, never argue with the surface phrasing; answer what the bucket is really asking.

TL;DR

Bucket	What they’re really saying	Your job
Change / status quo	The pain of switching feels bigger than the pain of staying	Make the cost of staying visible
Budget / cost	The value story hasn’t beaten the price tag yet	Reframe price against outcomes, resize scope
Trust / credibility	Prove it, and prove you’ll still exist next year	Replace promises with checkable proof
Timing / priority	This lost to something else on the list	Attach to what won, or earn the right to return

Change and status quo objections (1-25)

The hardest bucket, because “fine” is a feeling, not a metric. Your move is never to attack what they have; it is to make the cost of keeping it visible.

Objection	How to respond
“We’re happy with our current provider.”	“That makes sense, and I’m not asking you to switch today. When you say happy, is that happy with the results or happy that it’s not on fire? Most teams we talk to are the second kind.”
“It works fine for now.”	“Fine is usually the most expensive setting. What would need to break for this to become a priority, and what does it cost you while it doesn’t?”
“Switching is too much effort.”	“Agreed, switching badly is. That’s why migration is on us: data, setup, and training. What made past switches painful for you?”
“We built something internally.”	“Respect, that means the problem is real. What does maintaining it cost you in engineering hours, and who owns it when that person leaves?”
“We’ve always done it this way.”	“And it got you here. The question is whether the way that got you here gets you to the next number. What is the target this year?”
“We tried a tool like this and it failed.”	“That’s useful. What specifically failed: the tool, the rollout, or the fit? The answer usually changes what to try next.”
“Our team won’t adopt a new tool.”	“Then the tool failed them before they failed it. What did the last rollout skip: training, a champion, or a reason to care? We handle all three.”
“We don’t want to disrupt operations mid-quarter.”	“Neither do we; rollouts that ignore the calendar deserve to fail. What if setup happens now and go-live lands on day one of next quarter?”
“Change management is a nightmare here.”	“Then let’s not manage change, let’s shrink it. Which single team feels this pain most? Start there, let the results recruit the rest.”
“Our process is too unique for an off-the-shelf tool.”	“Every team says that, and about 20% are right. Walk me through the step you think we can’t handle, and I’ll tell you honestly if we can.”
“We just renewed with our current vendor.”	“Then the pressure’s off, which honestly makes this a better conversation. When’s the renewal date? I’ll be your comparison point 90 days before it, and until then I’ll only send you things worth reading.”
“Our workflow is built around the current tool.”	“That’s the real cost of switching and I won’t pretend otherwise. What I’d ask: is the workflow built around the tool because it’s right, or because the tool forced it? Teams usually discover the second.”
“The team just finished learning the last system.”	“Change fatigue is real. That’s an argument for timing, not for never. What if we scoped this so the team’s day one looks like their current day, and the new capability arrives underneath it?”
“Leadership hates changing vendors.”	“Usually because the last change was sold as painless and wasn’t. What went wrong last time? I’d rather design around that scar than pretend it isn’t there.”
“We’re consolidating tools, not adding.”	“Then we might agree more than you think: we typically replace two or three line items, not add one. Want me to map what we’d absorb from your current stack?”
“If it ain’t broke, don’t fix it.”	“Fair, and I’d never argue with working. One question though: is it not broken, or has the team just stopped reporting the workarounds? Those are different conditions with the same slogan.”
“Our manual process gives us more control.”	“It gives you more visibility into effort, which feels like control. What’s your error rate on the manual step? Control is knowing the number, not touching every row.”
“We need to fix internal processes first.”	“Sensible order. Which process, and what does ‘fixed’ look like? I ask because half the time the tooling IS the process fix, and the other half I should genuinely wait.”
“Our industry is different; this won’t work here.”	“Parts of it probably won’t, and I’d rather find those now. Which part of your world do you think breaks it? Let me show you how [same-industry customer] handled exactly that.”
“The team is attached to the current way.”	“Attachment usually means the current way respects something real: their time, their habits, their numbers. What would a new tool have to respect to earn them? That’s the rollout plan.”
“We tried to switch before and gave up mid-migration.”	“So the risk isn’t the destination, it’s the journey, and you have evidence. What killed the migration? If it’s data, we do that part for you. If it’s adoption, that’s a different fix and I’ll be honest about it.”
“Head office decides tooling, not us.”	“Understood. Two paths: I can equip you to raise it, or approach head office directly and credit you for the intro. Which serves you better?”
“We’re moving everything to [big platform] anyway.”	“Makes sense as a center of gravity. Most of our customers run us alongside it because [platform] is broad where this problem needs depth. Can I show you the seam where the two fit?”
“I personally built the current process.”	“Then you know its tradeoffs better than anyone, including where it strains. I’m not here to grade it; I’m here to ask what you’d build differently with today’s tools and no legacy.”
“Prove it works before we change anything.”	“Deal. Two-week pilot, your list, your inboxes, a number we agree beforehand. If it misses, I’ll write the closing summary myself.”

Budget and cost objections (26-50)

Price objections are almost never about the number. They are about the number relative to a value story that has not landed yet, or a budget process you have not mapped.

Objection	How to respond
“It’s too expensive.”	“Compared to what? If it’s the current tool, fair, let’s compare outcomes, not invoices. If it’s doing nothing, let’s price that too: what does the problem cost per month?”
“There’s no budget this year.”	“Understood. Is that no budget anywhere, or no budget labeled for this yet? Most of what we replace is paid for from three other line items.”
“Your competitor is cheaper.”	“They are, and if price is the deciding criterion, they may be the right call. Before you decide, compare what happens after the sale: support, data quality, and what’s in the fine print per seat.”
“We need a discount to move forward.”	“I’d rather change the scope than the price: fewer seats to start, annual terms, or a later start date. Which of those helps?”
“The ROI isn’t clear.”	“Then we shouldn’t proceed yet. Give me your numbers: reps, meetings per month, deal size, and I’ll build the math with you. If it doesn’t clear the bar, I’ll say so.”
“We just spent our budget on another tool.”	“Then the worst thing I can do is pile on. When does that tool have to prove itself by, and can we talk two weeks before that review?”
“Finance will never approve this.”	“What does finance need to see: payback period, a line-item comparison, or a customer reference in your industry? I’ll build the exact document they ask for.”
“Can you do month-to-month? Annual is too risky.”	“We can. It costs more per month, which is fair, you’re paying for the exit. Most teams switch to annual once the first quarter’s numbers land.”
“We’re cutting costs right now.”	“Then every tool should have to justify itself, including ours. What if this replaces two or three line items instead of adding one?”
“The price went up since we last talked.”	“It did, and I won’t pretend otherwise. Here’s what was added since then. If the old scope is what you want, let’s see if a smaller plan matches it.”
“We only have budget for must-haves.”	“As it should be. What made the current must-haves earn that label? If this doesn’t clear the same bar with numbers, it should wait. Let’s run the math and let it compete honestly.”
“The CFO cut all new spend this quarter.”	“Then the timing question is settled and I won’t fight it. Two things: does replaced spend count as new spend? And when does the freeze thaw? I’ll be useful in the meantime and ready on the date.”
“We can get 80% of this with a cheaper tool.”	“Sometimes true, and for some teams the right call. The 20% you’d give up is [specific]: if that’s decoration for you, buy the cheaper one, sincerely. If it’s the point, the discount is expensive.”
“Per-seat pricing kills us at our size.”	“Then let’s not price it per seat. Usage-based or a flat band might fit your shape better. What structure has worked for you with other vendors?”
“We’d rather hire another rep with that money.”	“A rep is a great spend, and here’s the honest comparison: a rep at $75K produces in month four; this produces in week two and makes your existing reps faster. Want the math side by side?”
“Last tool in this category didn’t pay for itself.”	“Then your bar is earned. What was supposed to happen that didn’t? We’ll set this contract’s success number against exactly that, with a check-in on the calendar before renewal.”
“Procurement will squeeze you anyway, so start lower.”	“I’d rather give procurement a clean, defensible number than pad one for the squeeze. The price is the price; what I CAN move is scope, terms, and start date, and I’ll move them for you, not for the process.”
“It’s cheaper to keep doing this manually.”	“On the invoice, yes. Count the hours: [estimate] rep-hours a month at loaded cost, plus the error rate. Manual is a price you pay in a currency that doesn’t show up in accounting.”
“What’s the real price after the discount games?”	“There are no games here, which I know is what someone playing games would say. Here’s the list price, here’s what changes it (term, volume, timing), and here’s the number for your scope. It won’t move at quarter-end.”
“We need three quotes for any purchase.”	“Good policy. Want me to tell you honestly who the other two should be? I’d rather be compared against the real alternatives than straw men, and you’ll trust the outcome more.”
“Budget belongs to another department.”	“Then the question is whose problem this officially is. If [dept] owns the budget but you own the pain, let’s build the one-pager that lets you hand them a decision, not a request.”
“Prices always jump at renewal; why start?”	“Ours is capped in the contract: renewals move at most [X]%. Put it in writing in the order form. The renewal-squeeze play only works on customers who didn’t ask; you just asked.”
“Show me ROI from a company exactly like us.”	“Here’s [same-size, same-industry customer]: their numbers, their timeline, and what didn’t work in month one, because something never does. I’ll intro you; ask them the hard version.”
“We’re bootstrapped; every dollar is scrutinized.”	“Then let’s scope to the smallest slice that pays for itself: one seat, the [core feature], and a monthly check on whether it earned the next seat. Growth should buy the expansion, not hope.”
“Honestly, it’s just a lot of money.”	“It is. The only question worth asking: compared to the cost of the problem, or compared to the budget line it has to fit? The first we can calculate together. The second, tell me the number and I’ll tell you what fits in it.”

Trust and credibility objections (51-75)

The bucket where talking makes it worse. Every response here replaces a claim with something checkable: a pilot, a reference, a document, a test the buyer runs themselves.

Objection	How to respond
“I’ve never heard of your company.”	“Most of our customers hadn’t either; the ones switching from the big names rarely announce it. Want three references from companies your size in your industry?”
“How do I know your data is accurate?”	“Don’t take my word for it. Send me 50 contacts you already know, and we’ll run them through and score ourselves in front of you.”
“You’re a small vendor. What if you disappear?”	“Fair risk to weigh. Here’s our funding, customer count, and growth. Also worth asking the incumbent: what happens to your pricing when their next earnings call goes badly?”
“The last vendor promised the same things.”	“Then don’t accept promises. Ask for a proof: a two-week pilot with your list, your inboxes, your targets, and a number we agree on beforehand.”
“Your reviews mention [weakness].”	“True, and here’s the honest context on that one. I’d rather you hear it from me than discover it in month two.”
“We only buy from established leaders.”	“That policy has a cost: leaders price like leaders and innovate like incumbents. What did your team pay for that safety last year?”
“Security won’t approve an unknown vendor.”	“Send me the questionnaire. SOC 2, GDPR, data residency: we’ve completed it for companies with stricter requirements than yours, and I’ll get it back in a week.”
“I don’t trust AI-generated outreach.”	“Neither do buyers, when it’s fake personalization. Ours shows its sources: every claim in a draft traces to where it was found, and your rep approves before anything sends.”
“Can I talk to a customer like us?”	“Yes, and pick your own: here are several in your industry and size band. Ask them what went wrong, too; every rollout has a bump.”
“You say that because you’re selling.”	“I am selling, so verify instead of trusting: the pilot, the references, and the numbers are all checkable without believing a word I say.”
“Your company is too new.”	“We’re [N] years in with [count] customers, and youth cuts both ways: you get roadmap influence the incumbent’s customers lost years ago. Ask [reference] what shipping a feature request feels like here.”
“What happens to our data if this fails?”	“You export everything, standard formats, any time, no ransom. It’s in the contract, section [X]. A vendor that makes leaving hard is telling you what staying will feel like.”
“Who else at our scale runs this?”	“[Two names in their band]. Not our biggest logos, your actual peers. I’ll intro either, and I’d suggest asking them what broke in month one, because the honest answer builds more trust than my pitch.”
“The AI stuff feels like a black box.”	“Then let’s open it: every AI-generated line shows its sources, and nothing sends without a human approving it. If a claim can’t cite where it came from, it doesn’t go in the email.”
“We got burned by exactly this kind of promise.”	“Then don’t accept promises; accept terms. Success number agreed upfront, pilot before commitment, exit without penalty if we miss. Burned customers make the best contracts.”
“Your support will disappear after we sign.”	“Check our response times in the reviews, and put an SLA in the contract. Also fair to ask: who specifically owns your account after signature? Here’s their name now, not a queue.”
“Everyone claims 95% accuracy.”	“They do, so don’t believe claims, run the test: send me 50 contacts you already know the truth about, and we’ll score ourselves in front of you. Ten minutes, and you’ll know which claims were marketing.”
“Compliance will never clear a vendor this size.”	“Send the questionnaire before we go further; if compliance is a wall, better to hit it in week one than month three. SOC 2, GDPR, DPA templates: ready. Smaller than the incumbent, yes; less compliant, no.”
“I looked you up and found almost nothing.”	“Fair, we spend on product, not PR, which is either reassuring or worrying depending on your taste. Here’s what does exist: reviews, customers, funding. And here’s a live login; the product is the best evidence we own.”
“How do I know you’ll still exist in three years?”	“You don’t, and neither do I with certainty, so hedge it contractually: data export rights, no multi-year lock-in unless YOU want the pricing, and a transition clause. Weigh that against the incumbent charging you like they’ll exist forever.”
“Our last vendor lied about the roadmap.”	“Common, because roadmaps are sales collateral nobody audits. I’ll only commit to what’s shipped or in beta you can touch today. If the deal needs a future feature to make sense, it isn’t a deal yet.”
“You’re just reselling someone else’s data.”	“Part of every data product is sourced, ours included; the difference is the verification layer on top: [method]. That’s why the test in front of you matters more than any sourcing story, mine or theirs.”
“The demo always looks great; production never does.”	“True of every demo ever given, including this one. That’s what the pilot is for: your data, your volume, your edge cases. The demo earns the pilot; only production earns the contract.”
“I don’t have time to vet another vendor.”	“Then let me compress it: reference contacts, security docs, and a scored test on your own data, all delivered this week, reviewable in an hour. Vetting is my job to make easy, not yours to endure.”
“Why is nobody talking about you online?”	“Our category’s loudest names spend eight figures on being talked about, priced into their contracts. Quiet costs less. But don’t take silence as the answer: here are three customers who’ll talk your ear off.”

Timing and priority objections (76-100)

“Not now” is the politest way to say “you lost to something else on my list.” The play is to find what won and attach to it, or to schedule your return with a reason.

Objection	How to respond
“Call me next quarter.”	“Happy to. So the call is worth your time then: what will be different next quarter, and what should I bring to that conversation?”
“This isn’t a priority right now.”	“Understood. What is the priority? Half the time what we do turns out to feed the thing that IS the priority, and if not, I’ll leave you alone.”
“We’re too busy to evaluate anything.”	“That busyness is usually the case for the tool, not against it. What’s eating the team’s time? If it’s not something we remove, this can wait.”
“We’re in the middle of a reorg.”	“Then nothing should be signed now. Who will own this problem when the dust settles, and can I send you the one-pager to hand them?”
“Let’s revisit after our busy season.”	“Makes sense. One thought: teams that set up before busy season enter it with the new capacity. Would a setup-now, pay-later start change the math?”
“I need to talk to my team first.”	“You should. What do you expect them to push back on? I’ll give you the answers to bring, or better, invite them and I’ll take the hard questions live.”
“The decision maker is out for two weeks.”	“Then let’s use the two weeks: I’ll prepare the business case so the decision takes one meeting instead of four when they’re back.”
“We just signed with someone else.”	“Congrats, genuinely, and I’ll stop selling. Two asks: how did you decide, and may I check in 60 days before renewal to be your comparison point?”
“Send me some information.”	“I will, and I’ll keep it to one page. So I send the right page: what would the information need to show for this to be worth 20 minutes?”
“Why now? We’ve survived without it.”	“You have. The question is what surviving costs: [specific metric] is the usual bill. If yours is different, then honestly, you don’t need us.”
“We’re heads-down on a launch until Q3.”	“Then I’ll be brief now and useful in Q3. One thought before I go: launches make pipeline demands. If the launch lands and leads spike, is the current setup ready for that? That’s the conversation I’d want ready.”
“Budget planning happens in November; it’s May.”	“Perfect, because November budgets are built from October business cases, which come from September pilots. Work backwards and this conversation is exactly on time.”
“New leadership starts next month; everything’s frozen.”	“As it should be. Incoming leaders review the stack in their first quarter; want me to prepare the one-pager that makes your team look ahead of that review instead of subject to it?”
“We need to see this year’s results first.”	“What number are you waiting on, and what does it need to show? If I know the threshold, I can have everything staged so the yes takes a week instead of a quarter.”
“Contract with the incumbent runs 14 more months.”	“Noted, and I won’t waste your year. Two things: overlap deals exist for switches worth making early, and either way I’m calendaring us for month 11. What should I bring to that call?”
“Ask me again after the holidays.”	“I will, on [specific date]. So that call is worth taking: what will have changed by then, and what would make it a yes-conversation instead of a repeat of this one?”
“We move slowly on purpose; it’s our culture.”	“Deliberate beats hasty, and I’ll match your pace. Let’s map the pace: what are the stages between here and a decision, and what does each one need? Slow with a map is fine; slow without one is a stall.”
“Too many projects in flight right now.”	“Then this shouldn’t become a project. What if it lands as a finished capability: we do the setup, one team pilots it, and your project list never grows? Projects are what vendors create when onboarding is their job to give you.”
“Let me get through quarter-end first.”	“Of course. And quarter-end is my best argument: the scramble you’re about to run is the thing this removes. Call me in week one and let’s make next quarter-end boring.”
“The person who’d own this just left.”	“Sorry, that’s disruptive. Who’s holding it in the interim? A tool that runs itself is worth more, not less, during a gap; and when the new hire lands, I’ll be one line in their onboarding instead of a cold pitch.”
“We’ll revisit in the new fiscal year.”	“Booked: [date]. Between now and then, one useful thing instead of check-in spam: I’ll send the benchmark for your segment when it’s out. What else would make the new-year conversation faster?”
“Something urgent came up; rescheduling everything.”	“Understood, urgent wins. When you resurface, would it be more useful to resume where we left off, or restart with a 10-minute recap? I’ll prep whichever, no momentum lost.”
“It’s on the roadmap for ‘someday.’”	“Someday is where good ideas go to age. What would promote it: a number getting worse, a leader asking, a competitor moving? I’ll watch for exactly that and call you when it happens, with evidence.”
“Honestly, I just don’t have bandwidth to think about it.”	“Then don’t; that’s the point of this call. Give me the two facts I need [X, Y] and I’ll bring back a one-page decision: worth your time or not, with the math shown. Your bandwidth cost: five minutes, twice.”
“Why now? Nothing’s on fire.”	“Nothing visible. The usual bill for waiting is [specific metric decay]; if yours is genuinely flat, then honestly, wait, and let’s set the one number that would change the answer. I’ll check it with you quarterly.”

The pattern behind all 100

Read back through any bucket and the responses repeat four moves: clarify the compressed statement (“compared to what?”), quantify the invisible cost (of staying, of waiting, of manual), replace the claim with something checkable (a pilot, a reference, a contract term), and schedule the return with a reason (a date plus what will be different). Every objection you hear that is not on this list yields to the same four moves; hear the bucket, pick the move, and stop memorizing scripts.

How to actually get better at this

• List your real top five. Not this list’s, yours. Pull the objections from your last twenty calls; most reps are surprised which ones actually recur.
• Build two responses for each: one soft, one direct. The soft one for early-stage calls, the direct one for late-stage stalls.
• Pre-handle the predictable ones. If every deal hears the same objection, put your answer in the pitch before the buyer raises it.
• Rehearse against an AI, not a mirror. Have Claude or ChatGPT play your buyer’s CFO and push back twice on every answer; we published the setup in how to use Claude for sales.
• Mine your transcripts. Objections you handled badly are the syllabus. Ten transcripts tell you which three answers to rehearse this month.

The objection you prevent beats the one you handle

A lot of objections are self-inflicted: generic outreach earns “I’ve never heard of you,” a wrong-fit list earns “this isn’t a priority,” and a stale contact record earns bounced follow-ups that end conversations silently. Research-grounded outreach through deep research and verified contact data does not make you better at objection handling; it makes the meeting start further down the field. And the timing objections (“call me next quarter”) only convert if the follow-up actually happens, which is a sequencing problem, not a memory problem.

Frequently asked questions