Marcus had been working the account for eleven weeks. A mid-sized financial services firm, 400 employees, a CX team that had been using legacy tooling for four years and knew it. Three calls, two demos, one full proposal. His champion, the Head of Customer Experience, had used the phrase “we’re basically decided” on their last call.
That was six weeks ago.
This story highlights how a seemingly healthy deal unraveled because three stakeholders walked away with different understandings of pricing, implementation, and project scope. Without a shared space to align expectations and surface questions, internal buyer conversations created uncertainty that ultimately stalled the opportunity. The lesson is clear: successful deals require not only strong seller engagement but also stakeholder visibility, transparency, and alignment throughout the buying process.
The deal that looked done
On paper, it was the cleanest opportunity in Marcus’s pipeline. The champion was engaged and well-informed. The buying committee had been identified: the CX lead who initiated the process, an IT director who needed to approve any integration work, and a Finance Director who would sign off on the contract. All three had been present at some point in the process. The proposal was thorough. It covered pricing, implementation timeline, integration requirements, and a phased rollout plan.
Marcus sent it on a Tuesday. He followed up Thursday. The champion replied the following week to say they were still reviewing internally and would come back to him. The tone was warm. The deal felt on track.
It wasn’t.
He sent two more follow-ups over the next three weeks. Both were read. Neither received a response. Then, on a Friday afternoon, a single-sentence email from the champion: “We’ve decided to pause the project for now. Thank you for your time.”
The silence after the proposal
The instinct in that situation is to call. Get on a video call. Find out what happened. Marcus did call, and the champion was gracious enough to spend twenty minutes explaining what had unfolded inside their organization.
What came out of that conversation was not what he expected.
The deal had not been lost to a competitor. It had not been killed by a budget freeze or a leadership change. It had stalled because three people walked away from the same proposal with three completely different understandings of what was being bought, and there was no shared space to surface those differences before the decision had to be made.
What the three stakeholders actually heard
The IT director had attended one demo and skimmed the proposal. His interpretation was that this was an exploratory pilot. He had no objection to running a pilot. He had significant concerns about a full integration with their existing CRM, concerns he had never raised with anyone because he assumed the commercial decision hadn’t been finalized yet. He was waiting for the right moment to bring them up. That moment never came.
The Finance Director had been sent the proposal by email and read the pricing section. She noted the setup fee and the annual subscription but assumed the figures were still open to discussion. The proposal didn’t say the pricing was final. To her, the numbers were a starting position in a negotiation that hadn’t properly started.
The CX lead, who had driven the entire process, believed implementation support was included in the contract. She had asked about it verbally in the first demo and received a general answer about the onboarding process. She took that as a yes. It wasn’t. Marcus had meant something narrower by onboarding.
Three stakeholders. Three versions of the same deal. None of them wrong about what they had heard. None of them aligned on what they had agreed to.
When the IT director’s integration concerns finally surfaced in an internal meeting, the Finance Director used the moment to revisit the pricing conversation she thought was still open. The CX lead, suddenly uncertain about the implementation scope, lost confidence. The whole thing unraveled in a meeting Marcus had no idea was happening.
What would have closed it
Not a better proposal. The proposal was complete.
Not more calls. There had been plenty of calls. Another touchpoint would have given Marcus another chance to answer questions, not an opportunity for the three stakeholders to work through their questions together, on record, with shared visibility.
What was missing was a single place where all three of them could see the same document, ask their actual questions, and get answers that were visible to the whole committee. The IT director’s integration concern, raised once in a shared context, would have been answered and addressed before it became a reason to delay. The Finance Director’s assumption about pricing would have been corrected by the written terms, not by an inference from a pricing table sent by email. The implementation scope would have been explicit in the proposal itself, not inferred from a verbal answer in a demo months earlier.
The deal had enough momentum to close. It lacked the structure to survive three people doing their due diligence separately.
The lesson that doesn’t make you feel better
Marcus’s process was not bad. It was solid. Multiple calls, thorough proposal, a strong champion, genuine responsiveness throughout. Most pipeline reviews would have called this deal healthy up until the Friday email.
What the process lacked was visibility. Not for Marcus, who had no way of knowing what each stakeholder privately understood about the deal. And not for the stakeholders, who had no way to see what the others were thinking before they all sat down in a room together.
A shared space where all three people could access the same proposal, see the same terms, and ask questions openly would not have guaranteed a yes. But it would have made the misalignment visible while there was still time to address it. It would have turned three private versions of the deal into one.
The deal did not die. It drifted. And no one noticed until it was already gone.
