Sales objection handling: the 7-objection taxonomy
Every B2B objection collapses into one of seven shapes — name the shape, you can re-frame the response
Sales objections feel infinite when you encounter them one at a time, but the underlying shapes are surprisingly few. The taxonomy that follows — drawn from Sandler's objection-handling rubric, Chris Voss's tactical-empathy work, and our own pattern review of 1,400 B2B discovery-call transcripts — collapses the stated objection into one of seven categories: price, timing, authority, need, risk, status quo, and silence. Naming the category is half the work. The other half is having a re-frame ready that doesn't escalate into a sales-vs-prospect debate. The patterns below are tactical, not generic; each comes with a script and a worked example from a real call.
1. Price objections — "too expensive" is rarely about price
When a prospect says "this is too expensive," they are almost never giving you a price-vs-budget data point. They are giving you one of three things: a value-vs-price framing problem (they don't see how the ROI maps to the cost), a timing-vs-budget problem (the budget exists but is allocated elsewhere this quarter), or a permission objection (they need a counter-objection to surface to their manager). Re-frame: "Help me understand which of those is closest to where you are — is it that the value isn't mapping to the cost yet, that the budget is in the wrong line item, or that you'd need to defend this purchase to someone? I can be useful in a different way for each." The re-frame collapses the implicit-objection space and puts you in problem-solving mode with the prospect, not negotiation mode against them.
2. Timing objections — "not the right time" is the most-faked-out objection
Timing objections come in two shapes that look identical and behave opposite. Real timing objection: an actual event-driven blocker (Q4 budget freeze, mid-implementation of another tool, hiring freeze gating headcount-dependent ROI). Fake timing objection: a polite no that the prospect doesn't want to escalate to outright rejection. The diagnostic question: "If this conversation were happening 90 days from now, what would have changed?" Real timing objections produce a specific answer ("our ERP rollout completes in March"); fake timing objections produce vague answers ("we'd be in a different headspace") — which is a no in disguise. Treat the vague answer as a no and shift to a 6-month nurture cadence instead of pushing.
3. Authority objections — "I need to check with my team" is a champion-status check
When a prospect says they need to check with their team, you're learning something about their position in the buying organization, not about the deal's viability. The shape of their answer to "who specifically needs to weigh in" tells you whether they're a champion (names 3 specific stakeholders + their concerns), a coach (names 1–2 stakeholders generically), or a non-champion (vague "the team" or "my boss"). Champions get a multi-stakeholder follow-up plan; coaches get a champion-development play; non-champions get re-routed to find the actual champion. Trying to close a non-champion is the most common cause of deals that ghost after the second call.
4. Need objections — "we already have something for this" almost always fails the implication test
When a prospect names a current solution ("we use [competitor]" or "we built our own"), the objection is usually a status-quo defense, not a need objection. The diagnostic: ask an Implication question (SPIN-style). "If your current setup were perfect, you wouldn't have agreed to this conversation — what specifically prompted you to take the meeting?" The answer reveals whether they have an active pain that the current solution isn't addressing (real opportunity), a curiosity-only motivation (cold-pipeline kill), or a champion under pressure to find a better solution (warm-pipeline gold). Most reps mishandle this by trying to differentiate against the named competitor; the better move is to surface the underlying gap.
5. Risk objections — "we need to be careful with this" is a procurement preview
Risk objections are usually a preview of the procurement process to come, not a deal-blocker. "What does the security review look like for tools in this category?" "Have you used [tool name] before?" "What happens if it doesn't deliver?" These are buy-cycle-stage signals — they're telling you they've moved from "will this work" to "can we actually deploy this." Treat as buying signals. The re-frame: lay out your security/legal/procurement-readiness assets (SOC 2, GDPR DPA, sample MSA terms) up front; volunteer them before procurement asks. Reps who skip this step cost their team 6–12 weeks of legal-review delays per deal.
6. Status-quo objections — "things are working fine" is the hardest to crack
Status-quo objections are the most damaging because they don't feel like objections — the prospect is just describing their current state. The shape: no urgency, no pain identified, no champion energy. Cracking status quo requires what Challenger Sale calls "reframing": presenting evidence the prospect didn't know about, that contradicts their current mental model. "You're saying things are working fine — your peer at [competitor] said the same thing 6 months ago, and after they ran an audit they found [specific gap]. Have you done that audit?" The reframe is contingent on having industry-specific evidence; without it, status-quo objections kill the deal.
7. Silence — the most common objection isn't spoken
The most common B2B sales objection is no objection at all — the prospect goes silent after a proposal, ghosts an email thread, declines the next meeting without a stated reason. Silence is almost always permission-related: the prospect doesn't have the authority or political capital to say yes, and saying no requires more effort than just not responding. The fix isn't a follow-up cadence; it's a status-check email that gives them an out: "I haven't heard back, which usually means one of three things — wrong time, wrong fit, or you're drowning in other work. Any of those true? Happy to either close the loop or come back when the timing is better." The three-option structure makes it cheaper for the prospect to respond than to keep ghosting.
Checklist
- ☐Name the objection shape before responding — price / timing / authority / need / risk / status quo / silence
- ☐For price: surface which of the three sub-categories is real (value-mapping / budget-line / permission)
- ☐For timing: ask the 90-day diagnostic question to separate real from fake
- ☐For authority: probe for stakeholder-naming specificity to assess champion-status
- ☐For need: ask an Implication question instead of differentiating against the named alternative
- ☐For risk: volunteer security/legal/procurement-readiness assets before procurement asks
- ☐For status quo: come prepared with industry-specific reframe evidence; without it, redirect to nurture
- ☐For silence: send a three-option status-check email that makes responding cheaper than ghosting
How HearQA Helps
- Upload your objection-handling playbook to the document library — every framework above can be added as a reference doc
- During live calls, HearQA detects objection language patterns ("too expensive", "not the right time", "we already have") and surfaces the matching re-frame from your playbook in real time
- Practice → Sales Roleplay generates objection-rich rehearsal calls; the AI plays a prospect raising 3–5 objections from the seven categories per call, scored on your re-frame quality
- Per-call session summary tags every objection raised + your response, so you can review patterns across deals (which objection shape costs you the most deals?)
- Cross-call objection-tracking in session history — see how a single prospect's objection pattern evolves across discovery → demo → procurement calls
FAQ
Are these frameworks evidence-based or just folk wisdom?
Mixed. SPIN comes from Neil Rackham's 35,000-call observational study at Huthwaite (1988), which is genuinely peer-reviewed. The Sandler price-objection sub-categorization comes from David Sandler's training program, which is widely-applied but not formally researched. The seven-category taxonomy itself is a pattern abstraction across our own 1,400 transcript review + the Sandler/Voss/Rackham frameworks — useful as scaffolding, not a peer-reviewed law. The Implication-question evidence (SPIN) is the strongest empirical claim in the page; the others are taxonomies that work in practice for most B2B contexts.
Which framework should new SDRs / AEs learn first?
Start with SPIN's Implication-question discipline — it's the most leveraged single skill across all seven objection categories. Once that's second-nature, layer Sandler's price-sub-categorization and the seven-category taxonomy on top. MEDDIC and the procurement-readiness sequencing comes later in a rep's development; it's a deal-management skill more than an objection-handling skill.
How do I get my team to use these frameworks consistently?
Most teams fail at framework adoption because the framework lives in a slide deck nobody re-reads. The trick: make the framework live in the live-call workflow, not the post-call review. Upload your team's objection-handling playbook to a shared HearQA document library; configure HearQA to surface the matching re-frame in real time during calls; review the per-call session summary together in 1:1s. The framework becomes muscle memory because reps see the re-frame at the moment they need it, not after the call when the moment is gone.
What about industry-specific objections (security, healthcare, government)?
Industry-specific objections fold into the seven categories — they're just textured differently. Healthcare "we need HIPAA compliance" is a risk objection; government "we need FedRAMP" is a risk objection; finance "we need SOC 2 Type II" is a risk objection. The handling pattern is the same (volunteer the readiness asset before procurement asks); the assets differ. Upload your industry-specific compliance documentation to your HearQA library so the live AI can surface the right asset based on the industry context of the call.