B2B Objection Handling Playbook

Use this playbook as a reference guide for SDRs handling live objections on cold calls, discovery calls, and in email replies. The goal is not to “overcome” every objection — some objections are genuine disqualifiers. The goal is to understand the real concern behind the words and respond with useful information.

The Core Objection Response Framework: APAC

Every objection response follows four steps:

1. Acknowledge — Show you heard them. No dismissing, no “I understand, but…”
2. Probe — Ask one question to understand the real concern behind the surface objection.
3. Answer — Respond with a specific, relevant point (not a feature dump).
4. Confirm — Check that you’ve addressed their concern before moving on.

Example in practice:

Prospect: “We already use HubSpot for this.”

Acknowledge: “Makes sense — HubSpot is solid for a lot of teams.” Probe: “Out of curiosity, is your team handling the full outbound workflow inside HubSpot, or do you have other tools in the stack too?” Answer: “Most teams I talk to at your stage are running HubSpot alongside Outreach and a couple of data tools. The gap is usually around reporting across those systems. That’s where our analytics layer fits — it pulls everything into one view.” Confirm: “Does that match your situation, or is your setup different?”

Objection Category 1: Timing

”Now is not a good time”

What they usually mean: I am busy right now, or this is not a current priority.

Response:

“Totally get it. Quick question so I can be useful when I follow up: is {{problem area}} something on the roadmap for next quarter, or is it genuinely not a priority right now? I ask because most teams wait until it is painful, and by then they are 6-8 weeks behind. I’d rather give you a heads-up now."

"We’re in the middle of a re-org”

What they usually mean: Decision-making is frozen.

Response:

“That makes sense — I hear this a lot. Re-orgs usually create the exact problems we solve: data scattered across systems, new leaders who need visibility fast, workflows that were built for the old structure. Would it be helpful to reconnect in 4-6 weeks when the dust settles? I can share what other teams did post-reorg so you have a starting point."

"Check back next quarter”

Response:

“Will do. So I don’t waste your time when I call back — what would need to be true for this to be a real conversation next quarter? That way I can come prepared with the right information.”

Objection Category 2: Budget & Pricing

”We don’t have budget for this”

What they usually mean: I don’t see enough value to justify the spend, OR budget is genuinely locked.

Response:

“Fair enough. Let me ask this — if budget weren’t a constraint, is this a problem your team would want to solve? Because if the answer is yes, there might be a way to build a business case. {{Reference_company}} justified the investment by showing they’d save {{X hours/week}} across the team, which translated to about {{$Y}} in recovered rep capacity. I could help you build a similar analysis."

"It’s too expensive”

Response:

“Compared to what? I ask because pricing usually comes down to what you’re comparing against — whether that’s the cost of the current setup, a competitor’s pricing, or doing it with headcount. Which one is closest for you?”

Then tailor the conversation based on their answer. If they are comparing to a competitor, pull up your differentiation points. If they are comparing to headcount, run the math on fully-loaded SDR cost vs. tool cost.

”We need to see ROI first”

Response:

“Absolutely. Let me share how {{reference_company}} measured it. They tracked three things: time saved on {{task}}, increase in {{metric}}, and reduction in {{waste metric}}. Within 90 days they were at {{result}}. I can walk you through their setup on a 20-minute call and you can judge whether the math works for your team.”

Use the event ROI calculator framework as a reference for building ROI models.

Objection Category 3: Competition & Status Quo

”We already have a solution”

Response:

“Good — that tells me this is a priority for you, which is half the battle. Most teams I talk to aren’t replacing their current tool entirely. They’re filling a gap. The most common gaps I hear about are {{gap_1}}, {{gap_2}}, and {{gap_3}}. Do any of those ring true, or is your current setup covering everything?"

"We built something internally”

Response:

“That’s actually pretty common at your stage. The question is usually whether the internal tool scales as the team grows. What I hear from teams who built their own is that maintenance becomes a full-time job — engineering time that could go toward the product instead goes toward keeping internal tools alive. Is that something you’re running into?"

"We’re happy with {{competitor}}”

Response:

“That’s good to hear — {{competitor}} does a solid job on {{their strength}}. I’m not going to trash them. The difference most teams notice is around {{your differentiator}}. For example, {{reference_company}} was on {{competitor}} for two years and switched because {{specific reason}}. Would it be useful to see a side-by-side comparison so you can judge for yourself?”

Objection Category 4: Authority

”I’m not the decision-maker”

Response:

“Appreciate you being upfront about that. Who would I need to loop in for a decision like this? And would it be helpful if I gave you a one-page summary you could forward? That way you don’t have to explain it — the document does the work."

"I need to talk to my team/boss”

Response:

“Of course. What would be most helpful — should I join that conversation to answer questions directly, or would you prefer a leave-behind doc your team can review async? I’ve found that having the right data in front of the decision-maker makes that conversation go faster."

"Send me some information”

This is the most common brush-off in B2B sales. Treat it as a soft “no” and try to qualify:

“Happy to send something over. So I can share the right materials and not a generic deck — what specifically would be most useful? Is it pricing, how it works with your current stack, or results from a company similar to yours?”

If they cannot articulate what they want, this is a brush-off. Send a brief email and move on.

Objection Response Tracker

Track which objections come up most frequently across the team. Review weekly.

Objection	Frequency (This Week)	Most Effective Response	Win Rate After Objection
Not the right time	___		%
Already have a solution	___		%
No budget	___		%
Send me info	___		%
Need to talk to boss	___		%
Too expensive	___		%

Feed this data into your GTM metrics dashboard so leadership has visibility into objection trends.

Training Drill: Weekly Objection Practice

Run this 15-minute drill in every team standup:

1. Manager picks an objection from the tracker (most common one that week)
2. One rep role-plays the prospect, one rep handles the objection
3. Team scores the response using APAC criteria (did they Acknowledge, Probe, Answer, Confirm?)
4. Rotate until 3-4 reps have practiced
5. Document the best response and add it to the playbook

How to Customize

• Add vertical-specific objections. Healthcare buyers will raise compliance objections. Financial services buyers will raise security objections. Build a supplementary page for each vertical your team sells into.
• Update monthly based on data. Pull objection frequency from Gong/Chorus call analytics. If a new objection starts appearing (e.g., after a competitor launches a new feature), write a response within 48 hours and distribute to the team.
• Create an “objection of the week” Slack ritual. Post the most challenging objection from the prior week in your SDR channel. Have the team submit their best response. Vote on the winner and add it to the official SDR playbook.