The multi-stakeholder problem: Initial advocates and final decision-makers want different things

The most dangerous moment in an enterprise sale is when the champion tells you the deal is done.

It is not done. It is not close to done. What has happened is that one person inside the buying organisation, usually a mid-level manager or a team lead, has fallen in love with your product. They have seen the demo. They have used the trial. They have imagined how much better their daily work would be. And they have told you, with genuine conviction, that this is going to happen.

But the person who signs the budget has never seen the demo. They have never used the trial. They do not care how the interface feels. They care about three things: what does it cost, what does it replace, and what happens if it goes wrong. The champion and the decision-maker are having two completely different conversations about your product, and your product team is only hearing one of them.

Act One: twelve people, twelve criteria

Enterprise buying groups now average twelve or more people. More than half of final decision-makers sit at VP level or above. Nearly eight in ten purchases require CFO approval. These are not statistics. They are the terrain.

The product champion, the person who found your product, tried it, and decided it would solve their problem, typically sits two or three levels below the person holding the budget. The champion evaluates the product on experience: does it work, does it feel right, does it make my job easier. The decision-maker evaluates the product on risk and return: does it reduce cost, does it integrate with what we already have, does the vendor look stable enough to bet on.

These are not two perspectives on the same question. They are answers to two entirely different questions. And most product teams build for one audience while assuming the other will simply follow.

I call this the champion gap. The distance between the person who loves your product and the person who controls the budget. The wider the gap, the more likely the deal dies in a room your product team never enters.

Act Two: two rooms, two losses

At Adobe, I watched this play out in a way that still bothers me. We had a product that a design team at a large financial services firm wanted badly. The lead designer had spent weeks building an internal case for it. She had documented the workflow improvements, mapped the time savings, shown how the product fit into their existing tool stack. By every measure that mattered to her team, this was the right product.

The CFO killed it in a single meeting.

Not because the product was wrong. But because the ROI case was not there. The design lead had built a case for adoption. The CFO needed a case for investment. She had explained how the product would improve her team's work. The CFO wanted to know how much it would save the company in hard dollars over three years, how it compared to the incumbent vendor's renewal pricing, and what the switching cost would be if the product failed to deliver. Those were not questions the design lead had prepared for, because nobody on our side had equipped her to answer them.

The product was perfect for the user and invisible to the buyer. That is a product failure, not a sales failure.

At Freshworks, I saw a different version of the same gap. We were selling into a mid-market enterprise, and the product champion was a support operations manager who loved the interface. He had run a trial with his team. Satisfaction scores were high. He was convinced. But when procurement entered the conversation, the entire language changed.

But procurement did not ask a single question about user experience. Not one. They wanted to know about vendor stability: how long had the company been profitable, what was the revenue trajectory, what happened to customer data if the company was acquired. They wanted contract flexibility: could they exit after year one without penalty, were there caps on price increases, who owned the integrations. They wanted to know whether the company would still exist in three years.

These are not unreasonable questions. But they are questions that live in a completely different universe from "the interface is intuitive and my team loves using it." The champion was selling the experience. Procurement was buying the risk profile.

I started calling this the boardroom inversion. The moment an enterprise deal moves from the team that will use the product to the function that will approve the spend, every evaluation criterion flips. What made the product attractive to the champion (beautiful design, easy onboarding, intuitive workflow) becomes irrelevant or even suspicious to the decision-maker. A product that feels too easy can signal immaturity to a procurement team evaluating for enterprise readiness.

Winning the room and losing the boardroom is the most common way good products die in enterprise.

Act Three: building for both rooms

The instinct here is to say "build a better ROI story." But that is only a piece of it, and not even the most important piece.

The product teams I have seen close this gap do something more structural. They design the product experience for the champion and the buying collateral for the decision-maker as two parallel workstreams, not an afterthought tacked onto the sales cycle.

Think of it like an architect designing a building. The architect designs the floor plans for the tenants, the people who will live and work in the space every day. But the architect also designs the maintenance plans, the energy efficiency projections, and the structural warranties for the building owner. If the architect only designs for the tenants, the building never gets approved. If the architect only designs for the owner, the building gets built and nobody wants to live in it.

Most product teams are designing only for the tenants.

The practical difference looks like this. Product teams that win both rooms build ROI cases into the product itself, not just into the sales deck. They include admin dashboards that surface cost savings and efficiency metrics in language a finance team recognises. They provide security and compliance documentation that procurement can evaluate without scheduling a call. They make it easy for the champion to build the internal case by giving them the materials that speak the decision-maker's language. Not marketing collateral. Evidence.

But the deeper shift is about empathy, and this is where most product teams resist. The person using your product and the person paying for it are having two completely different conversations about it. Respecting both conversations, genuinely and structurally, means accepting that user delight is necessary but not sufficient. The CFO at that financial services firm was not wrong to kill the deal. She was doing her job. We had not done ours.

The gap that never fully closes

The champion gap does not disappear. It exists in every enterprise deal because the people closest to the problem and the people closest to the budget occupy structurally different positions with structurally different incentives. But no amount of product polish resolves that tension, because the tension is not a flaw. It is how organisations make decisions when the money is large enough to matter.

The product teams that understand this stop trying to eliminate the gap and start designing for it. They accept that they are building for two audiences who will never fully agree on what matters. They equip the champion without abandoning the decision-maker. They build evidence alongside experience.

It is a harder way to build. But the enterprise deals that actually close are never won in a single room.