Sales training and objection handling, run out of Denver and delivered nationwide Call toll-free 1-800-481-8638
MySalesHelp.com, sales training and objection handling by Zach Wennstedt
Call toll-free 1-800-481-8638
Call toll-free 1-800-481-8638 Home Objection engine Spin the wheel Sales training makeovers The selling system Do The Right Thing course Objection library Sales glossary Training packages Sales arcade About Zach Book a call

The sales objection handling library

Every objection I've collected from real sales calls, organized into twelve families. Each one has the reframe, which is the thinking behind the response, two scripts you can say out loud today, and a power move. It's free, there's no signup, and every card copies to your clipboard in one tap.

Call toll-free 1-800-481-8638 Search it instead

216objections answered
432written scripts
12objection families
$0and no email wall

Showing all 216 objections across 12 families

How to actually use this

Do not read it front to back. Pick the one family you lose deals to most, open five objections, and say the scripts out loud. Reading them silently produces recognition, not recall, and recognition is useless at two in the afternoon when a buyer catches you off guard. Then rewrite them in your own words with your product in them. Five a day for a month covers the whole library and permanently changes how you sound under pressure.

The reframe matters more than the script. The script is one expression of the thinking; the reframe is the thinking. Learn the reframe and you can improvise a response to an objection that isn't in here at all, which is the actual goal. There are hundreds of objections and only about twelve underlying reasons for all of them.

If you want the psychology underneath why these work, that's the Do The Right Thing Sales Perfect training course. If you want this built specifically around your product and your buyer's actual words, that's the first deliverable of a sales training makeover.

Price objections

33

Almost never about available money. A price objection means the buyer has not connected the cost to an outcome they care about. Your job is to move the comparison, not lower the number.

The reframe

Move off the sticker and onto the comparison. 'Expensive' is meaningless until we know expensive compared to what.

Say this

Compared to what? I'm not being difficult — if it's compared to another quote, that's one conversation. If it's compared to doing nothing, that's a completely different one. Which is it?
Fair enough. Let me ask it this way: if price weren't part of this at all, is this the solution you'd want? Because if it is, we've only got one problem to solve instead of two.

Power move

Never defend the price. Investigate the comparison. 'Compared to what?' is the highest-yield four words in selling.

The reframe

A budget is a plan made before they had your information. Plans get revised when the information changes.

Say this

Understood. Out of curiosity, when was that budget set — before or after you knew what fixing this actually costs? Sometimes the budget was built on an estimate that turned out to be low.
Let's split it. What's the number you're comfortable with, and what's the number that would need approval? If we're close, there may be a way to phase this so it fits the first one.

Power move

Budgets are set by people. Find out who set it and on what assumption. Then update the assumption.

The reframe

Two numbers that aren't buying the same thing aren't comparable. Make the difference visible before defending the gap.

Say this

Good — you should be comparing. Can I see what's in their scope? Nine times out of ten the gap is a line item somebody left out, and I'd rather show you exactly where it is than just tell you we're worth more.
We might genuinely be more expensive. The question I'd want answered in your shoes is what the extra buys and whether you need it. Let me lay both out and you decide.

Power move

Ask to see the competing scope. Either you find the gap, or you learn something real about your pricing.

The reframe

A discount request this early is usually a habit, not a requirement. Answer with a question, not a number.

Say this

I can move on scope, or I can move on timing, but I don't move on price for the same work — that wouldn't be fair to the clients who paid it. What's driving the question? If there's a number you need to hit, tell me and I'll tell you honestly if it's reachable.
Before I answer that — if I could, would we be signing today? I ask because I don't want to trade margin for a maybe.

Power move

'If I could, would we be moving forward today?' turns a free discount into a conditional close.

The reframe

Distinguish 'no money' from 'no money allocated.' They're solved differently.

Say this

I hear you. Is it that the cash isn't there this month, or that it's committed to other things? Those have different answers and I want to give you the right one.
If cash is genuinely tight, let's not pretend otherwise. What I can do is scope this down to the piece that pays for itself fastest, and we revisit the rest when it's funded.

Power move

When the constraint is real, phase it. A smaller yes today beats a fictional yes later.

The reframe

Expectations came from somewhere. Find the anchor and address it directly.

Say this

That's useful to know. What number were you expecting? I want to understand where the gap came from — sometimes it's an old quote, sometimes it's a different scope entirely.
Totally fair reaction. Can I walk you through what's actually in the number? Most people are surprised by the price until they see what's underneath it, then they're surprised it isn't higher.

Power move

Ask for their expected number. It tells you their anchor, and anchors can be reset.

The reframe

Compare the whole transaction, not the product line item.

Say this

You probably can get the box cheaper. What's not in that price is the measurement, the install, the warranty, and the person who answers when something's wrong in year three. If you've got those covered, buying online is genuinely a reasonable move.
What's the total once you add shipping, install, and the time you'd spend managing it? I'd rather you compare the real numbers than have you feel like you overpaid.

Power move

Never mock the cheaper option. List what's missing from it and let them do the math.

The reframe

Answer specifically. Vague answers about 'quality' sound like a dodge.

Say this

Three concrete reasons, and you can decide if they matter to you. [Reason one]. [Reason two]. [Reason three]. If none of those are worth the difference to you, the other bid is the right call and I'll say so.
Honest answer: because we're not doing the same job. Let me put the two scopes side by side and you'll see the difference in about ninety seconds.

Power move

Name three specific differences. 'We're higher quality' is not an answer, it's an adjective.

The reframe

Yes. Say it calmly and immediately. Hesitation tells them the number was inflated.

Say this

It is. I price the same for everybody, which means the person who signed last week didn't get a worse deal for not asking. What I can flex is scope or timing if the number needs to come down.
Yes. And I'd rather tell you that straight than play a game where I come down five percent and you wonder what else was padded.

Power move

Instant, calm confirmation protects every future negotiation you'll ever have.

The reframe

Introduce the shopping tax — the real cost of the search itself.

Say this

You will find something cheaper. There's always something cheaper. The question is what it takes to find out whether it's actually comparable — three more calls, two site visits, and a couple weeks. What's that time worth to you?
Go ahead. Do me one favor though: when you get the other numbers, send them to me and I'll tell you honestly what's different. That way you're comparing scopes instead of just numbers.

Power move

Offer to help them compare. It positions you as an advisor and gets you the last look.

The reframe

Acknowledge it directly and explain without apologizing.

Say this

It did, and I'd rather explain than dodge. [Specific driver]. What I can tell you is that the increase is real cost, not margin — we held it as long as we could.
Yes. Here's what changed and here's what didn't. The scope is the same, the [material/labor/component] cost isn't. If it helps, locking in now protects you from the next one.

Power move

Never apologize for a price increase. Explain the driver and offer to lock the current number.

The reframe

Freezes are usually selective. Find out what's still getting funded and why.

Say this

Makes sense. Is that across the board, or is there still spending on things that protect revenue? Most freezes I see aren't total — they're just harder to get through.
Fair. Then let's not talk about spending. What would it take for this to be a cost-reduction conversation instead of a cost-increase one? Because that's a different meeting.

Power move

Reposition from expense to protection. Frozen budgets still fund things that stop losses.

The reframe

Scale the number to their actual revenue rather than to the feeling of the number.

Say this

It is real money and I don't want to minimize it. Let's put it against what it produces — if this brings in [X] over a year, what's the ratio look like from where you sit?
Small businesses feel every dollar, which is exactly why the decision matters. What would have to be true for this to feel like the right allocation instead of a big number?

Power move

Never say 'it's only.' Validate the size, then anchor it against the return.

The reframe

You presented before discovering, or you presented benefits they didn't ask for. Go backward.

Say this

That's fair, and it probably means I got ahead of myself. Let me back up — what would this need to do for you to be clearly worth it?
Help me out. Of everything I described, what mattered least to you? I'd rather cut what you don't need than argue for something you don't want.

Power move

'I don't see the value' is a discovery failure, not a closing failure. Return to discovery.

The reframe

Usually a good sign. Say yes if you can do it without setting up a failure.

Say this

I like that instinct. The only thing I'd caution is picking a piece too small to produce a result, because then we both learn nothing. Let me suggest the smallest version that still proves it.
Absolutely. Here's what a phase one looks like and here's what you'd know at the end of it that you don't know now.

Power move

Say yes to pilots, but define the success criteria in advance or you'll get a false negative.

The reframe

A buying question wearing a price objection's clothes. Answer it and move forward.

Say this

We do. Here's how it works. Which matters more to you — the lowest total cost, or the lowest monthly number? Those point to different options.
Yes. Let me show you what the monthly looks like, and let's compare it to what the problem is costing you monthly right now.

Power move

Financing questions are buying signals. Answer them and immediately ask a closing question.

The reframe

Rate is meaningless without output. Move to the total or the outcome.

Say this

Rate isn't the number that matters — total is. Somebody at half my rate who takes three times as long costs you more and takes longer. What's the total you're comparing?
Would you rather pay less per hour or less overall? I ask because those often point in opposite directions.

Power move

Convert hourly to total project or to outcome. Rate comparisons are almost always misleading.

The reframe

Respect the capability, then price the time honestly.

Say this

You probably could. The question is whether you want to spend the hours. How long do you think it'd take you, and what else would you not be doing during that time?
Genuinely, if you've got the time and the interest, do it yourself. What usually happens is people start, get eighty percent done, and it sits there for a year. If that's a risk, that's what I'm actually solving.

Power move

Never argue that they can't. Argue about the cost of their time and the risk of the eighty-percent stall.

The reframe

Give a real range with the variables attached, or you'll be anchored to the low end forever.

Say this

I can give you a range, but let me tell you what moves it so the number means something. Projects like this run [low] to [high], and the driver is [variable]. Where you land depends on [X].
Happy to. Fair warning — if I give you a number without knowing [key detail], I'll be wrong in one direction or the other. Give me two minutes of questions and the number will actually be useful.

Power move

Always attach the variable to the range. A bare ballpark becomes the price they remember.

The reframe

Explain what the paid version includes that the free one can't.

Say this

A free estimate is a guess made from the driveway. What we do is [specific work], and it takes real hours. If you want a rough number over the phone, I'll give you that for free right now.
Sure, and free estimates are worth exactly what you pay for them when the change orders show up. I'd rather charge you for a real number than surprise you later.

Power move

Contrast the free guess with the paid accuracy, and offer a free rough number to remove the sting.

The reframe

Free options cost time, risk, and results. Price those.

Say this

Free is a real option and for some people it's the right one. What free doesn't include is [X] and [Y]. If you don't need those, save your money.
The free version costs you time instead of money. Which of those do you have more of right now?

Power move

Never disparage free alternatives. Name the trade and let them choose.

The reframe

Find out what 'last time' actually included before you defend anything.

Say this

