Uncovering the Cost of Inaction: The Discovery Question That Turns Interest into Urgency

Every Solution Engineer has seen it: a prospect who loves the demo, agrees with the business case, nods at the architecture, and then does nothing. The deal sits in the pipeline for months and quietly dies. The competitor was not another vendor. It was the status quo.

The antidote is a discovery skill that many SEs skip: uncovering the cost of inaction. Instead of only asking what the prospect wants to gain, you help them see, clearly and in their own words, what it costs them to keep things exactly as they are.

Why “do nothing” wins so often

Change is risky for the buyer. A new platform means migration work, retraining, budget approvals and the personal risk of championing something that might not land. Staying put feels safe because its costs are usually invisible: spread across teams, absorbed as overtime, or simply accepted as “how things work here.”

Your job is not to scare anyone. It is to make those hidden costs visible so the decision is made on an honest comparison: the cost and risk of changing versus the cost and risk of not changing.

Three layers of inaction cost

When you explore the cost of inaction, look across three layers. Each speaks to a different stakeholder.

1. Technical degradation

What gets worse over time if nothing changes? Think about growing technical debt, systems approaching end of support, manual workarounds that multiply, performance that declines as volumes grow, or security exposure that widens. Engineers and architects feel this layer first.

2. Financial loss

Where does the current state leak money? Common examples are staff time spent on repetitive tasks, licences for overlapping tools, revenue lost to outages or slow processes, and penalties tied to missed service levels. Finance and operations leaders care about this layer.

3. Competitive and strategic risk

What does the business fail to do because of the current state? Slower launches, weaker customer experience, inability to enter a new market, or falling behind compliance expectations. Executives respond most strongly to this layer.

Questions that surface the cost

The key is to let the prospect quantify, not you. Numbers they produce are numbers they believe. Useful questions include:

• “If this process stays the same for the next year, what happens as your volume grows?”
• “How many people touch this workflow today, and roughly how much of their week does it take?”
• “The last time this system failed, what was the impact on customers or revenue?”
• “What initiatives are on hold or slowed down because of this?”
• “Who in the organisation feels this pain most, and how do they describe it?”
• “If you decided not to address this now, when would you have to revisit it, and would it be easier or harder then?”

Follow each answer with a gentle “How do you know?” or “How would you measure that?” This turns opinions into estimates and estimates into something you can later use in a business case.

Turning answers into a simple model

You do not need a complex spreadsheet during discovery. A short, shared summary is enough:

• The current state: what happens today, in the prospect’s words.
• The trend: whether it is stable, getting worse, or about to hit a limit.
• The estimated cost: time, money or risk, with the assumption behind each figure.
• The trigger: what event would make this cost unavoidable (a renewal, an audit, a peak season, a launch).

Send it back to your contacts after the call and ask them to correct it. Their corrections improve accuracy and, just as importantly, build their ownership of the problem.

How to do this without sounding manipulative

• Stay curious, not dramatic. You are investigating, not catastrophising.
• Use their numbers. Never invent figures or borrow statistics that do not apply to them.
• Accept a low cost of doing nothing. Sometimes the honest answer is that the status quo is fine for now. Knowing that early saves everyone time and protects your credibility.
• Separate discovery from pitching. Do not jump to your solution the moment a pain appears. Let the cost be fully understood first.

Where it pays off later

A well-documented cost of the status quo feeds almost every later stage of the deal. It shapes the outcome-first story in your demonstration, gives your PoV or PoC its success criteria, and becomes the baseline for converting technical results into ROI in the executive readout. It also arms your internal champion with a reason to act now rather than next year.

Keep practising

Asking about the cost of inaction feels uncomfortable at first, especially for technically minded SEs who prefer talking about capabilities. It gets easier with repetition. SE Ignite Academy includes this skill in its free, vendor-neutral discovery curriculum, with practice scenarios where you can rehearse these questions before using them with a real customer. Try just two of the questions above on your next call and notice how the conversation changes.