Objections are not obstacles to closing. They are the closing. Every objection a prospect raises is a signal that they're engaged enough to push back — which means they're engaged enough to buy. The rep who treats objections as problems to overcome will always struggle. The rep who treats them as information to understand will consistently close.
44% of salespeople give up after one objection — yet 80% of sales require five follow-ups or objection responses before closing (Source: Marketing Donut / Invesp, Sales Follow-Up Statistics, 2024)
This playbook covers the 12 most common sales objections and the specific language patterns that resolve them. Pair it with our sales script guide and battle card templates for a complete conversation toolkit. The framework behind each response is the same: acknowledge the objection genuinely, reframe it in a way that opens a different perspective, and ask a question that invites the prospect to engage with the reframe. This structure works because it respects the prospect's intelligence while moving the conversation forward.
The Acknowledge-Reframe-Question Framework
Before the specific objections, the framework. This structure also applies to discovery calls — the same listen-reframe-question discipline that makes great discovery makes great objection handling. Every effective objection response has three components. First, acknowledge: show the prospect you heard them and that their concern is valid. Skipping this step makes you sound defensive and dismissive. Second, reframe: offer a different way of looking at the situation — one that doesn't dismiss the concern but puts it in a context where your solution makes sense. Third, question: ask something that invites the prospect to engage with the reframe rather than just receiving it. The question turns a monologue into a dialogue.
The 12 Most Common Objections — and What to Say
1. "It's too expensive."
Acknowledge: "I hear you — budget is always a real consideration." Reframe: "The way most of our customers think about it is in terms of what the problem is costing them right now. If [specific pain] is costing your team [estimated cost], then the question becomes whether [price] is an investment or an expense." Question: "What would the value need to be for this to feel like an obvious decision?"
2. "We're already using [Competitor]."
Acknowledge: "[Competitor] is a solid tool — I know a lot of teams use them." Reframe: "The teams that come to us from [Competitor] usually do so because of [specific gap]. Is that something you've run into?" Question: "What would need to be different about your current setup for you to consider making a change?"
3. "We don't have budget right now."
Acknowledge: "Totally understand — budget cycles are real." Reframe: "A lot of our customers started conversations in Q3 and had budget approved for Q4 by building the business case internally. Would it be useful to put together the ROI numbers so you have something concrete to take to your CFO when the cycle opens?" Question: "When does your next budget cycle typically kick off?"
4. "I need to think about it."
Acknowledge: "Of course — this is a real decision and I want you to feel confident." Reframe: "In my experience, 'I need to think about it' usually means there's a specific concern that hasn't been fully addressed." Question: "What's the one thing that would need to be true for you to feel ready to move forward?"
5. "We're not ready yet."
Acknowledge: "That makes sense — timing matters." Reframe: "Can I ask what 'ready' looks like? Sometimes there are things we can do to accelerate that timeline, and sometimes the timing is genuinely not right — I'd rather know which one this is." Question: "What would need to happen internally for the timing to be right?"
6. "We need to involve more stakeholders."
Acknowledge: "Absolutely — getting the right people aligned is important." Reframe: "I'd love to help make that process easier. The most effective way is usually a short session where I can address their specific questions directly." Question: "Who are the key stakeholders, and what are the 1–2 questions they're most likely to ask?"
7. "We tried something similar before and it didn't work."
Acknowledge: "That's really useful context — I appreciate you sharing that." Reframe: "Can you tell me more about what happened? I want to understand whether we'd run into the same issue or whether the situation is different enough that the outcome would be too." Question: "What specifically didn't work — was it the tool, the implementation, or the adoption?"
8. "Your product is missing [Feature]."
Acknowledge: "That's a fair point — [feature] is something we hear about." Reframe: "Can I ask how critical that feature is to your core use case? Sometimes it's a must-have and sometimes it's a nice-to-have, and I want to understand which this is before I respond." Question: "If [feature] weren't available, what would the workaround look like, and how much of a burden would that be?"
9. "We're going to build this internally."
Acknowledge: "That's a real option — some teams do go that route." Reframe: "The teams I've seen build internally usually find that the build takes 3–4× longer than expected and the maintenance cost is significant. The question is whether that's the best use of your engineering resources." Question: "What's the estimated timeline and resource cost for the internal build?"
10. "We need a discount."
Acknowledge: "I understand — everyone wants the best value." Reframe: "I'm not in a position to discount the standard price, but I can look at what we can do on terms — whether that's a longer contract for a better rate, or a phased rollout that reduces the initial commitment." Question: "Is the issue the total cost, the upfront commitment, or something else?"
11. "I don't see the ROI."
Acknowledge: "That's the right question to ask." Reframe: "Let me walk through how our customers typically measure the impact. For a team your size, the most common ROI drivers are [X, Y, Z]. Based on what you've shared about your current situation, the rough numbers would be [estimate]." Question: "Does that framing match how you'd measure success internally?"
12. "Now isn't a good time — call me in six months."
Acknowledge: "I respect that." Reframe: "I want to make sure I'm not wasting your time in six months either. Can I ask what's driving the timing — is it a budget cycle, a specific project, or something else? That way I can reach out at the right moment with the right context." Question: "What would need to be different in six months for this to be a priority?"
The Role of Real-Time AI in Objection Handling
35% improvement in objection handling success rate when reps receive in-call AI prompts vs. relying on memory alone (Source: MagicScreen Internal Customer Data, 2025)
The challenge with objection handling is not that reps don't know the right responses — it's that they can't always access them in the moment. Under the pressure of a live call with a senior buyer, the well-rehearsed response can disappear. Real-time AI tools like MagicScreen address this by detecting objections as they're spoken and surfacing the relevant response framework immediately — so the rep has the language available at the exact moment they need it, not after the call when they're reviewing what they should have said.