LinkedIn Prospecting Message Examples by Situation
LinkedIn prospecting message examples for five real situations, each with why it works and what to adapt. No pitch, no generic copy-paste line.
By Maxime Pudzeis, Founder, Kaizen Agency
· 10 min read
On this page
A LinkedIn prospecting message example only works when it fits the situation it is sent in: a connection note, a first message after acceptance, a reply to something the prospect posted, a message triggered by a buying signal, or a follow-up. Below are message examples for each situation, with what makes it work and what to change before sending it.
The same line sent in all five reads as copy-paste.
The introduction itself, short, no pitch, no company name.
Opens a conversation. Still no product name, no "thanks for connecting."
Reacts to something specific the prospect wrote, not a generic compliment.
Fires on a hire, a funding round or a tool change, named in the first line.
Adds a new angle. Never "just checking in" with nothing new to say.
Why a message example needs a situation, not just a template
Most lists of LinkedIn prospecting message examples hand over a number to swap in and a line to copy. That misses the part that decides whether anyone replies: the situation the message answers. A connection note and a first DM after acceptance are not the same message sent twice. One is the introduction. The other opens a conversation once the introduction already landed. Treat them as interchangeable and both read as mass-sent.
This page assumes the sequence itself, visit the profile, send the connection request as the intro, wait, then message, already makes sense. If it does not yet, how to prospect on LinkedIn covers that order step by step, along with Sales Navigator, safe sending volume and the account-restriction risk. This page picks up from there and fills in the actual wording for five situations, with what to adapt in each one.
Connection request examples
The connection request is the introduction, not a step before the real message. It carries no pitch and no company name either way, and stays short enough to read at a glance, under roughly 250 characters when a note is used.
Blank request (no note). With senior profiles, a note from a stranger can read as presumptuous before any context exists. Use it when the prospect is senior and the reason for connecting is already obvious from a shared context (same event, same group, a mutual connection LinkedIn shows on the request screen).
Short note, shared context:
"Hi [First name], saw we're both in [shared group or event]. Following your work on [specific topic], would be glad to connect."
Why it works: it names something true and checkable (the group, the event), not a compliment that could apply to anyone. What to adapt: the shared context has to be real and specific. A group name alone, with nothing about why it matters to this prospect, reads as generic as no context at all.
Short note, recent move or post:
"Hi [First name], congrats on the move to [new company/role]. Following the space, would be glad to connect."
Why it works: it proves the sender looked at the profile before sending, the single biggest filter a prospect applies before accepting. What to adapt: only send this within roughly a week of the move showing up; a congratulations three months late reads as scraped from a list, not noticed.
First message after acceptance examples
The DM sent right after someone accepts should never pitch. No product name, no company name, no "thanks for connecting." It goes out within four to twenty-four hours of acceptance, while the connection is still fresh in their notifications, not the next week. It stays short (40 to 70 words, one paragraph, three or four sentences) and ends on a real question.
Opening on their world, not yours:
"[Team/role] at companies like [company] usually feel [specific problem] first, especially with [context: growth, a recent change, the industry]. Curious whether that's shown up on your side, or you're seeing something different."
Why it works: it opens on an observation, not a question. "Thanks for connecting" followed straight by a question is one of the clearest tells of an automated sequence; the observation earns the question that closes the message. What to adapt: the "specific problem" has to come from something an ICP document or the prospect's own activity already pointed at, not a guess at their industry's generic pain.
Opening on a specific detail from their profile or post:
"Hi [First name], noticed your post on [topic]. The point about [specific detail] matched something we're seeing too. How are you thinking about it day to day?"
Why it works: it references something that only applies to this one prospect, which is what separates it from a template sent to five hundred people at once. What to adapt: pick a detail from the post that is specific enough that it could not have been written without reading it. "Interesting post!" is not that detail.
For one of our clients, we built LinkedIn, cold email and buying-signal outreach as one engine rather than three channels tested in sequence. A prospect who went quiet on LinkedIn still got a researched cold email the same week, and a prospect who replied on LinkedIn never received a duplicate pitch through the other channel. Qualified pipeline moved from zero to three million euros in eighteen months, with every channel sending a message built from the same proven angle instead of guessing at its own version.
Reply-to-a-post examples
A reply triggered by something a prospect actually posted carries more credibility than a cold connection request, because the prospect already put the topic on the table.
Agreeing with a specific point, then asking:
"Really agree with your point on [specific detail from the post]. Curious how that plays out for [specific context: their team size, their market]?"
Why it works: it engages with the actual argument, not the fact that a post exists. A generic "great post!" comment or DM gets ignored because it could sit under any post on the platform. What to adapt: comment publicly first if the post invites discussion; move to a DM only once there is a reason beyond "I want to sell you something," such as a genuine follow-up question the comment thread does not fit.
Disagreeing respectfully, then asking why:
"Interesting take on [topic]. We've seen it go the other way in [specific context]. What's driving it differently on your side?"
Why it works: a respectful disagreement stands out against a feed full of agreement, and it invites the prospect to explain their reasoning, which is itself useful signal. What to adapt: only use this when there is a real, defensible alternative view to offer, not disagreement for the sake of getting noticed.
Signal-based message examples
A signal-based message fires on something that just happened: a new hire, a funding round, a tool change, an expansion, or something warmer still, a mutual connection, a post the prospect engaged with. The signal belongs in the first line, named plainly, not implied.
New hire on the team:
"Hi [First name], saw [company] just hired a [role]. Usually means [specific operational shift] is starting to matter more. How's that landing so far?"
Why it works: the trigger is checkable and recent, which is the difference between a signal-based message and a guess dressed up as one. What to adapt: the "usually means" clause has to be something the sender genuinely believes connects to the signal, grounded in real pattern recognition, not a forced link to whatever is being sold.
Funding round or expansion:
"Congrats on the round. Teams usually see [specific pressure point] shift once hiring ramps. Has that started to show up yet?"
Why it works: funding and expansion are public, dated events, so the message cannot read as generic even to a skeptical reader. What to adapt: send this within days of the announcement. A signal-based message sent a month late loses the one thing that made it credible: timing.
Shared engagement, not a cold trigger:
"Hi [First name], noticed we're both connected to [mutual connection], and that you engaged with [their recent post or comment] on [topic]. Curious how [specific angle] is playing out on your end?"
Why it works: a mutual connection or the prospect's own engagement on a related post is a warmer signal than a public announcement, because it points to existing relevance instead of a guess built on a news item. What to adapt: only use a mutual connection as the hook when the relationship is real enough that the prospect could ask that person about it. A connection LinkedIn suggests with no actual relationship behind it reads as invented.
A signal-based message works best when it is built on the same buying-signal practice that feeds the rest of an outbound system, not a one-off check of a news feed. Buying signals for B2B covers how to build that list continuously instead of catching one signal by chance.
Follow-up message examples
A follow-up adds a new angle, sent around day 5 to 7 after the first message, with at most one more around day 10 to 14 before the thread closes. It is never "just checking in," because that line gives the reader no new reason to answer.
New angle, same conversation:
"Hi [First name], following up with something that might be more useful than my last note: [a specific insight, resource, or question tied to their situation]. Still relevant on your end?"
Why it works: it treats the silence as information (the first angle did not land) and tries a different one, instead of repeating the same ask. What to adapt: the new angle has to actually be new. A rephrased version of the same ask reads as a nudge, not a second idea.
The direct, low-pressure close:
"Hi [First name], I'll leave it here unless the timing shifts. If [specific problem] becomes a priority later, happy to pick this back up then."
Why it works: it removes pressure, which paradoxically gets replies from people who went quiet because they felt chased, not because they were uninterested. What to adapt: use this as the second and last follow-up, around day 10 to 14, after one real follow-up with a new angle already went out. Sending it as the first follow-up reads as giving up rather than respecting the reader's time.
Common mistakes with LinkedIn prospecting message examples
- Sending the same template to every situation. A connection note, a first DM and a follow-up each need their own wording, because each answers a different question for the reader.
- Pitching in the connection request or the first DM. Either one turns into a pitch the moment a product or company name shows up before the reader has said a word.
- Copying a template's exact wording without changing the specific detail it depends on. A line built around "your recent post" with no real post referenced reads worse than no personalization at all.
- Treating a signal-based message as optional personalization instead of the trigger that makes the whole message credible. Without a real, named, recent signal, it is just a generic message with a name merge field.
- Following up with "just checking in." It adds no new information and costs the second chance to be read.
- Sending more than two follow-ups after the first message. It reads as pressure, not persistence; our own practice stops at two before closing the thread.
FAQ
What is the best LinkedIn prospecting message example?
There is no single best one, because the right example depends on the situation: a connection note, a first DM, a reply to a post, a signal-based message, or a follow-up each need different wording. The common thread across every working example is that it references something specific and real about the prospect, never a generic compliment or a merge field alone.
Should a LinkedIn prospecting message always include a question?
Most working examples end on a real question, because a statement invites no reply while a specific question gives the reader something concrete to answer. The exception is a low-pressure follow-up meant to remove pressure rather than extract an answer, which can close without one.
How personalized does a LinkedIn message example need to be?
Personalized enough that the detail referenced could not apply to five other people at once. A first name in a merge field is not personalization; a specific post, a specific signal, or a specific shared context is.
Can the same message example work for a connection request and a first DM?
No. The connection request is the introduction itself and carries no pitch; the first DM opens the conversation that follows acceptance. Using the same wording for both skips a step and usually reads as a pitch arriving too early.
How many message examples should a LinkedIn sequence use?
Enough to cover the situations that actually occur: typically a connection note, a first DM, one or two follow-ups, and a signal-based or reply-to-post variant for the prospects where that trigger exists. A sequence built from a single template reused everywhere is the exact mistake this page tries to fix.
Getting the wording right still depends on getting the list and the sequence right first. The GOALS method covers how we build and run that full system, LinkedIn, cold email and buying signals together, for B2B SMEs, and the 4-minute diagnostic scores where your own outbound is leaking today.