Multithreading B2B deals on LinkedIn: reaching more than one person per account

Multithreading means building relationships with several people in an account instead of relying on one champion. On LinkedIn it works when each person gets a different message for a different reason: the user hears about their daily work, the manager about results, and the person who might know the owner gets a simple question. Space the messages out, never copy text between them, and treat a referral to a colleague as a win.

A single threaded deal is a deal with one contact. It feels fine until that person goes on holiday, changes job or loses an internal argument, and then the deal disappears without a no. Multithreading is the habit of making sure there is always more than one person who knows you and wants the outcome.

Why do single threaded deals stall?

B2B purchases usually involve more than one person: someone who uses the product, someone who pays for it, and often someone who checks it, such as finance, security or procurement. If you only talk to one of them, three things go wrong:

• You hear one view. The champion's priorities may not be the decider's.
• You depend on one calendar. Holidays, sick days and busy weeks stop everything.
• You lose the deal when they leave. A new person in the role starts from zero, or with a tool they already know.

Who should you reach at each account?

Start with two or three. Add the checkers when the deal reaches them, not in the first week.

How do you write to several people without it feeling like a campaign?

Three rules:

1. Different reason, different message. Never copy text between colleagues. They compare notes.
2. Space it out. Days apart, not the same morning.
3. Be open about it when it helps. "I have been speaking with Ana on your team about X" is fine once there is a real conversation. Do not imply a relationship that does not exist.

Illustrative examples for one account:

• To the user: "Hi Ben, you run the inside sales team at [Company]. When a lead comes in from the website after hours, how long does it usually wait before someone answers?"
• To the manager, a few days later: "Hi Clara, I have been reading about [Company]'s expansion into Poland. When a team grows across two markets, response time to new leads is often the first thing to slip. Is that on your radar this quarter?"
• To the person who may know: "Hi Dan, quick question: who at [Company] looks after how inbound leads are handled? I want to make sure I write to the right person."

Why is a referral a good outcome?

Because the colleague who points you to the right person has just introduced you inside the account. In the Lamothermic foundry campaign, about 23 replies said not my department. One question, asking who handles sourcing, turned those into 14 referrals, 12 of them to buyers, and those 12 counted among the campaign's 42 buyer side outcomes. When someone says it is not their area, thank them and ask who it is. Then write to that person, mentioning who sent you, which is honest and much warmer than a cold message.

When should you multithread?

• At the start, for target accounts where you know the deal will involve several people.
• After the first meeting, to meet the decider and the people who will use the product.
• When the champion goes quiet, to find out whether the deal is still alive.
• When the champion leaves, immediately, as the customer success guide describes for existing customers.

What should you track?

For each open deal, count the people who know you and have replied. One is fragile. Two or three is healthy. Note who each person is and what they care about, so every message builds on the last one. A CRM that holds the full conversation history across channels, as Sellinger's does, keeps that view in one place.

Where can an AI agent help?

An agent can find the people in each role at an account, write a different first message for each from what is public about them, space the messages out and follow up on silence. When someone refers you to a colleague, it can draft the next message to that person, mentioning who sent you.

What stays with you: choosing which people matter, reading the internal politics, and every conversation once a deal is real. In Sellinger, a campaign can run in approval mode, where every message waits for you, and you can take over any conversation. LinkedIn activity stays steady: the defaults are 20 invitations a day per account, varied by a few each day, and 150 a week.

What if the champion does not want you to contact colleagues?

It happens, especially when the champion fears losing control of the project. Do not go around them. Instead:

• Ask for their help. "Who else will have a view on this? I want to make sure we answer their questions before they become blockers."
• Offer something for the others. A short summary they can forward, or a call they lead and you join.
• Explain the risk honestly. Deals with one contact stall when that person is busy. Most champions understand that it protects them too.

If the champion still refuses, respect it and note the risk in your forecast. Going around a champion who said no usually loses both the champion and the deal.

Common mistakes

• Adding people too fast. Five new contacts in one week at one account looks like a campaign.
• Copying the champion on every message. It can feel like you are reporting on them.
• Forgetting the checkers. Finance, security and procurement can stop a deal late if nobody spoke to them.
• Letting a referral go cold. Write to the referred person within a day, while the introduction is fresh.

A checklist

• [ ] Target accounts have two or three named people, each with a reason to talk.
• [ ] No two colleagues receive the same text.
• [ ] Messages to the same account are days apart.
• [ ] A not my department reply always gets a who is it question.
• [ ] I count people engaged per deal, not just deals.