Losing Deals to No Decision: How to Reduce Buyer Indecision

Look at your closed-lost reasons from last quarter. You will probably see a few lost to competitors, a few lost on price, and a long tail marked "no decision", "went dark" or "timing". Those deals rarely get a proper review. Nobody won, so it feels like nobody lost.

That tail is bigger than most teams think. In a 2022 Harvard Business Review article, Matthew Dixon and Ted McKenna described their analysis of more than 2.5 million recorded sales conversations and reported that 40% to 60% of deals ended in no decision. For many SaaS teams, that makes inaction the single biggest competitor.

The most interesting part of their research is why those deals died. Of the deals lost to no decision, they found that 44% were lost because the buyer preferred the status quo. The other 56% were lost to indecision: the buyer wanted to change, but could not bring themselves to choose. Those are two different problems, and they need two different responses.

Status quo bias is well documented. In a 1988 paper in the Journal of Risk and Uncertainty, William Samuelson and Richard Zeckhauser showed in a series of experiments and field studies that people disproportionately stick with the option they already have, even when other options are at least as good. Daniel Kahneman's work, summarized in Thinking, Fast and Slow, explains part of the reason: losses loom larger than equivalent gains, so giving up what we have feels worse than the benefit of something new feels good.

Most sales training is built to fight the status quo. You show the cost of the current situation, make the problem feel urgent and paint a picture of a better future. Challenger's commercial teaching is one example; see Challenger selling on video calls.

But Dixon and McKenna found that indecision is a different fear. The buyer already agrees that change is needed. What stops them is the fear of making the wrong choice: picking the wrong product, the wrong package, or a project that will not deliver and will be blamed on them. On their JOLT Effect site they put the difference neatly: overcoming the status quo is about dialing up the fear of not purchasing, while overcoming indecision is about dialing down the fear of purchasing.

Their research also found that the usual response, making the case against the status quo even more strongly, backfired in 84% of the cases they studied when the real problem was indecision. If a buyer is afraid of choosing wrong, telling them how bad things are only increases the pressure on a decision they already feel unable to make.

Dixon and McKenna identify three main drivers of indecision. Each shows up in SaaS deals in recognizable ways.

• Valuation problems: the buyer cannot decide which option, package or configuration to choose. "We are not sure whether we need the Pro plan or the Business plan." "Should we start with one team or roll out to everyone?"
• Lack of information: the buyer feels they have not done enough homework. "We would like to see a few more case studies." "Can we talk to two more references?" "Let us look at one more vendor first."
• Outcome uncertainty: the buyer fears they will not get the benefits they expect. "What if the team does not adopt it?" "What if the integration takes longer than you say?"

These can all sound like reasonable requests, and sometimes they are. But when they keep coming, and each answer produces another question, the buyer is usually not missing information. They are looking for a reason to feel safe.

Group dynamics make this worse. Gartner reported in 2025 that 74% of B2B buyer teams demonstrate unhealthy conflict during the decision process, and that buying groups range from five to 16 people across as many as four functions. When nobody wants to own a risky decision, it is easiest for the group to make none. The same Gartner research found that buying teams that reach consensus are 2.5 times more likely to report a high-quality deal. Helping the group agree is part of the job; see selling to a buying committee.

Dixon and McKenna found that the best performers handled indecision in a consistent way, and that they achieved nearly double the win rate of average performers. They summarized it as JOLT: Judge the indecision, Offer your recommendation, Limit the exploration, and Take risk off the table.

Most qualification asks whether a buyer can buy: budget, authority, need and timing. JOLT adds a different question: is this buyer ready to make a decision and own it?

Signs of high indecision include repeated requests for more options, more information or more meetings without moving forward; worrying about worst-case scenarios; asking what other customers chose rather than what is right for them; and a champion who agrees with everything but cannot say who will sign.

You can ask about it directly. "On a project like this, what would make you nervous about making a decision?" or "If this went wrong, who would be blamed?" The answers tell you much more than another discovery call about features.

Indecision is a spectrum, not a yes-or-no. Almost every buyer has some. The goal is not to find buyers with none, but to recognize how much there is and address it early instead of discovering it in the last week of the quarter.

When a buyer struggles to choose between options, the common sales response is to present more options, or to ask more questions about their preferences. JOLT suggests the opposite: give a firm, reasoned recommendation.

The JOLT Effect site suggests imagining that you are advising your best friend. You would not lay out six options and say "it depends". You would say, "Go with this one, and here is why." A recommendation also shares the responsibility for the choice, which is exactly what an anxious buyer needs.

In a SaaS deal, that sounds like this:

