Your champion loves your product. Here's why the deal still dies.

The champion loved it. The deal died anyway.

We write that autopsy the same way every time.

They went cold. The timing was wrong.

The budget got cut. Someone upstairs changed their mind.

What actually happened is that we wrote for one person, then sent them into a room holding four others who could say no.

The room we're never in

A head of engineering at a growing fintech has used our product at two previous companies. She wants it here. Good demo, thoughtful follow-up, scoped rollout, verbal yes.

Two weeks later she goes quiet. Three weeks later the deal is on hold and nobody will say why.

Here's the part we never see. She carried our one-pager into a review with a CFO, a security lead, an IT director and a procurement contact. Four people who skipped the demo, reading our messaging for the first time, in about five minutes, with an amateur translator.

Committees argue their way to a decision and almost none of that argument reaches the seller. What reaches us is silence, so we file the loss under timing.

The shared drive nobody can search

The strange part is that the answers usually exist already.

Somebody wrote a security one-pager last spring. An SE built a clean integration timeline for a deal in March. There's a slide with real payback math in a deck from the last board meeting.

All of it lives in the shared drive, in a folder called Marketing_Final, sitting next to Marketing_Final_v2. The champion has access. The champion will never find it.

A document nobody can retrieve in the moment is a document that doesn't exist. What matters is whether the champion can put a hand on the CFO answer at two o'clock on a Tuesday, without emailing us first.

The chairs and their questions

Every chair carries one fear and one question.

The champion wants the tool and quietly fears looking foolish for pushing it. Will this make me look smart for picking it?

The CFO protects the P&L. What's the payback, and what happens if we're wrong?

The security or legal lead exists to prevent the breach and the audit finding. What's the worst thing that happens if your platform is compromised?

IT keeps the stack running and fears an integration that eats a quarter. How much of my team's time, in week one and in month six?

Procurement owns vendor risk and contract terms. Who else uses you at our scale, and what are my exit terms?

Five chairs, five questions. Our messaging usually answers one of them.

The reply-all thread

And the review is rarely a meeting.

Someone forwards the pricing. Someone adds two people who weren't on the original.

Nine messages in, the security lead replies to all with a single line. Has anyone looked at their breach notification terms?

Nobody answers for four days. The thread goes quiet and nothing gets decided, which turns out to be its own kind of decision.

That's what our messaging has to survive. A thread we're not on, where one unanswered question from one person stops everything, and where the answer has to already be in the champion's hands.

The instinct at this point is to personalize harder. Write the one-pager for the head of engineering, tuned to her language, full of the outcomes she cares about. That makes the translation problem worse, because a document written to work in one person's hands only works in one person's hands.

Corporate Visions' work with Dr. Leff Bonney found that when seller and buyer agree on the problem being solved, win odds climb sharply, and that sellers get that agreement right less than half the time. That research is from 2024 and it still holds, because it describes how agreement forms between two people rather than what a market did last quarter.

Now add four more people to the thread. Agreement has to form four more times, in writing, without us.

This is the failure mode from positioning that sounds right while nobody buys, one stage later. What resonates with one persona comes apart across five.

The Committee Carry Test

Before a deal enters committee review, walk the champion through four questions. A fumble names the chair where the deal will die.

Can you explain our payback in one sentence a CFO will believe? "We save time" won't survive the thread. "It pays back in four months because it replaces $180K of contractor spend" will. If the champion can't say it cold, the CFO assumes there's no payback case, and that assumption is fair.

Can you answer the security lead's first question without coming back to us? They want to know what happens if we're compromised while their data is inside. One sentence covering data residency, encryption, breach notification and who carries the liability. "I'll get back to you" gets written down as vendor not ready.

Can you describe the integration without overselling how easy it is? IT doubles every claim of simplicity on instinct. "Two engineers, three weeks, one day of API config and the rest inside their existing identity system" gets believed. "Easy" gets discounted, and the discount applies to everything else we said.

Can you defend us as a vendor to procurement? Reference customers at their scale, funding stage, renewal rate, termination terms. Without those at hand, procurement assumes we're a flight risk, because that's the cheapest safe assumption available.

Four questions, one per chair that can stop us. Answer all four cold and the deal can survive a room we'll never sit in.

What each chair reads for

The CFO reads for payback and for the cost of waiting. Product copy goes unread.

A one-page brief that opens on the payback line, names what another quarter of waiting costs, and states the worst case in dollars will travel further than any deck. Frame the spend as cost per outcome rather than cost per seat.

The security lead reads for downside. They've already watched one vendor cause an incident and they're pattern-matching for the next one.

Open on breach response, then let the certifications sit underneath as evidence. A team selling into healthcare should have the HIPAA and BAA brief ready before the first demo, not on request.

IT reads for hidden cost. Give them a real week-by-week timeline and name the hours it takes from their people.

Say plainly which integrations we don't support. IT rewards the boring answer.

Procurement reads for whether we'll still exist in two years. Funding stage, customers at their scale, renewal rate, termination terms, data export policy. An early-stage company selling into a large enterprise has to overcompensate on stability signals, because "too early, no proof points" is the easiest reason to say no.

Build for the room

Start with the existing messaging house. Most have a lane for the champion and a vague executive lane pointed roughly at the CFO.

That vague lane is where deals die. Replace it with four real ones.

Each lane gets a one-pager, a few proof points, and one defensible answer to that chair's question. Build the CFO lane first, then whichever blocker shows up most often in stalled deals.

To find it, run a Monday audit. Pull the last three stalled deals and ask the AE which committee member pushed back. "It just stalled" doesn't count as an answer, so push for the name of the chair.

This is where buyer persona work earns its keep. A real persona is a decision profile for one chair in that room, and if ours only describes the champion, the messaging house has a hole in it.

Then build the carry kit. Four one-pagers, each written so one specific person reads it in a minute and walks out with their question answered. That's sales enablement at its most concrete, and the 40-slide deck stays in the drawer.

Put the kit somewhere the champion can reach without asking us. One link, four documents, each named for the person who needs it.

Then the test becomes a stage gate. No deal enters committee review until the AE confirms the champion can pass all four questions.

The room is the deal. It has five chairs, and our messaging furnishes one.

Send the answer before the thread starts.

What to do next

Run the Committee Carry Test on the three deals that stalled most recently. The chair the champion couldn't carry is the next positioning project, and fixing one lane usually moves committee-stage win rate on its own.

For a deeper template on documenting the persona lanes themselves, see how to write a B2B positioning document.