Reps spend more time prospecting than managing pipeline, which means…
Directors don’t have pipeline coverage to hit team quota, which means…
The SVP will miss their goal of returning 4X each seller’s fully-loaded cost.
While framing the product’s value, you could say:
Reps can engage warm leads who already know their value, which means…
Directors always see a healthy pipeline coverage ratio, which means…
The SVP hits every per-rep target in their financial model.
Now, your message ties everyone together.
2/ Handpick the Buying Team With Your Champions
Next, it’s time to work with your champions to buildout the buying team.
Assuming you have the 3 T’s of Multithreading in place, start weaving invitational language into your conversations to find and engage the right people:
Who else will this project impact, that hasn’t had a chance to weigh in yet?
Is there someone you turn to for advice on new projects or questions that are important to you?
That last question is particularly helpful, because it draws out contacts from the “shadow org chart,” and into your committee.
It captures the reality that influence isn't found in:
It's more often found in:
Finding and adding high-influence (they can change internal direction) and high-incentive (they’re personally aligned with your deal) contacts to your committee is key.
3/ Proactively Multithread in Parallel to Your Champions
I’ve worked on multiple deals involving four or more different business units, where group calls started with introductions. Not for me. But for them.
So that people inside the same company could meet each other for the first time.
Champions can’t introduce you to people they don’t know. So it’s your job to enable them with outreach to new contacts who should be involved.
This type of outreach sounds like:
< New Contact >, I was hoping to include you in a conversation about < internal priority > with the < business unit > team next week. Would it make sense for you to weigh in on this?
If this doesn’t sound relevant for you right now, all good — < your business unit > tends to be closest to this topic at first, so I thought I’d reach out.
Even if that contact doesn’t take you up on the invitation, nobody was ever mad they were invited into the process early. It can only help, especially if they end up playing a role later on. They'll remember your invite.
4/ Engage Your Own Team to Mirror the Buying Team
Your access to a buyer's team often mirrors their access to your team:
Bring an executive, meet their executive.
Bring a technical team, meet their technical team.
Collaborate with your team, multithread with theirs.
Operate in your own silo, they will too.
Do the same thing you're asking your buyers to do. Show up with your team.
Language to kick this off might sound something like:
You mentioned needing to keep < Exec > posted, and it’s always helpful when we’re all on the same thread as questions or changes come up.
So, I can either write them a quick update before our next call CC’ing you and < Your Exec >, or, I can send it to you, so you can forward on the invite while CC’ing us.
What would you be more comfortable with?
When Multithreading Goes Wrong: 5 Risks to Avoid
1/ Don't Ignore the Difference Between Contact & Deal Stages
Basing your deal stage (and therefore, close probability) on a small subset of engaged contacts — like champions — instead of group behavior is a recipe for forecasting whiffs.
The reason is that buying committee members don’t move in sync. Their “contact stages” don’t line up with their “deal stage.”
Move your deals backwards as needed to line up with 1 & 2 here. (This will drive your leadership nuts, but it's better to be accurate than commit to what won't close.)
2/ Don't Leave Champions to Handle Group Conflict Alone
If your sale feels too smooth, there’s a good chance your champions are sanding down points of friction on their own, to keep your deal gliding along.
The reality is someone always has a different opinion. You don’t want to leave champions to find and disarm those counterpoints alone.
Instead, you want to ask questions that invite yourself into the consensus-building process. Encourage dissent, and help the buying committee find consensus by saying:
Seems like everything’s moving forward smoothly, so I’m wondering, is there someone on your team who you think might be willing to disagree with us, so we can be sure we have a good fit?
The key to this phrasing is “willingto disagree.”
You’re asking for a nomination. Someone who would be so kind as to play the role of devil’s advocate. Which is a practice I’ve used with my own internal teams. If we’re launching a new project, we ask someone to poke holes in the plan to make sure it stays on track.
Guess who ends up filling the role? The strongest critic.
If you're feeling some dissent already, call this out more directly:
It doesn’t seem like < contact > fully agrees with this point. Is there something you feel we might have missed considering?
The idea here is that there’s never a single “decision maker,” because of all the people who can say no.
While there may be one “economic buyer,” everyone in the committee who can say "no" is a decision maker, too.
“No,” is a pretty clear decision just the same as “yes.” So you as the committee grows, bring dissent into the open. It’s exists whether you’re part of addressing it, or not.
3/ Stop the Sprawl: Don't Let the Buying Team Keep Expanding
Related to that last point, you want to keep the buying team narrow. If more people get involved than you truly need, not only are you increasing deal risk and indecision, you're compounding your workload.
Seth Godin describes how the volume of communications and approvals compounds with each new person on the committee:
Handshake Overhead is the result of the simple law of more people: n*(n – 1)/2. Two people need one handshake to be introduced. On the other hand, 10 people need 45 handshakes. More people involves more meetings, more approvals, more coordination.
The False Consensus Effect. Which leads people to overestimate just how much others actually agree with them.
The Transparency Illusion. Which causes us to believe that others know the full scope of what we’re thinking.
Champions fall prey to both when they believe the rest of the buying team is on the same page with them, when in fact, others may not understand why they believe in the deal so strongly.
A question like this can help pull your champion out of that illusion:
It seems like you want others to want this more than they do. If that’s a fair characterization, how do you think we could help them see what you see?
Or, you can try labeling someone who seemed to be scrolling LinkedIn during your last call:
Seems like < contact > could be happy with any outcome to our conversations. Whether we move forward, or don’t. Is there something missing from this project, that you think means this isn’t a must-have for them?
This is particularly key if who you’re calling out is a “High Influence” contact.
5/ Don’t Multithread When You Hear These Two Things
There are a handful of occasions when multithreading is counterproductive.
One case is when you see a buyer triangulating themself. Giving someone a clear and direct “no” is uncomfortable. So they’ll deflect to their team:
Sorry it’s taken a while to reply. The rest of our team just hasn’t been very interested.
This means you need to ask a question, to separate their interest from their team’s:
Gotcha. How are you feeling about that? Were you wanting your team to want this too? It’d be understandable if you weren’t.
Asking helps you determine if there’s a challenge with the committee — or this one contact.
Another occasion is discussing pricing. Holding a group call to discuss pricing is rarely the way to go. The reason?
People react how they believe they’re supposed to react in group settings.
They're less likely to share what they truly think. “Will I look like a pushover if I don’t push back on this?” Besides, you don’t need group approval on price. Just to finalize your scope. The first topic depends on budgets. The second depends on needs.
Since they’re separate topics, make them separate meetings.
You’ll have a more transparent and productive conversation this way.
An example here is:
< Champion >, I’m thinking we have a good handle on the full group’s needs now. It was also helpful to hear < Decider’s > goal on keeping your recurring spend low.
I rolled both of these inputs into a set of contract options for us to look at. Could the three of us put our heads together on feedback this week?
Creating the MVC: Minimally Viable Committee
If you find that the buying committee keeps expanding, it’s a sign of dysfunction. When we’re not confident, we let others decide for us. This shifts the blame, because if I let you make the call, and things go south, then ultimately, it’s your fault. Not mine.
In this case, you’re too multithreaded. Instead, you want to maintain the MVC. Just enough people to confirm the problem, create a use case, and clear the contract.
Reselling the Problem & Priorities Lastly, if you’re still hitting unresolved conflict or indecision, you might need to step back to see if something’s changed about the problem or its level of priority.
In complex deal cycles that stretch up to a year or longer, anything can happen. For example, you’re more likely to hit turbulent air and get rerouted while flying from London to Los Angeles, than from Los Angeles to San Francisco.
Nate is the CEO & Co-Founder of Fluint, the Buyer Enablement platform built for high-velocity sales teams. He's a 3X sales leader, 2x founder, and loves his wife, daughter, dark chocolate, and the Rocky Mountains.