Objection Handling

Objection Handling

When to activate

You are in a live discovery call, email thread, or async response where a prospect has voiced resistance. Use this skill to convert objections into qualification opportunities rather than conversation endings. Applies specifically to B2B SaaS/tech sales cycles where you've already passed initial gatekeeping.

When NOT to use

• During a first touchpoint or cold outreach (objections here usually mean "no context" — go back to pre-call qualification)
• For prospects who have explicitly unsubscribed or asked not to be contacted (honor the boundary)
• After a contract negotiation has stalled (escalate to deal team, not cold reframing)
• When objection is "we're switching vendors and have a signed contract" (prospect is unavailable for 12+ months)

Instructions

The ACI Framework: Acknowledge → Clarify → Indicate Next Step

All six objections follow this pattern:

1. Acknowledge (10 seconds) — Validate their statement without agreeing or disagreeing. This defuses defensive posture.
2. Clarify (30–60 seconds) — Ask a specific, open-ended question that reveals the real blocker beneath the surface objection.
3. Indicate Next Step (15 seconds) — Propose a concrete action tied to their answer, or leave a door open for future conversation.

The Six Objections & Response Frameworks

Objection 1: "Just send me some information"

What it really means: "I'm not convinced this conversation is worth my time right now."

Why people say it:

• They want you gone without being rude
• They have genuine interest but are context-switching
• They think information alone will auto-educate them

ACI Response Framework:

What to send (not what to send):

• ✅ DO: A 1-page PDF with one specific problem + your angle on it + one case study of similar company
• ✅ DO: A 3-minute Loom video addressing their exact stated problem
• ❌ DON'T: Your deck (14+ slides, generic positioning)
• ❌ DON'T: Your company overview video (no frame of reference for them yet)
• ❌ DON'T: Generic "here are our product features" content

When to persist (follow up) vs. concede:

• Persist if: They named a specific problem in the call, asked a technical question, or work in your ICP
• Concede if: They said "maybe someday," gave monosyllabic answers throughout, or asked for info on a tangent product line

Objection 2: "We already have a solution for that"

What it really means: "I don't see why your thing is better, or I'm protecting my current choice."

Why people say it:

• They may genuinely have a tool (and it's working fine)
• They're testing you to see if you'll attack their vendor
• They've been burned by vendor pitch battles before

ACI Response Framework:

How to research their current tool (before/during the call):

• Check their public tech stack (BuiltWith, G2, LinkedIn job posts)
• Ask in discovery: "What are you using today to solve [problem]?"
• Ask the real gap: "If you had to fix one thing about [tool], what would it be?"

Key principle: Never say "we're better than [tool]." Instead, say "we solve [specific use case] that [tool] wasn't built for."

When to persist vs. concede:

• Persist if: They describe a specific gap in their current setup, or they mention frustration with their vendor
• Concede if: They say "it works great for us," or your product and theirs don't actually overlap much

Objection 3: "This isn't a priority right now"

What it really means: "This is a nice-to-have, or there's something else more urgent."

Why people say it:

• They genuinely have a burning fire (migration, outage, funding round)
• Your problem is real but lower-ranked than 5 other initiatives
• They're waiting for approval from leadership before prioritizing

ACI Response Framework:

The real blocker (uncover it):

• Budget cycle? → "When does planning kick off for [next year]?"
• Competing project? → "When does [other project] wrap?"
• Waiting for headcount? → "When does hiring happen?"
• Regulatory/compliance? → "When does [audit/deadline] hit?"

Timeline language to use:

• "Worth reconnecting in [month], so you can bake it into the plan early" (vs. "let me check in later")
• "I'll send a 2-minute deck you can share with [stakeholder] — that way, when the convo happens, it's already on their radar"

When to persist vs. concede:

• Persist if: They give you a specific trigger date or stakeholder name
• Concede if: They say "2024 at the earliest" (too far out for a human sales follow-up cycle)

Objection 4: "No budget"

What it really means: "We didn't plan for this expense, or leadership hasn't approved discretionary spend."

Why people say it:

• Budget is actually locked (they're truthful)
• They don't see enough value to fight for the budget
• They're testing to see if you'll suddenly offer a discount

ACI Response Framework:

What NOT to do:

• ❌ Offer a discount ("we can do [lower number]")
• ❌ Suggest a "pilot" (code for "hoping they'll commit later")
• ❌ Say "ROI is so clear you'll find budget" (they've heard this before)

What to do:

• ✅ Get the next planning cycle date
• ✅ Ask if another person (CFO, founder, ops lead) should be in this conversation
• ✅ Send a "build it into the budget" template email in advance

When to persist vs. concede:

• Persist if: They give a specific planning cycle date (Q1 planning, January budget review, etc.)
• Concede if: They say "no budget" for the third time across different conversations (move to nurture, not active sequence)

Objection 5: "Not interested"

What it really means: "I don't see how this applies to me, or you haven't positioned it well yet."

Why people say it:

• They're busy and this doesn't feel relevant
• You led with features, not their problems
• They genuinely don't have the problem you solve

ACI Response Framework:

The key phrase: "Can I ask one thing before we wrap?" — This is permission to ask without it feeling like another pitch.

Follow-up question variations:

• "How are you handling [specific problem] today?"
• "What does [operational pain] actually cost you when it happens?"
• "If you could fix one thing about [their process], what would it be?"

What gets people talking:

• Specific, singular problem (not "how's your entire stack?")
• Framed as their problem, not your product fit
• Opens with "can I ask" rather than "let me tell you"

When to persist vs. concede:

• Persist if: They start answering your question — engagement signal
• Concede if: They say "not interested" a second time or give one-word answers to your clarifying question

Objection 6: "Bad timing"

What it really means: "You're calling at a chaos point, or I'm already committed elsewhere."

Why people say it:

• They literally just started a project / migration / fundraise
• They're ramping up / onboarding / in a crunch
• You called during their busiest quarter

ACI Response Framework:

Specific timeframes to offer (don't say "next quarter"):

• "End of [month]?"
• "Once [their obvious project] wraps?"
• "Mid-[month] — does that feel better?"
• "I'll check in [date] — does that land?"

Why this works: You're not disappearing; you're respecting their timeline and showing up at a better moment.

When to persist vs. concede:

• Persist if: They give you a specific date or project name ("after we go live")
• Concede if: They say "way too early" (6+ months out, or no timeline at all)

Decision Tree: Persist vs. Concede

Did they give you a specific trigger (date, event, stakeholder name)?
├─ YES → Persist (add to nurture, reconnect at date/event)
├─ NO → Did they engage with your clarifying question?
    ├─ YES (gave a real answer) → Persist (send relevant asset, schedule light follow-up)
    └─ NO (one-word answers, redirected) → Concede (move to lower-touch nurture)

Concession language (respectful exit):

• "Sounds like now's not the right moment — totally understand. I'll stay on your radar, and if it becomes relevant, just reach out. Fair?"
• "I get it. Want to stay connected on LinkedIn so you can loop me in when it makes sense?"

Email vs. Call Response Differences

On a Live Call:

• ACI is real-time: acknowledge (5s) → clarify (ask and listen, 30s) → indicate (10s)
• You can read tone and adjust on the fly
• Silence after your clarifying question is OK — let them think
• If they go quiet, you ask again: "What would you say?"

In Email:

• Acknowledge in subject or first line
• Clarify with one specific question (not multiple)
• Indicate with a proposed action
• Keep to 4–6 sentences
• Include a specific call-to-action: "Reply with what would help" or "Let me know if [specific date] works"

Example Email Response to "Send info":

Subject: One specific thing to check on

Got it — I can definitely send something over.

Before I do, I want to make sure it's actually useful. When we talked, you mentioned [specific problem]. Is that the area you'd want me to focus on, or is it more about [alternative problem]?

Once I know, I'll send a one-pager specific to your situation instead of the generic deck.

Thoughts?

[Your name]

Role-Play Format Example

Setup: SaaS vendor (you) calling a VP of Ops (prospect) who said "We already have a solution for that" in initial discovery.

YOU: "So you're using [tool name] today — how long have you been on it?"

PROSPECT: "About two years. Works pretty well for us."

YOU: "Got it. Most teams we work with had [tool name] as their starting point too. Usually where they hit friction was [specific operational gap — e.g., 'needing to pull data from five different places to get one single report']. Is that something you're dealing with, even if [tool name] handles most of it?"

PROSPECT: "Actually, yeah — we spend way too much time manually syncing data between [tool name] and our data warehouse."

YOU: "There it is. That's the exact problem we solve. How much time per week is that burning for you?"

PROSPECT: "Maybe 8–10 hours a week across the team."

YOU: "That's significant. If you could automate that, what would your team do with the time?"

PROSPECT: "Honestly, we could focus on strategy instead of data plumbing."

YOU (Indicate Next Step): "Makes sense. Here's what makes sense: I'll send you a two-minute video of how another ops team set this up — different industry, but same manual-sync problem. If it resonates, we can do a 20-minute technical call with our ops lead. Does that work?"

PROSPECT: "Sure, send it over."

Key moves in this role-play:

1. You didn't attack their current vendor ✅
2. You named a specific operational gap, not a vague feature ✅
3. You asked about impact (time, cost, distraction) ✅
4. You moved them toward a next step, not another pitch ✅

Real Benchmarks

If 30%+ of your calls hit the same objection, that's a signal to shift your positioning earlier in the call (pre-emptively address it in your discovery questions).

If a prospect says the objection twice in the same conversation, assume concession — thank them, exit gracefully, add to nurture.

Persistence ROI: Prospects who give you a specific date/trigger and get a thoughtful follow-up have a 3–5x higher close rate than those you ask to "think about it" with no timeline.

Example

Real Scenario: Finance SaaS → Controller at Mid-Market E-commerce

Company: ZoomFinance (cash flow forecasting tool)
Prospect: Controller, $50M e-commerce company
Call stage: 20-minute discovery, first conversation

PROSPECT (at 12 min mark): "Look, this is interesting, but we already use Netsuite. Our accountant set it up, and it's handling our forecasting."

YOU (Acknowledge → Clarify → Indicate):

ACKNOWLEDGE: "Makes sense — Netsuite's a solid platform. How long have you been on it?"

PROSPECT: "About three years."

YOU (Clarify): "So here's what I see with a lot of finance teams on Netsuite — the forecasting module works great if you have a stable product line. But for e-commerce, where you're running multiple SKUs, promos, and seasonality... they usually end up doing the forecast in spreadsheets anyway because Netsuite doesn't handle variance. Is that what's happening for you?"

PROSPECT: "Actually, yes — we run three brands with different seasonal patterns. Netsuite can't model that, so we're pulling data and building forecasts in Excel. Takes forever."

YOU (Indicate): "There it is. That's exactly where we sit in — we take your Netsuite data and add the scenario modeling Netsuite doesn't do natively. Here's what I'd suggest: I'll send you a 3-minute walkthrough of how another e-commerce company set this up — they're similar scale, also three brands. If that resonates, we do a 20-minute call with our product lead to talk implementation. Fair?"

PROSPECT: "Yeah, send that over. What's your timeline for getting that to me?"

YOU: "Today — should be in your inbox in the next 30 minutes. And I'll send a Slack message Friday with a couple of time slots for next week. Cool?"

PROSPECT: "Works."

What happened:

• You didn't argue about Netsuite ✓
• You named their specific problem (seasonal SKU forecasting) ✓
• You positioned yourself as complementary, not competitive ✓
• You moved to a next step with specifics (video + call) ✓
• You've got a follow-up pattern (Friday slack with times) ✓

Expected outcome: 70%+ probability they watch the video. 40%+ probability they take the 20-minute call.

Counter-Example: What Not to Do

PROSPECT: "We already have a solution for that."

YOU (Bad response 1): "Yeah, but we're way better than Netsuite. We have machine learning and—"

PROSPECT (internally): Vendor is bashing my choice. I'm done. [Closes door mentally]

YOU (Bad response 2): "No problem. Let me send you our deck so you can see all the features."

PROSPECT (internally): More slides. No thanks. [Ignores email]

YOU (Bad response 3): "Okay, well, when you're tired of paying so much for your current solution, reach out."

PROSPECT (internally): Snarky. Not engaging. [Deletes contact info]

Why these fail:

• They don't clarify the real gap → You're guessing, not solving
• They don't respect the prospect's current choice → You're building walls, not bridges
• They don't get permission to reconnect → You're hoping, not planning