Then either prices moved a lot or the scopes are different. Tell me what was in the last one — I bet we find the difference in about a minute.
That's worth understanding. What did the last one cover, and how did it turn out? Sometimes the cheaper version is exactly why we're having this conversation now.

Power move

'How did that one work out?' often turns a price objection into your best argument.

The reframe

Build it with them, using their numbers, conservatively.

Say this

You should. Let's build it right now with your numbers, not mine. What's your average deal worth and how many are you losing to this problem?
Absolutely. And I'll be conservative on purpose — if the math only works with optimistic assumptions, I don't want you to buy it.

Power move

Build the ROI live, on the call, in their numbers. A model you hand them is a model they distrust.

The reframe

Find the next budget cycle and lock the decision to it, or find the emergency line.

Say this

Understood. When does the new budget open, and who builds it? Let's get this in the plan instead of fighting for scraps this year.
Is there a line for things that come up unexpectedly? Most organizations have one, and this may or may not qualify — depends how much the problem is costing between now and then.

Power move

Turn a dead 'no' into a calendared 'yes' by targeting the next budget cycle explicitly.

The reframe

Explain what the setup buys, then explore restructuring rather than removing.

Say this

The setup is the part that makes the monthly work — it's [specific labor]. What I can look at is spreading it, not removing it, because removing it means starting without the foundation.
Makes sense. Would it help if we split the setup across the first three months? Same total, easier landing.

Power move

Restructure the timing before you cut the amount. Cash flow is often the real issue.

The reframe

Fear of being trapped, not of the price. Address the exit, not the entry.

Say this

Totally reasonable. Here's what the exit looks like and what notice we need. Nobody's ever been held hostage — the term exists so I can staff it, not so you can't leave.
What specifically are you worried about? If it's that this doesn't work, let's talk about what happens in that scenario, because that's a real question and it deserves a real answer.

Power move

Explain the exit clause before they ask. It removes the trap feeling entirely.

The reframe

Matching a price without matching a scope teaches them your price was never real.

Say this

If I matched their number I'd have to match their scope, and then you'd be buying their thing from me. What I can do is show you exactly what the difference buys and let you decide if it's worth it.
No — and here's why that's actually good news for you. If I dropped fifteen percent because you asked, you'd rightly wonder what the first number was made of.

Power move

Refusing to match, calmly and with a reason, is more persuasive than matching.

The reframe

They're pricing the deliverable, not the expertise or the outcome. Reframe onto what it produces.

Say this

I get that — the deliverable looks simple because the point is for it to look simple. What you're paying for is knowing which version of it works, which took a lot of expensive learning.
What are you comparing it to in your head? I want to make sure we're valuing the same thing.

Power move

When the artifact looks simple, sell the judgment that produced it, not the artifact.

The reframe

Arm them for the internal conversation instead of trying to close around it.

Say this

Probably. What's the argument that would land with them? Let's build it together, because you're the one who has to make it and I'd rather you go in with the right numbers.
What matters most to them — the total, the monthly, or the risk of it not working? Different answers need different arguments and I want you to have the right one.

Power move

Never fight the absent person. Equip your champion to win the room you're not in.

The reframe

Don't get defensive. Get curious and stay warm.

Say this

Fair. What's the piece you'd never want to do yourself, if any? Sometimes there's a version of this where you keep the parts you like and I take the parts you don't.
I hear that a lot, honestly. What's it costing you in hours right now? If the answer is 'not much,' you're probably right to keep doing it.

Power move

Agreeing with a hostile objection defuses it faster than any rebuttal.

The reframe

They're reacting emotionally. Slow down and get specific before responding.

Say this

What number were you picturing? I'd rather understand the gap than argue about the number.
Say more — is it the total, or is it that you didn't expect this category to cost anything like this? Those are different conversations.

Power move

Emotional reactions need a question, not an answer. Ask and let the temperature drop.

The reframe

They're comparing two things that multiply each other, not two things that compete.

Say this

That might be right. Quick check though — what's your close rate on the leads you're already getting? If it's under twenty percent, more leads means more of them going to waste, and the ad money buys less than it looks like.
Fair. If you spend it on ads, how many extra conversations does that buy you? Now multiply by your current close rate. Then tell me what the same money does if the close rate moves seven points on the conversations you already have.

Power move

Never argue against their marketing. Show them the multiplication: leads times close rate, and ask which factor is cheaper to move.

The reframe

A fair question that usually hides a trust problem. Answer the structure, then find the real concern.

Say this

I've done it and I'll tell you why I usually don't: I control the process, not your pricing, your lead flow, or whether your reps show up. If I only get paid on an outcome I half-control, I'd have to charge triple for the risk and you'd pay more. What's the concern underneath it — that it won't work?
Here's a middle version: a reduced fee plus a defined bonus tied to one number we both agree I actually influence. Which number would you pick?

Power move

Counter with a shared-risk structure tied to a metric you genuinely control, and treat the request as a risk objection rather than a price one.

Timing objections

22

Delay is a decision with a cost. The move is always the same: find out what will actually be different later, and if the answer is nothing, name that gently.

The reframe

There's a specific unresolved concern. Find it now, while you're still in the room.

Say this

Completely fair. So I'm not guessing while you're thinking — what's the piece you want to think through? If it's something I can answer now, that saves you the thinking.
Of course. Most people who say that are weighing one specific thing. If you had to name it, what is it?

Power move

'What specifically?' Almost nobody has thought about it. They have one concern they didn't say.

The reframe

Separate 'bad moment' from 'bad idea.' One is scheduling, one is a real objection.

Say this

No problem. Is it a bad week, or a bad quarter? Those are different conversations and I don't want to waste your time on the wrong one.
Understood. When would be a good time — and I mean a real date, not a 'reach out later,' because we both know how that goes.

Power move

Always convert 'later' into a date on a calendar during the call. Vague later means never.

The reframe

Ask what will be different. If nothing will be, the delay is a decoy.

Say this

Happy to. What's going to be different in six months? If something specific changes then, I'll time it to that. If nothing changes, we'll be having this exact conversation again in the fall.
I'll put it in the calendar. Meanwhile — what's this costing you between now and then? Sometimes the waiting is the expensive part.

Power move

'What will be different?' exposes whether the delay has a reason or is just avoidance.

The reframe

Real constraint, usually. Respect it and get specific about the other side.

Say this

That's real and I won't push. When does that wrap? Let's put a conversation on the calendar for the week after, so it doesn't fall through the cracks.
Makes sense. Would it help to do the groundwork now so that when you come up for air, you're not starting from zero?

Power move

Offer to do the prep work during their busy period. It costs you little and keeps the deal warm.

The reframe

Book the date now, and quantify the cost of the gap.

Say this

Let's do it. What date works — I'd rather book it now than both of us hope we remember. And between now and then, what happens with [the problem]?
Sure. Quick question so I'm useful in that meeting: what would need to be true by then for it to be a yes?

Power move

Never accept a soft timeline. Get a date and get the criteria that make it a yes.

The reframe

Find out what, and whether it's actually a dependency or a stall.

Say this

What are you waiting on? I ask because sometimes it's a genuine dependency and sometimes the two things are independent, and it'd be a shame to lose a quarter to a sequencing assumption.
Got it. Does that thing have to finish, or just start? Sometimes we can run parallel.

Power move

Test whether the dependency is real. Many are assumed rather than actual.

The reframe

Busy season is often the strongest argument for acting now, not later.

Say this

Then this is exactly the wrong month to be doing it the old way. What does the busy season cost you in missed opportunity when the process isn't tight?
Understood. Would you rather go into the busy season with this fixed or fix it after you've already paid for another one?

Power move

Reframe the deadline as the reason to move, not the reason to wait.

The reframe

Fine, if it's a real reason. Book it and quantify the wait.

Say this

That's reasonable if it's a budget-cycle thing. Is it? Or is it more of a 'clean slate' feeling? Both are legitimate, but they lead to different plans.
Let's lock January then. One thing to consider — if we start the groundwork in December, you hit January running instead of starting from a blank page.

Power move

Distinguish a calendar reason from a psychological one. Only one of them is immovable.

The reframe

Take the pressure off explicitly, then define the next step.

Say this

I wasn't asking you to. What I'd like is to figure out what would make you ready, so the next conversation is productive instead of a repeat.
No pressure at all. What's the next step that makes sense to you? I'd rather move at your pace than push you into something you'll resent.

Power move

Explicitly removing pressure often produces more forward motion than applying it.

The reframe

Uncertainty is an argument for flexibility, not paralysis.

Say this

Fair. Does uncertainty make this more or less important? Sometimes the answer is genuinely less. Sometimes it's the thing that protects you when it gets rough.
What would have to settle down for this to make sense? If we can't name it, we might be waiting for a feeling rather than an event.

Power move

Ask what specifically has to resolve. Undefined uncertainty never resolves.

The reframe

Human and legitimate. Honor it and stay in orbit.

Say this

Completely get it. Let's not start anything now. Can I check back in [specific timeframe] — and in the meantime is there anything low-effort I can send that's actually useful?
Take the break. When you're ready, the groundwork we did today still applies, so we won't be starting over.

Power move

Respecting exhaustion earns goodwill. Pushing through it earns a permanent no.

The reframe

Small delay. Book past it and keep momentum.

Say this

Sure. First week of next month — Tuesday or Thursday work better?
No problem. I'll assume everything we discussed still stands unless you tell me otherwise, and we'll pick up where we left off.

Power move

Offer two specific dates instead of asking when. It's easier to answer and it books the meeting.

The reframe

Find out what result triggers a yes and what result triggers a no.

Say this

Makes sense. What does a good Q4 look like, and what does it mean for this if it goes the other way? I want to know if I should be planning for both.
Understood. If Q4 goes well, is this funded? I ask because sometimes a good quarter creates the budget and sometimes it removes the urgency.

Power move

Ask what happens in both scenarios. The answer tells you whether you have a real opportunity.

The reframe

The most common soft no in selling. Convert it or lose it.

Say this

I appreciate that. Can I be direct? 'I'll get back to you' usually means one of three things — you're not sold, you're not the decision, or you're being polite. Any of those is fine, I just want to know which so I don't chase you.
Sounds good. What's a realistic timeframe, and is it okay if I follow up if I haven't heard by then?

Power move

Name the three possibilities out loud. Giving permission to say no produces honesty.

The reframe

A polite exit. Make sending it conditional on learning something.

Say this

Happy to. So I don't send you forty pages you'll never open — what specifically do you want it to answer?
I'll send it. Quick question first, because the useful version depends on the answer: is this something you're actively looking to solve, or are you gathering for later? Both are fine, I'll just send different things.

Power move

Never send information without knowing what question it should answer.

The reframe

'Settled' is a feeling, not a date. Make it concrete.

Say this

