Multi-Threading Without Going Behind Your Champion's Back

The way single-threaded deals actually die

Nobody loses a single-threaded deal in a dramatic phone call. There is no moment where the buyer tells you they went with a competitor and you get to fight for it. What actually happens is much quieter.

Your contact stops replying. You send the follow-up. You send the second follow-up with the case study. You send the breakup email that you read on LinkedIn, the one that is supposed to be so charmingly self-deprecating that they cannot help but respond. Nothing. Three months later you find out on LinkedIn that they moved to a new company in March, or that the whole department got folded under a different VP, or, worst of all, that the deal went to a competitor because someone in a room you were never invited to said "I've heard bad things about them" and your champion did not have the ammunition or the political capital to fight back.

That is the real failure mode. Not rejection. Evaporation.

I have watched a lot of reps respond to this by deciding they need to multi-thread, and then executing it in the clumsiest way imaginable. They go find the CFO on LinkedIn and send a connection request. They cc the champion's boss on a follow-up email. They mention on a call that they "reached out to a few other people on the team just to make sure everyone's aligned." And then they are confused when the champion, the one human being in that entire building who actually liked them, goes cold.

Multi-threading sales deals is not a contact-count problem. It is a permission problem. The reps who are good at it are not the ones who are best at finding email addresses. They are the ones who have made their champion feel like bringing in more people was the champion's own idea, and a good one.

Why going around your champion is worse than doing nothing

Start with the thing that is easy to forget when you are staring at a pipeline review and someone is asking why the deal only has one contact on it. Your champion is a person with a job, a boss, and a reputation inside that company. When you go over their head or around their side without asking, you are not just being rude to them. You are creating a problem they now have to manage.

Their boss emails them: "Who is this vendor and why are they contacting me directly?" Now your champion has to explain a process they had not planned to explain yet, defend a purchase they had not built the case for yet, and do it while looking like they are not fully in control of their own evaluation. You have made them look junior in front of the exact person whose approval you need.

Almost every rep I have watched do this thought they were being proactive. From the buyer's side it reads as untrustworthy. And here is the part that should worry you more: it tells them something about how you will behave after they sign. If you will go around them to close, you will go around them when there is an implementation problem, or a renewal, or an upsell. The single-threaded relationship you had was fragile. The one you have now is hostile.

So the whole game is getting to a multi-threaded deal with the champion's blessing, out in the open, ideally with the champion doing the introductions for you.

Ask on discovery, before you need it

The biggest mistake in timing is asking for other stakeholders when you have started to need them. That is usually somewhere around proposal stage, when the deal has gone quiet and your manager is asking questions. By then the ask is transparently self-serving. Your champion can hear the desperation in it. "Is there anyone else we should loop in?" at week eight means "I do not trust you to close this."

Ask on the first real call instead. On discovery, when you are still in diagnosis mode and the ask sounds like process rather than pressure.

The way I frame it is to make it about how their company buys, not about who I want to talk to. Something close to this:

"Before we go further — when your team has bought something like this before, what does that usually look like internally? Who ends up needing to have a view on it?"

That is a discovery question, not a sales question. It is genuinely useful to you regardless of the answer, and buyers answer it honestly because it does not feel like you are angling for anything. You will hear things like "IT has to sign off on anything touching customer data" or "anything over a certain number goes to the exec committee" or, revealingly, "honestly I have no idea, we have never bought one of these."

That last answer is gold, by the way. A champion who does not know their own procurement process is a champion who will get ambushed later. You now know your job includes teaching them how to buy.

Then the second half of the ask, which is the one that actually gets you the meetings:

"The reason I ask — the deals that go badly for both of us are the ones where someone comes in late with a question nobody prepared for. I would rather find those questions now, while there is time to answer them properly, than have them land on you in week six. Who would you want in the room early?"

Notice what that does. The risk is framed as landing on them. The extra stakeholders are protection for the champion, not access for you. And you are asking who they would want, which leaves them in control of the guest list.

In regulated industries this lands even more cleanly, because the buyer already knows a committee is coming. When I am working through a set of discovery call questions for a financial services buyer, the compliance and risk stakeholders are not an awkward addition to the conversation — they are the conversation, and the wealth management buyer is usually relieved that you brought them up before they had to. Same in security. If you are running discovery on a SOC, the analyst you are talking to knows perfectly well that their CISO will have opinions. Naming that early makes you look like you have done this before.

The three roles you need mapped before you write a proposal

I do not care how many contacts you have. I care whether you have covered three specific jobs. You can have six people on the thread and still be single-threaded in the only sense that matters, because all six of them are peers with the same view and none of them can say yes.

The technical validator

This is the person who can say "yes, this will work in our environment" and be believed. Sometimes it is IT, sometimes security, sometimes an ops lead, sometimes the one engineer everybody defers to. Their power is almost entirely negative — they usually cannot buy anything, but they can kill anything, and their kill is rarely appealed. Nobody overrules the security review.

What you need from them is not enthusiasm. You need the absence of an objection. Get them on a call early, let them ask their integration and data questions, and answer the ones you cannot answer with "I do not know, I will get you the exact answer by Thursday." Then get them the exact answer by Thursday. Technical validators are, in my experience, the easiest stakeholder in the deal to win over, because most reps talk over them and almost nobody actually follows up with documentation.

The budget owner

The person whose number the money comes out of. Not necessarily the signer — signing is often an administrative act that happens somewhere in finance. I mean the person who feels the cost personally, whose budget is smaller after this.

You need to know two things about them. Whether the money exists already, and what it is currently earmarked for. "We have budget" and "we would have to find budget" are entirely different deals with entirely different timelines, and a champion will sometimes tell you the first when the truth is the second, because they do not want to look powerless.

