1# Objection Library
2 
3Common B2B SaaS objections with response frameworks. Organized by category for quick reference.
4 
5## Quick-Reference Table
6 
7For live calls. Find the objection, scan the response, reference the proof.
8 
9| Objection | Response (1-line) | Proof Point |
10|-----------|--------------------|-------------|
11| "Too expensive" | "Compared to what? Let's look at what the problem costs you today." | ROI case study showing payback in X months |
12| "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 |
13| "Competitor is cheaper" | "They are — here's what you give up at that price point." | Feature comparison + customer who switched |
14| "Not the right time" | "What changes next quarter that makes it better timing?" | Cost-of-delay calculation |
15| "Maybe next quarter" | "Happy to reconnect. What would a pilot look like before then?" | Customer who started small and expanded |
16| "We use X already" | "How's that working for [specific pain area]?" | Customer who switched from X |
17| "What makes you different?" | "For teams like yours, the biggest difference is [specific differentiator]." | Side-by-side comparison for their use case |
18| "Need to check with my boss" | "Absolutely. What would help you make the case? I can send materials." | Champion one-pager, ROI calculator |
19| "The committee decides" | "Who's on the committee and what does each person care about?" | Multi-persona case study |
20| "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 |
21| "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 |
22| "Does it integrate with X?" | "Yes / Let me check and get you specifics by end of day." | Integration documentation, customer using same stack |
23| "Security concerns" | "Completely fair. Here's our security overview — happy to loop in our team." | SOC 2 report, security whitepaper |
24| "Can it scale?" | "We serve companies from [small] to [large]. Here's an example at your scale." | Case study at similar scale |
25| "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 |
26 
27---
28 
29## Detailed Objection Responses
30 
31### Price Objections
32 
33#### "It's too expensive"
34 
35**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.
36 
37**Response approach:**
381. Don't defend the price immediately. Ask "Compared to what?"
392. Reframe from cost to investment — what does the problem cost them today?
403. Walk through the ROI calculation together
414. If budget is real, explore smaller starting points
42 
43**Talk track:**
44> "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."
45 
46**Proof point:** ROI calculator or case study showing payback period.
47 
48**Follow-up question:** "If the ROI was clear, is this something you'd prioritize this quarter?"
49 
50---
51 
52#### "We don't have budget for this"
53 
54**Why they say it:** Budget may genuinely be allocated. Or they haven't identified budget because priority isn't established.
55 
56**Response approach:**
571. Validate — budget constraints are real
582. Understand timing — when does budget cycle reset?
593. Explore alternatives — pilot, smaller scope, different budget line
604. Help them build the business case to create budget
61 
62**Talk track:**
63> "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."
64 
65**Proof point:** Customer who started with a small pilot and expanded after proving ROI.
66 
67**Follow-up question:** "Would it help if I put together an ROI brief you could share with your finance team?"
68 
69---
70 
71#### "Competitor X is cheaper"
72 
73**Why they say it:** They're comparing prices, possibly without comparing capabilities. May be using competitor price as leverage.
74 
75**Response approach:**
761. Acknowledge the price difference — don't pretend it doesn't exist
772. Shift to total cost of ownership and value delivered
783. Highlight what they lose at the lower price point
794. Share proof from customers who evaluated both
80 
81**Talk track:**
82> "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."
83 
84**Proof point:** Customer who switched from the competitor, with specific reasons.
85 
86**Follow-up question:** "What's most important to your team — the lowest price or the best fit for [their specific need]?"
87 
88---
89 
90### Timing Objections
91 
92#### "Not the right time"
93 
94**Why they say it:** Competing priorities, organizational change, genuine capacity constraint, or lack of urgency.
95 
96**Response approach:**
971. Understand what's competing for their attention
982. Quantify the cost of waiting
993. Explore low-commitment next steps that keep momentum
1004. Set a concrete follow-up date
101 
102**Talk track:**
103> "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?"
104 
105**Proof point:** Cost-of-delay calculation based on their specific numbers.
106 
107**Follow-up question:** "What would need to change for this to move up in priority?"
108 
109---
110 
111#### "Maybe next quarter"
112 
113**Why they say it:** Genuine scheduling, or a polite way of saying "not interested enough right now."
114 
115**Response approach:**
1161. Accept the timeline gracefully
1172. Propose a small action now that maintains momentum
1183. Get a specific date for follow-up
1194. Send value in the meantime (content, benchmarks, insights)
120 
121**Talk track:**
122> "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?"
123 
124**Proof point:** Customer who started the evaluation process early and was live by their target date.
125 
126**Follow-up question:** "Is there anything I can send between now and then that would be helpful?"
127 
128---
129 
130### Competition Objections
131 
132#### "We already use X"
133 
134**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.
135 
136**Response approach:**
1371. Don't trash the competitor — ask how it's working
1382. Probe for specific pain points with their current solution
1393. Position as complementary if possible, replacement if not
1404. Offer a side-by-side comparison or trial
141 
142**Talk track:**
143> "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."
144 
145**Proof point:** Customer who switched from that specific competitor.
146 
147**Follow-up question:** "If you could change one thing about your current setup, what would it be?"
148 
149---
150 
151#### "What makes you different?"
152 
153**Why they say it:** They're evaluating options and want a clear differentiator. Sometimes a genuine question, sometimes a test.
154 
155**Response approach:**
1561. Don't list features — give the one thing that matters most for their situation
1572. Tie the differentiator to their specific pain
1583. Back it up with proof
1594. Offer to show, not just tell
160 
161**Talk track:**
162> "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?"
163 
164**Proof point:** Case study of a customer who chose you over alternatives.
165 
166**Follow-up question:** "What's the most important criteria for your decision?"
167 
168---
169 
170### Authority Objections
171 
172#### "I need to check with my boss"
173 
174**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.
175 
176**Response approach:**
1771. Support them, don't pressure them
1782. Arm them with materials to sell internally
1793. Offer to join a meeting with their boss
1804. Understand what their boss cares about
181 
182**Talk track:**
183> "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?"
184 
185**Proof point:** Champion enablement one-pager, ROI calculator.
186 
187**Follow-up question:** "What questions do you think your boss will ask?"
188 
189---
190 
191#### "A committee decides this"
192 
193**Why they say it:** Enterprise buying involves multiple stakeholders. Genuine process, not a brush-off.
194 
195**Response approach:**
1961. Map the buying committee — who's involved and what each person cares about
1972. Provide persona-specific materials
1983. Offer to present to the committee
1994. Help your champion navigate the internal process
200 
201**Talk track:**
202> "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."
203 
204**Proof point:** Multi-stakeholder case study showing how different personas were addressed.
205 
206**Follow-up question:** "Who on the committee is most likely to push back, and what would their concern be?"
207 
208---
209 
210### Status Quo Objections
211 
212#### "What we have works fine"
213 
214**Why they say it:** Inertia is real. The current solution may be adequate, and change has real costs.
215 
216**Response approach:**
2171. Agree — don't argue with their experience
2182. Shift from "broken vs. fixed" to "good vs. great"
2193. Introduce the concept of opportunity cost
2204. Show what peers are achieving
221 
222**Talk track:**
223> "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?"
224 
225**Proof point:** Benchmark data showing what's possible vs. status quo.
226 
227**Follow-up question:** "If there were one area where your current approach could be better, what would it be?"
228 
229---
230 
231### Technical Objections
232 
233#### "Does it integrate with X?"
234 
235**Why they say it:** Integration is a real requirement. They need to know your product fits their stack.
236 
237**Response approach:**
2381. Answer directly — yes, no, or "let me check"
2392. If yes, provide specifics (native, API, Zapier, etc.)
2403. If no, explain alternatives or workarounds
2414. Never bluff — they'll find out during evaluation
242 
243**Talk track (if yes):**
244> "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."
245 
246**Talk track (if no):**
247> "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?"
248 
249**Proof point:** Customer using the same tech stack, integration documentation.
250 
251**Follow-up question:** "What other tools are in your stack that we'd need to work with?"
252 
253---
254 
255#### "We have security concerns"
256 
257**Why they say it:** Legitimate concern, especially in regulated industries or enterprise. Non-negotiable for many buyers.
258 
259**Response approach:**
2601. Take it seriously — never dismiss security concerns
2612. Provide documentation proactively (SOC 2, security whitepaper)
2623. Offer to loop in your security team
2634. Ask about their specific requirements
264 
265**Talk track:**
266> "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?"
267 
268**Proof point:** Security certifications, compliance documentation, customers in regulated industries.
269 
270**Follow-up question:** "Do you have a security questionnaire you'd like us to fill out?"
271