What does settled look like? If we can describe it, we can watch for it. If we can't, we might be waiting on something that doesn't arrive.
Understood. In the meantime, is the current situation stable or slowly getting worse? Because those point different directions.

Power move

Force a definition of the vague future state. Undefined conditions never get met.

The reframe

You're losing to priority, not to a competitor. Find out what it would take to move up.

Say this

That's honest, thank you. What are they, and what would have to happen for this to jump ahead of one of them? I might not be able to make that case, but I'd rather know.
Fair. Are those three things bigger, or just earlier? Sometimes we're not competing on importance, just on queue position.

Power move

'Bigger or just earlier?' often reveals the queue is arbitrary and movable.

The reframe

Set the calendar and start earning the switch now.

Say this

Good to know. Let's put the renewal date in both our calendars and talk sixty days before it. Meanwhile, what would you want to be different in the next one?
Understood. Two questions: is it auto-renewing, and what's the notice period? Those matter more than the end date.

Power move

Auto-renewal and notice periods are where switches die. Get those dates early.

The reframe

Wrong time, right prospect. Play the long game gracefully.

Say this

Then I'm late and I'll say so. I hope it goes well — genuinely. Can I check in around the six-month mark, just in case anything's not going the way you hoped?
Fair enough. What made you go with them? I'm asking for my own learning, not to talk you out of it.

Power move

Grace here pays off in eight months when the honeymoon ends. Bitterness never does.

The reframe

Common and usually genuine. Book a real date on the far side.

Say this

Sounds good. What's the first week you're actually back and functional — I'll book it now so it doesn't drift to February.
Enjoy the break. I'll put something on the calendar for [specific date] and you can move it if you need to.

Power move

Book the meeting before the holiday, not after. Post-holiday outreach gets ignored.

The reframe

The hire is months away and the new person inherits whatever exists. Better to hand them something built.

Say this

Makes sense. One thing worth thinking about: whoever you hire will spend their first ninety days trying to work out how you sell. If it's already written down, they start coaching in week two instead of archaeology in month three.
Fair. What's the realistic timeline on that hire? And would having a documented process make the role easier to fill, or is it something you want them to own from scratch?

Power move

Position the documented process as a recruiting asset and an onboarding accelerator for the hire they haven't made yet.

The reframe

A real, dated constraint. Take it at face value and use the runway.

Say this

Then we won't touch anything until it's over. What's the actual date you come up for air? I'll book something for the week after so neither of us has to remember.
Understood. Does anything about how you sell change once it's over, or is it purely a bandwidth thing? If it's bandwidth, we can do the listening part now and the building part later.

Power move

When the constraint has a real date, book past it in the same conversation and offer to front-load the low-effort work.

Trust objections

22

Risk is the real currency here. Answer with proof, structure, and verifiable specifics, never with adjectives about yourself.

The reframe

Fair and unemotional. Answer with proof, not with protest.

Say this

That's fair — we're not the biggest name. What would help you get comfortable? References, examples of similar work, or something else? I'd rather give you the specific thing than a general reassurance.
Reasonable. Here's the short version of who we are and who we've done this for. If you want to talk to two of them before we go further, I'll set it up.

Power move

Ask what specific proof would help. Volunteering proof they don't care about wastes the moment.

The reframe

Answer with structure — milestones, guarantees, references — not with sincerity.

Say this

You don't yet, and I wouldn't expect you to take my word for it. What I can do is structure this so you see results before you're fully committed. Here's how that works.
The honest answer is that you're taking a risk. Here's how I reduce it: [milestones/guarantee/references]. Does that get you close enough?

Power move

Admitting the risk exists is more credible than promising it doesn't.

The reframe

A strong buying signal. Say yes fast and make it easy.

Say this

Absolutely. Do you want someone in your industry, someone your size, or someone who had a rocky start and came out well? I've got all three and the third one is usually the most useful.
Yes. Give me until tomorrow and I'll get you two people who'll actually pick up the phone.

Power move

Offer the reference who had problems and stayed. It's far more persuasive than a glowing one.

The reframe

Turn size into an advantage without dismissing the concern.

Say this

We are small, and that cuts both ways. You get me instead of whoever's free, and there's nobody between you and the person doing the work. What worries you specifically — capacity, or what happens if I get hit by a bus?
Fair concern. Here's how we handle [continuity/capacity]. And here's what you get from small that you can't get from large.

Power move

Ask which small-company risk they mean. Capacity and continuity need different answers.

The reframe

Answer with the specific person and the specific service structure.

Say this

Reasonable worry. Here's exactly who you'd work with, how often you'd hear from them, and what the response time commitment is. It's in writing.
Fair. Ask any of our smaller clients whether they feel like an afterthought — I'll give you their numbers.

Power move

Name the individual human who owns their account. Abstractions don't reassure.

The reframe

This is the most important thing they'll tell you. Slow down and get the whole story.

Say this

Tell me what happened. Seriously — I want the whole thing, because whatever went wrong is what I need to make sure doesn't happen here.
I'm sorry. That's more common than it should be. What would you need to see from me to feel like this is different?

Power move

Never rush past this. The story they tell contains the exact objection you must solve.

The reframe

Explain honestly and offer a substitute proof.

Say this

We don't have many, and that's on us — we've been bad about asking. What I can give you instead is direct references you can call today. Would that work?
Fair point. Here's why: [honest reason]. Here's what I can offer instead.

Power move

Never fake or excuse. Explain and substitute a stronger form of proof.

The reframe

Answer directly. If it's short, pivot to relevant experience.

Say this

[X years]. Before that, [relevant background]. What's behind the question — are you worried about staying power, or about whether we've seen your situation before?
Since [year]. What matters more to you: total years, or experience with your specific type of project? Those aren't always the same company.

Power move

Ask what the tenure question is really about. It's usually stability or competence, not the number.

The reframe

A qualifying question. Answer immediately with specifics and offer documentation.

Say this

Yes — [license number], [insurance details]. I'll send the certificates over today so you have them on file.
Yes, and you should be asking. Here's the documentation. Anybody who hesitates on that question is telling you something.

Power move

Volunteer the documentation before they ask twice. Speed here signals legitimacy.

The reframe

Agree and immediately name the downsides. Credibility comes from limitations.

Say this

Then let me tell you what it doesn't do, because I've probably oversold it. [Real limitation]. [Real limitation]. Still interested?
Healthy skepticism. Here's the catch: [honest trade-off]. If that's acceptable, the rest is real.

Power move

Volunteering a genuine limitation converts skepticism into trust faster than any proof.

The reframe

Don't be offended. Give them a verification path.

Say this

Reasonable question in this world. Here's how to check us out independently: [business registration, license lookup, references, physical address]. Don't take my word for any of it.
Verify me. [Specific verification steps]. I'd rather you check than take a leap of faith.

Power move

Give them independent verification paths. Self-vouching is worthless to a suspicious buyer.

The reframe

Answer with concrete continuity provisions.

Say this

Fair thing to plan for. Here's what you'd retain and how: [documentation/access/ownership]. Everything we build, you own.
Good question. The protection is that you own the assets, not me. Here's what that looks like in the agreement.

Power move

Ownership of deliverables is the answer. Make sure it's actually in your contract.

The reframe

Either be local or explain how proximity is replaced.

Say this

We're based in [location]. If local means being able to sit across a table, tell me — I travel for that.
Understood. What does local get you that matters most? If it's responsiveness or accountability, let me show you how we handle those, and if it's not enough, I'll say so.

Power move

Ask what 'local' is a proxy for. Usually it's accountability, which you can provide remotely.

The reframe

Take it on the chin. Defensiveness here is fatal.

Say this

You're right, and thanks for saying it. It's on the list. What I'd rather be judged on is the work — can I show you some?
Fair hit. We've been spending on delivery instead of on the site, which is arguably the wrong call. Let me show you what we actually produce.

Power move

Agreeing with a valid criticism builds more trust than any explanation.

The reframe

Name real ones. If you have none, say so and offer transferability.

Say this

[Specific names or descriptions]. Want me to walk you through one that looked a lot like your situation?
Honestly, none exactly like you. Here's the closest, and here's why I think the differences don't matter — but you tell me if I'm wrong.

Power move

Admitting a gap and arguing transferability beats stretching a weak analogy.

The reframe

Disagree with them about something, immediately.

Say this

Then let me tell you something you don't want to hear: [genuine caution or limitation]. I'd rather you buy this with your eyes open.
Fair — let me push back on something you said earlier. [Specific disagreement]. I'm not here to agree with everything.

Power move

Nothing rebuilds credibility faster than a well-placed, genuine disagreement.

The reframe

Agree, change the frame, and hand them control.

Say this

Neither do I, honestly. Can we do it this way instead — I ask questions, you decide if there's a fit, and if there isn't I'll tell you before you have to?
Fair. Then I won't. Tell me what's going on and I'll tell you whether I can help. If I can't, I'll say so and we're done in five minutes.

Power move

Offering to disqualify yourself removes the sales frame instantly.

The reframe

Agree, then differentiate with something checkable rather than a claim.

Say this

They do, and most of it is noise. So let me not claim anything — here are three things you can verify yourself. [Verifiable facts].
You're right. Instead of telling you we're different, let me ask you a question they probably didn't: [insightful discovery question].

Power move

Differentiate through the quality of your questions, not the volume of your claims.

The reframe

Yes, immediately and enthusiastically. Any hesitation is fatal.

Say this

Yes. Which part specifically — I'll get it into the agreement today.
Absolutely. If I say it, it goes in writing. What would you like included?

Power move

Instant yes. Hesitating on this question ends deals more than any price ever has.

The reframe

Answer honestly. A sanitized answer is obviously sanitized.

Say this

Two reasons, honestly. [Real reason one] — that one was on us and here's what changed. [Real reason two] — that one was a fit problem we should have caught earlier.
Some outgrow us, some weren't right in the first place, and one or two we let down. Want the specifics on the last category? That's the useful one.

Power move

Owning a failure with what you changed is the single most trust-building thing you can say.

The reframe

A new objection with an old shape. Prove provenance with specifics only a human who did the work would know.

Say this

Fair question, and the easy way to test it is to ask me something the material doesn't cover. Ask me why I dropped a section, or what happened the first time I tried it and it failed. Anything generated will answer smoothly. I'll answer specifically.
Some of the production is assisted, and I'd rather say that than pretend. The judgment isn't. Every script here came out of a real call I was on or reviewed. Pick any one and I'll tell you the conversation it came from.

Power move

Answer with a verifiable specific and a failure story. Generated material is fluent about successes and vague about scars.

The reframe

Speed reads as a template unless you show what was customized.

Say this

It came back fast because the structure is already built. What's customized is [specific list], and those came out of what you told me on Tuesday. If any of it reads generic to you, point at it and I'll show you where it came from.
Fair concern. Would you rather I sat on it for a week? Let me walk you through the three decisions I made specifically for your situation, and you can judge whether the speed cost you anything.

