15 LinkedIn Cold Message Examples That Get Replies

Most LinkedIn cold messages fail for the same reason: they are about the sender, not the recipient. The examples below flip that. Every message starts with something specific about the person, stays under 50 words, and ends with an easy question.

Steal the structure, not the words — swap in a real detail from the profile you're writing to.

What makes a cold message work

A real reason to reach out — a role change, a post they wrote, a problem their company obviously has. Not "I came across your profile."
Under 50 words — readable in 5 seconds on a phone. Long pitches get skimmed and archived.
One clear question at the end — low-effort to answer. "Worth 15 min?" beats "Let me know your thoughts on a potential collaboration."
Sounds like a human — short sentences, no marketing language, no "I hope this finds you well."

Sales cold message examples

1. New role = new priorities

Sarah — new Head of Sales at Datadog? First months usually mean a hard look at the stack. We help sales teams keep demos from breaking mid-call. Worth 15 min?

Why it works: a role change is a genuine buying signal — new leaders re-evaluate tools in their first quarter.

2. Their own words as the hook

Marcus, your line about "pipeline reviews that turn into therapy sessions" was painfully accurate. We built a tool that makes forecast calls boring again. Curious how you run yours today?

Why it works: quoting their post proves you actually read it. Nobody ignores a good reader.

3. Company growth signal

Ana — 40 open roles at Vercel right now, half in sales. Onboarding that many reps usually breaks the playbook. That's the exact problem we work on. Open to comparing notes?

Why it works: public hiring data is a free, verifiable signal of a real internal pain.

4. The competitor angle (careful, no trash talk)

Tom, teams switching from spreadsheets to real forecasting usually hit the same wall around 20 reps. Looks like Klarna's team just crossed that. Want to see how others got past it?

Why it works: it names a specific, stage-relevant problem — not a generic pitch.

5. Direct and honest

Priya — this is a cold message, so I'll keep it short. We cut QA time for engineering teams by ~10 hours a week. If that's a real number for your team, worth a look?

Why it works: naming the cold outreach disarms it. One concrete number does the selling.

Recruiter message examples

6. Career trajectory, not job title

Alex, your move from Google Cloud infra to Stripe payments caught my eye. Hiring a Staff Backend Engineer at Coinbase — similar problems, but you'd own the architecture. Open to hearing more?

Why it works: it shows you understood their career story, and pitches ownership — not "an exciting opportunity."

7. The quiet-signal read

Dana — three years building the same platform is usually when great engineers start wondering what's next. Not pitching a role yet. What would actually make you look?

Why it works: no job spec, no pressure. It starts a conversation instead of pushing a vacancy.

8. Skills match with specifics

Miguel, you've done Rails-to-Kubernetes migrations twice now. We have a team about to start their first one and they need someone who's seen the movie before. Interested in the details?

Why it works: "you've done this exact thing twice" is flattery backed by facts.

9. Re-engaging a silver medalist

Nina — you made it to the final round with us last year, and the team still brings your systems-design answer up. New Staff opening, stronger comp band. Want the spec?

Why it works: specific shared history plus a concrete change since last time.

Founder outreach examples

10. Peer-to-peer, no pitch

Leo — saw you led billing at Stripe before starting out on your own. We're rebuilding pricing infrastructure for mid-market SaaS and keep hitting edge cases. Your take would be genuinely useful. Got 15 min?

Why it works: founders respond to specific, honest asks for expertise — not "let's explore synergies."

11. Design partner ask

Rachel, you've complained twice about agency reporting tools on here — fair complaints. We're building the fix and want three design partners who'll be brutally honest. In?

Why it works: it references their public frustration and offers influence, not a discount.

12. Shared problem space

Omar — we're both selling into compliance teams, different products. I've learned some expensive lessons about that buyer this year. Happy to trade notes if useful. What's been hardest on your side?

Why it works: offers value first, asks for nothing but a conversation.

Follow-up examples (when the first message got silence)

13. The new-information follow-up

Sarah, since I wrote last — we shipped the Salesforce integration you'd have asked about. Demo takes 12 minutes now. Still a bad time?

Why it works: it adds something new instead of "just bumping this up."

14. The graceful exit

Alex — last note from me. If the timing's wrong, no hard feelings. If it's the message that missed, tell me what would've landed. Either answer helps.

Why it works: a clean close gets replies from people who were on the fence.

15. The short nudge done right

Priya — resurfacing this in case it sank. One question: is QA time even a top-3 problem for your team this quarter? If not, I'll stop guessing.

Why it works: it makes "no" easy — which paradoxically makes "yes" more likely.

Openers to avoid

These phrases mark a message as mass outreach in the first second. Recipients have seen each one a thousand times:

"I came across your profile..."
"I hope this message finds you well..."
"I was impressed by your background..."
"I'd love to pick your brain..."
"Quick question..." (followed by a long pitch)
"I'm reaching out because..."

Get messages like these for any profile

FirstLine reads the LinkedIn profile, finds the real reason to reach out, and writes two short messages — free.

Install FirstLine — Free