LinkedIn outreach that gets accepted: warm up, then ask
LinkedIn outreach that gets accepted: fix your profile, warm the lead first with a view, follow and like, then ask. Notes, first messages and pacing.

Most LinkedIn outreach fails before the message is read. A stranger with a thin profile sends a connection request with a pitch in it, and the person on the other end, who has never heard of them, ignores it. Good LinkedIn outreach reverses that order: look credible, get noticed gently, then ask.
This is how we'd set it up, from profile to pacing, and how it fits next to email.
Fix the profile first
Everyone you contact will click your name. Make that click answer three questions: who are you, who do you help, and why should I care.
Photo and headline. A clear photo, and a headline that says what you do for whom, not just a job title.
About section. Two or three plain sentences on the problem you solve. No buzzwords.
Recent activity. A few real posts or comments show a person, not a shell.
Do this before anything else. No sequence makes up for a profile that looks like a throwaway.
Warm the lead before the connection request
The cold version of the ask is a connection request from someone they've never seen. The warm version gives them a reason to recognize you first. Before you send the request:
View their profile. Depending on their settings, they may see that you looked.
Follow them. A small, low-pressure signal.
Like a recent post. Pick their latest one; it ties to something they care about.
None of this is clever. It means that when the request arrives, your name isn't the first time they've seen it.
In SendingOS, a LinkedIn campaign can do exactly this: view their profile, follow them and like their latest post, then send the connection request. It can also check whether you're already connected first, and fall back to a note if needed.
LinkedIn outreach with or without a note
There's no universal answer, but there are two rules.
A generic note is worse than no note. "I'd love to add you to my network" says nothing, and it reads like a template. If you can't write one specific sentence about this person, send the request without a note.
A specific note is a small bet. One sentence that references something real (their post, their company, a shared group) gives them a reason to accept. Keep it short and leave the pitch out.
The simplest approach is to test both on similar small batches and compare acceptance. Don't borrow someone else's rate; measure your own.
The first message after they accept
Acceptance isn't a reply. It's permission to say a first sentence.
Thank them, briefly, and say why you connected.
Ask one small question related to their work, or share something useful.
Don't pitch in the first message, and don't attach a calendar link.
If they respond, then it's a conversation, and you can move toward your offer. If they don't, wait a bit before the next message and make it add something new, the same rule that applies to cold email follow-up.
For people who never accept, an InMail is another way to reach them outside your network. In SendingOS, you can add an InMail step on the not-connected path.
Pacing: slow is safe
LinkedIn doesn't publish exact invitation limits, so be skeptical of anyone quoting one as fact. What LinkedIn does say is about automation: its help page on prohibited software and extensions says it doesn't permit third-party software that automates activity on the site, and that accounts using such tools can be restricted or closed. Any automation carries that risk, including ours. Read the page yourself, and treat low volume and a slow ramp as the way you keep the risk small.
Practical pacing, as a principle rather than a number:
Start with a small daily volume and ramp over weeks, not days.
Spread activity across the day; don't batch it.
Back off if LinkedIn shows warnings or restricts the account.
Stay well under anything you'd guess is the ceiling.
In SendingOS, each LinkedIn avatar is set to up to 20 invites and 50 messages a day, and these are our own caps rather than a number from LinkedIn.
Run it next to email
LinkedIn works better as part of a plan than alone. A person who ignored two emails may accept a connection request from a name they've seen; a person who accepts may then see your email and recognize it. Run them as separate campaigns against the same target list: an email campaign and a LinkedIn campaign, each with its own steps.
The part that needs care is coordination. If someone replies on LinkedIn, your email sequence shouldn't keep sending. In SendingOS, email, LinkedIn and calling run in one sequencer, LinkedIn chats show up in the same Unibox thread as the email, and a reply on any channel stops the sequence everywhere.
For the strategy around it, see GTM strategy, and for the email side start with how to write a cold email.
Run email, LinkedIn and calling from one sequencer, with the deliverability setup built in.
Book a callQuestions
Should I add a note to a LinkedIn connection request?
A short, specific note can help, but a blank request is fine too, and a generic note is worse than none. The most reliable improvement is warming the lead before you ask, so your name is already familiar.
What should the first message after a connection be?
Thank them briefly and say something specific about why you connected. Don't pitch in the first message; ask a small question or share something useful.
How many LinkedIn connection requests can you send?
LinkedIn doesn't publish an exact limit, so any number you see quoted is an estimate. Start low, ramp slowly, and stop if you see warnings.


