Outbound strategy and playbooks
LinkedIn outreach for sales managers: running a team's outreach without chaos
By Asen Levov, co-founder of Sellinger. Published . Last updated . 8 minute read.
A sales manager makes LinkedIn outreach work across a team by setting four things before anyone sends: who owns which accounts, one set of rules for what may be said, a safe pace for every profile, and a weekly review of real conversations. Report meetings held with their base, not invitations sent, and coach from the threads, not from the dashboard.
This post is for people who run a team and its process: who owns what, which rules apply and how you review the work. If you are the person sending the messages every day, read LinkedIn outreach for SDRs and BDRs for the daily routine, and LinkedIn outreach for business development managers if your focus is partnerships.
One rep doing LinkedIn outreach is a habit. Eight reps doing it is a system, and systems fail in predictable ways: two reps write to the same buyer, one rep promises a discount nobody approved, another sends at a pace that gets the profile restricted, and the weekly report counts invitations because they are easy to count. This post is about preventing those failures.
Who owns which account?
Decide it before the first message. The simplest rule is that accounts are owned, not leads: if a rep owns a company, every person at that company is theirs. It prevents the most embarrassing failure, a buyer receiving the same pitch from two colleagues in one week.
Write the rule down and put it where reps work. A shared record of every conversation is what makes the rule enforceable. In Sellinger, the built in CRM holds contacts, deals and the full conversation history across channels, so anyone can see who already wrote to a person and what they said.
What are the team's rules?
Every rep should sound like themselves, but inside one set of rules. Most of the damage in team outreach comes from what reps say, not how often they send. A short rule sheet covers it:
| Rule | Example |
|---|---|
| What may be promised | Delivery times you can meet, features that exist today |
| What must go to a manager | Discounts, custom terms, anything about a contract |
| What is never said | Claims about competitors, invented results, fake familiarity |
| When to stop | After a no, after an opt out, after the last follow up |
| How to hand over | Who takes a qualified lead, and how fast |
In Sellinger these become the agent's rules, which apply to every message it writes for the team. A campaign can run in approval mode, where every message waits for a person to approve it, and the agent stops on its own when it cannot answer, for example a price it was not given. The rule packs for a B2B SDR team are a starting point.
How do you keep every profile safe?
Each LinkedIn profile has its own limits, and the profile belongs to a person. A restriction does not just stop a campaign, it locks a rep out of their own network. Set the pace per profile, not per team.
Sellinger's defaults are 20 invitations a day per account, varied by a few each day, 150 a week, and a quiet window from 01:00 to 08:00 account time. Every account can carry its own value. You connect each profile through a hosted login and Sellinger does not store LinkedIn passwords. No tool can guarantee that LinkedIn will never restrict an account, so treat any promise of unlimited volume as a warning.
Two team habits help: withdraw old pending invitations every couple of weeks, and do not let a new rep's profile start at full speed if it has never been used for outreach.
What should you review each week?
The dashboard tells you what happened. The threads tell you why. Spend most of the review on real conversations.
- Read five threads per rep. Two that booked, two that went quiet after a reply, one that ended badly.
- Ask what the buyer actually said. Most lost conversations die on the second message, not the first.
- Look for one change per rep. A better question, a faster answer, a cleaner hand over.
- Check the rules held. Any promise that was not allowed, any message after an opt out.
This turns coaching from opinions into evidence. A rep who sees their own thread next to a colleague's that booked learns more than from any training deck.
What should the team report?
Report outcomes with their bases, the same way every week:
| Metric | Base | Why |
|---|---|---|
| Reply rate | People messaged | Tells you whether the first message lands |
| Real reply rate | People messaged, quick replies such as thanks for connecting removed | Stops pleasantries inflating the number |
| Meetings booked | People messaged | The number leadership asks for |
| Meetings held | Meetings booked | Booked is not held |
The wealth advisor network study shows why the real reply rate matters: 44.8% of people messaged replied, but 44% of first replies were quick replies. The agent turned 1,035 of 1,751 thanks for connecting replies into real conversations by asking one question. A report that counted every reply the same would have hidden that work. Read count meetings honestly for the definitions we use.
How many profiles does a team need?
As many as you have people who are willing to send from their own name, and no more. Writing as a real person is what makes LinkedIn work. Our own outbound at Sellinger used on average 7.5 LinkedIn accounts, and over 1,500 calls were booked in the last 12 months by the owner's count. The wealth advisor network ran 26 profiles. Neither is a target. The right number is the number of people who will answer the replies.
Where does an AI agent fit in a team?
It takes the part of the work that is the same for every rep: building lists from the team's filters and signals, writing first drafts, sending follow ups on schedule and sorting replies. Each rep keeps their own voice, their accounts and their judgment on when a lead is ready.
For a manager the gain is visibility. Every message the agent sent sits in one place, with who sent it and what the buyer answered. The sales leaders use case describes the approval and analytics side in detail.
A first month plan
- Week 1: write the account ownership rule and the team rule sheet. Connect each rep's profile with default limits.
- Week 2: every campaign in approval mode. Reps approve their own drafts, the manager reads a sample daily.
- Week 3: first weekly thread review. One change per rep.
- Week 4: move reps whose drafts need few edits to automatic sending, and keep the rest in approval mode.
A worked example: one account, two reps
Example, invented for illustration. A team of six sells to logistics companies. Two reps, Mia and Jonas, both find the same freight company through different searches.
- Mia's search finds a head of operations. Jonas's search finds a regional director at the same company.
- Before either writes, the shared record shows the company is already owned by Mia, because she added it to her list last week.
- Jonas skips the company and moves on. If he finds a strong reason to write, he asks Mia in the team channel first.
- Mia writes to the head of operations. Three days later, if the first conversation is going well, she asks the manager whether to add the regional director as a second contact.
Nothing here needs special software. It needs one written rule and one place where everyone looks first.
Where do things usually go wrong?
| Symptom | Likely cause | What to change |
|---|---|---|
| A buyer says they heard from your company twice | No account ownership rule | Write the rule and check ownership before sending |
| Replies are fine but meetings are rare | Reps answer slowly or do not ask for a time | Review threads, agree an answer time |
| A profile gets a warning | Pace too high for a new or quiet profile | Lower the limits for that profile and ramp slowly |
| Reports look great but pipeline is flat | Invitations counted, not meetings held | Change the report to meetings held with a base |
| Reps sound alike | Rules are too tight | Keep rules about content, not about voice |
How do you handle a rep who is struggling?
Start with the threads, not the number. Read ten of their conversations. Often the problem is one repeated thing: a first message that asks for too much, a slow answer, or a reply that ends the conversation. Pick one change, try it for two weeks, and read the threads again.
A checklist
- [ ] Accounts are owned, and the rule is written down.
- [ ] One rule sheet covers what may be promised and what goes to a manager.
- [ ] Each profile has its own pace and a quiet window.
- [ ] I review real threads every week, not only the dashboard.
- [ ] Reports show meetings held with their base.
- [ ] Every rep answers their own replies within the hour.
Common questions
How do you stop two reps contacting the same prospect?
Should every rep write their own messages?
What should a sales manager review each week?
Can a team run several LinkedIn profiles safely?
How Sellinger helps
Read how it works on See Sellinger for sales leaders, or see a real campaign in Read the wealth advisor network case study.