The demos went well. The proof of concept checked out. You found root causes the incumbent couldn't touch.
And yet, nothing is moving.
This is one of the most common and frustrating places a presales team can find itself: technically ahead, commercially stuck. You've earned the right to win. You just haven't earned the commitment to buy.
Here's the truth: when a deal stalls after a successful proof of concept, the problem is almost never the product. It's the gap between what you've proven and what the business actually cares about.
You Won the Technical Argument. That's Not Enough.
In a recent live deal coaching session with the Presales Collective, Chad Wilson, VP of Operations at 2Win Global, worked through exactly this scenario in real time with a presales professional named Karthik.
The deal: an AI analytics company competing to displace an incumbent vendor at a travel company. The prospect had migrated to a new website months earlier and was watching revenue drop. Karthik's team had run two proof of concepts, demonstrated clear findings, and surfaced root causes the client's own team hadn't identified.
By every technical measure, the win was there.
But the deal was stalled.
When Chad dug in, the issue came into focus fast: the proof of concept had been built around finding the root cause of the revenue drop. And it succeeded. But it never explicitly connected that root cause to what actually mattered to the executives in the room: fixing the revenue problem itself.
"At the top, the person that's going to weigh in on this doesn't see it as a data problem. They see it as a revenue problem." — Chad Wilson
That's the gap. And it's more common than most presales teams realize.
The Value Pyramid Problem
In Discovery2Win, we use a model called the Value Pyramid to map where motivation lives inside an organization.
At the base: operational impacts. How does your solution change the way work gets done day to day? This is where most presales conversations live, where proof of concepts are designed to play, where features get demonstrated and technical wins get logged.
But operational clarity doesn't close enterprise deals.
Moving up the pyramid, you reach departmental impacts: team productivity, department-level metrics, efficiency of the function. Higher still, you reach strategic impacts: market position, competitive risk, business performance.
Here's the nuance most miss: decision-makers don't fund solutions based on what sits at the base of the pyramid. They fund solutions based on what's being discussed in their leadership meetings, and those conversations are happening at the top.
In Karthik's deal, the SVP of Data wasn't under pressure because dashboards were slow. He was under pressure because a publicly listed company was watching a revenue metric decline with no clear owner of the fix.
That's a strategic problem. Karthik had solved an operational one.
Discovery Doesn't Stop After the POC
One of the most important coaching moments in the session came when Chad pointed out that Karthik didn't yet know who had asked the SVP of Data to look into this problem, or who the SVP would ultimately report back to.
That gap matters.
"Who is accountable to the revenue number?" Chad asked. "Because that person is probably not in your stakeholder map right now. And they're the one who's going to fund this."
This is the discipline the CDIM™ Framework (Current, Desired, Impact, Metrics) is designed to build. Not just capturing what your prospect says their challenge is, but stacking the impact of that challenge upward until you reach the level where real decisions get made.
- Current: The dashboards give them numbers, not root cause.
- Desired: Understand exactly why revenue dropped after the website migration.
- Impact: If they can't identify the root cause, the revenue problem doesn't get fixed, quarter after quarter.
- Metrics: Search-to-book ratio. Overall purchase revenue. Ancillary add-on revenue.
Karthik had the metrics. What he didn't have was a clear line connecting those metrics to who owned the pressure to improve them, and whether that person was in the room.
Discovery isn't a pre-POC activity. It runs the full length of the deal. And it doesn't end until you understand who owns the outcome you're being asked to solve.
The Stakeholder You're Ignoring
There's another layer here that often gets missed.
Not everyone in a deal is neutral. In Karthik's case, the Director of Data, sitting between the technical team and senior stakeholders, was in a weak-to-neutral posture. The working hypothesis: her team was deeply trained on the existing platform, and Karthik's AI tool had surfaced findings her team hadn't caught.
That's not just inertia. That's potential threat perception.
Think about it from her perspective. An outside vendor comes in and identifies something your team missed. Your job is to know this data. You're the Director of Data.
Chad framed it directly: "Maybe they perceive that you knowing something they couldn't figure out as a risk. And in that case, they want to discredit you, not support you."
This is where stakeholder mapping stops being an org chart exercise and starts being a strategy problem. You don't just need to know who's in the deal. You need to know how each person is experiencing the deal, and what it would mean for them personally if you win.
Some blockers just need to be neutralized. Others can be converted. But you can't manage someone you haven't diagnosed.
What to Do When the Deal Is Stalled
Here's what Chad recommended to Karthik, and what applies to any deal that's technically proven but commercially frozen.
1. Build a mutual action plan tied to one specific metric. Don't ask for open-ended adoption across all use cases. Pick one metric the prospect cares enough about to act on. In Karthik's case, that's search-to-book ratio. Time-bound the pilot. Get agreement from both sides on what success looks like, and what happens next if you achieve it.
2. Connect operational findings to strategic pressure. The proof of concept found root causes. Now connect those root causes to the revenue metric the organization is measured on. The SVP of Data needs to be able to walk upstairs and say: here's what we found, here's what it will take to fix it, and here's what fixing it is worth.
3. Find the executive with a revenue stake. Somewhere above the SVP of Data, someone is accountable for the revenue number. That person may not know enough about your solution, or may not know about it at all. That's the gap. Find them.
4. Address potential blockers before they become vetoes. Have the conversation about the Director of Data with your internal sponsor. Understand whether her team needs to be converted, neutralized, or managed around. Then build a plan.
The Real Work Starts After "Technical Win"
There's a moment in every POC where you know you've built something that works. The data supports it. The findings are real. The technical problem is solved.
That moment feels like a win. And in one sense, it is.
But in a complex enterprise deal, the technical win is the beginning of the commercial conversation, not the end of it.
Buyers don't approve budgets because you found something their old vendor missed. They approve budgets because someone with a stake in the outcome is convinced that approving this budget is the best way to fix a problem they're accountable for.
Your job after the POC is to build that conviction. Connect the finding to the outcome. Map the outcome to the stakeholder. Find the pressure that's driving the urgency, because there's always pressure. You just have to find where it lives.
The deal isn't stalled because your solution doesn't work.
It's stalled because the right people don't yet feel enough reason to move.
That's a discovery problem. And discovery has a framework.
Want to work through a deal live? The 2Win Global and Presales Collective partnership is bringing exactly this kind of coaching to the PSC Pro+ community: real deals, real time, real guidance. Stay connected for what's next.
2Win!
