peterod99 Objection Reframing (NEPQ-Style)
When to use
When a prospect raises an objection, don't fight it or discount it. Use Jeremy Miner's NEPQ-style reframing to ask curious questions that let the prospect surface their own logic. Works in discovery, during demos, and in negotiation. Turns objections into discovery data.
The framework
Acknowledge without agreeing: "That's a fair question / concern." Don't say "No, you're wrong" or "Actually, it's not that expensive."
Ask a neutral question: Redirect their objection back to them with genuine curiosity. Let them think through the issue.
Listen to their reasoning: Don't interrupt. They'll often talk themselves into the solution by explaining the objection aloud.
Identify the real concern beneath the surface concern: Price objections usually signal budget constraints, timing misalignment, or unclear ROI. "You're too expensive" often means "I don't see value yet." Push deeper.
Reframe with their own words: Use what they said to position next steps or alternatives. This feels collaborative, not sales-y.
How to apply it
Example 1: Price objection
Prospect: "Your pricing is higher than [competitor name]."
Old (wrong) approach: "Actually, we're the same price if you factor in...": Defensive. Makes them explain why they're wrong.
NEPQ reframe:
You: "That makes sense. When you say higher, have you already decided what functionality you need, or are you still figuring out which features matter most to you?"
Prospect: "Well, we haven't fully mapped it out yet. We're mostly comparing on cost."
You: "Got it. If you did map out what you actually need, do you think the cost-per-feature picture would change?"
Prospect: "Probably. Once we know what we're really solving for, pricing might make more sense."
You: "Would it help to do that mapping before comparing pricing? That way you're not comparing apples and oranges."
Result: You've moved them from price-shopping to needs clarity. Objection dissolved, not fought.
Example 2: Timeline objection
Prospect: "We can't do this until next quarter. We're too busy right now."
Old approach: "I understand, but things won't get less busy. How about we start next month?": You're pushing. They're resisting harder.
NEPQ reframe:
You: "When you say you're too busy, is that a resource capacity issue, or is this project just not a priority compared to what's on your plate now?"
Prospect: "Both, honestly. We've got a system migration happening and it's eating up IT resources."
You: "How long is that migration?"
Prospect: "Six weeks, probably."
You: "So six weeks from now, would you have capacity to start a conversation about this, or is there something after the migration that would also keep you slammed?"
Prospect: "After the migration, things should calm down. Maybe early Q3."
You: "Got it. Let's aim for a quick 20-minute call the first week of Q3 to see if this still matters to you then. Fair?"
Result: You didn't pressure them. You mapped the real constraint (migration), identified the actual timeline window, and confirmed relevance at a future date. Objection answered without manipulation.
Example 3: Internal buy-in objection
Prospect: "I like this, but I need to get my finance team's sign-off, and they're going to have a lot of questions."
Old approach: "Sure, set up a call with finance. I'll handle their objections.": Risky. Finance often has unstated priorities or constraints.
NEPQ reframe:
You: "What do you think finance will want to understand first? Is it ROI, cost control, implementation time, or something else?"
Prospect: "Definitely ROI. And they'll want to know if there are any hidden costs."
You: "If you walked them through the ROI math using your specific use case, like how much time your team would save, do you think that changes their stance?"
Prospect: "Yeah, if I can show them we're saving 10 hours a week, they'll probably approve it."
You: "Perfect. Here's what I can send you: a one-pager that shows the time savings and the math on cost per hour saved. You can use that when you talk to finance. And if they have follow-up questions after that, you can loop me in. Does that work?"
Result: You've enlisted the prospect as your internal champion. You've given them a tool to sell internally. You haven't dismissed finance's concerns; you've acknowledged them and made it easy for the prospect to address them. Objection transformed into collaboration.
Common traps
Countering immediately: You hear "We're happy with our current solution" and jump to "Well, our solution is different because..." You've started arguing, not asking. Prospect shuts down.
Assuming the objection is the real issue: "Too expensive" usually isn't really about price; it's about unclear value. "Not the right time" usually means priority, not calendar. If you address price without surfacing the real concern, you lose.
Asking leading questions instead of neutral ones: "Don't you think ROI is important?" is leading. They hear a close coming. Neutral version: "What would ROI look like for you?" lets them think.
Not listening for silence: You ask a question and they pause. You get uncomfortable and keep talking. NEPQ requires you to sit in the silence while they think. Silence = thinking = progress.
Reframing with your words, not theirs: You ask good questions but then answer for them. "So what you're really saying is..." no. Let them say what they mean.
Source credits
- Jeremy Miner & Matthew Rider, 7th Level Communications Hunter Gatherer (NEPQ framework): Reframe objections as discovery data; use neutral questions to surface prospect's own reasoning
- Michael Oliver, The Art & Science Of Selling With Integrity: Buyer-driven vs. seller-driven intention; listening disciplines; feeling-finding questions (emotional drivers beneath surface objections)