By Siddharth Gangal "We do not have the budget for this."
Why they say it
Budget is often not approved, not allocated to this category, or sitting with a different budget owner. "No budget" rarely means the company has no money — it means there is no pre-approved line for this purchase.
The response
"Where does budget usually come from for a problem like this — operations, sales, or something else? And what would need to happen for this to get approved outside the normal cycle?"
Follow-up
"If the business case were solid, who would you bring it to first?"
"I can get a cheaper version somewhere else."
Why they say it
The buyer is comparing on price before comparing on outcomes. They have a lower-cost option in mind but have not yet confirmed whether it solves the same problem at the same depth.
The response
"I want to make sure you pick the right option — even if that is not us. What does that solution do that ours does not? And what does it not cover that you still need solved?"
Follow-up
"Is the gap on price, on features, or on both? That tells me whether there is a conversation worth having here."
"We do not have budget until next fiscal year."
Why they say it
Legitimate budget cycles exist. This objection is real when the company genuinely does not have discretionary spend available. It is a stall when the buyer is using the budget cycle to delay a decision they are not ready to make.
The response
"I understand. Two questions: first, when does your next planning cycle open? And second, if we can show a payback inside the current year, is there a path to getting this approved now through a different budget line?"
Follow-up
"Let us set up a call with whoever owns budget planning so we are positioned for Q1 — rather than starting that conversation from scratch when the cycle opens."
"I need to think about it."
Why they say it
This is almost always a stall, not an objection. "I need to think about it" typically means: the rep did not build sufficient urgency, the buyer is uncomfortable saying no directly, or there is a concern the buyer has not voiced yet.
The response
"Of course — that makes sense. What specifically do you need to think through? I want to make sure I have given you everything you need to make a confident call, rather than leaving a gap."
Follow-up
"Is there a concern you have not raised yet? If there is something that does not add up, I would rather know now than have you walk away with an unanswered question."
Timing objections — 4 responses that work
Timing objections are the second most common category. They feel like deferrals but they are usually urgency failures — the rep has not yet connected the problem to a consequence that creates pressure to act now. The response is always the cost-of-inaction question: what does it cost the business to leave this unsolved for another quarter?
Real timing objections exist. If a company just completed a major acquisition and is in integration mode, sales conversations go nowhere until the dust settles. The rep's job is to distinguish a genuine timing constraint from a manufactured one — and to build the case for urgency when it is the latter.
"Now is not a good time."
Why they say it
The buyer is busy, distracted, or genuinely in a high-priority period. This objection is also used as a soft rejection when the buyer does not want to say no directly. The rep has to diagnose which it is.
The response
"Completely understand. What is the cost of this problem continuing for another 90 days while things settle? I ask because the pain you described on our last call typically compounds — it rarely pauses while the timing improves."
Follow-up
"When would be a good time? I want to put a date on the calendar now so we do not lose the thread."
"Call me back next quarter."
Why they say it
This is a delay tactic disguised as a calendar preference. The buyer is kicking the can. Without a specific reason tied to a genuine business event — a product launch, a new hire, a budget approval — this objection typically means the rep did not build sufficient urgency.
The response
"Absolutely — I want to be respectful of your timing. Can I ask: what changes next quarter that makes this a better time? That way I know what to prepare so the conversation is actually useful when we reconnect."
Follow-up
"If the answer is nothing specific, I would rather we figure out now whether this is the right fit — saves time on both sides."
"We are too busy right now to evaluate anything new."
Why they say it
Operational overload is real in B2B SaaS teams. But this objection often signals that the rep has framed the solution as an addition to the buyer's workload rather than a reduction of it. Position correctly and the objection disappears.
The response
"That is exactly why our customers tend to prioritize this — when a team is overloaded, the manual work this replaces is what is burning the most time. Our typical customer sees setup in under a week and net admin reduction from day one."
Follow-up
"What is the one workflow that is eating the most time right now? Let me show you what our customers did with that specifically."
"This is not a priority right now."
Why they say it
Priority objections are discovery failures dressed as timing objections. If the rep connected the solution to a business metric the buyer tracks — pipeline, revenue, churn, ramp time — this objection does not appear. It surfaces when the pain conversation was shallow.
The response
"Fair. Can I ask what is sitting above this on the priority stack right now? I want to understand whether this problem is actually lower priority or whether it feeds into something that is higher priority — because it often does."
Follow-up
"What would need to change for this to move up the list? And is there anything I can give you to take to that conversation?" For more on this specific objection, see the guide on why "not a priority right now" keeps killing deals.
Competitor objections — 4 responses that work
Competitor objections require the most discipline. The instinct is to attack the competitor directly — list their weaknesses, undercut their pricing, or dismiss the incumbent relationship. All three approaches backfire. Buyers who hear a rep badmouth a competitor immediately distrust the rep. The correct approach is curious, not combative.
The key insight on competitor objections: the buyer is not telling you they are happy with the competitor. They are telling you they have an existing relationship. Those are not the same thing. Most B2B software renewals happen out of inertia, not satisfaction. The rep's job is to surface the gap.
"We already use [competitor]."
Why they say it
The buyer has an existing vendor relationship. They may be satisfied, or they may be staying out of inertia. The rep does not know which until they ask.
The response
"Good to know — a lot of our customers came from [competitor]. Can I ask: what is working well for you, and what is the one thing you wish it did better? I am not here to sell against them — I just want to understand the landscape."
Follow-up
"When does your current contract renew? It might be worth a quick look at what has changed in this space since you made that call."
"We are locked into a contract until next year."
Why they say it
A contract is a real constraint. But "locked in" is often an overstatement — most enterprise contracts have exit clauses, and the cost of switching is frequently lower than the buyer believes. The buyer is also testing whether the rep will persist or fold.
The response
"That makes sense. Three things are worth noting: contracts often have flexibility that teams do not explore, the setup time for a switch is usually shorter than buyers expect, and starting the evaluation now means you are ready to move on day one of the new cycle — not three months in."
Follow-up
"When does the renewal decision window open? I want to make sure we are in the conversation early, not last."
"We tried something similar before and it did not work."
Why they say it
A prior failure creates a trust barrier. The buyer has been burned and is projecting that outcome onto the current conversation. This is a serious objection that requires surfacing what went wrong, not dismissing it.
The response
"Can I ask what failed? Was it the tool, the implementation, the adoption, or something about how the problem was scoped? I ask because the answer completely changes whether we are a fit — and I would rather know now."
Follow-up
"Most failed implementations we see come down to one of three things. Tell me which one hit you and I can show you specifically what we do differently."
"Your competitor offers this feature and you do not."
Why they say it
The buyer has done their research and identified a feature gap. This is a legitimate objection. It requires an honest answer, not deflection. Lying about the roadmap destroys trust faster than the gap does.
The response
"You are right — they have that and we do not currently. Let me ask: how often does that specific feature come into your workflow, and what does it change for you when it does? I want to understand whether this is a core use case or an edge case before we decide it is a dealbreaker."
Follow-up
"If that feature were not in the picture, is everything else there? That tells me whether this is a fit-or-no-fit conversation or a negotiable one."
Need objections — 4 responses that work
Need objections appear when the rep has not yet connected the solution to a problem the buyer already knows they have. The buyer is not saying "we do not have this problem." They are saying "I do not yet see why your product solves my problem." The response is always diagnostic — return to discovery and find the pain.
Need objections in the middle or late stages of a deal are red flags. They signal that either the rep skipped discovery, the wrong person is in the room, or the rep is selling a feature instead of a business outcome. Address the root cause, not the surface symptom. For more on running discovery correctly, see the discovery call framework.
"We are happy with how things are."
Why they say it
Status quo bias is the strongest force in B2B buying. The buyer is comparing the pain of change against the pain of the current problem — and right now, change feels riskier. The rep has not yet made the cost of inaction concrete enough.
The response
"That is good to hear — I respect that. Out of curiosity: if you could wave a wand and change one thing about how this workflow runs today, what would it be? Not a problem that needs solving urgently — just the one thing that would make your life easier."
Follow-up
"What does that problem cost you on a monthly basis — in time, in missed deals, or in team hours? Let me show you how we handle that specifically."
"We do not see the need for this."
Why they say it
The rep is speaking to the wrong person, or the pitch was product-first instead of problem-first. "We do not see the need" from a VP Sales usually means the rep never connected the solution to a pipeline or revenue metric the VP tracks.
The response
"Fair — I may have led with the wrong angle. Can I ask: what is the metric you are most focused on improving this quarter? I want to show you this through that lens, not through the lens of the product."
Follow-up
"If improving [their metric] by 15% were on the table in 60 days, would that change the conversation? Because that is specifically what [customer name in same industry] achieved."
"We do this manually and it works fine."
Why they say it
"Works fine" is the enemy of improvement in every organization. The buyer has normalized a workaround and does not realize the hours or revenue it is costing. This objection responds well to time-cost math — not product features.
The response
"How long does it take your team to do this manually each week? I want to put a number on what 'fine' costs — because in our experience, manual processes that work fine usually consume 8–15 hours of rep time per week that could be recovering pipeline instead."
Follow-up
"If you got that time back, what would your reps do with it — more calls, more pipeline, more follow-up? Because that is where the ROI actually lives."
"I do not see how this applies to our business."
Why they say it
The rep pitched horizontally — using generic language that does not map to this specific industry, stage, or team shape. The buyer cannot see themselves in the pitch. The fix is to narrow the framing immediately.
The response
"Let me try that differently. We have three customers who look exactly like you — [similar stage], [similar team size], [similar motion]. Here is what they were dealing with before and what changed in 90 days. Tell me if any of that maps to what you are seeing."
Follow-up
"Does any of that land? If not, I would rather know now and save us both time."
Authority and stakeholder objections — 4 responses that work
Authority objections tell the rep they are in the wrong conversation. The buyer in the room does not have the power to say yes. The correct response is to get in the right conversation — not to convince the wrong person to be the champion.
The classic mistake on authority objections is trying to arm the buyer with materials to sell internally, then waiting for them to come back. Buyers who cannot say yes almost never sell as effectively as a rep on a live call. Use the authority objection as a signal to multi-thread — get a meeting with the economic buyer directly, with the current contact as the bridge. For the full multi-threading playbook, see multi-threading in sales.
"I need to run this by my boss."
Why they say it
The buyer is not the economic buyer. This is a legitimate and common objection in B2B deals — purchase decisions at enterprise scale almost always require approval above the contact level. The rep's job is to get into that conversation, not to arm the contact and wait.
The response
"That makes sense — decisions at this level usually require sign-off. Can I ask: would it be easier if I put together a one-pager for that conversation, or would it be better to include your boss directly on the next call so we can cover their questions live? I want to make sure the right information gets to the right person."
Follow-up
"What are the two or three questions your boss will ask? Let me make sure I have the answers ready — or better yet, let us get them on a call together so nothing gets lost in translation."
"We have a committee that needs to approve this."
Why they say it
Enterprise buying committees are real. Gartner research shows the average B2B deal now involves 6 to 10 stakeholders. The rep who ignores the committee loses the deal to a rep who mapped it on day one.
The response
"I appreciate you flagging that — it actually helps a lot. Can you walk me through who is on the committee and what each person cares about most? I want to make sure every stakeholder has what they need, not just the people on this call."
Follow-up
"Would it help to run a short call with the full committee? I would rather answer their questions live than have them surfaced three weeks from now when the deal stalls."
"Send me more information and I will take a look."
Why they say it
"Send me information" is a polite exit from the conversation. PDFs do not answer questions, handle objections, or build urgency. They sit in inboxes. The rep who accepts this response is handing the decision to a document.
The response
"Happy to send something over — I want to make sure it is the right thing. What specifically would be most useful: a case study from a similar company, a one-page ROI breakdown, or a product overview? And when you look at it, who else will be in the room?"
Follow-up
"Let us put 20 minutes on the calendar for the week after — that way I can answer any questions that come up from the materials directly, rather than through email."
"Procurement has to be involved in any vendor decision."
Why they say it
Procurement involvement is a reality in mid-market and enterprise deals. It often signals a deal is serious — companies only run procurement processes on purchases they intend to make. Treat it as progress, not as an obstacle.
The response
"Completely understand — and that is actually a good sign that this is moving forward. Can you connect me with the procurement contact? The earlier I can get them standard documentation — security review, MSA, pricing structure — the faster we can move once business approval lands."
Follow-up
"What is the typical procurement timeline here? I want to make sure the business side and the procurement side move in parallel rather than sequentially."
Trust and credibility objections — 4 responses that work
Trust objections are the hardest category to respond to in the moment because they are personal — the buyer is questioning the rep's credibility, the company's staying power, or the product's ability to deliver on its claims. The only response that works is specific proof. Not assertions. Not testimonials quoted verbatim. Customer names, specific metrics, and an invitation to verify.
"I have never heard of your company."
Why they say it
Brand recognition objections reflect risk aversion, not a substantive product concern. The buyer is calculating the career risk of betting on an unknown vendor. The correct response removes the risk, not the anonymity.
The response
"Fair — we are not Salesforce. We are purpose-built for [specific use case] for companies exactly your size and stage. Here are three customers you can call right now — [name], [name], [name]. They were in your position 12 months ago. I would rather you hear it from them than from me."
Follow-up
"What would give you confidence here — a reference call, a pilot, or a shorter initial commitment? I want to remove the risk, not just the concern."
"How do I know this will actually work for us?"
Why they say it
The buyer is reasonable — they want proof before committing. This objection is an invitation to demonstrate, not to assert. Generic claims at this point actively damage trust.
The response
"That is the right question. Let me show you specifically: here is what [customer in same industry, similar stage] looked like before — [specific metric]. Here is what changed in 90 days — [specific outcome]. Can I connect you with them directly so you can ask exactly what you would ask me?"
Follow-up
"Would a limited pilot remove that uncertainty? We can scope one to your specific use case so you see results before any long-term commitment."
"What happens if your company goes under?"
Why they say it
Enterprise buyers are responsible for the tools their team depends on. Business continuity is a legitimate procurement concern, especially with newer vendors. This question is not hostile — it is due diligence.
The response
"That is a fair question to ask of any vendor. Here is what is relevant: our runway, our funding status, our data export policy so you always own your data, and our SLA terms. I can send you all of that in writing. What specifically concerns you most about continuity?"
Follow-up
"If we can satisfy the continuity question, is that the last concern on the table? I want to make sure we are not whack-a-mole-ing objections one at a time."
"Your reviews online are mixed."
Why they say it
The buyer has done their research and found negative reviews. Dismissing or disputing reviews backfires immediately. The correct approach is to acknowledge honestly, contextualize specifically, and redirect to a live reference.
The response
"Can I ask which reviews you saw? Some of the critical ones from 2023 reflect a period when we had onboarding gaps — we changed that process in Q2 2024 and the scores have moved materially since. I want to show you a current customer in your segment so you can see what the experience actually looks like now."
Follow-up
"Reviews are a start — but a 15-minute reference call from a customer in your specific situation is worth a hundred G2 ratings. I can get you three names today."
The Objection Pattern Loop — how top reps turn call recordings into prepared responses
Every rep in this guide has read the 25 responses above. The reps who actually use them in the right moment — on a live call, under pressure, when a buyer says something unexpected — are the ones who have practiced. And the reps who practice most effectively are the ones who review their own call recordings to see which objections actually appeared, in which order, and what they said in response.
This is the Objection Pattern Loop: record every call, detect which objections appeared, surface the pattern across the team's calls, coach reps on responses before the next call, and measure whether win rate improves. Reps who run this loop close at 2.3× the rate of reps who handle each objection from memory with no pattern data behind them (Gangly customer data, Q1 2026).
The value of the loop is not in the analysis — it is in the preparation. A rep who walks into a call knowing that 80% of discovery calls with Series B fintech companies surface a competitor objection by minute 14 is a fundamentally different rep than one who encounters it cold. They are ready. The response is already loaded. They do not need to think.
Gangly's call recording and conversation intelligence layer does three things in this loop. First, it flags every objection in the call transcript by category — price, timing, competitor, need, authority, trust — so the rep and manager can see the objection pattern across all calls, not just the ones they remember. Second, it surfaces the response the top-performing reps used in the same scenario so the rest of the team can learn from it. Third, it builds a call prep brief before each call that includes the objections most likely to appear based on the account type, deal stage, and prior conversation history.
The result is a rep who walks into a discovery call knowing that this type of account surfaces a budget objection 60% of the time at minute 12, a competitor objection 40% of the time before the demo, and a timing objection 30% of the time after pricing. That preparation does not eliminate the objection — it makes the rep impossible to surprise by it. See how this connects to the sales call prep workflow and how to win more sales calls.
35–40%
Of B2B sales objections are price-related — the most common single category
Gong Labs · 2025 · 100,000+ calls
2.3×
More likely to close when reps prepare for known objections using call pattern data
Gangly customer data · Q1 2026
3 avg
Objections per call for top-performing B2B reps — they field more, not fewer
Gong Labs · State of Sales 2025
Get the full playbook
See Gangly's objection pattern reports in action
Gangly records every call, detects objections by category, and builds your prep brief before the next one. 14-day free trial. No credit card.