Power move

Name what was custom and offer to trace each element back to something the buyer said.

Authority objections

16

Either they genuinely cannot decide, or they can and are using someone else as cover. Find out which, then equip your champion for the room you will not be in.

The reframe

Find out whether they're the decision or hiding behind one, then equip them.

Say this

Of course. Quick question — if they said yes right now, would you? I ask because if you've got reservations of your own, I'd rather solve those first.
Makes sense. What's likely to be their biggest concern? Let's get ahead of it so you're not defending it alone.

Power move

'If they said yes, would you?' separates a real approval step from a polite exit.

The reframe

Become the champion's ally in the meeting you won't attend.

Say this

Understood. What does your boss care most about in a decision like this? I'll get you the one-pager that speaks to exactly that.
Makes sense. Would it help if I joined that conversation, or would you rather go in alone with the numbers? Either is fine — I just don't want you unarmed.

Power move

Always offer to join the internal meeting. Half say no, but the offer costs nothing and signals confidence.

The reframe

Board decisions need a written business case, not a conversation.

Say this

Got it. When does the board meet, what format do they expect, and who presents it? Let me build the version that fits their process instead of a generic proposal.
Understood. What kills proposals in that room, historically? I'd rather design around the objection than discover it after the vote.

Power move

Ask what has failed in that room before. It's the fastest way to build a winning submission.

The reframe

Find out what they are — influencer, gatekeeper, or researcher — and route accordingly.

Say this

No problem. What is your role in it — are you gathering options, or do you have a recommendation? Both are important and I'd handle them differently.
Understood. Who is, and what's the best way to get in front of them? Also — what would make you personally comfortable recommending this?

Power move

Never discard a non-decision-maker. Recommenders and blockers both control outcomes.

The reframe

Team resistance is usually about change, not about you. Help them handle it.

Say this

Smart — this fails without them. What's the objection you expect from the team? Let's plan for it rather than hope.
Would it help if I did a short session with them? Sometimes hearing it directly removes the sense that it's being done to them.

Power move

Offer to address the team directly. It converts your champion's risk into your responsibility.

The reframe

Procurement optimizes price unless someone gives them criteria. Get the criteria set before you're routed.

Say this

Understood. Before it goes to them — can we agree on what the requirements actually are? Otherwise it becomes a price comparison between things that aren't comparable.
Got it. What's the process and timeline? And who defines the specification they'll evaluate against?

Power move

Whoever writes the spec wins the RFP. Try to be helping write it before it exists.

The reframe

Give them financially literate material rather than sales material.

Say this

Absolutely. What would they want to see — the payback math, the tax treatment, the cash flow impact? I'll put together whatever's most useful.
Makes sense. Most accountants ask the same three questions. Let me answer them in advance so it's a five-minute conversation.

Power move

Prepare material in the language of the reviewer, not the language of the buyer.

The reframe

Map the group. Every group has an owner, an advocate, and a skeptic.

Say this

Makes sense. Who's in the group, and is there anyone likely to push back? I'd rather know now than find out from a forwarded email.
Understood. How do you usually break a tie? I'm asking because I want to make sure the right information gets to whoever ends up deciding.

Power move

Ask who the likely skeptic is. Then solve for them specifically.

The reframe

Get both people in the conversation, gracefully.

Say this

Then let's make sure they're part of this. When are you both usually free? I'd rather answer their questions directly than have you relay mine.
Makes sense. What matters most to them in a decision like this? I want to make sure we're addressing the right things.

Power move

Never let the financial decision-maker be absent. Reschedule rather than proceed.

The reframe

Either scope under the threshold or arm them for the approval.

Say this

Good to know. Two options — we scope a phase one that sits under that line, or we build the case for the approval. Which is more realistic here?
Understood. Who approves above that, and what do they need to see? Let me make that easy.

Power move

Threshold objections are the easiest authority objection to solve. Just scope under it or arm them.

The reframe

Offer a structured way to gather that reaction.

Say this

Reasonable. Rather than a hallway poll, would a short session with them give you a cleaner read? I'll run it and you watch.
Makes sense. What reaction would tell you yes, and what would tell you no? I'd hate for lukewarm to get read as negative when it's just unfamiliar.

Power move

Define in advance what reaction counts as a green light, or ambiguity becomes a no.

The reframe

A gap is an opportunity, not just a delay.

Say this

That's tough. Does the work stop while the role is open, or does someone absorb it? If it's the latter, this might matter more right now, not less.
Understood. Would having this documented make the next person's onboarding easier? Sometimes a vacancy is the best time to fix a process.

Power move

Vacancies create urgency. The pain of the gap is felt daily by whoever absorbed the work.

The reframe

Their personal risk is the real objection. De-risk them, not the purchase.

Say this

That's the real question and I appreciate you saying it. What would make this a safe recommendation for you personally? A pilot, a guarantee, a reference from someone they respect?
Understood. Let's make sure you're not the one holding the bag if it goes sideways. Here's how we structure that.

Power move

When personal career risk is the objection, structure and guarantees matter more than features.

The reframe

Unanimity means one skeptic can kill it. Find them first.

Say this

Then let's find the hardest person to convince and start there. Who is it?
Understood. Rather than presenting to everyone at once, would it help to talk to the most skeptical person first? Their questions usually improve the whole proposal.

Power move

In unanimous-consent environments, sell to the skeptic first. Everyone else follows.

The reframe

Find out whether it's a rule, a preference, or an approved-vendor process nobody has run in years.

Say this

Is that a written policy or a habit? I ask because approved-vendor lists usually have a path onto them and nobody uses it. If there's a form, I'll fill it out.
Understood. Does the restriction cover training, or purchasing? Sometimes a documented process build lands in a different category than a training program, and that's worth ten minutes with whoever owns the policy.

Power move

Ask whether the restriction is written down. Half of corporate 'can't' is an unexamined 'nobody has.'

Need objections

16

A need objection means discovery failed. Do not present harder. Go backward and find a problem they will admit to owning.

The reframe

Discovery failed or there genuinely is no problem. Find out which without arguing.

Say this

Then you probably don't need me, and I'd rather say that than push. Just so I understand — what's working best right now?
Fair. Can I ask one question and then get out of your way? If you could change one thing about how [area] works, what would it be?

Power move

Offering to disqualify yourself is the most reliable way to get an honest answer here.

The reframe

Go backward to discovery. Presenting harder makes it worse.

Say this

You might be right. What made you take the call in the first place? There was something, and I'd like to understand it before I agree with you.
Fair. Help me understand what you're already doing about [problem area] — if it's handled, we're done.

Power move

Never argue that someone has a problem. Ask questions until they describe one or confirm there isn't.

The reframe

Find the delta between what they have and what they wish they had.

Say this

Good. What do they handle, and is there anything falling outside that? I'm not looking to replace anyone — sometimes the gap is the interesting part.
Makes sense. If you could add one capability to what they do, what would it be?

Power move

Position as complement first. Displacement conversations can come later if the gap is real.

The reframe

Priority is relative. Find out what it's losing to and why.

Say this

Fair. What is a priority right now? I might not be relevant to that, but if I am, that's the conversation we should be having.
Understood. What would make it one? Sometimes it's a number, sometimes it's a deadline, sometimes it's a bad month.

Power move

Ask what's above it on the list. Sometimes you can attach to the thing that's already funded.

The reframe

Fine is a low bar and everyone knows it. Explore the edges gently.

Say this

Good — that puts you ahead of most. Where does it strain? Every process has one place it breaks, usually under volume or when someone's out.
Fair. What happens when [volume spike / key person is out / edge case]? That's usually where I find the interesting part.

Power move

Probe the edge cases. Processes fail at the boundaries, not in the middle.

The reframe

Believe them, and ask about an adjacent one.

Say this

Good, glad to hear it. Is [adjacent problem] something you deal with? If not, I'll let you go and you've got my number if things change.
Okay. Out of curiosity — how do you avoid it? Most companies your size struggle with that and I'd genuinely like to know.

Power move

Asking how they solved it is flattering, disarming, and occasionally reveals they haven't.

The reframe

Ask them to teach you. You're missing information.

Say this

Then teach me — how does it work? I'd rather understand your model than pitch something that doesn't fit it.
Fair, I probably made an assumption. Walk me through how [process] actually happens on your end.

Power move

Curiosity beats correction. Let them describe the model and the fit will become clear either way.

The reframe

Get the full story of the failure. It's your entire roadmap.

Say this

Tell me what happened. What did you try, how long did you give it, and where did it break down? That's the most useful thing you could tell me.
I'm sorry that happened. What would have had to be different for it to work?

Power move

The failure story tells you exactly what your proposal must address to be credible.

The reframe

Adoption is a real risk and a real objection. Address it structurally.

Say this

That's a legitimate concern and it kills more of these than anything else. What's failed to get adopted before, and why do you think that was?
Fair. What would make it something they actually want rather than something imposed on them? That's usually the whole game.

Power move

Adoption objections are the most honest ones you'll hear. Take them seriously or you'll fail in month three.

The reframe

Right-size the offering or honestly disqualify.

Say this

You might be. What size do you think this is built for? Let me tell you where the line actually is, and if you're under it I'll tell you.
Fair. There's a smaller version that makes sense for a team your size — want me to describe it, or is this genuinely not the moment?

Power move

Being willing to say 'you're too small' honestly makes the times you say 'you're not' believable.

The reframe

Demonstrate scale credibility with a specific comparable.

Say this

Reasonable concern. What's the biggest thing you'd need it to handle? Let me tell you honestly whether we've done that.
Fair. The largest deployment we've run is [specific]. If you're bigger than that, I'll tell you where the edges are.

Power move

Give a real ceiling number rather than claiming unlimited scale. Specificity reads as honesty.

The reframe

Look for capacity, expertise, or opportunity-cost gaps.

Say this

Makes sense. Is that person doing it as their whole job, or is it one of several things? That's usually where the gap shows up.
Good. What's the piece they'd most want off their plate, if you asked them?

Power move

Ask what the internal person would want to hand off. They'll often tell you themselves.

The reframe

Stop presenting. Ask what they're actually dealing with.

Say this

Then I've missed something. Forget what I described — what's the thing that's actually bugging you about [area] right now?
Fair. Let me start over. What made this worth twenty minutes of your time today?

Power move

When relevance is questioned, abandon the presentation entirely and restart discovery.

The reframe

Good times are the best time to build systems and the hardest time to sell them.

Say this

That's exactly why it's worth asking. Systems get built during good times because during bad times there's no room. What breaks first if you doubled volume tomorrow?
Genuinely happy to hear it. Does the current setup scale with where you're headed, or does it start straining at some point?

Power move

Growth is the vulnerability of the successful. Ask what breaks at 2x.

The reframe