The way I get at this without interrogating anyone is to ask the champion: "If this goes ahead, whose budget does it come out of, and does that person know we are talking yet?" The second half of that question is the important one. If the budget owner does not know the conversation is happening, you do not have a deal, you have a research project.

The person who gets blamed if it fails

This is the one that almost everybody misses, and it is the one that kills the most deals late.

Somewhere in that organisation is a person whose name goes on this. If your product gets rolled out and it does not work, or the team hates it, or it causes an outage, or the numbers do not move, someone specific takes the hit. Sometimes that is your champion, which is convenient. Often it is not. Often it is an operations director or a department head who was not in the evaluation but will inherit the consequences.

That person, if they find out about the deal late, becomes the most dangerous stakeholder in it. They have every incentive to slow it down, because from where they sit, all of the downside is theirs and none of the upside is. And they can slow it down almost indefinitely with reasonable-sounding questions.

So find them early and give them something the others do not get: a serious, specific conversation about what failure would look like and what you do about it. Rollback plans. Support escalation. What happens in month two when adoption dips. Nobody else in the deal wants to talk about failure. Talking about it with the person who owns the downside is how you convert your biggest threat into a quiet ally.

When all three of those roles end up in the same room, the meeting gets genuinely hard to run, because each of them is scoring you against different criteria in real time. That is a preparation problem more than a talent problem — the structure I use for a demo in front of a managing partner, a litigation chair, and a risk committee is built entirely around sequencing whose question you answer first, and the same logic works in any room where the technical validator, the budget owner, and the blame-owner are all present at once.

When your champion says no

They will sometimes. "Let me handle the internal side." "He is very busy, I would not bother him." "Let's wait until we have something more concrete to show."

Do not push on the first no. Pushing turns a soft political preference into a hard position they now have to defend. Instead, treat the no as information and get curious about it, because there are only about three reasons behind it and they require completely different responses.

The first is that the champion is protecting their own status. They want to be the one who found this, who ran the process, who brings the finished recommendation to the exec team. That is not a bad instinct and you should not fight it. What you do instead is offer to make them look better rather than to replace them: "Totally understood. Can I build you the material you would need to take to them? Send me what their priorities are for this year and I will put together something you can present in your own words." You are not in the room, but you are writing the script for the room, which is often the better position anyway.

The second is that the champion does not actually have the relationship they implied. They said the CFO was on board. The CFO has never heard of this. Getting a real answer here requires you to make it safe to admit: "No problem at all. Out of interest, how much of a heads-up have they had? I only ask because if this is landing on them cold, we should probably pace it differently." You are giving them a graceful way to say "they do not know yet" without losing face.

The third is that there is politics you cannot see. A rivalry, a restructure in progress, a previous vendor failure with somebody's fingerprints on it. When I sense this, I stop asking about people and start asking about history: "Has the team looked at anything in this space before? How did that go?" The story you get back usually explains everything about why your champion does not want to introduce you to a particular person.

And if the no holds after all of that? Then you accept it, you note in your CRM that the deal is single-threaded and therefore fragile, and you forecast it accordingly. A deal you have honestly labelled as risky is worth more to you than one you have lied to yourself about.

The second-stakeholder intro call

You got the introduction. Now do not waste it. The single most common way reps blow the second stakeholder meeting is by treating it as discovery call number one all over again, asking a busy senior person to explain their own business to you while your champion sits there watching you re-litigate ground you already covered.

Here is roughly how I open those calls.

"Thanks for making the time. Sarah and I have had two conversations already, so I do not want to make you repeat any of that — I would rather use the time on the parts that matter to you specifically. Here is my understanding of where things stand."

Then thirty to sixty seconds of summary. What the problem is, what you have discussed, what is still open. Say it in the champion's language, using their words, and credit them for the thinking. Your champion should be sitting there feeling like they look smart in front of their colleague.

"Sarah, correct me if I have got any of that wrong."

That single line does more work than anything else in the call. It publicly positions the champion as the authority and you as the support act. It also gives them a chance to add the political context they could not put in an email.

Then you turn to the new stakeholder and ask the only question that really matters:

"What I do not know is what this looks like from where you sit. If this went ahead, what would have to be true for you to consider it a good decision six months from now? And what would worry you?"

Ask both halves. The first gets you their success criteria. The second gets you their objection while it is still small and unspoken, before it has hardened into a position they have stated out loud to other people. Take the worry seriously. Write it down visibly. Then close the loop by tying it back:

"That is useful. Sarah, did you know that was the concern? Good — then that is what we should build the next conversation around."

Now your champion has learned something from the meeting too. Which means the introduction paid off for them, which means the next one is much easier to ask for.

The habit, not the tactic

Multi-threading is not a stage you complete. It is a way of running the whole deal, where every conversation ends with you knowing slightly more about who else has a stake in this and slightly more about whether your champion is willing to introduce you. The reps who are good at it are not better networkers. They have just made the ask so many times that it comes out casually, as process rather than pressure, and their voice does not change when they say it.

Which is the actual difficulty. You can read the language above and agree with all of it, and then on a live call with a senior stakeholder listening, you will soften the ask into something so vague that nobody feels obliged to answer it. That gap between knowing the line and being able to say it cleanly under pressure is exactly what I built DrillCall to close — if this is the part of your deals that keeps breaking, I would take the permission ask and the second-stakeholder opener and run them out loud against an AI buyer twenty times before you use them on a real one. It is a very cheap way to find out that your version of the ask sounds apologetic.

Do that, and the worst thing that happens is your champion says no and you learn why. Which is still a better deal than the one that evaporates in March.