• "Based on what you told me, I would start with the Business plan for the support team only. You get the reporting your director asked for, and you can add the other teams once it is working. I would not buy the Enterprise plan yet; you would be paying for features you will not use this year."
• "Of the three rollout options, I recommend starting with the London team. They have the clearest process and the most motivated manager, so you will get a clean result to show everyone else."

A recommendation only works if it is honest. If you always recommend the most expensive option, buyers will notice quickly. Recommending less than they expected is one of the fastest ways to earn trust.

Many reps respond to an indecisive buyer by sending everything: ten case studies, three white papers, a comparison chart and an invitation to a webinar. It feels helpful. According to Dixon and McKenna, it often makes the paralysis worse, because more information creates more questions and more ways to second-guess.

Limiting the exploration means being clear about what information actually matters for this decision, and saying when something does not. "You asked about our API rate limits. With your volume, you will never get close to them, so I would not spend time on it." Or: "You do not need five references. Talk to this one customer; they had the same integration and the same team size."

This requires trust. Buyers will only accept your guidance on what to skip if they believe you are on their side. That trust is built earlier, through honest discovery and through admitting what your product cannot do.

A shared screen helps here. Build a short list of decision criteria together, on screen, early in the deal. Later, when new questions come up, you can look at the list together and ask, "Does this change any of these criteria?" Most of the time it does not, and the buyer can see that for themselves.

The final skill addresses outcome uncertainty: the fear that the purchase will not deliver. The answer is to make failure less likely and less costly. In SaaS, that can include:

• A short pilot with clear success criteria agreed in advance, rather than an open-ended trial.
• Starting with one team or one use case, with a planned expansion if it works.
• Monthly terms for the first period, or an opt-out at a defined checkpoint.
• A written onboarding plan with named people, dates and milestones.
• Introducing the buyer to the person who will lead their onboarding before they sign.

The JOLT Effect site makes an important point about expectations. If you promise an optimistic time to value based on a best-case implementation, you increase indecision rather than reduce it, because the buyer senses the risk you are hiding. It is more reassuring to describe the common obstacles honestly and show a plan for handling each one.

That plan is also the start of a good handoff to the team that will onboard the customer. See the handoff from sales to customer success.

Indecision is often a sense-making problem. Gartner reported in 2019 that 89% of B2B customers encounter high-quality information during their purchase, but customers who struggle to make sense of it are significantly more likely to settle for a course of action that is smaller or less disruptive than they originally planned. The problem is rarely a lack of information. It is too much information that does not fit together.

On a call, this is where a shared screen earns its place. Instead of sending another document, put the pieces together with the buyer:

• A one-page comparison of the options they are considering, against their own criteria.
• A simple cost model with their numbers, showing what each choice means over a year.
• A rollout timeline that shows exactly what happens in the first 30, 60 and 90 days.

When the buyer can see the decision laid out clearly, the fear often becomes manageable. When they can forward that page to their boss, it becomes much easier for the group to agree.

Imagine a mid-sized company evaluating a scheduling tool. The demo went well. The operations manager said it was exactly what they needed. Then, for three weeks, the deal stalled. Each week brought a new request: another reference, a comparison with a competitor, a question about a feature nobody had mentioned before.

A rep focused on the status quo would make the case again: here is what the current process costs, here is how much time you would save. But the manager already agreed with that. The problem was elsewhere.

A rep using JOLT would first judge the indecision. On the next call, they might say: "It seems like something about the decision is making it hard to move forward." The manager might admit that the last software rollout she led went badly, and she was worried about being blamed again.

Now the rep knows what to do. Offer a recommendation: start with one team, not the whole company. Limit the exploration: "You have seen two references with the same setup as yours. A third will not tell you anything new." Take risk off the table: a six-week rollout to one team, with agreed success criteria and a review with her director at the end. The decision is no longer "Should we change how the whole company schedules work?" It is "Should we try this with one team for six weeks?" That is a much easier decision to make.

Watch for these patterns in your pipeline:

• The buyer asks for a new option or package after every meeting. Respond with a recommendation, not another option.
• New stakeholders keep appearing late with new questions. Ask your champion who else needs to be comfortable, and meet them early.
• The buyer asks for more references or case studies after already seeing several. Ask what specific worry the next one would address.
• Next steps are vague: "We will get back to you." Propose a specific step with a date, and ask what is making it hard to commit.
• The deal moves to "next quarter" without a reason. Ask directly whether the problem is still a priority, or whether something about the decision feels risky.

None of this guarantees a decision. Some buyers will still choose to do nothing, and sometimes that is the right choice for them. But a clear recommendation, a narrower set of questions and a lower-risk way to start give the buyer a real chance to say yes.