Be genuinely useful. Research-stage buyers remember who helped.

Say this

Perfect, that's the right time to talk. What are you trying to figure out? I'll answer straight and tell you when something's outside what I do.
Great. What's the question you most want answered by the end of your research? Let me just answer it now.

Power move

Being maximally useful to a researcher costs one call and often wins the deal three months later.

The reframe

Experience is repetition, not necessarily calibration. Look for the gap between tenure and consistency.

Say this

Then they know more about your product than I ever will, and I'd be an idiot to teach them selling. What I'd want to know is whether they all do it the same way. Do they? Because twenty years of three different methods is the hardest thing to hand to a new hire.
Fair. Here's the question I'd ask them: can they write down what they do? Most veterans can't, and that's not a criticism. It's why the knowledge can't leave their heads.

Power move

Never challenge a veteran's ability. Challenge whether their method is transferable, which it usually isn't.

Competitor objections

17

Switching cost, not dissatisfaction, is usually the barrier. Never attack the incumbent, because you are insulting a decision your buyer made.

The reframe

Happy rarely means perfect. Look for the one percent they'd change.

Say this

Good — I'd never ask you to leave someone who's doing right by you. If you could wave a wand and change one thing about how they work, what would it be?
That's great to hear. Can I stay in touch anyway? Things change, and I'd rather be the call you already know than a cold one.

Power move

'What one thing would you change?' finds the crack without insulting their choice.

The reframe

Respect the relationship. Attacking it attacks their judgment.

Say this

That says good things about both of you. I'm not looking to disrupt that. Is there any part of the work they don't cover?
Fifteen years is real. What's kept it going that long? I ask because whatever that is, it's the bar I'd have to clear.

Power move

Never attack a long incumbent. Look for scope gaps beside them, not displacement.

The reframe

Compare scopes, not numbers.

Say this

They may well be. Can I see what's in their number? If it's the same scope, that's a real conversation. Usually it isn't, and I'd rather show you where than just claim it.
Probably. What's the difference in what you'd get? If you can't tell, that's actually the problem worth solving before you decide.

Power move

Ask to see the competing proposal. It's the fastest route to an apples-to-apples conversation.

The reframe

Tenure and results aren't the same thing. Redirect without dismissing.

Say this

True. Does longer mean better for what you need, or does it just mean longer? Genuinely asking — sometimes it does.
They have. What matters more to you — years in business or experience with your specific situation? Let's compare on the one that actually predicts your outcome.

Power move

Convert 'longer' into 'more relevant experience' — a comparison you may actually win.

The reframe

Don't compete with friendship. Compete beside it or wait.

Say this

Then you should absolutely give them the shot. I mean that. If it doesn't work out, or if there's a piece outside what they do, I'm here.
Understood, and I'd do the same. Would it be useful to have a second opinion on scope, just so you know what you're comparing? No obligation.

Power move

Offer value without asking for the business. Relationships beat pitches, but not forever.

The reframe

That's a fixable, factual criticism. Fix it fast.

Say this

Fair criticism. Tell me what was in theirs that wasn't in mine and I'll get you a version that answers all of it by tomorrow.
Then mine was incomplete. What were the sections that mattered most to you? Let me redo it properly.

Power move

A proposal criticism is a gift. Fix it same-day and you demonstrate responsiveness in the process.

The reframe

Compare the value of the extras honestly. Don't reflexively match.

Say this

What did they include? If it's something you actually need, let's talk about it. If it's something you'd never use, it's not a discount — it's a distraction.
I could throw things in too, but I'd rather ask: of those extras, which would you genuinely use?

Power move

Free extras are only value if they're wanted. Ask before you match.

The reframe

Stop pitching. Differentiate with a question they haven't been asked.

Say this

That's a fair complaint. Let me try something different — nobody's probably asked you this: [specific, insightful discovery question].
Then I'll stop talking about us. Tell me what none of them asked about, and let's go there instead.

Power move

Sameness is a symptom of pitching. Differentiate through the depth of your questions.

The reframe

Never compete with family. Compete on the consequences of it going wrong.

Say this

Then use him — seriously, family first. One thing to think about: if something goes sideways, how does that conversation go at Thanksgiving? Some people are fine with it, some aren't.
Makes sense. Is he set up to handle [specific requirement]? If yes, go with him. If not, I'm around.

Power move

Raise the relationship risk gently and once. Then let it go.

The reframe

Explain what you can guarantee and why the other guarantee may be hollow.

Say this

Ask them what happens when the guarantee is invoked — the mechanism matters more than the promise. What I guarantee is [specific, enforceable thing], because I can actually control that.
I don't guarantee outcomes I don't control, and I'd be careful with anyone who does. What I do guarantee is [specific]. Is that enough?

Power move

Attack the enforceability of the guarantee, not the guarantee itself.

The reframe

Get in before the spec is written or accept you're the price benchmark.

Say this

Happy to bid. Before I do — has the specification been finalized? If there's still input to be had, I'd rather help define what good looks like than respond to somebody else's definition.
Understood. Who wrote the requirements, and what's the evaluation weighting? That tells me whether it's worth both our time.

Power move

If the spec is written and you didn't influence it, you're probably column fodder. Find out early.

The reframe

Ask for specifics, then supply the missing proof.

Say this

What did theirs have that mine didn't? If it's someone in your exact situation, let me find you one — I probably picked the wrong references.
Fair. Who would you want to hear from? Give me the profile and I'll find them.

Power move

Let the buyer specify the reference profile. Then deliver exactly that.

The reframe

Sometimes fine, sometimes a coordination disaster. Say which honestly.

Say this

That can work. Where it usually breaks is [specific handoff]. Who owns that seam? If nobody does, that's the risk.
Understood. Which half would you want us on, and who arbitrates when the two approaches conflict?

Power move

Name the coordination risk. If it's real, you become the adult in the room.

The reframe

Compare what 'done' means in each timeline.

Say this

They might be able to. What does their timeline assume — and what does 'done' include? Faster usually means something got moved to later or dropped.
Possibly. Is speed the priority here, or is it doing it once? I can go faster too, I'd just want you to know what changes.

Power move

Speed claims usually hide scope cuts. Ask what 'complete' means in their timeline.

The reframe

You need a reason bigger than 'we're better.' Find their specific frustration.

Say this

Honestly, if nothing's broken, you shouldn't. Switching costs you time and risk. What I'd want to know is whether there's something that bugs you enough to be worth that.
You probably shouldn't unless there's a specific thing that isn't working. Is there?

Power move

Telling them not to switch unless there's a reason makes you credible when a reason appears.

The reframe

Popularity is a proxy for safety, not for fit. Explore gently.

Say this

That's usually a good sign. It also means everyone in your industry has the same capabilities. Is there an advantage in doing something different, or is standardization the point here?
Fair. Does that make them the best fit for you, or the safest choice? Both are legitimate answers.

Power move

'Best or safest?' is a gentle way to surface conformity as a decision driver.

The reframe

A platform stores and delivers content. It does not decide what the content should say.

Say this

Good, that solves distribution. What's loaded into it? Most platforms I see are full of product training and almost empty on what to say when a buyer pushes back. If yours has that, you're ahead of nearly everyone.
Makes sense. Would it help if what I build got loaded into the platform you already own? I'd rather use your rails than sell you new ones.

Power move

Never fight the tool. Offer to fill it, and ask what is actually inside it today.

Status Quo objections

15

The hardest competitor in every market is doing nothing. Inertia costs zero today and everything eventually. Your job is to make the invisible cost visible.

The reframe

Respect the history, then ask what it was designed for.

Say this

Usually for a good reason. What was going on when you set it up that way? Sometimes the reason is still true and sometimes the business outgrew it.
Fair. Is it still producing what you need, or is it just familiar? No judgment either way.

Power move

Ask what conditions the process was designed for. Those conditions have usually changed.

The reframe

Agree with the principle, then test whether it's actually not broken.

Say this

Agreed as a rule. So let's check — is it not broken, or is it broken in a way you've gotten used to? Those feel identical from the inside.
Fair enough. What would 'broke' look like? If we can define it, you'll know when you get there.

Power move

'Broken or just familiar?' is the single best question for status quo objections.

The reframe

Quantify the disruption honestly, then compare it to the ongoing cost.

Say this

Then let's talk about how much disruption we're actually talking about, because I think it's less than you're picturing. Here's who does what and when.
Fair. What if we phased it so nothing changes for the front line until [milestone]? Most of the disruption fear is about the first week.

Power move

Break the change into phases. Disruption fear is about the transition, not the destination.

The reframe

Comfort is real and worth respecting. Find whether it's masking friction.

Say this

That matters — adoption is usually the hard part. If you asked them what annoys them most about the current setup, what would they say?
Fair. Is comfortable the same as effective here, or are there workarounds people have built up?

Power move

Ask about workarounds. Every comfortable-but-broken system is held together by them.

The reframe

Price the build honestly, including the maintenance nobody budgets for.

Say this

You could. What's the realistic timeline with your current team, and who maintains it after? The build is usually the cheap part.
Makes sense if it's core to what you do. Is it? If it's supporting work, building it means you own it forever.

Power move

The maintenance cost, not the build cost, is what kills internal builds. Say so.

The reframe

This is factually wrong almost always. Make the invisible cost visible.

Say this

Let's test that. You said [problem] takes about [X] a week. Over a year that's [Y]. That's not nothing — it's just not on an invoice.
It feels that way because nothing gets billed. What's the number if we count the time and the missed opportunities?

Power move

Convert the status quo into a line item with a dollar figure. Invisible costs feel like zero.

The reframe

Absence of complaints is not evidence of health.

Say this

Do people complain here generally, or do they just work around things? Those look the same from the top.
Fair. Has anyone asked them directly? Complaints usually stop long before the frustration does.

Power move

Silence often means people gave up complaining, not that the problem stopped.

The reframe

Waiting is a decision with a cost. Name it neutrally.

Say this

That's a legitimate choice. What are you watching for? If we know the signal, we'll both recognize it.
Fair. What does waiting cost between now and then? If the answer is nothing, waiting is clearly right.

Power move

Ask what signal they're watching for. Undefined waiting continues indefinitely.

The reframe

Find the threshold where it does justify it, and how close they are.

Say this

Fair. What would make it bad enough? I want to know if we're talking about next month or next decade.
Understood. Is it getting worse, staying flat, or improving? That's the number that matters more than where it is today.

Power move

Trend matters more than current state. A tolerable problem getting worse is urgent.

The reframe

Believe them, and check whether your thing feeds theirs.

Say this

Probably true. What are they? There's a chance this is upstream of one of them, and if it isn't I'll get out of your way.
Fair. Is this related to any of them, or genuinely separate? If separate, let's talk when the fires are out.

Power move

Look for the upstream connection. Sometimes your small problem causes their big one.

The reframe

