# Scaling LinkedIn outreach with a small sales team
> A practical checklist for splitting target accounts, setting per-account limits, and handing off LinkedIn leads when more than one rep does outreach.
- HTML: https://getkinlead.com/checklist-for-scaling-linkedin-outreach-with-teammates
- Markdown: https://getkinlead.com/checklist-for-scaling-linkedin-outreach-with-teammates.md

**Short answer:** Split your target market so each rep owns a clear segment, set invite and message limits for each LinkedIn account rather than for the team, and keep one shared list of who owns which lead. LinkedIn doesn't publish exact limits, so watch each account's pending invitations and back off before it gets restricted.

## Divide the target market before you add a second rep

Lead collision shows up before it costs you a deal. Two reps message the same founder in the same week, the founder notices both work at the same company, and the second message reads like a copy of the first one. The fix is ownership, decided in advance, before anyone opens LinkedIn.

Pick one attribute to split on and stay with it. Region, industry, company size and product line all work as long as a rep can tell from a glance at a profile which side someone falls on. If a rep has to think about whether a lead is theirs, the split is too vague.

Write the split into a document the whole team can open. A new person should get a segment, a list and a limit on their first day, not a login and good luck.

| | Split on | Example | Watch out for |
| --- | --- | --- | --- |
| Region | Priya takes North America, Tom takes EMEA | People in global roles belong to nobody |
| Industry | Priya takes fintech, Tom takes health tech | Companies that sell into several industries |
| Company size | Priya takes 1 to 20 people, Tom takes 21 to 100 | Accounts that grow past the line mid-quarter |
| Product line | Priya takes the reporting tool, Tom takes the API | Buyers who would want both |

> Put the owner in the lead list name, for example us-fintech-founders-priya, so anyone who opens the list knows whose it is before they message anyone.

## Set limits for each LinkedIn account, not for the team

LinkedIn does not publish how many invitations, messages or profile views an account can send per day. Anyone quoting an exact number is guessing, and copying someone else's number is how accounts get restricted. What you can control is how fast each account acts and whether it backs off when LinkedIn pushes back.

Set limits per account, because each account has its own history. One that has been active for years and posts every week can carry more than one created last month. Start below what you think the account can handle, watch what happens for two weeks, then raise it.

New reps on new accounts cause most of the trouble. Give them the smallest allowance on the team, add to it slowly, and don't set a first-week target that pushes them past it.

1. **Write each limit down.** Give every rep a number in a shared doc: invitations per day, messages per day, and the hours they should be sending. If the number only exists in your head, it isn't a limit.
2. **Stagger the sending.** Reps should work in small batches through the day. A burst of activity first thing in the morning looks nothing like a person using LinkedIn.
3. **Watch pending invitations.** If a rep has a pile of requests nobody accepted, they are spending their allowance on people who will never reply. Withdraw the oldest before sending more.
4. **Agree a stop rule.** If LinkedIn asks for verification or limits a feature on an account, that account stops sending for the day and the rep tells you. Nobody works around it.

> A limit nobody can see is not a limit. Keep every account's numbers in the same doc the team uses for lead lists.

## Give reps a framework instead of a script

Scripts degrade. One rep writes a message that works, the next copies the structure and swaps the name, and by the fifth person it reads like a mail merge.

Give the team a structure with slots they fill from the lead's own profile: something the person wrote or shipped, what their company does, the connection to what you sell, and one question that is easy to answer. The words change, the order doesn't.

Review openers together once a week. Read three aloud and ask the room which one they'd answer. Reps copy what they hear working far faster than what they're told to do.

**Copied script**

- Hi Dana, I help founders grow their business with AI. Do you have 15 minutes this week?
- Hi Marcus, I came across your profile and thought we'd be a great fit. Let me know if you want a demo.

**Filled-in structure**

- Hi Dana, your post about going from a 6-person team to 14 in one quarter stuck with me. We talked to a few agencies about that same jump and onboarding was where it got messy. How did you handle it?
- Hi Marcus, saw Northwind just opened a second warehouse. We work with ops leads wiring up inventory across two sites. Is that on your list this quarter?

## Keep one record of who owns which lead

Two spreadsheets become four, and the CRM nobody updates is worse than no record at all. Pick one place and make it the only place a lead can live.

