# Connection request checklist for target account lists
> Coordinate LinkedIn connection requests across multiple stakeholders in a target account to create internal buzz and increase response rates.
- HTML: https://getkinlead.com/connection-request-checklist-for-account-based-marketing
- Markdown: https://getkinlead.com/connection-request-checklist-for-account-based-marketing.md

**Short answer:** To run a LinkedIn connection strategy for target accounts, connect with a cluster of stakeholders instead of one person. When several people at the same company see your name, you stop being a stranger in their notifications. Coordinate the order and the notes so you look like one consistent presence rather than a list being worked through.

## Map your account stakeholders

Targeting one person at a company is a gamble. If that person is busy, on holiday, or simply doesn't see the value, the whole account goes quiet. Multi-threading means you build connections across several levels of the same organization, so one ignored request doesn't end the conversation.

Start by listing everyone at the account who touches the problem you solve. Read the company page, look at who posts, and check who comments on those posts. Job titles help, but the org chart on LinkedIn is often out of date. A person with a plain title who posts about the team's roadmap is worth more than a director who hasn't logged in for months.

Aim for three to five people per account. More than that starts to look like a campaign against the company rather than interest in the team.

| | Role | Responsibility | Goal for connection |
| --- | --- | --- | --- |
| Decision maker | Signs the contract, for example a VP of Sales | High-level business outcome and return on spend |
| Champion | Uses the tool daily, for example a Sales Ops manager | Solving one specific frustration they feel every week |
| Influencer | Trusted advisor, for example a Head of Enablement | Making sure the change fits how the team already works |
| End user | Does the work, for example a senior SDR | Making their day easier or faster |

## Sequence your outreach

The order of your requests decides whether you look like a strategic partner or a salesperson working through a list. Going straight to the VP makes you one more pitch in a crowded inbox. Starting lower gives you context you can use later.

Leave a few days between each request. You want the earlier person to have seen your name before the next one arrives, and you want time to read whatever they post in between. If someone accepts and replies, pause the sequence and talk to them properly before you add another name.

1. **Start with the end user or champion.** Send requests to the people doing the daily work first. Ask about the bottleneck they actually hit, not the one your deck is built around.
2. **Connect with the influencer.** Reach out to the person the VP trusts. Reference a shared goal, or something you learned from the first conversation, without quoting anyone by name yet.
3. **Target the decision maker last.** Send the request to the VP once their team has seen your name. The note can mention that you've been talking with the team about a specific problem.
4. **Keep posting while you wait.** Publish something relevant to the account's industry each week. Your posts land in the feeds of everyone who accepted, which keeps your name in front of them without another message.

## Write requests that don't read like pitches

People decline connection requests that look like the first line of a sales sequence. The note has one job: give the person a reason to accept that has nothing to do with your product.

Reference something specific. A post they wrote, a hire their team made, a comment they left on someone else's thread. If you can't find anything specific, you probably haven't looked hard enough yet.

Keep it short. LinkedIn caps connection notes under 200 characters, so you have roughly one sentence plus a greeting. Write it the way you'd say it out loud to someone across a table.

**The pitch**

- I see you are the VP of Sales and I have a tool that helps teams grow revenue.
- I'd love to jump on a 15 minute call to show you my demo.

**The observation**

- I'm following your team's move into the EMEA market and wanted to connect.
- I noticed you commented on Priya's post about pipeline gaps and wanted to join your network.

```
Hi {first name}, your comment on {colleague}'s post about {topic} matched something we keep hearing from {role}s. Sending a request so I can follow what your team posts.
```

## Coordinate the internal buzz

Internal buzz happens when two people at the same company compare notes and realize they've both seen your name. You can nudge that along by mentioning a colleague in a later note, but only after the first conversation has actually happened.

Don't invent a conversation. If you say you spoke with someone, you need to have spoken with them. People at the same company talk to each other more than you expect, and a made-up reference ends the relationship before it starts.

- **you:** Hi Mark, I've been chatting with your Sales Ops lead, Jane, about the friction in your lead routing. Wanted to connect here as well.
- **them:** Oh, Jane mentioned you. I'm curious to see how you're thinking about this. Request accepted.
- **you:** Happy to share. Jane said the handoff between marketing and sales breaks down around the qualification step. Is that how you see it from your side?

> Mention other stakeholders by name only after you've actually spoken with them. Saying 'I'm already talking with Sarah about your onboarding process' creates curiosity. Inventing it creates a problem.

## Keep the pace human

LinkedIn doesn't publish exact limits for connection requests, and anyone who quotes you a number is guessing. What matters is that the account you send from doesn't look like a machine working through a list.

Spread requests across days. If you have five people at one account, that's five requests over a week or two, not five in an hour. Watch your pending invitations too. If a large share of them sit unanswered, slow down and let the pool clear before you add more.

The same applies across accounts. Ten requests to ten different companies in one morning is still a burst, and it still looks the same to LinkedIn.

> If LinkedIn pushes back on your account, stop sending and read the warning before you do anything else. Adding more requests to a flagged account is how small problems get bigger.

## Track what happens after the request

Most of the value from multi-threading shows up after the request is accepted. Note who accepted, who replied, and who ignored you, because that pattern tells you which role in the account actually cares about the problem.

Keep a simple record per account: name, role, date sent, accepted or not, and what they said. After ten accounts you'll see which role tends to reply first, and you can start your sequence there instead of guessing.

| | Signal | What it means | What to do next |
| --- | --- | --- | --- |
| Accepted, no reply | They recognize the name but have no reason to talk yet | Engage with their posts for a week, then send one message with a specific question |
| Accepted and replied | Real interest in the topic | Ask one question about how their team handles the problem today |
| Request ignored | Wrong person, wrong timing, or the note missed | Leave it. Move to another stakeholder and revisit next quarter |
| Request declined | Usually means the note read like a pitch | Rewrite the note before you try the next person at that account |

## Doing this with Kinlead

Running this by hand across a dozen accounts gets messy fast. Kinlead finds people who match the customer you describe or your website, scores each lead from 0 to 100 against that profile, and keeps only the ones above the fit line. Leads live in lead groups, and any campaign can point at any group, so one group per target account works.

Outreach runs from your own LinkedIn account through Unipile, at a human pace: each account sends at most one action every five minutes, inside daily limits you set and inside a send window in the lead's time zone. Connection notes are AI-written under 200 characters and open with why that person became a lead. You can read and edit queued messages on the Actions page before they send, and pause any campaign.

The [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles, reads the comments on their recent posts, and turns commenters who look like buyers into leads, keeping the post URL and what they commented. Pro costs $49 a month after a 7-day free trial, and you can book a call at /demo to run it on your own target list.

## Related

- [AI LinkedIn connection request templates](https://getkinlead.com/ai-linkedin-connection-request-templates.md)
- [Building prospecting lists](https://getkinlead.com/building-prospecting-lists.md)
- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)

## Common questions

**Should I send a note with every connection request?**

Yes, when you're targeting specific accounts. A note built on a real observation gives the person a reason to accept that has nothing to do with your product.

**What if the decision maker ignores me but the champion accepts?**

Ask the champion how they'd bring the decision maker in, based on the value you've already discussed. A warm introduction from inside beats a second cold request.

**How many people per account is too many?**

Three to five is a workable range. Past that it starts to feel like the company is being worked rather than the team being understood.

**Do I need Sales Navigator for this?**

No. Standard LinkedIn search and company page employee lists are enough to build the stakeholder map for most accounts.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