Get the whole story. It defines what your implementation must avoid.

Say this

Tell me what happened. Specifically — I need to know what to build around so we don't repeat it.
That's exactly the thing to plan for. What was the moment it went wrong?

Power move

The disaster story is your implementation plan. Ask for it in detail and design around it.

The reframe

Acknowledge the honesty and quantify the muddling.

Say this

Honest answer, and sometimes it's right. What's muddling through costing you a month? If it's small, keep muddling.
Fair. When does muddling stop working — is there a volume or a date where it breaks?

Power move

Find the breaking point. Muddling has a ceiling and they usually know where it is.

The reframe

Old systems fail suddenly. Explore the contingency.

Say this

Fair. What's the plan if it stops working on a Tuesday? Old systems usually don't degrade — they just stop.
Understood. Is anyone still supporting it, and how hard would it be to replace under pressure?

Power move

Legacy systems fail catastrophically, not gradually. Ask about the emergency plan.

The reframe

The objection is political, not practical. Address the politics.

Say this

Understood — that's a real consideration. Who would be most likely to push back, and is there a version of this that doesn't threaten them?
Fair. Is there a way to do this that makes someone look good rather than makes someone look wrong?

Power move

Internal politics kills more deals than price. Ask who would be threatened and solve for them.

The reframe

Waiting for a technology to settle is waiting forever. Ask what decision the answer would actually change.

Say this

Reasonable thing to be watching. Here's the thing though — whatever tooling shows up still needs somebody to decide what a good conversation sounds like. That decision is the thing I'd be helping you write down, and it survives whatever the tools do.
Fair. What would you do differently depending on how it goes? If the answer is 'nothing yet,' then waiting is costing you a year of the same conversations.

Power move

Separate the tooling question from the method question. Tools change fast, and what a good conversation sounds like changes slowly.

Risk objections

17

Fear of a visible, blameable mistake. De-risk with pilots, phasing, guarantees, and a written picture of what happens if it goes wrong.

The reframe

Answer concretely rather than reassuring. Describe the actual failure scenario.

Say this

Then here's what happens: [specific remedy, refund, or exit]. I'd rather tell you the plan for failure than pretend it can't happen.
Good question. Let's define what 'not working' would look like and at what point, and agree in advance what we do about it.

Power move

Define failure and the remedy in advance. It removes the fear and it's just good practice.

The reframe

State it precisely. Vague guarantees read as no guarantee.

Say this

Here it is exactly: [specific terms, timeframe, mechanism]. And here's what it doesn't cover, so there are no surprises.
[Specific guarantee]. I don't guarantee things outside my control, and I'd be cautious of anyone who does.

Power move

State the exclusions unprompted. It makes the inclusions believable.

The reframe

Reduce exposure with phasing and checkpoints rather than promises.

Say this

Let's structure it so you can't waste much. Here's a first phase with a defined result — if it doesn't land, you stop and you've risked [small amount] instead of everything.
You don't yet. What would need to happen in the first thirty days for you to feel good about continuing?

Power move

Convert a large irreversible bet into a small reversible one. Risk objections dissolve.

The reframe

Describe the exit clearly and calmly.

Say this

Then here's how you get out: [notice period, terms, what you keep]. No drama and no lawyers.
Fair. What would 'not liking it' look like? Let's define it now so we both recognize it, and let's agree what happens if we get there.

Power move

A clean, stated exit path is more persuasive than any promise of satisfaction.

The reframe

Answer with a specific capacity number and a scaling plan.

Say this

Our current ceiling is [specific]. You'd be at [X percent] of that. Here's what we do if you grow past it.
Fair. What volume are we talking about at peak? Let me tell you honestly whether that's comfortable or a stretch.

Power move

Give a real capacity number. Claiming unlimited capacity is not believable.

The reframe

Answer with documentation and process, not with reassurance about loyalty.

Say this

Here's how we handle it: everything is documented, [second person] is familiar with the account, and handoff takes [timeframe]. Nothing lives in one head.
Good question and it happens. The protection is that the process is written down, not that nobody ever leaves.

Power move

Continuity is a documentation question. Answer it structurally.

The reframe

Walk them through the actual sequence, hour by hour.

Say this

Let's walk through it. Week one, you do [X] and it takes about [Y] hours. Week two, [X]. Most of the worry disappears when it's specific.
Fair. What part concerns you most — the time it takes, the disruption, or whether it'll actually get finished?

Power move

Specificity kills implementation anxiety. Vague reassurance amplifies it.

The reframe

Describe the flexibility mechanism concretely.

Say this

Here's how we adjust: [specific mechanism, notice, cost]. It's designed for that because everybody's needs change.
Fair. What kind of change are you anticipating? Let me tell you specifically how that would work.

Power move

Ask what change they anticipate. It usually reveals something useful about their plans.

The reframe

Right-size it or acknowledge the weight honestly.

Say this

It is, and I don't want to talk you out of feeling that. What's the smallest version that would still tell you whether this works?
Fair. What makes it feel big — the money, the time, or that it's hard to undo? Each of those I'd handle differently.

Power move

Ask which dimension feels big. Money, time, and reversibility need different answers.

The reframe

Build a conservative case and define the checkpoint.

Say this

Let's set a checkpoint. At [timeframe], here's what should be true. If it isn't, we've both learned something and you can stop.
Fair. Let's build the number conservatively — if the math only works on optimistic assumptions, I don't want you to do it.

Power move

Set a named checkpoint with named criteria. It converts a leap of faith into a test.

The reframe

Answer precisely from the agreement.

Say this

Here's exactly how liability works in our agreement: [specific terms]. Want me to send the clause so your attorney can look at it?
Good question. [Specific answer]. It's in writing and I'd rather you read it before signing than after something happens.

Power move

Point directly at the contract language. Improvised liability answers are dangerous.

The reframe

If they'd be first, say so and price the risk in.

Say this

You wouldn't be — here's who's done this before. But if you were, I'd tell you and we'd structure it accordingly.
Fair. If it makes you more comfortable, let's structure it so the risk sits with me rather than you: [specific structure].

Power move

Never hide being early. Structure the risk onto yourself and say so.

The reframe

Name a real trade-off. Denying a catch confirms one exists.

Say this

The catch is [genuine trade-off or limitation]. If that's acceptable, there isn't another one.
Fair to ask. Here's what people find hardest about working with us: [honest thing]. Not a trick, just a real cost.

Power move

Always have a real answer to 'what's the catch.' 'There isn't one' is never believed.

The reframe

Meet it with documentation or disqualify honestly.

Say this

Good. What standard do you need to meet? Let me tell you honestly whether we clear it and where the gaps are.
Understood. Here's what we hold and how: [specifics]. If you need [standard] and we don't have it, I'll tell you rather than waste your compliance team's time.

Power move

Honesty about a compliance gap costs one deal. Discovered dishonesty costs your business.

The reframe

Answer with a transition plan, not a denial.

Say this

Then we'd help you transition. Everything is yours and documented — that's deliberate, so that leaving is clean if it ever makes sense.
Honest answer: at [size] you'd probably need something different. Here's what that looks like and how we'd hand off.

Power move

Planning for their success, including outgrowing you, is deeply persuasive.

The reframe

Answer immediately and completely. Hesitation is fatal.

Say this

[Notice period], [what you keep], [what happens to the work]. No penalty beyond [specific]. Want me to walk through the clause?
Easy: [specific exit terms]. I'd rather have clients who stay because they want to.

Power move

Instant, complete exit answers are one of the strongest trust signals available.

The reframe

The older version of this question answers itself. Ask the opposite one.

Say this

The answer everybody gives is 'what if you don't and they stay,' and it's a cheap line, so let me give you the real one. Reps leave because they're failing and nobody can tell them why. Training is one of the few things that reduces the turnover you're worried about.
Fair risk. Here's the structural protection: the process is documented and owned by you, not carried in their heads. If they leave, the method stays. That's the whole point of writing it down.

Power move

Answer with the structural protection, not the cliché. Documented process means the investment stays with the company.

Fit objections

15

They think you built this for somebody else. Answer with a near-identical case at their exact scale, not with reassurance.

The reframe

Agree that it's different, then find the structural similarity.

Say this

Every industry is, in the specifics. What's the part you think wouldn't translate? Let me either address it or agree with you.
Fair. What's most different about how buying decisions get made in your world? That's usually where it matters.

Power move

Ask which specific element wouldn't translate. It's usually one thing and it's usually solvable.

The reframe

Take it seriously. Everyone believes it and occasionally it's true.

Say this

Tell me what makes it unique — I'd rather understand than assume it's like something else.
Fair. What's the thing about you that most people don't get when they first hear about it?

Power move

Genuine curiosity here builds more rapport than any rapport-building technique.

The reframe

Agree instantly and ask to be taught. Defending is fatal.

Say this

You're right, I don't — not yet. Teach me. What's the thing outsiders always get wrong about what you do?
Fair. Rather than guess, walk me through a typical [week/deal/customer] and I'll shut up and listen.

Power move

'You're right, teach me' converts a hostile objection into a discovery session.

The reframe

Right-size the example immediately.

Say this

Fair — the version I described probably is too heavy. Here's what it looks like at your scale.
Let me use a better example. [Specific comparable at their size]. Does that land closer?

Power move

Always have a comparable at their exact scale ready. Abstract scaling claims fail.

The reframe

Remove the intimidation. This is usually confidence, not capability.

Say this

You're probably more ready than you think. What part sounds complicated? I bet it's simpler than it came across, and if it isn't, we simplify it.
Fair. Let's find the version you'd actually use rather than the version that impresses people at conferences.

Power move

Sophistication objections are self-esteem objections. Simplify and reassure without condescending.

The reframe

Adjust the framework to their cycle rather than defending yours.

Say this

Then the framework changes shape. How long is a typical cycle, and how many touches? Let me map it to what you actually run.
Good to know. What are the natural stages in your cycle? Let's build around those instead of a generic template.

Power move

Never force a framework onto a mismatched cycle. Rebuild it around their actual stages.

The reframe

Technical buyers need different framing, not softer selling.

Say this

Then the last thing they want is a pitch. What questions do they ask that your reps struggle with? That's usually where the work is.
Understood. Technical buyers respond to being taught something, not persuaded. Does your team have anything to teach them?

Power move

With technical buyers, insight beats enthusiasm. Ask what your team can teach them.

The reframe

If it did, they wouldn't take the call. Explore gently.

Say this

Then you're in a great position. What happens with the ones that don't close — is there a pattern?
Good problem to have. Are you converting everyone who inquires? Because if not, something's happening in the gap.

Power move

Ask about the deals that don't close. The pattern in the losses is the real conversation.

The reframe

Owner-sellers and accidental sellers need the process more, not less.

Say this

