Customer Indecision: Why Your Enterprise Deals Stall, and How to Unstick Them

Enterprise Sales Is a Decision-Confidence Problem

An Enterprise deal can build real momentum and still be slowed by strong headwinds inside the customer’s org.

Our champion has to explain the investment to their colleagues and leadership, each of whom may have different priorities

• a CxO accountable to deliver business outcomes
• an IT leader concerned about implementation risk
• other stakeholders fighting to fund their own projects
• a CFO balancing conflicting priorities, or
• a board asking why this initiative should be funded now.

We quickly realize that impactful demos are not enough. Neither are impressive ROI calculations.

It is not simply an individual buyer’s belief that a product is useful. It is a buying group’s shared ability to make, defend, and carry through a decision.

When that confidence is missing, a deal can look healthy until it reaches the point where the customer must choose among competing priorities and commit resources. And accept responsibility for the outcome.

So what we see is Enterprise opportunities ending in

• delay ("let's revisit this in Q1 next year")
• value erosion ("how about we start start smaller"), or
• silence.

The customer may want something better than what they have. They may agree that the problem is real. They may even see real value in your solution. But they do not yet have a sufficiently clear, shared, and defensible case for action.

What this means for revenue teams is that the job is not merely to demonstrate value. It is to help customers build the confidence to act on it.

01. Why buying has become harder

Enterprise buying has always involved competing interests. What has changed is the intensity of the trade-offs.

Budgets are under increasing scrutiny. Major initiatives often span several functions. Leaders are asked to demonstrate not only the potential upside of an investment, but also why it deserves priority over everything else that could be funded instead.

At the same time, buying groups have become broader and more complex. A customer may have an operational team living with the problem every day, managers accountable for performance targets, and executive stakeholders responsible for capital allocation, risk, and strategic direction. Each group sees the decision through a different lens.

The supplier landscape compounds the challenge. In many software categories, buyers can choose from several credible options. Features converge quickly. Pricing models are easier to compare. A vendor may be differentiated in meaningful ways, but the customer still has to decide whether that difference justifies the disruption, cost, and internal coordination required to change.

That does not mean the status quo is genuinely cost-free. It means the perceived risk of making the wrong decision can outweigh the perceived risk of doing nothing. A buyer who backs a poorly executed initiative may have to explain missed targets, implementation problems, and wasted investment. A buyer who delays may simply be able to revisit the issue next quarter.

This is the context in which indecision emerges. It is rarely a lack of information. More often, it is a lack of collective confidence.

02. Distinguish value uncertainty from organizational friction

When an opportunity stalls, sellers often ask a narrow question: “Have we communicated the value clearly enough?”

It is the right question, but only half the diagnosis.

A value uncertainty problem occurs when the customer can describe an operational benefit but cannot connect it to a meaningful business outcome. They may believe the product could improve a workflow, reduce manual effort, or provide better visibility. But they cannot explain which strategic initiative it supports, which KPI it will affect, or why the problem matters enough to solve now.

An organizational friction problem looks different. Here, the customer may understand the value but struggle to agree on ownership, timing, budget, implementation responsibilities, or the trade-offs involved. The disagreement is internal. It may have little to do with the product itself.

These problems often reinforce each other. A vague value case creates space for competing interpretations. Competing interpretations make it harder to establish urgency. The deal then loses momentum, even when no stakeholder explicitly rejects it.

A useful way to diagnose both issues is to consider value at three levels.

At the operational level, value is about the work itself. How does this change the process, the user experience, the speed, quality, or effort required to get something done?

At the managerial level, value is about performance. Which KPI, initiative, resource constraint, or departmental priority does the change affect?

At the executive level, value is about the business. How does this help the company compete more effectively, operate more efficiently, or control risk more confidently?

The operational level explains how the work changes. The managerial level explains what performance improves. The executive level explains why the company should care.

Too many deals remain trapped at the first level. The seller can articulate a functional improvement, and the operational champion agrees. But neither can bridge that improvement to the metrics, strategic priorities, and financial trade-offs that determine whether the investment is funded.

03. Buyers open up when the conversation improves their thinking

When a conversation helps buyers see their situation more clearly, they move beyond surface-level descriptions of pain. They begin to recognize how work actually happens, where it breaks down, who is affected, what has already been tried, and why previous attempts have failed. They also start to see how those issues connect to other teams, competing priorities, implementation risks, and the incentives shaping the decision.

That does not happen through questions alone. A useful seller brings a point of view grounded in research, market knowledge, and experience with similar business problems.

That point of view gives buyers language for challenges they have felt but not fully articulated. It can reveal dependencies they have not considered, trade-offs they have not named, and consequences they have not yet quantified.

04. Personalize for the group, not only for the champion

A champion is essential. But in a complex enterprise purchase, they are rarely powerful enough to carry the decision alone.

The risk of tailoring the entire value narrative around one senior stakeholder is that it can deepen the divisions already present in the buying group. It may reinforce one person’s priorities while leaving others unconvinced about the financial case, implementation burden, or impact on their team.

