How to multi-thread a LinkedIn account without looking like spam
Contact several people at one company on LinkedIn without spamming them. Map the roles, space the touches, tailor each message and stop when one replies.
Get startedShort answer
Multi-threading means contacting more than one person at the same account, each with a message written for their role. Start with the person who feels the problem, find out how the team decides, then talk to the person who signs. Space the touches out and stop everyone on your side the moment one of them replies.
Map the roles at one account before you write anything
Pick five accounts you actually want this quarter. For each one, search the company name on LinkedIn and list every person whose job touches the problem you fix. Not the whole company. The people who either feel the problem or control the money to fix it.
Then write down what each of them loses while nothing changes. The person doing the work loses hours. Their manager gets asked why the team is behind. The budget owner is already paying for something that half works and has to defend that spend in a review. Three different losses, three different first messages, and none of them are about your product.
The person doing the work
- Role
- Hours on a manual step
- What they lose today
- The task, named, and how long it takes them
Their manager
- Role
- Predictability and headcount
- What they lose today
- Volume, missed deadlines, the workaround the team built
The budget owner
- Role
- Money and risk
- What they lose today
- What the current tool or process costs, and what happens if it stays
Decide who goes first and how far apart the touches land
Start with the person closest to the problem. They have no reason to stonewall you because you aren't asking for budget. A question about how the work gets done today usually gets a straight answer, and that answer is what you use later.
Then leave a gap. Two people at the same company hearing from you on the same morning reads as a mailshot. A few days apart reads as one person working an account.
Assume none of them compare notes until after they've replied to you. Both the manager message and the budget owner message have to make sense standing alone, with no reference to a conversation they never saw.
- 1
Day 1: message the person doing the work
One question about a specific part of their job. No pitch, no link, no calendar.
- 2
Day 3 or 4: message their manager
Name the problem at team level. Volume, missed deadlines, the extra hire. Ask how the team handles it now.
- 3
Day 6: go back to the first person
Thank them for the answer and ask who owns the decision on that kind of tooling. This is the message that produces an internal name.
- 4
Day 8 or later: message the budget owner
Use the name you were given and the problem you heard about. Say who pointed you there. Keep it to three sentences.
Write a different message for each role
The person doing the work wants their Tuesday back. The manager wants the team to hit the number without another hire. The budget owner wants to stop paying for two overlapping tools. Same product, three different openings.
Use the words they use. If their job post says reconciliation, don't call it financial operations optimisation. If a manager's post mentions burnout, ask about workload, not wellness.
One message, sent to three people
- We help companies like yours improve efficiency across the whole team. Do you have 15 minutes this week?
- I'd love to show you how our platform helps teams grow faster.
Written for the role
- To the person doing the work: your post mentions closing the books on the 5th. Is the reconciliation still done by hand?
- To their manager: you're hiring two ops analysts. Most teams that size hit a wall at the same point. What's the wall here?
- To the budget owner: Priya said your team spends a day a week on reconciliation. Worth 10 minutes on what that day costs you?
Paste this job
Note template:
Hi {first name}, you're hiring a {role} and the post mentions {task}. We do {thing} for {kind of company}. Is {task} still done by hand there?
Swap in the actual task from their post. If you can't name it, you haven't picked the right person yet.Keep the story straight when one of them replies
The first reply is where multi-threading either pays off or turns messy. Whoever answers is now your route into the account, and the other threads need to reflect what you just learned.
Example
- You
Hi Priya, saw Northwind is hiring two ops analysts. Is the weekly reconciliation still done in spreadsheets?
- Prospect
It is, and it's the reason we're hiring. Takes my team about a day a week.
- You
That matches what I see at other 40-person agencies. Who owns the decision on tooling for that team?
- Prospect
Probably Marcus. He runs finance ops.
- Suggested reply
Thanks Priya, I'll keep this short so I don't add to your week. Is the reconciliation problem something Marcus is already looking at, or would a two-line note from you land better than a cold message from me?
The draft asks for one thing: a read on whether Marcus is already looking at this. Priya can answer that in a sentence without booking a meeting or vouching for you. That is the whole ask.
Split accounts across a small team without stepping on each other
Two people from your side messaging one account is fine when they are after different people and know about each other. It's a problem when the founder's cold note lands the day after the SDR's follow-up.
Give every account one owner. The owner sends. Everyone else can read the thread and pass on what they learn. In a shared sheet that means one row per company with the owner's name on it.
The second half is the pause rule. The moment anyone at that company replies, the rest of your team stops sending to that account until the owner says otherwise.
- Columns worth having: company, owner, who has been contacted, the date of the last touch, and the last thing they said.
- Someone senior joining late reads the thread first, then sends a message that references it. A founder who opens cold after a week of SDR work undoes the week.
- If a reply lands with someone who isn't the owner, they answer once and hand it back. Ignoring a reply is worse than two voices.
- When someone says no, take the whole company off every list for that quarter. Not just that person.
One owner per account. Everyone else reads, nobody else sends.
Doing this with Kinlead
Kinlead holds the role split in the lead data, so you aren't maintaining a second spreadsheet. You describe the buyer you want or point it at your website, and each lead is scored from 0 to 100 against that profile, with anything under the fit line dropped. Stakeholders for one account can sit in a lead group named for that account or that role.
Outreach runs from each person's own LinkedIn account, connected through Unipile, and Kinlead never stores the LinkedIn password. It sends at most one action every five minutes per account, inside limits you set and a send window in the lead's time zone, so the gap between a first touch and a follow-up comes from the schedule instead of from you remembering.
- 1
Build the groups
Score and group leads by role, so the ops manager and the finance owner sit in separate groups even when they share an employer.
- 2
Point campaigns at each group
Different [campaigns](/features/campaigns-and-send-windows) can point at the same group or different ones, each with its own goal, tone and your sales playbook.
- 3
Read before it sends
Queued messages sit on the Actions page where you can read and edit them, and any campaign can be paused.
- 4
Watch one inbox
Replies from every campaign land in a [unified inbox](/features/unified-inbox), sorted by intent with interested ones first, and you get an email when someone replies.
If you want to read every reply before it goes out, set the campaign to hand the conversation to you at the first reply. The AI modes reply on their own.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to multi-thread a LinkedIn account without looking like spam.md