Then this matters more, not less. Whoever's talking to customers is selling, whether it's on their business card or not. Who's doing it now?
Understood. Is it you, or is it whoever picks up the phone? Both are common and both are fixable.

Power move

'No sales team' usually means untrained people selling by accident — the highest-leverage situation.

The reframe

Inbound selling is still selling, and it's often worse for being unexamined.

Say this

Then the conversations you're having matter more, because they're already interested. What's your conversion on inbound inquiries?
Good position. What happens between the inquiry and the sale? That's the part I'd want to look at.

Power move

Inbound teams often have the worst processes because nobody thinks they're selling.

The reframe

Simplicity makes systematization easier and more valuable, not less.

Say this

That's ideal, actually. When there's one sale, you can get it near-perfect and every rep can run it identically. What does the current version look like?
Then we can optimize one conversation instead of forty. What's the most common reason someone doesn't buy?

Power move

Single-product sales are the easiest to systematize and produce the fastest results.

The reframe

The channel changes, the structure doesn't.

Say this

Then the framework applies to text — the sequence is the same, it's just shorter. Can you send me a few threads so I can see the actual pattern?
Good to know. Text collapses discovery, which means the few questions you do ask have to be the right ones. Which ones are you asking?

Power move

Ask to see real message threads. It's the equivalent of call recordings.

The reframe

Thin margins make discount discipline the highest-value skill available.

Say this

Thin margins are exactly why discounting is expensive for you. What's your average discount right now? At your margin, a few points is a lot of revenue.
Fair. Then the goal isn't more deals, it's fewer discounts. Would that math change the conversation?

Power move

In thin-margin businesses, discount elimination often pays for training by itself.

The reframe

Fundraising and enrollment are selling. Translate the language.

Say this

The vocabulary is different but the structure isn't. Donor conversations have discovery, objections, and a close. What's your hardest moment in those conversations?
Fair — I'd change every word. What's the conversation you most wish went better?

Power move

Translate 'selling' into their acceptable vocabulary. The mechanics transfer completely.

The reframe

Video compresses attention and removes the room. The sequence survives, the pacing does not.

Say this

Then two things change and nothing else does. Attention runs out faster, so discovery has to be tighter, and you lose the ability to read a room, so you have to ask for the reactions you used to see. Which of those is hurting you more?
Understood. Send me two recordings. Video is the easiest channel to coach because everything is captured, which is the one genuine advantage over in-person.

Power move

Reframe recorded video as a coaching advantage. Every call is a training asset instead of a memory.

Comparison objections

15

They lack criteria, so price becomes the only visible axis. Whoever gives them the comparison framework usually wins the deal.

The reframe

Give them a comparison framework so price isn't the only visible axis.

Say this

Smart. Can I give you a short list of what to compare besides the number? Even if you don't pick us, you'll get a better comparison.
Good. What are you comparing on? If it's just price, the numbers will look almost random, because the scopes won't match.

Power move

Handing them a comparison checklist positions you as an advisor and shapes the criteria.

The reframe

Be fair about them, specific about you, and honest about where they win.

Say this

They're genuinely good at [X] — if that's your priority, they're a fine choice. Where we're different is [Y] and [Z]. Which matters more for what you're doing?
Honestly? They win on [something real]. We win on [something real]. It comes down to which of those you need.

Power move

Conceding a genuine competitor strength makes every claim you make afterward credible.

The reframe

Answer with something checkable and specific, not with adjectives.

Say this

Three things you can verify: [specific], [specific], [specific]. And one thing we're not good at: [honest limitation].
Rather than tell you, let me ask something the others probably didn't: [insightful question]. That's the difference.

Power move

Differentiate with verifiable specifics and one honest weakness. Adjectives don't differentiate.

The reframe

They're right. Break the pattern with specificity from their own words.

Say this

They usually do. Mine will use your words and your numbers — if it reads like a template, throw it out.
Fair. Tell me the three things you actually need answered and I'll answer only those. No boilerplate.

Power move

Offer a proposal that answers only their stated questions. It stands out immediately.

The reframe

Help them build the comparison. Whoever defines the columns wins.

Say this

Agreed, and that's harder than it sounds because nobody scopes identically. Want me to put together the comparison grid? I'll include where they beat us.
Yes. Let me give you the line items that should be on every quote — then you'll see instantly which ones left something out.

Power move

Volunteering to build the comparison grid, including your weaknesses, is a powerful move.

The reframe

Fixable in one hour. Do it.

Say this

Fair. Give me an hour and I'll send you a one-page version with the number, the scope, and the timeline. The long one's there if you want the detail.
Noted. What are the three things you actually need to decide? I'll send just those.

Power move

Same-day proposal revisions demonstrate responsiveness better than any promise about it.

The reframe

Also fixable. Get specific fast.

Say this

Then it's not doing its job. What's unclear? I'll rewrite those sections with real numbers and real deliverables today.
Fair. Vague usually means I hedged somewhere. Point at the parts and I'll commit.

Power move

Vagueness in a proposal usually reflects vagueness in your own understanding. Fix both.

The reframe

Build it, include competitors fairly, and mark where you lose.

Say this

I'll build it. And I'll include the two places they beat us, because if I only show my wins you won't trust the chart.
Absolutely. What criteria should be in it? Let me use your list rather than mine.

Power move

A comparison chart where you lose two rows is far more persuasive than one where you win all of them.

The reframe

Reduce it to the two or three questions that actually decide it.

Say this

That's because they're all optimizing for their own strength. Here are the three questions that actually determine the outcome, regardless of who you pick.
Fair — it's noisy. If you only knew the answers to these two things, you could decide: [question], [question].

Power move

Clarity is a competitive advantage. Reduce a confusing decision to two questions.

The reframe

Teach them the criteria. It's the most valuable thing you can do.

Say this

That's the honest problem here, and it's not your fault — it's not your field. Let me give you the five things to check, and use them on everybody including me.
Fair. Here's what I'd look at if I were you, and here's the question that catches most weak proposals: [question].

Power move

Teaching a buyer to evaluate is the single most trust-generating act in a competitive deal.

The reframe

Name the tactic calmly. Don't match it.

Say this

That's a pressure tactic and you should treat it as information about how they'll behave later. My price is the same tomorrow as today.
I won't do that. If a price is only good for four hours, it was never the real price.

Power move

Refusing to match a false-urgency discount contrasts you favorably in the buyer's memory.

The reframe

Ask for the criteria and the weighting. Sometimes it's wrong.

Say this

Can I see the criteria and weights? Not to argue — sometimes a category is measuring the wrong thing and it's worth knowing before you commit.
Fair. Which categories did we lose? If it's something fixable I'd rather fix it than lose on a technicality.

Power move

Ask which specific rows you lost. Often one is a misunderstanding you can correct.

The reframe

Fine. Make sure your information is the last and clearest thing they read.

Say this

Good idea. Before you do — is there anything I've said that you're unsure about? I'd rather clear it up now than have it sit overnight.
Makes sense. I'll send a one-page summary tonight so you're comparing against something clear rather than your memory of a conversation.

Power move

Always send a clear one-pager before an overnight comparison. Memory favors the last clear document.

The reframe

Be factual, be fair, and never be gleeful.

Say this

I'll tell you what's missing rather than what's wrong, because I don't know their reasoning. [Specific gaps]. Ask them about those — the answers might be fine.
I'd rather not trash them. What I'll do is tell you the three questions I'd ask them, and if the answers are good, go with them.

Power move

Give them questions to ask the competitor rather than criticisms. It's more credible and more effective.

The reframe

The plan is probably fine. Plans are not the constraint. Execution and enforcement are.

Say this

It probably gave you a decent one, honestly. Can I see it? If it's solid I'll tell you and save you the money. What it can't do is listen to your calls, tell your top rep something she doesn't want to hear, or be in the room when nobody runs the process in week five.
Fair, and I'd start there too. The question isn't whether the plan is right. It's who writes it down for your product, who drills it, and who notices when it stops happening. That's the part you'd be paying for.

Power move

Never dismiss the free plan. Ask to see it, agree with what is right, and reposition onto execution, enforcement, and accountability.

Bandwidth objections

14

A real objection disguised as a soft one. Quantify the client-side hours precisely, because vague implementation asks feel infinite.

The reframe

Show the actual hours required. It's usually far less than they picture.

Say this

Let's find out if that's true. Here's exactly what you'd need to do and when: [specific hours]. If that's still too much, I'll tell you to wait.
Fair. What's your realistic capacity — two hours a week? Let me tell you whether that's enough, honestly.

Power move

Quantify the client-side hours precisely. Vague implementation asks feel infinite.

The reframe

Position as relief, not addition — if that's honest.

Say this

Then adding something is the wrong move unless it takes work off them. Does it? Let's be honest about the net.
Fair. Who specifically would be affected and what would they have to stop doing? If there's no answer to that, this isn't the moment.

Power move

Ask what they'd stop doing. If nothing, the implementation will fail regardless of the sale.

The reframe

Name the owner explicitly. Unowned initiatives die.

Say this

Good question and it's the one that determines whether this works. Here's what the owner role actually requires: [hours, tasks]. Who's the realistic candidate?
That's the right question. If the answer is 'nobody,' we should either build it so it doesn't need managing or not do it.

Power move

Refusing to proceed without a named owner protects your results and your reputation.

The reframe

Being short-staffed sometimes makes the case stronger.

Say this

That's tough. Does being short-staffed make the current process more painful or less? If more, this might be the moment rather than the wrong one.
Understood. When do you expect to be back to full? Let's plan around that — or ask whether this reduces what you need staffed for.

Power move

Short-staffing increases process pain. Sometimes it's the argument, not the obstacle.

The reframe

Price the downtime honestly and compare to the ongoing loss.

Say this

It does. Here's the actual time commitment: [specific hours]. And here's what the current close rate is costing over the same period. You tell me which is bigger.
Fair. Would splitting it into short sessions instead of full days work better for your floor coverage?

Power move

Offer a format that fits their coverage constraints. Rigid schedules lose deals unnecessarily.

The reframe

Reduce the ask dramatically and make it concrete.

Say this

Fair, and I don't want to add to that. Fifteen minutes, three questions, and I'll tell you at the end whether it's worth more time. If it isn't, we're done.
Understood. Would you rather do it by email? Send me your three biggest questions and I'll answer them in writing.

Power move

Offering an asynchronous option respects their time and often gets a better answer anyway.

The reframe

Sequence around the peak, or argue that peak is when it matters most.

Say this

Then let's not touch anything during peak. What if we do the build now and go live after? You get the prep without the disruption.
Fair. When does peak end? Let's target the week after and use the run-up to get ready.

Power move

Separate the build from the go-live. Most disruption fear is about the switchover.

The reframe

Reduce the cognitive load rather than pushing.

Say this

Then let me make it simple. Here's the one-sentence version and one question. If the answer's no, I'll leave you alone.
Understood. Would it help if I did the thinking and brought you a recommendation instead of options? Sometimes that's the actual ask.

