The deal was done. That’s what I told my manager, my forecast, and myself.

Seven-figure infrastructure modernization deal. We’d beaten two competitors in the technical evaluation. The economic buyer, the CFO, had nodded along in the business case review. And our champion, the VP of Infrastructure, was all in. He was selling internally for us, running interference with procurement, telling me exactly what the CIO needed to hear. I’d built the entire forecast around him.

Then the reorg happened. He was moved to a different division, his replacement came in from outside, and within two weeks my emails started going unanswered. Within six weeks, the deal was officially “paused pending strategic review.” A year of work, dead. Not because we lost to a competitor, but because our entire deal lived inside one person’s head and that person left the building.

That loss rewired how I sell. Here’s what I learned.

The Anatomy of a Dead Deal

Single-threaded deals die in predictable ways. The champion leaves, gets reorganized, loses a political battle, or simply goes quiet under pressure, and because nobody else in the account knows your value story, there’s nothing holding the deal together. It’s not dramatic. There’s no lost bake-off. The deal just… stops.

The scary part is how good single-threaded deals feel while they’re alive. Your champion gives you perfect information, coaches you on every meeting, and makes you feel like an insider. It feels like the strongest position you can be in. It’s actually the most fragile. One person is a thread. A thread breaks.

Enterprise IT deals today almost never have a single decision-maker. Budgets cross IT, security, procurement, finance, and business units. If you’re only talking to one of those rooms, you’re not selling. You’re hoping.

Build the Buying Committee Map

After that loss, I started drawing a map for every serious deal. Not in my head. On paper. Five boxes, filled in with names, not titles:

1. The economic buyer, the person who can say yes to the money and whose budget it hits. If you can’t name them, you don’t have a deal, you have a project.
2. The technical evaluators, the architects and engineers who will bless or kill your solution. They don’t sign, but they can veto.
3. The end users and their managers, the people whose daily lives change. They’re your best source of real pain and your best internal sellers, if you earn them.
4. Procurement and commercial, the people who will negotiate you into the ground if you meet them for the first time at the end.
5. Security, legal, and compliance, the silent killers. In enterprise IT, a security review can add three months to your cycle. Engage them early or pay later.

For each name, I ask: what do they personally win if this deal happens, and what do they fear? That question, asked honestly, tells you more than any org chart.

How to Thread Without Threatening Your Champion

Here’s the objection every rep raises: “If I go around my champion, I’ll lose their trust.” And it’s a fair fear. Handled badly, multi-threading looks like going behind someone’s back.

The trick is to make your champion the hero of the threading, not the victim of it. Don’t ask for permission to “talk to your boss.” That sounds like an end run. Instead, ask questions that make expanding the circle their idea:

• “Who else feels this pain? I want to make sure we’re solving it for everyone, not just your team.”
• “When this goes to the CFO, what objections will we hear? Can we get ahead of them together?”
• “What usually stalls deals like this here? Let’s map the landmines now.”

Frame every new relationship as something you’re doing for the champion: building them an internal coalition, giving them air cover, making their business case bulletproof. A good champion doesn’t want to carry the deal alone. It’s exhausting and politically risky. You’re offering to share the load.

And the ultimate test: if your champion is genuinely threatened by you meeting their colleagues, they’re not a champion. They’re a gatekeeper. That’s critical information to have early.

The Champion Insurance Policy

Multi-threading isn’t just about more meetings. It’s about independent verification. For every critical fact in your deal (the timeline, the budget, the decision process, the competition), you need to hear it from at least two people. Champions, even honest ones, filter reality through their own optimism and politics. I now treat anything I’ve only heard from one person as unconfirmed, no matter how much I trust them.

Practically, this means:

• Get to the economic buyer yourself. Not through forwarded slides. In a room, hearing their priorities in their words. If your champion won’t facilitate it, that’s a red flag about the deal, not a scheduling problem.
• Build your own relationship with procurement early. Introduce yourself when there’s nothing to negotiate yet. When the endgame comes, you’ll be a known partner, not a stranger across the table.
• Never let your forecast rest on one person’s word. In every deal review, I ask my team: “If our champion disappeared tomorrow, who would keep this deal alive?” If the answer is nobody, the deal isn’t as far along as we think.

That dead deal still stings, years later. But it made me a better seller than any win. I haven’t lost a deal to a disappearing champion since. Because I never let a deal live inside one person’s head again.

Have you ever lost a deal when your champion went dark? How do you multi-thread without stepping on toes? Share your story in the comments.