Objection Library
Common B2B SaaS objections with response frameworks. Organized by category for quick reference.
Quick-Reference Table
For live calls. Find the objection, scan the response, reference the proof.
| Objection | Response (1-line) | Proof Point |
|---|
| "Too expensive" | "Compared to what? Let's look at what the problem costs you today." | ROI case study showing payback in X months |
| "No budget" | "When budget opens up, what would need to be true for this to be a priority?" | Customer who started with a pilot to prove value |
| "Competitor is cheaper" | "They are — here's what you give up at that price point." | Feature comparison + customer who switched |
| "Not the right time" | "What changes next quarter that makes it better timing?" | Cost-of-delay calculation |
| "Maybe next quarter" | "Happy to reconnect. What would a pilot look like before then?" | Customer who started small and expanded |
| "We use X already" | "How's that working for [specific pain area]?" | Customer who switched from X |
| "What makes you different?" | "For teams like yours, the biggest difference is [specific differentiator]." | Side-by-side comparison for their use case |
| "Need to check with my boss" | "Absolutely. What would help you make the case? I can send materials." | Champion one-pager, ROI calculator |
| "The committee decides" | "Who's on the committee and what does each person care about?" | Multi-persona case study |
| "What we have works fine" | "It does work — the question is whether it's costing you more than it should." | Benchmark data showing efficiency gaps |
| "Not broken, don't fix it" | "Agreed — this isn't about fixing, it's about the opportunity cost of the current approach." | Customer who didn't know what they were missing |
| "Does it integrate with X?" | "Yes / Let me check and get you specifics by end of day." | Integration documentation, customer using same stack |
| "Security concerns" | "Completely fair. Here's our security overview — happy to loop in our team." | SOC 2 report, security whitepaper |
| "Can it scale?" | "We serve companies from [small] to [large]. Here's an example at your scale." | Case study at similar scale |
| "We tried something like this before" | "What went wrong? Understanding that helps me show how we're different." | Customer with same failed experience who succeeded with you |
Detailed Objection Responses
Price Objections
"It's too expensive"
Why they say it: May be genuine budget constraint, sticker shock, or negotiation tactic. Often means they don't yet see enough value to justify the cost.
Response approach:
- Don't defend the price immediately. Ask "Compared to what?"
- Reframe from cost to investment — what does the problem cost them today?
- Walk through the ROI calculation together
- If budget is real, explore smaller starting points
Talk track:
"I hear that. Let me ask — what's the cost of the problem we discussed? You mentioned your team spends [X hours] on [task] every week. At your team's loaded cost, that's roughly [$ amount] per year. Our solution runs [$ price] — so the question is whether eliminating that problem is worth the investment."
Proof point: ROI calculator or case study showing payback period.
Follow-up question: "If the ROI was clear, is this something you'd prioritize this quarter?"
"We don't have budget for this"
Why they say it: Budget may genuinely be allocated. Or they haven't identified budget because priority isn't established.
Response approach:
- Validate — budget constraints are real
- Understand timing — when does budget cycle reset?
- Explore alternatives — pilot, smaller scope, different budget line
- Help them build the business case to create budget
Talk track:
"Totally understand. Two questions: When does your next budget cycle open? And — if we could show clear ROI with a limited pilot, is that something you could fund from a different line item? Sometimes teams fund this from the efficiency savings it creates."
Proof point: Customer who started with a small pilot and expanded after proving ROI.
Follow-up question: "Would it help if I put together an ROI brief you could share with your finance team?"
"Competitor X is cheaper"
Why they say it: They're comparing prices, possibly without comparing capabilities. May be using competitor price as leverage.
Response approach:
- Acknowledge the price difference — don't pretend it doesn't exist
- Shift to total cost of ownership and value delivered
- Highlight what they lose at the lower price point
- Share proof from customers who evaluated both
Talk track:
"You're right, [Competitor] is less expensive. Here's what I've seen from teams who evaluated both: [Competitor] works well for [their strength]. Where it falls short is [specific gap]. Customers like [name] actually switched to us after starting with [Competitor] because [specific reason]. The question is whether [specific capability] is worth the difference for your team."
Proof point: Customer who switched from the competitor, with specific reasons.
Follow-up question: "What's most important to your team — the lowest price or the best fit for [their specific need]?"
Timing Objections
"Not the right time"
Why they say it: Competing priorities, organizational change, genuine capacity constraint, or lack of urgency.
Response approach:
- Understand what's competing for their attention
- Quantify the cost of waiting
- Explore low-commitment next steps that keep momentum
- Set a concrete follow-up date
Talk track:
"I get it — timing matters. Can I ask what's taking priority right now? The reason I bring up timing is that every month of [problem], based on our earlier conversation, costs your team roughly [$ amount]. A 3-month delay is [$ amount]. What if we mapped out a start date that works with your calendar so you're not losing that value?"
Proof point: Cost-of-delay calculation based on their specific numbers.
Follow-up question: "What would need to change for this to move up in priority?"
"Maybe next quarter"
Why they say it: Genuine scheduling, or a polite way of saying "not interested enough right now."
Response approach:
- Accept the timeline gracefully
- Propose a small action now that maintains momentum
- Get a specific date for follow-up
- Send value in the meantime (content, benchmarks, insights)
Talk track:
"Next quarter works. To make sure we hit the ground running, would it make sense to do [small next step] now? That way when Q[X] starts, you're not starting from scratch. I'll also send over [relevant content] in the meantime. Can we lock in [specific date] to reconnect?"
Proof point: Customer who started the evaluation process early and was live by their target date.
Follow-up question: "Is there anything I can send between now and then that would be helpful?"
Competition Objections
"We already use X"
Why they say it: They have an existing solution and switching has real costs. May be satisfied, or may have frustrations they haven't voiced.
Response approach:
- Don't trash the competitor — ask how it's working
- Probe for specific pain points with their current solution
- Position as complementary if possible, replacement if not
- Offer a side-by-side comparison or trial
Talk track:
"How's that working for you? Specifically, when it comes to [area where you're stronger] — is that meeting your needs? The reason I ask is that most teams who come to us from [Competitor] tell us [specific pain point] was the tipping point. Not saying that's you, but worth exploring."
Proof point: Customer who switched from that specific competitor.
Follow-up question: "If you could change one thing about your current setup, what would it be?"
"What makes you different?"
Why they say it: They're evaluating options and want a clear differentiator. Sometimes a genuine question, sometimes a test.
Response approach:
- Don't list features — give the one thing that matters most for their situation
- Tie the differentiator to their specific pain
- Back it up with proof
- Offer to show, not just tell
Talk track:
"For teams like yours — [their industry/size/use case] — the biggest difference is [specific differentiator]. That matters because [connection to their pain]. For example, [Customer] was evaluating us alongside [Competitor] and chose us because [specific reason]. Want me to walk you through how that works?"
Proof point: Case study of a customer who chose you over alternatives.
Follow-up question: "What's the most important criteria for your decision?"
Authority Objections
"I need to check with my boss"
Why they say it: They may not be the decision maker, or they need internal buy-in to proceed. Could also be a stall tactic.
Response approach:
- Support them, don't pressure them
- Arm them with materials to sell internally
- Offer to join a meeting with their boss
- Understand what their boss cares about
Talk track:
"Absolutely — what would help you make the case? I can put together a one-pager that covers the ROI and addresses the concerns your boss is likely to have. Also happy to jump on a quick call with them if that would be helpful. What does your boss typically prioritize — cost savings, risk reduction, or efficiency?"
Proof point: Champion enablement one-pager, ROI calculator.
Follow-up question: "What questions do you think your boss will ask?"
"A committee decides this"
Why they say it: Enterprise buying involves multiple stakeholders. Genuine process, not a brush-off.
Response approach:
- Map the buying committee — who's involved and what each person cares about
- Provide persona-specific materials
- Offer to present to the committee
- Help your champion navigate the internal process
Talk track:
"That makes sense. Can you walk me through who's on the committee and what each person cares about? I can tailor materials for each stakeholder so you're not doing all the heavy lifting. I've also got a deck designed for executive presentations if that would be useful."
Proof point: Multi-stakeholder case study showing how different personas were addressed.
Follow-up question: "Who on the committee is most likely to push back, and what would their concern be?"
Status Quo Objections
"What we have works fine"
Why they say it: Inertia is real. The current solution may be adequate, and change has real costs.
Response approach:
- Agree — don't argue with their experience
- Shift from "broken vs. fixed" to "good vs. great"
- Introduce the concept of opportunity cost
- Show what peers are achieving
Talk track:
"It probably does work — and I wouldn't suggest changing something that's truly meeting your needs. The question I'd ask is: is 'works fine' the bar? Teams using [your product] are seeing [specific outcome]. If you're leaving [X% improvement] on the table, is that worth exploring?"
Proof point: Benchmark data showing what's possible vs. status quo.
Follow-up question: "If there were one area where your current approach could be better, what would it be?"
Technical Objections
"Does it integrate with X?"
Why they say it: Integration is a real requirement. They need to know your product fits their stack.
Response approach:
- Answer directly — yes, no, or "let me check"
- If yes, provide specifics (native, API, Zapier, etc.)
- If no, explain alternatives or workarounds
- Never bluff — they'll find out during evaluation
Talk track (if yes):
"Yes, we integrate with [X] natively. It takes about [time] to set up. [Customer] runs the same stack and here's how they have it configured."
Talk track (if no):
"We don't have a native integration with [X] today. Here's what customers typically do: [alternative]. We also have an open API that [description]. Would it help to get our technical team on a call to explore options?"
Proof point: Customer using the same tech stack, integration documentation.
Follow-up question: "What other tools are in your stack that we'd need to work with?"
"We have security concerns"
Why they say it: Legitimate concern, especially in regulated industries or enterprise. Non-negotiable for many buyers.
Response approach:
- Take it seriously — never dismiss security concerns
- Provide documentation proactively (SOC 2, security whitepaper)
- Offer to loop in your security team
- Ask about their specific requirements
Talk track:
"That's exactly the right question to ask. Here's our security overview — we're [SOC 2 Type II / ISO 27001 / etc.] certified, and I can share our full security documentation. We also have a security team that's happy to do a review call with your infosec team. What are your specific requirements?"
Proof point: Security certifications, compliance documentation, customers in regulated industries.
Follow-up question: "Do you have a security questionnaire you'd like us to fill out?"
Claude
ChatGPT
Gemini
OpenClaw