Power move

Overwhelmed buyers want fewer choices, not more information. Bring a recommendation.

The reframe

Test whether the hire is really required or an assumed cost.

Say this

Would you? Let's check — here's the actual weekly time. If that's more than someone can absorb, then yes, and we should price the whole thing including the hire.
Fair. Is there a version that doesn't need a dedicated person? Let me describe it and you tell me if it's realistic.

Power move

An assumed headcount cost can double the perceived price. Test whether it's actually required.

The reframe

Reduce or eliminate the IT dependency if you can.

Say this

Then let's find out what actually needs them. If the answer is very little, we can move without waiting.
Understood. What's the minimum IT involvement — hours, not weeks? If it's small, is there a way to get it prioritized?

Power move

Quantify the IT ask in hours. 'IT involvement' sounds like months until it's specified.

The reframe

Offer to do it or scope it honestly.

Say this

Would you? Let's see what actually changes. And if there's real rewriting, that's something we can do rather than hand you.
Fair. What documentation exists now? Sometimes it's less than people think and sometimes we can update rather than rewrite.

Power move

Offering to absorb the documentation work removes a large hidden cost objection.

The reframe

Real constraint. Sequence around it and stay close.

Say this

Then absolutely not now. When does that wrap, realistically? Let's talk sixty days after, when the dust has settled.
Understood. Does the new system change what you'd need from this? Might be worth a short conversation now so we design for the destination rather than the origin.

Power move

Migrations are genuine blockers. Respect them and be the person who checks in at the right time.

The reframe

Fit the format to their constraint or find the real objection.

Say this

Then let's fit it to what exists. Twenty minutes a week for eight weeks, in your existing meeting. Does that clear the bar?
Fair. Is it genuinely time, or is it that training hasn't been worth the time before? Both are legitimate and I'd handle them differently.

Power move

Ask whether it's time or worth. 'No time' is often 'not worth it' in a politer form.

The reframe

True, and it is the reason to shorten the format rather than skip the people.

Say this

That's almost always true, and it's why I don't do full days for the top of the team. Twenty minutes on one specific thing, using their own recorded call, is worth more to a busy person than a day of general content.
Fair. Would you rather I worked with the busy ones in short bursts, or built the process with your manager and let them cascade it? Both work, they just cost different amounts of your time.

Power move

Shrink the format instead of skipping the person. Busy top performers respond to short, specific, self-referential coaching.

Apathy objections

14

The least discussed and most common. The deal never had a real problem attached. Giving them permission to say no produces honest answers.

The reframe

Send the permission-to-close message. It gets replies when nothing else does.

Say this

I haven't heard back and I don't want to keep filling your inbox. Should I close the file on this, or is it just bad timing? Either answer is completely fine and I'd rather know.
Last one from me — if this isn't a priority anymore, just say so and I'll stop. No hard feelings at all.

Power move

The 'should I close the file?' message has the highest reply rate of any follow-up in selling.

The reframe

Enthusiastic vagueness is a no. Test it directly and kindly.

Say this

I might be reading this wrong, but it feels like a polite no. Is it? Genuinely fine if it is — I'd just rather know than chase.
Can I ask directly? On a scale of one to ten, how likely is this actually happening? And whatever the number is, what would move it up one?

Power move

The 1-to-10 question extracts honest information from people being polite.

The reframe

Convert a passive request into a specific future date.

Say this

Happy to. What should trigger a real conversation though? A list is easy to ignore for both of us.
Sure. Rather than a list, can I just put a note to call you in [timeframe]? Feels more useful than an email you'll archive.

Power move

Convert list requests into calendared follow-ups. Lists are where deals go to be forgotten.

The reframe

Accept it graciously and ask for one thing: the trigger.

Say this

Of course. What'll be the sign that you're ready? If I know it, I won't bother you before then — and I'll be useful when it happens.
Sounds good. Mind if I check in once a quarter, just briefly? I'll stop the moment you tell me to.

Power move

Ask for the trigger and permission for a specific cadence. Both get granted more than you'd expect.

The reframe

Make the email conditional and short.

Say this

Will do. What one question do you want it to answer? Otherwise I'll write four paragraphs you'll never read.
Sure. And if I don't hear back, is it okay if I follow up once? I'd rather ask now than guess.

Power move

Get permission to follow up before you send the email. It removes the awkwardness later.

The reframe

Route to the person who does, gracefully.

Say this

Totally fair. Who does? And is it worth me mentioning your name, or would you rather I found them another way?
Understood. Before I go — what would you personally want fixed, if anything? Sometimes the person who doesn't care sees the problem most clearly.

Power move

Ask the disengaged person what they'd fix. They're often the most honest source in the building.

The reframe

Find out why, and whether that reason still holds.

Say this

What made you pass? If the reason's still true, I'll save us both the time.
Fair. Was it price, fit, timing, or the specific vendor? Those age very differently.

Power move

Old objections expire. Find out which one it was and whether it still applies.

The reframe

Take it lightly and restart cleanly.

Say this

Completely fair, it's been a while. Two-sentence recap, then you tell me if it's still relevant: [recap]. Still worth a conversation?
No worries at all. Should I restart this or let it go? Either is fine.

Power move

Never guilt someone for forgetting. Restart clean or close clean.

The reframe

Either find the urgency or accept there isn't any.

Say this

There might not be. What would make it urgent? If nothing would, then it probably isn't the right thing right now.
Fair. Is the problem getting worse or holding steady? Steady problems genuinely can wait. Worsening ones usually can't.

Power move

Trend, not magnitude, creates urgency. Ask whether it's getting worse.

The reframe

Logic without emotion doesn't close. Find what they'd actually be excited about.

Say this

That's useful — logic without any pull means I've solved a problem you don't feel. What would you actually be excited to fix?
Fair. What's the thing that, if it got better, you'd genuinely notice on a Monday morning?

Power move

'Makes sense but I'm not excited' means you found a real problem they don't emotionally own.

The reframe

Reorgs are real, indefinite, and often permanent stalls. Get a name and a date.

Say this

Understood. Who's likely to own this after? I'd rather start a relationship there than wait for a decision nobody's assigned to.
Fair. Is there a date for that, or is it open-ended? I'll set my own reminder either way so I don't lose track of you.

Power move

Reorgs never end. Find who'll own it afterward and build there now.

The reframe

Indifference is a no. Find out if anyone cares.

Say this

That's honest and it probably means this isn't your problem. Who does it affect most? They'd be the better conversation.
Fair. Then let's not do it. If it changes, you know where I am.

Power move

Walking away from genuine indifference preserves credibility and saves months of chasing.

The reframe

Ask for the decision to be made, or for the door to be closed.

Say this

Can I ask you to decide? Not right now — but at some point, because 'maybe' costs us both more than either answer would.
Fair. What would tip it one way or the other? If we can name it, we can watch for it.

Power move

'Can I ask you to decide?' is a legitimate, respectful close. Maybe is more expensive than no.

The reframe

A friendly no with a date attached to make it feel like a yes. Test whether the date is real.

Say this

I'll take that, and I'll hold you to it kindly. What has to be true by then? If nothing specific, next year usually becomes the year after, and I'd rather we both knew that now.
Happy to. Which month, and who else needs to be in that conversation? If we can name those two things it's a plan. If we can't, it's a polite no and that's fine too.

Power move

Ask for the month and the people. A future commitment that can't survive two specifics was never a commitment.

Nothing matched that.

Try fewer words, or the buyer's exact phrasing. If a buyer said something that isn't in here, I want to know about it — send it over and I'll write the response and add it.

The five-step method behind every response

Every card in this library follows the same structure, because structure is what lets a nervous person perform under pressure. If you learn nothing else here, learn this sequence.

  • Pause. Two full seconds of silence. Instant responses sound rehearsed and tell the buyer they aren't being listened to.
  • Acknowledge. Reflect the concern back in your own words and let them confirm it. Now you're defining the problem together instead of arguing about it.
  • Isolate. "If we solved that, is there anything else?" This converts an infinite objection queue into a finite list.
  • Reframe. Change the axis of comparison. This is the part written at the top of every card.
  • Advance. End with a small forward-moving question, not a request for the whole decision.

Notice what's missing: arguing. When you answer a stated objection with an argument, you win the argument and lose the sale. When you answer it with a question, you find the real objection underneath, and the real one is almost always easier to solve than the one they said out loud.

You don't overcome objections. You dissolve them by finding out what was actually being asked.Zach Wennstedt

Every term used on this page is defined in the sales training glossary, and the full framework is laid out on the sales training and coaching home page.

From the same shop

Handling objections is easier when they already know who you are

Eye To Ad Media builds the SEO, AIO, and answer-engine visibility that turns cold calls into warm ones. Search Converts is the conversion rate optimization agency that fixes what happens between the click and the call. Both Denver-built, both running since 2012.

Visit Eye To Ad Media

Questions about objection handling

There are hundreds of phrasings and roughly twelve underlying reasons. This library documents 216 distinct objections grouped into those twelve families: price, timing, trust, authority, need, competitor, status quo, risk, fit, comparison, bandwidth, and apathy. Learning the twelve families matters more than memorizing the 216, because the family tells you the move even when the exact wording is new.

Pause for two full seconds, acknowledge the concern in your own words and let the buyer confirm it, isolate it by asking whether anything else stands in the way, reframe the axis of comparison the buyer is using, then advance with a small next-step question rather than asking for the whole decision again. Every response in this library follows that five-step structure.

Yes. There is no signup, no email wall, and nothing stored. Every objection, reframe, script, and power move can be copied, adapted, printed, and used with your own team. What is sold is the custom version built from your recorded calls in your buyer's vocabulary, which is a different thing than a general library.

Learn the reframe rather than memorizing the words. The reframe is the thinking and the script is only one expression of it. Read the scripts out loud, then rewrite them with your product and your buyer's vocabulary in them. Reading silently produces recognition, and recognition is useless at two in the afternoon when a buyer catches you off guard.

Price is the most frequently reported and apathy is the most frequently fatal. Price objections are usually a reframing problem rather than a money problem. Apathy, meaning ghosting, indifference, and endless circling back, kills more deals than any competitor because the deal never had a problem the buyer actually owned.

Five a day for a month covers this entire library and holds far better than a single workshop. Pick the one family you lose deals to most often rather than trying to learn all twelve at once, and say the responses out loud, because speaking produces the motor memory you need under pressure.

Want this version, but with your product in it?

This library is general on purpose, because it has to work for a contractor and a software rep at the same time. What closes deals is the version built from recordings of your calls, in your buyer's vocabulary, drilled with your team until it's automatic. That's the first deliverable of every engagement.

Call toll-free 1-800-481-8638 See training packages
Call 800-481-8638 Book a call