I once watched a friend lose his entire photo library. Twenty years of it. Children growing up, holidays, his wedding, the lot.
He had it all on one laptop. No backup. The laptop didn't even break dramatically, it just quietly stopped turning on one Tuesday. And that was that. Two decades, gone, because everything important had been trusted to a single point of failure.
A single-threaded account is that laptop. One warm contact, no backup, and everything important resting on whether that one person stays put, stays happy, and stays employed. It works right up until the Tuesday it doesn't.
Multi-threading is the difference between an account that grows with the customer and an account that evaporates the moment your champion changes jobs. It is the single biggest predictor of both renewal rate and expansion rate in enterprise accounts. And most reps simply don't do it.
The data is brutal
Let me hand you the numbers, because this is not opinion.
Gartner says the average B2B purchase now involves 11 stakeholders. Buying groups have grown from around 5 people a decade ago to as many as 20 in enterprise deals. Forrester says 94% of sellers engage buying groups of 3 or more, and 38% sell to groups of 10-plus. Over 80% of sellers have lost or stalled a deal in the last 12 months because a key stakeholder left.
And then the one that should genuinely worry you: LinkedIn research says 78% of sales reps are single-threaded.
Put those together. The buying group has tripled in size, the cost of losing one stakeholder is enormous, and roughly four out of five reps are still betting the whole account on a single person.
One more, the optimistic one. Gartner found that customers who get information from suppliers that helps the buying group align internally are about three times more likely to pursue a bigger deal with less regret. Multi-threading does not just protect the account. It grows it.
Why single-threaded accounts fail
A single-threaded expansion attempt fails for one of three reasons, and each one is inevitable given enough time.
Your champion leaves or changes role. The retention rate for a rep who loses their single champion with no second thread is roughly 20%. Reps with two or more executive relationships keep nearly all of them through a champion change. That is not a small gap. That is the gap between a book that survives turnover and one that doesn't.
Your champion becomes a bottleneck. Every question routes through one person. They get busy. The deal slows. The customer's internal buying process has quietly evolved past what your champion can control, and you cannot see it because you only have the one window.
Procurement enters without context. At renewal, a procurement team looks at the spend and starts negotiating. Your champion tries to defend the value, but procurement is paid to cut, not to defend. With no second thread to the budget owner, you get commoditised. It is one of the ten ways an expansion deal dies.
And a fourth, specific to expansion: the next deal almost always needs a buyer you do not have. A security module needs the CISO. A sister business unit needs that division's GM. Every expansion vector beyond more-of-the-same requires someone new. If you have not been building those relationships before you need them, you will not close.
What multi-threaded actually means
Here is where most people fool themselves. Multi-threaded does not mean three people on the org chart you have emailed. It means three people who take your call when you ring, who have an opinion on the value you deliver, and who can speak internally on behalf of the relationship.
The principle is three-across-three. At least three stakeholders, across at least three functions or levels:
- An operator who feels the value daily.
- A manager or director who owns the outcome.
- An executive sponsor who owns the budget, or is the downstream beneficiary of it.
Three users on the same team at the same level is not multi-threading. That is redundancy. You have backed up the laptop to a folder on the same laptop.
The grid that fixes it
For every important account, draw a simple grid. Three functions down the side, your function, an adjacent function, governance: finance, legal, procurement, IT. Three altitudes across the top, operator, manager, executive. Colour each cell green, amber or red by relationship strength. A discipline like this is closer to MEDDPICC than to charm.
Almost every AM has a strong diagonal. Champion, an operator, maybe an exec, all in the same function. And nothing anywhere else. The whole job is to colour in the rest of the grid over two to four quarters.
Aim for: three green cells minimum at steady state. Two or more relationships in an adjacent function before you attempt any cross-sell. At least one relationship in governance before you walk into a renewal negotiation.
On the executive sponsor
An executive sponsor is not a name on a slide. The test is simple, and uncomfortable. If your exec sponsor at the customer has not been in a meeting with someone from your company in the last six months, you do not have a sponsor. You have a name on a slide.
A real sponsor knows what you do for their organisation, has had at least one substantive conversation a year about outcomes rather than features, and takes your call when you need to escalate. That is built by delivering something to them specifically (an insight, a connection, a data point they cared about) and by showing up at their altitude when the topic warrants it. You should not be the only person from your side talking to them, either. Your own executive belongs in that mix. A VP-to-VP conversation is a different meeting from two individual contributors, and you cannot fake the altitude.
The cadence
Multi-threading is a discipline, not a project. Roughly:
- Monthly: review the grid on each top-tier account. Pick one cell to improve.
- Quarterly: one executive-sponsor conversation per top-tier account, maintaining or opening.
- On every trigger: a new hire, a re-org, a leadership change, add that person to your map within 30 days.
And avoid the four classic traps. LinkedIn-only "threading," a connection request is not a relationship. Over-investing in one strong thread because it feels productive. Refusing to bring in your own executives. And only threading when you need something: showing up to the economic buyer three weeks before renewal, having spoken to them twice in a year. You will lose.
Why this is a coaching problem
Every AM agrees with all of this. Then they go back to their book and over-invest in the one champion who replies fastest, because that thread feels warm and the cold cells feel like hard work. The knowledge is not the gap. The behaviour is.
That is the slice we work on at Replicate Labs. Not a one-off training on stakeholder maps, but a coach in the workflow that keeps your three-across-three grid in front of you, names the account that has quietly gone single-threaded, and pushes you to colour in the cell you have been avoiding. That is one slice of the complete guide to AI sales coaching.
Back up the photos. All twenty years of them. Not to a folder on the same laptop.