Every lead gets one owner and one row. A row changes hands only when the new owner says they've taken it. Anything looser recreates the collision you split segments to avoid.

```
lead_url,name,company,owner,segment,first_touch,status,last_reply
linkedin.com/in/example,Dana Whitfield,Acme,Priya,us fintech,2025-03-04,replied,asked about pricing
linkedin.com/in/example2,Marcus Reed,Northwind,Tom,emea ops,2025-03-05,queued,

Rules:
- one row per person, never one row per message
- owner changes only when the new owner confirms
- status is one of queued, sent, replied, booked, dead
```

## Hand off interest without making the lead repeat themselves

Most hand-offs lose the thread. The rep says "I'll pass you to my colleague", the next message starts from scratch, and the lead explains their problem a second time to someone who wasn't there.

Hand off when the person has said yes to a conversation, not when they've merely replied. The first rep writes one sentence about who the next person is and why, then makes the introduction in the same thread with the context already on screen.

- **you:** That makes sense. The integration piece is where most teams we work with get stuck too. Worth a proper conversation?
- **them:** Sure, Thursday afternoon works.
- **you:** I'll bring in Sam, who handles the technical side. Adding them here so you don't have to repeat any of this.
- **draft:** Hi Tom, Priya filled me in on the warehouse sync issue, including the nightly job failing on the second site. I've held Thursday at 3. If you can send the error log before then, I'll come prepared.

## Check the team's numbers once a week

A weekly look at three or four numbers keeps the team honest without turning into surveillance. Look at the account, not just the rep.

Pick the numbers on Monday, share them openly, and fix what they point at. If everyone's pending invitations are climbing, the team is messaging the wrong people, not working too little.

| | What to look at | What it tells you | When to act |
| --- | --- | --- | --- |
| Pending invitations | how many requests are still unanswered on each account | withdraw the oldest before anyone sends more |
| First replies | which opening messages get a response | rewrite the openers that get ignored |
| Accepted hand-offs | whether the second person actually picked up the thread | ask the pair what broke before blaming the lead |
| Leads with no owner | rows in the list nobody has claimed | assign or delete them the same day |

## Doing this with Kinlead

Kinlead is built for the setup above: more than one person doing outreach and no shared password anywhere. A Pro admin invites teammates by email and chooses which workspaces each teammate can open. Every teammate signs in with their own login and connects their own LinkedIn account, and the admin pays for each seat.

Seats are priced like an extra LinkedIn account, and [pricing](/pricing) lists the current rate for extra accounts and seats.

1. **Invite the team and assign workspaces.** Each teammate opens only the [workspaces](/features/workspace) you give them, so lead groups stay with the rep who owns that segment.
2. **Set limits and send windows per account.** Kinlead sends at most one action every 5 minutes on each LinkedIn account, inside the daily invite and message limits and the [send window](/features/campaigns-and-send-windows) you set. If LinkedIn pushes back on an account, Kinlead pauses invites there and emails you.
3. **Read every reply in one inbox.** Replies from all campaigns land in one [inbox](/features/unified-inbox), classified by intent with interested replies first, and you get an email when someone replies.

> Removing a teammate ends their access and disconnects the LinkedIn account they connected. Do it after their campaigns wrap, not mid-week.

## Related

- [LinkedIn outreach playbook for early stage founders](https://getkinlead.com/linkedin-outreach-playbook-for-early-stage-founders.md)
- [Handling LinkedIn limits with multiple personas](https://getkinlead.com/handling-linkedin-limits-with-multiple-personas.md)
- [Team workspaces inside Kinlead](https://getkinlead.com/features/workspace.md)

## Common questions

**Can one person run two LinkedIn accounts for outreach?**

It works if each account has its own limits, its own send window and a clear reason to exist. Running two accounts from the same browser session with the same wording is what draws attention.

**What should happen when a teammate leaves?**

Remove their access the same day, disconnect the LinkedIn account they connected, and reassign their leads so nobody messages the same person twice.

**How do I know which rep writes the best messages?**

Compare replies against requests sent for each rep over the same period, then read their top three openers out loud to the team. Copy the wording that gets answers.

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

No. Standard LinkedIn search finds the same people for most small teams. Buy Sales Navigator when you need its filters, not because a process document told you to.

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