Why the Same Objections Keep Winning
The most common sales objections have not changed in thirty years. Price, timing, authority, competition, trust, need, and product fit - these seven categories cover the vast majority of every objection a B2B sales rep will hear on a live call. Every sales enablement programme covers them. Most reps can name them. And yet the same objections that should be the easiest to handle are still the ones that most consistently stall and kill deals.
The gap is not knowledge. It is performance under pressure. A rep who knows the reframe for a price objection in a training session is a different rep from the one who delivers it confidently on a live call when a CFO has just said ‘that’s significantly more than we were expecting.’ The pressure compresses cognitive bandwidth. The well-rehearsed response competes with the instinct to defend, discount, or apologise.
This article covers the seven most common objections with a proven reframe for each - structured around the Acknowledge → Probe → Reframe model that top performers consistently use. Each objection also includes an AI roleplay practice prompt you can use to rehearse before facing it live, and a note on how a real-time AI copilot handles the objection in the moment it arrives.
“Top performers respond to objections with questions, not answers - maintaining conversational flow rather than shifting into presentation mode.” - Analysis of 67,149 sales calls
The Model Behind Every Response: Acknowledge → Probe → Reframe
Every effective objection response follows the same three-move structure. Understanding the pattern before the specific objections makes each reframe easier to adapt in the moment when the prospect phrases things differently than the script anticipated.
| Move | Purpose | Example language |
|---|---|---|
| Acknowledge | Validate the concern without agreeing with it. Removes defensiveness before any reframe can land. | “That’s fair.” / “I hear that a lot.” / “Makes sense.” |
| Probe | Ask a diagnostic question to find the real concern behind the stated one. Most objections are proxies. | “When you say expensive - is that a budget question or a value question?” |
| Reframe | Shift the frame - from cost to ROI, from timing to urgency, from risk to cost-of-inaction. Never argue. Reposition. | “The way most teams think about it is…” / “What it usually comes down to is…” |
The 7 Most Common Sales Objections
Objection 1: Price
How it usually sounds:
- “That’s more than we were expecting.”
- “It’s too expensive for us right now.”
- “We can’t justify that cost.”
- “The other option is cheaper.”
What it is really saying: One of three things: the value case has not been made convincingly, the budget is genuinely constrained and needs a timing or phasing conversation, or the prospect is testing for a discount. Treating all three the same way is the error most reps make.
The wrong move: Discounting immediately or defending the price point - both signal that the price was never properly justified and invite further pressure.
The reframe:
“Completely fair to raise. Can I ask - when you say expensive, is that relative to a budget that’s already committed elsewhere, or is it more about whether the value justifies the number?”
[If value:] “The way most teams frame it: if this cuts ramp time from 90 to 45 days for five reps, that’s five months of additional productive output. What does a month of quota attainment cost you?”
Why it works: The probe separates three fundamentally different problems before any reframe is attempted. A rep who diagnoses first and responds second sounds in control. A rep who jumps to the ROI case before understanding which price problem they are dealing with sounds scripted.
AI roleplay practice prompt:
Play the role of a VP of Sales at a 30-person SaaS company. When I present my product’s pricing, say: ‘That’s quite a bit more than we budgeted for this.’ Push back when I attempt to justify the price without first asking a diagnostic question. If I probe well, reveal that the concern is value, not budget.
What Convinco surfaces live: Convinco detects price objection language semantically - ‘that’s a lot,’ ‘more than we expected,’ and ‘the other option is cheaper’ all trigger the same diagnostic prompt. Your ROI benchmarks from the knowledge base surface alongside it.
Objection 2: Timing
How it usually sounds:
- “Now isn’t the right time.”
- “Come back to us next quarter.”
- “We’re in the middle of something else right now.”
- “Ask me again in six months.”
What it is really saying: Either genuine bandwidth or capacity constraints, a priority ranking issue (this is not important enough to fight for), or a polite way of ending the conversation without confrontation. All three require different responses - which is why probing first matters.
The wrong move: Scheduling a follow-up for next quarter without establishing what will be different which produces the same conversation with the same outcome three months later.
The reframe:
“That makes sense. Can I ask - when you say the timing isn’t right, is it a capacity thing on your end, or is there something that needs to happen internally before this makes sense to evaluate?”
[If priority:] “That’s actually more useful to understand.
What would need to be true for this to move up the list?”
[If genuine timing:] “Got it. So if [trigger event] happens in Q3,
that’s the right window — would it help if I put a note in for
[specific date] rather than a generic follow-up?”
Why it works: Anchoring the follow-up to a specific trigger rather than a calendar date gives the rep a reason to reconnect that the prospect cares about - and makes the follow-up call about something that changed, not just ‘checking in.’
Al roleplay practice prompt:
Play a Head of Revenue Operations at a Series B company. When I pitch, respond with: ‘We’re in the middle of a CRM migration right now - this really isn’t the right time.’ If I probe well and ask what needs to change, reveal that the CRM migration is expected to complete in about six weeks.
What Convinco surfaces live: Timing objection recognised. Convinco surfaces the diagnostic question and prompts the rep to anchor the follow-up to a specific internal trigger before ending the call.
Objection 3: Authority
How it usually sounds:
-“I need to run this by my manager.”
- “This would need sign-off from the CFO.”
- “I’m not the decision-maker here.” -“My team would need to be involved.” What it is really saying: There are additional stakeholders who will influence or block the decision - and this person either does not have the authority they implied, or they do but are not yet willing to commit without cover. This is a MEDDPICC signal: the Economic Buyer and Decision Process are not yet mapped.
The wrong move: Saying ‘of course, let me know what they think’ and waiting passively - which hands the deal to a conversation the rep cannot influence.
The reframe:
“Absolutely — that makes total sense. Can I ask who else would be involved, so I can make sure they have what they need?”
“Would it be useful if I put together a short summary they could review first — or would you prefer I join that conversation?”
“And just so I can be helpful on timing — when does that discussion typically happen, and when would I hear back?”
Why it works: Three moves at once: map the stakeholders, offer to support the internal conversation rather than wait for its outcome, and establish a specific follow-up timeline. The rep stays active in the deal rather than becoming a passive observer.
AI roleplay practice prompt:
Play a Sales Operations Manager who is genuinely enthusiastic about the product but does not have budget authority. When I ask about next steps, say: ‘I’d need to get VP approval for something like this.’ If I probe on who the VP is and offer to help prepare the internal case, respond warmly. If I just say ‘sounds good, let me know what they think,’ go cold and stop responding to follow-ups.
What Convinco surfaces live: Multi-stakeholder signal detected. Convinco surfaces the stakeholder mapping question and MEDDPICC Economic Buyer prompt - and flags that Paper Process should also be surfaced at this stage.
Objection 4: Competition / Status Quo
How it usually sounds:
- “We already have something for this.”
- “We’re happy with our current setup.”
- “We use [Competitor] for that.”
- “We’ve tried something like this before.”
What it is really saying: There is an existing solution or habit that the prospect would need to abandon or supplement. The question is whether the current solution is genuinely meeting their needs or is simply familiar - and whether the pain is significant enough to justify the disruption of switching.
The wrong move: Attacking the current vendor or existing process - which puts the prospect on the defensive and forces them to justify a decision they made.
The reframe:
“Good to know - I’m not trying to replace anything that’s working.
Can I ask: what drew you to [current solution] originally?”
[Listen, then:] “The reason I ask is that teams come to us specifically
when [name the gap your product fills]. Is that something that’s
come up for you at all?”
Why it works: Curiosity disarms the defensive posture. The follow-up question probes for the gap rather than attacking the incumbent. If the gap exists, the prospect names it themselves - which is far more persuasive than the rep asserting it.
AI roleplay practice prompt:
Play a VP of Sales who uses Gong and is broadly satisfied with it. When I introduce Convinco, say: ‘We already have Gong - I’m not sure what you’d add.’ If I ask what they use Gong for and probe for the live-call gap, open up. If I just say ‘we’re different from Gong,’ remain unconvinced.
What Convinco surfaces live: Competitor name detected. Convinco retrieves the specific battlecard for that vendor from your knowledge base - surfacing your differentiation tied to the gap the prospect has not yet named.
Objection 5: Need / Relevance
How it usually sounds:
-“We don’t really have that problem.”
- “I’m not sure this is relevant for us.”
- “Our team handles that fine.”
- “This isn’t a priority for us.”
What it is really saying: Either the pain has not been surfaced convincingly enough to be felt, the rep is pitching the wrong solution to the wrong problem, or the prospect has not connected their existing frustration to the category of solution being offered.
The wrong move: Defending the relevance of the product by listing features - which adds more information to a conversation where the prospect has already stopped listening.
The reframe:
“That’s helpful to know. Can I ask - when your reps are on live discovery calls and a prospect raises a tough objection, what typically happens? Do they handle it confidently or does it vary?”
[If they acknowledge variance:] “That’s exactly the gap we address.
It’s less about whether the team has the problem in theory and more about what happens in the moment - when the pressure is on and the script doesn’t fit.”
Why it works: The question invites the prospect to describe their own situation rather than evaluate the rep’s claim about it. A prospect who says ‘it varies’ has just identified the pain themselves - without being told they have a problem.
Al roleplay practice prompt:
Play a Sales Manager who genuinely believes their team handles objections well. When I pitch live call coaching, say: ‘Our reps are pretty experienced - I don’t think this is something they need.’ If I ask a specific question about what happens on their toughest calls, pause and acknowledge that there is variance. If I just try to convince you the product is relevant, remain dismissive.
What Convinco surfaces live: Low-relevance signal detected. Convinco surfaces a diagnostic question designed to surface the pain through the prospect’s own description rather than the rep’s assertion.
Objection 6: Trust / Credibility
How it usually sounds:
- “I’ve never heard of you.”
- “How long have you been around?”
- “We prefer to work with established vendors.”
- “Can you show me some references?”
What it is really saying: The prospect is risk-managing. Choosing a newer or smaller vendor carries personal and organisational risk - if it fails, they are accountable for the decision. They are not asking for your founding story. They are asking for evidence that the risk is manageable.
The wrong move: Over-explaining company history or becoming defensive about size - both signal insecurity and make the risk feel larger, not smaller.
The reframe:
“Fair - we’re relatively new in the market. The reason you haven’t heard of us yet is that we’ve been focused on a specific type of team rather than broad brand building.
We’re currently working with [named customer type or specific customer].
The fastest way to evaluate us is honestly just to see it on a call if it doesn’t land in fifteen minutes, you’ll know immediately.”
Why it works: The ‘heads-down’ framing reframes small size as focus rather than risk. A named customer reference provides social proof without a case study. The low-commitment ask (fifteen minutes, self-selecting out quickly) reduces the activation energy of the next step.
AI roleplay practice prompt:
Play a Director of Sales at a 200-person company who prefers established vendors. When I introduce Convinco, say: ‘We tend to stick to tools we know - I’ve never heard of Convinco.’ If I provide a specific customer reference relevant to your industry and offer a low-risk next step, engage. If I give a long company history, lose interest.
What Convinco surfaces live: Trust objection recognised. Convinco surfaces your most relevant customer reference for this prospect’s industry or company size from the knowledge base - along with the low-commitment ask language.
Objection 7: Product Fit
How it usually sounds:
- “You don’t have [feature] we need.”
- “It doesn’t integrate with our CRM.”
- “We need something that does X.”
- “It’s not quite what we were looking for.”
What it is really saying: Either a genuine capability gap, or a surface-level feature request that masks a deeper use case the rep has not yet understood. Responding before diagnosing which it is produces the wrong answer for one of the two situations.
The wrong move: Immediately promising a roadmap item or explaining why the feature is not actually necessary - both dismiss the stated need without understanding what it is actually trying to accomplish.
The reframe:
“Helpful to know - can I ask how you’d use [feature] today and what it enables for your team?”
[Listen, then:] “The reason I ask is that some teams need that for
[use case A] and others for [use case B]. If it’s [use case A],
we handle that through [alternative approach]. If it’s [use case B],
that’s genuinely something we don’t do - and I’d rather tell you
that honestly than oversell it.”
Why it works: The question uncovers the underlying use case before any response is given. The honest ‘we don’t do that’ option, when relevant, builds credibility for everything else the rep says and positions them as a trusted advisor rather than a feature vendor.
AI roleplay practice prompt:
Play a RevOps lead who is evaluating AI sales tools. When I demo, say: ‘We need this to integrate with Outreach - does it?’ If I ask what specifically you need the integration to do before answering, reveal the actual use case (auto-logging call notes). If I just say yes or no without probing, make the question harder.
What Convinco surfaces live: Feature gap signal detected. Convinco retrieves your product documentation for relevant alternative approaches. If the feature genuinely does not exist, the copilot flags this so the rep can respond honestly rather than guessing or overpromising.
Quick Reference: All 7 Objections
| Objection | Real concern behind it | First move | Never do this |
|---|---|---|---|
| Price | Value gap or budget constraint - diagnose which | Probe: budget or value? | Discount immediately |
| Timing | Capacity, priority, or polite exit | Anchor follow-up to a specific trigger | Schedule for next Q without probing |
| Authority | Additional stakeholders not yet mapped | Map the stakeholders; offer to help internally | Say ‘let me know what they think’ |
| Competition | Existing solution or status quo to displace | Ask what drew them to it; probe for the gap | Attack the incumbent |
| Need / Relevance | Pain not yet felt or connected to the solution | Ask a question that surfaces the pain themselves | List features to prove relevance |
| Trust | Risk management - new vendor accountability | Named reference + low-commitment ask | Give company founding history |
| Product fit | Feature request masking a use case | Ask what the feature enables before responding | Promise roadmap or dismiss the need |
How AI Changes Objection Handling: Two Distinct Modes
There are two distinct ways AI helps with objection handling - and they address different parts of the problem. Understanding the difference helps you choose the right tool for the right gap.
| Mode | When It Operates | What It Does | Best For |
|---|---|---|---|
| AI objection handling roleplay | Before live calls practice environment | Simulates the prospect raising the objection so the rep can rehearse their response repeatedly until it feels natural | Building muscle memory before facing the objection live; new reps who have not heard the objection enough times to respond confidently |
| Real-time AI copilot (Convinco) | During live calls — invisible to prospect | Recognises the objection semantically as the prospect raises it and surfaces the right diagnostic question and reframe within 1-2 seconds | Ensuring the right response is available in the moment even when the phrasing is unexpected or the rep draws a blank under pressure |
The two modes are complementary. Roleplay builds the foundation. Real-time support is the safety net on live calls - and the delivery mechanism for all the rehearsal to actually matter in the moment it is needed.
“Instead of spending months learning, I can execute immediately and rely on Convinco where needed, at a lower cost.” - Ryan Holanda, Commercial Representative, Ventairy
How to Use the Roleplay Prompts in This Article
Each of the seven objection blocks above includes a roleplay prompt you can paste directly into an AI assistant to practice your response. The prompts are designed to reward good technique (probing before reframing) and resist bad technique (defending, discounting, listing features) - so the practice session produces useful feedback, not just a pleasant exchange.
- Run each scenario at least three times. The first time you will likely default to the wrong move. The second time you will be more deliberate. By the third, the probe-first structure starts to feel natural rather than effortful.
- Vary the prospect’s phrasing. After the first run, ask the AI to raise the same objection using different language. ‘That’s too expensive’ and ‘we can’t justify the ROI’ are the same objection - your response should recognise both.
- Practice the transition out of the reframe. Most reps practise the response but not what comes next. End each roleplay scenario by asking: ‘What is the natural next step after the reframe lands well?’ That transition is where many reps lose the momentum the reframe built.
- Use the live copilot on real calls. The roleplay builds the foundation. Convinco’s real-time AI copilot ensures the right response is available when the objection arrives in a phrasing you did not practise which is almost always how it happens.
Conclusion: The Objections Do Not Change - Your Response Can
Price, timing, authority, competition, relevance, trust, and product fit will be the objections your reps hear on their calls today, next month, and next year. The frameworks in this article have not changed in a decade because the psychology behind them has not changed. What has changed is how reps can prepare for and respond to them.
Al roleplay removes the excuse of insufficient practice. Real-time Al coaching removes the excuse of insufficient recall under pressure. A rep who has rehearsed each objection type and has a live copilot surfacing the right move when the moment arrives has every structural advantage over a rep relying on memory and nerve alone.
Practice these seven objections against a live AI before your next call - then let Convinco handle the ones that arrive unexpectedly. Book a demo: https://tally.so/r/eqYkZk View pricing: convinco.co/pricing Download the assistant: convinco.co/download
Further Reading
- Elevator Pitch Template: How to Write One in 60 Seconds (With Real Examples)
- B2B Discovery Call Checklist: Mastering Complex Pitches
- Conversation Intelligence vs Real-Time AI Coaching: What Your Sales Team Actually Needs
- How to Automate Your MEDDIC Playbook with an Al Sales Copilot
- 10 Best AI Sales Enablement Platforms in 2026: Ranked by Real-Time Capability
- How Al Sales Copilots Cut SDR Ramp Time
Top comments (0)