Operational users may need to understand how the change will affect their daily work. A functional leader may need to see how it improves performance against a critical KPI. IT may need confidence that implementation will not create disproportionate complexity. A CFO may need a credible view of investment, risk, and trade-offs.

Those interests will not be identical. But at the managerial and executive levels, they must converge on the company’s Key Business Requirements.

The role of the seller is to help the group uncover these requirements and connect the investment to those requirements: the outcomes the company has decided matter most, whether growth, lower operating costs, or risk reduction.

The goal is not to win one person and hope they persuade the rest. It is to help the buying group reach a decision they can support together.

05. An ROI calculation is not a business case

An ROI calculation is useful. A TCO comparison can also be useful.

Neither is, on its own, a business case.

A defensible business case has five elements.

1. It establishes the strategic rationale. What business priority does this initiative support? Does it help the company grow, improve operating performance, reduce exposure, or enable a larger strategic shift?
2. It connects the initiative to performance. Which KPIs, operating constraints, or cross-functional priorities will change if the customer acts?
3. It quantifies the business logic. This may include revenue growth, cost reduction, productivity, avoided risk, cash-flow impact, payback period, or other financial measures appropriate to the size and nature of the investment.
4. It provides evidence that the outcome is achievable. This is where customer proof, implementation plans, technical validation, and organisational readiness matter. Buyers need confidence not only that the value is possible, but that their organisation can realise it
5. It addresses risk honestly. What happens if the company does nothing? What could go wrong if it acts? What assumptions need to hold true? What change-management work will be required?

The last point is often underestimated. Enterprise buying is not simply about proving upside. It is about reducing the perceived risk of being wrong.

A business case assembled in the final week of a deal will rarely solve that problem. By then, the customer has already formed assumptions about the initiative, its urgency, and its risks.

Strong business cases are built gradually through value discovery. The seller and customer co-create the logic over time. The champion contributes the data, the internal context, and the political reality. The seller contributes structure, perspective, and evidence.

06. AE and SE alignment is an operating model for decision confidence

Sales and presales teams often focus heavily on role division. Who owns the commercial process? Who leads discovery? Who handles the technical conversation? Who presents to executives?

Those questions matter, but they are secondary to a more important one: what must the team understand together?

In a complex opportunity, AEs and SEs should share ownership of the customer’s strategic initiative, the cost of the current state, the relevant stakeholders, the competing priorities, the implementation risks, and the financial logic of the decision.

They do not need to perform identical roles. An AE may lead orchestration, executive alignment, and commercial process. An SE may lead technical diagnosis, operational discovery, and solution design. Customer success, services, partners, and subject-matter experts may each play important roles.

But the customer should experience one coherent conversation.

The AE may speak about strategic value without enough operational evidence. The SE may demonstrate a compelling solution without knowing which executive outcome it must support. The result is often a deal that appears active but lacks a coherent rationale for action.

This shared decision-confidence mode helps identify what is missing. Is the strategic rationale unclear? Is the economic case weak? Is the buying group misaligned? Does the champion lack the evidence to persuade a sceptical stakeholder? Is implementation risk still unaddressed?

These are not abstract questions. They determine what the team should do next.

07. Financial fluency turns value into a fundable decision

In complex sales, revenue teams need to be fluent in two languages.

The first is the operational language of the champion: process friction, wasted effort, capability gaps, customer experience, delivery risk, and the KPIs their team is expected to improve.

The second is the financial language of leadership, finance, and procurement: revenue, gross margin, EBIT, cash flow, total cost of ownership, payback period, risk exposure, and capital allocation.

Most sellers learn to speak the first language well. They can understand the problem, articulate how their solution improves the current state, and often connect that improvement to a departmental priority.

That is essential. But in a larger deal, it is rarely sufficient.

That translation follows a simple chain:

Operational problem → measurable impact → financial consequence → fundable decision

Reducing manual effort may increase throughput. Increased throughput may lower cost, accelerate revenue, protect margin, improve retention, or free capacity for higher-value work. A technical capability may reduce compliance exposure, avoid future costs, or enable an initiative the company would otherwise struggle to execute.

An ROI calculation can support that case. It is not the case itself.

Financial fluency does not require every AE or SE to earn an MBA. It requires enough commercial understanding to ask better questions, recognise how value is created in the customer’s business, and connect the proposed change to the financial consequences that matter.

The critical question now answers more than “Will this make life better for the team?”

It answers “Why should I allocate scarce budget, attention, and organisational energy to this now?”

When sellers can answer that question with the customer, they help their champion make and defend the case when the seller is not in the room.

That is how decision confidence becomes something a revenue team actively builds rather than something it hopes a champion already has.

———

This article grew out of a recent conversation on the Presales Collective podcast.

I work with CROs, sales leaders, and solutions engineering leaders to help revenue teams build decision confidence into complex opportunities. When promising deals repeatedly stall late in the cycle, the issue is often not product value. It is the customer’s ability to make and defend the decision.