Beating Do-Nothing
vs. we already have something in place
Your real competitor in most deals is not another vendor, it is the buyer doing nothing. Your wedge is making the cost of inaction concrete, urgent, and personally owned, because status quo always wins by default until you quantify the bleeding.
Buyer mindset
The buyer has something that mostly works and a hundred other fires. Change feels risky and effortful, while the pain of the status quo is familiar and discounted. They are not lazy, they are rationally avoiding a project whose payoff feels vague. No-decision is the path of least resistance and the most likely outcome of any deal.
Where they win
- ›Zero switching cost, zero risk, zero effort to keep doing what they do
- ›The current pain is known and budgeted for emotionally, even when it is large
- ›No internal politics, no procurement, no change management to navigate
- ›Genuine competing priorities that are louder this quarter
Where you win
- ›Quantified cost of inaction: the bleeding is real but uncounted, so counting it changes the math
- ›A trigger event, a deadline, an audit, a growth target, that makes this quarter the right quarter
- ›A small, low-risk first step that makes change feel safe instead of monumental
- ›Personal stakes: tie the status quo's cost to a goal the champion is measured on
- ›Compounding pain: the gap between you and the status quo widens every month they wait
Traps to avoid
- ›Selling features against no-decision, when the buyer is not comparing features, they are comparing change against comfort
- ›Failing to quantify the cost of inaction, which leaves do-nothing looking free
- ›Letting the deal stall without a compelling event, so it dies a slow death in a forecast
- ›Pushing a big-bang rollout that makes change feel risky, instead of a small reversible first step
- ›Mistaking polite interest for intent, then forecasting a deal the buyer was never going to pull the trigger on
Discovery questions
- ›What made you take this meeting now, what changed, or is this just exploratory?
- ›If nothing changes and you keep doing exactly what you do today, what does that cost you over the next year?
- ›Who feels the pain of the current approach most, and what does it stop them from doing?
- ›Is there a deadline, a target, or an event coming that this needs to be solved before?
- ›What would have to happen for doing nothing to become unacceptable?
- ›If you brought this to your boss, what is the one number that would make them say yes?
Landmines to plant
- ›Ask them to put a dollar or hours figure on the current pain per month, then let that number sit with them.
- ›Ask what the consequence is if the underlying problem is still unsolved at their next planning cycle or audit.
- ›Ask who specifically is accountable if the status quo causes a miss, so the risk has a name.
Objection talk tracks
“We already have something that works fine.”
Good, and if it truly works fine you should keep it, I mean that. Let me ask one thing though. What does fine cost you? Most teams I talk to have quietly absorbed a pain so familiar they stopped counting it. Let me help you put a number on what the current approach costs per month. If it is small, we are done. If it is bigger than you expected, at least now it is a decision instead of a default.
“This just is not a priority right now.”
I respect that, and I would rather you solve the right problem at the right time than rush this. Help me understand the timing though. Is there a point, a target, an audit, a growth number, where this stops being a someday and becomes a must? Because the cost of waiting is not zero, it compounds quietly, and I would rather start the small first step before it becomes a fire than during one.
“Switching feels like a big risky project we do not have time for.”
That fear is the real reason most teams stay stuck, and it is legitimate, so let me take it off the table. We do not have to boil the ocean. Let me propose one small, reversible first step that proves value in weeks with almost no lift from your team. If it does not deliver, you have lost nothing. If it does, you have your business case for the rest.
“Let me think about it and circle back.”
Totally fair, and I want to make circling back easy instead of letting this drift. What specifically do you need to think through, and who else needs to weigh in? Let me give you the one-page cost-of-inaction summary so the conversation you have internally is grounded in a number, not a vague maybe. When is your next planning checkpoint? Let me make sure you have what you need before it.
Proof to gather
- ›A cost-of-inaction calculator tailored to the buyer's metrics, the single most important asset for this matchup
- ›Win-loss data on deals lost to no-decision, with the common reason change never got prioritized
- ›Quick-win case examples showing a small first step that became a full rollout
Make this card yours in 60 seconds
Drop your product and competitor into the builder to generate a tailored, exportable version of this play.
Open the builder