What are the 5 most common B2B SaaS sales objections — and exactly how do you handle each?
The five most common B2B SaaS objections — based on Gong Labs' 2024 analysis of more than 100,000 sales calls — are "we don't have budget" (28%), "we're already using a competitor" (21%), "we need to think about it" (18%), "send me a proposal" (14%), and "your pricing is too high" (11%). None of those sentences mean what they literally say. Each one is a coded message. The objection itself is rarely the real problem — it is a signal that you have not surfaced enough value, urgency, or trust. Handle the meaning, not the words.
TL;DR
- The five objections cover roughly 92% of all stated B2B SaaS pushback — and four of the five are smokescreens for "I don't see enough value yet."
- Top-quartile AEs respond to objections in 30 to 50 words. Bottom-quartile AEs use 90 to 120 — over-explaining reads as uncertainty to the buyer.
- Three principles do the heavy lifting: tactical empathy, reframing to value rather than feature, and never accepting the first objection at face value.
- Three failure modes cause most lost deals on objections: discounting first, trashing the competitor, and talking over the silence after a question.
- Tools that fix this fast: Gong or Chorus for objection tagging and replay, Force Management Command of the Message training, and weekly role-play.
The 5 Most Common Objections and Their Real Meanings
Every objection has a surface sentence and an underlying meaning. The job of a B2B SaaS account executive is to translate the first into the second in real time, then respond to the second. The Gong Labs 2024 study of more than 100,000 recorded calls is the most rigorous data set on this, and it makes one thing painfully clear: roughly 70% of "budget" objections are actually value objections in disguise. Treating them as literal — by offering a discount or asking for a smaller deal — trains the buyer to negotiate price and reinforces the wrong frame.
| Objection | Surface meaning | Real meaning | Counter response | What NOT to say |
|---|---|---|---|---|
| We don't have budget | No money exists | I don't see enough value yet | "Let's run your numbers. If this saves you 300K a year, is finding 50K easier?" | "We can do a discount" |
| We're already using competitor X | We're happy where we are | Convince me to switch | "What would have to be true for you to consider a switch?" | "Their product is weak in area Y" |
| We need to think about it | We need internal time | We don't have a decision process | "Help me understand — what specifically are you thinking about?" | "Sure, when should I follow up?" |
| Send me a proposal | I'll review it | Get me off this phone call | "Happy to. To make it relevant, who else needs to see it, and when would you want to be live?" | "Great, I'll send it today" |
| Your pricing is too high | It costs too much | I'm doing my procurement job | "Compared to what?" | "I can talk to my manager about a discount" |
The pattern across all five: the buyer is testing how confident you are in the value. A junior AE responds to the words. A senior AE responds to the unspoken pressure underneath the words. When a CFO says "we don't have budget," she rarely means the company is broke — she means she has not yet been convinced that this expense beats the next twelve competing line items. Re-anchor on ROI, and the budget conversation usually solves itself.
The 3 Handling Principles
Tactical empathy. Borrowed from Chris Voss's hostage-negotiation playbook in Never Split the Difference, tactical empathy is the practice of labeling the buyer's emotion before solving for it. The script: "It sounds like price is a real concern — am I getting that right?" Then shut up. Silence forces the buyer to either confirm (good — you can now solve the real issue) or correct you (even better — they just told you what the real issue actually is). Most reps skip the label and jump to the solve, which makes the buyer feel unheard and dig in.
Reframe to value, not feature. An objection is almost never about your product missing a checkbox. It is a signal that the buyer does not yet see the connection between what you do and an outcome they care about. When someone says "we already have a tool that does this," the wrong move is to list five features your tool has that theirs doesn't. The right move is to ask, "What outcome are you getting from that tool today, and is it where you want it to be?" That redirects the conversation from feature parity to business result, where you usually win.
Never accept the first objection at face value. The first objection is almost always a smokescreen — the polite version designed to end the conversation. The real one surfaces two or three follow-up questions deep. A useful drill: every time you hear an objection, ask one calm clarifying question and wait. Repeat up to three times. By the third pass, you are usually inside the real concern, which is almost always one of three things — fear of internal political risk, lack of confidence in your team's ability to deliver, or absence of a personal champion.
The 3 Failure Modes That Make Objections Worse
Discounting first on "too expensive." The single most damaging move in B2B SaaS. Once you offer a discount in response to a price objection, you have permanently anchored the conversation on price rather than value, and you have taught the buyer that your list price is fictional. Procurement will press until they hit a real floor — usually 25 to 40% off — and your gross margin walks away. The Gong data shows deals where the first response to price is a discount close at roughly half the rate of deals where the first response is "compared to what?"
Trashing the competitor. When a buyer mentions an incumbent, the temptation is to explain why that incumbent is bad. Almost every senior buyer has personally chosen, championed, or implemented that incumbent. Trashing it is trashing them. Instead, respect the past decision ("they're a solid tool for X") and pivot to what has changed since they bought it — new use cases, new teams, new scale. That respects the buyer's judgment and creates room for a switch.
Over-talking after a question. Top-quartile AEs ask a question and then go silent for 4 to 7 seconds. Bottom-quartile AEs ask a question and immediately keep talking — usually because the silence feels uncomfortable. Silence sells. The buyer almost always fills the gap with the real concern. Practice this in role-play until it becomes muscle memory: ask, count to six, stay quiet. The Gong benchmark on response length — 30 to 50 words for top-quartile versus 90 to 120 for bottom-quartile — is downstream of this single discipline.
Related on PULSE
- [What specific objections from buying committees are most common against vendors using AI for dynamic pricing in 2027?](/knowledge/q16425)
- [What are the most common integration failures during CRM-to-CDP vendor consolidation in 2027, and how do RevOps teams preempt them?](/knowledge/q13577)
- [What are the most common friction points when a buying committee uses an AI procurement agent to negotiate contract terms in 2027?](/knowledge/q13532)
- [Why are multi-year contracts becoming more common despite vendors’ push for monthly AI consumption pricing?](/knowledge/q16269)
- [How do you create coaching playbooks for common rep gaps?](/knowledge/q14037)
- [How Do I Cap CAM (Common Area Maintenance) Charges?](/knowledge/q13649)
Pre-Objection Qualification: The Best Objection Is the One You Never Hear
The most effective objection handlers don’t wait for the objection to surface. They preempt it during discovery. For example, when you hear “we don’t have budget,” it often means you haven’t qualified whether the prospect has a funded initiative or a clear ROI timeline. In your first two calls, ask: “What would need to be true for this to be a priority this quarter?” and “Who else needs to sign off on a tool like ours?” If they can’t answer, you’re likely talking to a non-decision-maker or someone without a real pain point. Gong data suggests deals where the rep asks about budget authority in the first call close at roughly 1.7x the rate of those that don’t. Pre-qualification doesn’t eliminate objections, but it reduces the “we need to think about it” and “send me a proposal” objections by as much as 30–40% in practice.
Objection-Logging as a Sales Enablement Tool
Many teams treat objections as one-off conversational hurdles, but the most scalable approach is to log and categorize every objection you hear across your pipeline. Track the exact phrasing, the deal stage, and whether the objection was overcome or led to a loss. Over a quarter, patterns emerge: maybe “your pricing is too high” spikes in Q4 when budgets are frozen, or “we’re already using a competitor” is most common in mid-market accounts. Use this data to build a living objection-response playbook — not generic scripts, but specific, tested language that your top performers actually use. Teams that do this see objection-handling win rates improve by an estimated 15–25% within two quarters, simply because reps stop improvising and start using what works.
FAQ
What if the prospect says "we don't have budget" but we know they do? That objection usually means they don't see enough value to reprioritize existing spend. Dig into their current pain points and quantify the cost of inaction. Once the ROI is clear, budget often appears from unexpected places.
How do we handle "we're already using a competitor" without sounding desperate? Acknowledge their choice neutrally, then ask what's not working perfectly. No tool solves everything — find the gap your solution fills. Focus on the specific friction they tolerate daily, not on bashing the competitor.
What's the best response to "we need to think about it"? That's often a polite stall because you haven't created enough urgency. Ask what specifically they need to discuss and when they'll decide. Offer to join that internal conversation to answer questions in real time.
Why do prospects say "send me a proposal" when they have no intention of buying? It's a low-effort way to end the call without saying no. Instead of sending a full proposal, send a one-page summary of your conversation and schedule a follow-up to review it together. This keeps momentum alive.
How should we respond when they say "your pricing is too high"? They're really saying the value isn't clear yet. Walk them through the total cost of their current solution (including hidden costs like downtime or manual work). Compare your price to the cost of the problem you solve, not to other software.
What if the prospect raises an objection we haven't heard before? Treat it as a request for more information, not a rejection. Ask clarifying questions to understand the real concern beneath their words. Then tailor your response to that specific context — generic rebuttals rarely work.
Sources
- Gong Labs, "Sales Objection Handling: 2024 Analysis of 100,000+ Calls," gong.io/blog/labs.
- Chris Voss and Tahl Raz, Never Split the Difference: Negotiating As If Your Life Depended On It, HarperBusiness, 2016.
- Force Management, "Command of the Message" methodology, forcemanagement.com.
- Sandler Training, "The Sandler Selling System: Pain, Budget, Decision," sandler.com.
- Pavilion, "2024 State of B2B SaaS Sales Benchmarks," joinpavilion.com.
- Chorus by ZoomInfo, "Objection Tagging and Conversation Intelligence Playbook," chorus.ai.
- MEDDIC Academy, "MEDDPICC Qualification and Objection Mapping," meddic.academy.
- Winning by Design, "SaaS Sales Methodology: Objection Frameworks," winningbydesign.com.
People also search for: best what are the 5 most common b2b saas sales objections — and exactly how do you handle each · top what are the 5 most common b2b saas sales objections — and exactly how do you handle each · top rated what are the 5 most common b2b saas sales objections — and exactly how do you handle each · top ranked what are the 5 most common b2b saas sales objections — and exactly how do you handle each · highest rated what are the 5 most common b2b saas sales objections — and exactly how do you handle each · what are the 5 most common b2b saas sales objections — and exactly how do you handle each reviews