How to build a LinkedIn outreach sequence
Build a LinkedIn outreach sequence that moves a prospect from a connection request to a booked meeting without sounding like a spammer or a bot.
Get startedShort answer
A LinkedIn outreach sequence is a small set of messages sent to one person over two or three weeks: a connection request, a first message that names a problem, and a few follow-ups that each add something new. It ends when the person replies, books a call or asks you to stop. Most of the work happens before the first message, when you pick people who have a reason to hear from you.
What a LinkedIn outreach sequence looks like
A sequence is a few messages sent to one person over two or three weeks, each one adding something the last one didn't. It starts with a connection request and ends when someone replies, books a call, or asks you to stop. Five touches is plenty. Past that you're messaging someone who has already decided.
The first message decides whether the rest get read. Someone who accepted your request an hour ago has no reason to care about your product, so the opener has to be worth reading on its own. That usually means naming a problem they have and giving away a small piece of the answer.
Space the touches by days. A message every morning reads as automation, and three weeks of silence means the earlier context is gone. Four to seven days between touches is a pace a person could plausibly keep up with, which is the point.
Connection request
- Touchpoint
- Day 0
- When
- Gives one specific reason you picked them
First message
- Touchpoint
- Same day or next morning
- When
- Names a problem their role actually has
Follow-up with proof
- Touchpoint
- 4 to 6 days later
- When
- Shows what the problem looks like solved
Low-pressure ask
- Touchpoint
- 5 to 7 days after that
- When
- Offers a short call with no pitch attached
Close the loop
- Touchpoint
- About two weeks later
- When
- Gives them an easy out and frees your pending invites
Choosing who goes into the sequence
Copy can't rescue a list of the wrong people. Before you write a word, decide the role, the company size and the trigger that makes someone worth a message this month. A 40-person agency and a 4,000-person software company need different sequences, different proof and different asks.
Triggers are easier to spot than most people assume. A company hiring three account executives is staffing up for outbound. A competitor's post about pricing pulls comments from people rethinking their stack. A founder writing about churn has told you what's keeping them up at night. Any of those gives you a first line that couldn't have been sent to anyone else.
Write the trigger next to every name before the sequence starts. It takes ten minutes per twenty leads and it's the difference between a message that gets a reply and one that gets ignored. If you're starting from zero, define your ICP first, then work through the buying signals checklist.
If you can't finish the sentence 'I'm writing to you because...', the person isn't ready for the sequence. Wait for a trigger.
Writing the connection note
The note exists to get the request accepted. Two sentences is enough: what you noticed, and why that made you send the request.
Reference something you actually read. A comment on a competitor's post, a launch announcement, a job posting for a role that didn't exist last quarter. Specific works better than clever.
If you have nothing specific, send the request without a note. A generic note gives people a reason to decline, and a declined request costs you more than no request at all. Skip 'I came across your profile', 'I'd love to pick your brain' and 'we help companies like yours'.
Generic or pitchy
- Hi Sarah, I'd love to connect and tell you about our platform that helps agencies grow.
- I came across your profile and would like to add you to my network.
- We help companies like yours save time and money. Let's connect!
Specific and short
- Your comment on Northwind's pricing post was the clearest take I've read on it. Sending a request.
- Saw you just hired your first AE. I've watched four agencies make that hire and the first 90 days are usually the messy part.
- You wrote that churn is a product problem, not a CS problem. I've been arguing that for a year.
The first message after they accept
Send it the same day or the next morning while your name is still familiar. The structure holds every time: the thing you noticed, the problem that follows from it, something useful, one question.
Keep it under about 80 words. Long first messages get skimmed on a phone, and the question at the end is the part you want them to reach. That question matters more than everything above it, because it's the only part asking for a response.
- 1
Open with the detail
One line about what you saw: a post, a comment, a job posting, a launch. It proves the message was written for one person.
- 2
Name the problem in their words
'Two new AEs and no pipeline to feed them' lands. 'Scaling challenges' doesn't. Use the language their team would use in a Monday meeting.
- 3
Give something away
A checklist, a teardown of their signup flow, a direct answer to the question they posted. No form, no gate, no 'book a call to get it'.
- 4
Ask one question
'Is that showing up for you yet?' is easy to answer from a phone. 'Do you have 15 minutes Thursday?' is not, at least not in the first message.
Follow-ups that don't sound like chasing
Most meetings come from the second or third message. That's also where accounts get restricted, because it's the point where people start sending 'just checking in' on a schedule. The rule that fixes both: every follow-up carries information the last one didn't.
A follow-up can share a result from a similar company, a short resource, or a change in their situation you noticed since. It can also be a shorter, plainer version of the same question. What it can't be is a reminder that you exist.
Example
- You
Hi Sarah, saw your comment on Northwind's post about pipeline coverage. Most agencies at your size hit the same wall around 20 people: the founders are still the only ones sourcing. Is that showing up for you yet?
- Prospect
Ha, yes. I'm still doing most of it myself.
- You
Same pattern at three other agencies this year. I put together a one-page breakdown of how they split sourcing between the founders and a first hire. Want me to send it?
- Prospect
Sure, send it over.
When someone replies, a person is on the other end. Stop the sequence and answer them, including when the answer is no.
What to do when someone replies
Answer within a few hours if you can. The person was thinking about the problem when they wrote back, and that attention doesn't last until Thursday.
Sort the reply before you write anything. Four kinds cover almost all of them, and each one gets a different response.
- Interested: send your scheduling link in the next message and say what you'll cover. One link, one sentence.
- Not now: ask when to come back, note the date, and stop the sequence so it doesn't fire again.
- Not interested: thank them and stop. Pushing back on a no costs you the account and any referral they might have made.
- Wrong person: ask who owns it. A forwarded intro beats a cold message every time.
- A question instead of an answer: answer it properly before you ask for anything.
Doing this with Kinlead
Running this by hand works for twenty leads a week. Past that, the sorting and the timing eat the hours you meant to spend selling.
Kinlead finds people who match a description of your customer or your website and scores each lead from 0 to 100 against that profile. Leads under the fit line aren't kept, so a sequence only starts with people worth messaging. Lead search uses LinkedIn's standard search, so a Sales Navigator seat isn't required. The Steal Customers agent 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, what the post was about and what they commented. That's your first line, written from something real.
Outreach runs from your own LinkedIn account through Unipile, at most one action every 5 minutes inside the daily limits and send window you set. Connection notes are written by AI under 200 characters and open with why that person became a lead. Messages and follow-ups come from the campaign goal, tone and your own sales playbook, and queued messages can be read and edited on the Actions page before they send.
- Leads sit in lead groups, and any campaign can point at any group. Export to CSV or import a list of LinkedIn profile URLs.
- Replies from every campaign land in one unified inbox, classified by intent with interested replies first, and you get an email when someone replies.
- Each campaign chooses how replies are handled: hand off at the first reply, let the AI reply until there's real interest, or let it reply until a meeting is booked on your scheduling link.
- Stale pending invitations are withdrawn automatically, and Settings shows pending invites and acceptance rate with warnings.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to build a LinkedIn outreach sequence.md