At 8.12 on a Tuesday, Maya opens LinkedIn with coffee in hand and a small hope that today’s messages might be different. They mostly are not. A wall of generic notes greets her. I hope you are well. I would love to connect. We help companies like yours. She deletes three in a row. Then one catches her eye. It references a specific project from last week, asks a single, easy question, and leaves her space to say no. She replies in under a minute.
Most outreach fails because it asks the recipient to do the sender’s work. The fix is simple, but it requires discipline. Put the other person’s context first, keep it short, and make the next step obvious. Below are scripts you can tailor in 60 seconds, with a quick read on why they draw replies.
What actually gets a reply on LinkedIn
- Start with context from their world. Mention a post, role, project, or event they touched.
- Keep it to three short lines. The eye should see air, not a pitch block.
- Add one line of relevance proof. A shared point of view, a mutual contact, or a result stated plainly.
- Ask one question with a small yes. Suggest a next step that takes little time or risk.
- Offer an easy out. It signals respect and reduces pressure.
Short scripts you can personalise quickly
After you comment on their post
Hi [Name], I appreciated your post on [specific topic] and left a note in the comments. I worked on [related thing] at [your company or role] and we learned [one precise insight]. Happy to share the short version. Would a 10 minute chat next week be useful, or not a priority?
Why it gets replies: You prove you are not cold. You bring a concrete insight and a time box. The easy out lowers the guard.
Connection request with a tight 300 character note
Fellow [profession or group]. Your take on [topic] was practical. I’m working on [related thing] at [your role]. Keen to connect and swap one idea on [very specific angle]. If not helpful, no stress.
Why it gets replies: It fits the character limit without fluff and sets a narrow agenda.
Event or webinar follow up the same day
Hi [Name], thanks for the session on [event or talk]. Your point about [specific takeaway] stuck with me. We faced something similar on [project] and tried [one tactic]. If you are curious, I can send a 3 line summary. Want it?
Why it gets replies: You make the next step frictionless. No meeting ask, just a quick send.
Warm outreach via a clear mutual link
Hi [Name], we are both connected with [mutual contact] from [context]. I liked your recent note on [topic]. I am exploring [related challenge] for [audience or team]. Could I ask you one question on how you approached [specific piece]? If now is not ideal, I understand.
Why it gets replies: The mutual link provides light credibility. The ask is one question, not a call.
Job seeker to a hiring manager
Hi [Name], I saw the role for [job title] in [location or team]. In my last role I [result tied to the job, stated plainly]. May I send two bullet points on how I would approach the first 30 days, so you can see the fit? If you prefer applications only, I will follow that path.
Why it gets replies: You mirror the job’s needs and give a low lift way to evaluate you without asking for a chat.
Vendor to a potential customer, without the hard sell
Hi [Name], noticed your team is hiring for [role] and rolling out [initiative]. Teams at [your segment, not a brand] often hit [very specific snag]. We tackled that with [one method] and learned what not to do. Would a short note on the pitfalls be useful? Happy to leave it there if not.
Why it gets replies: You anchor to a real trigger and offer value before pitching. No long case study, no calendar link dump.
Partnership or collaboration with a peer
Hi [Name], your work on [project or series] aligns with what my team is building for [audience]. I can contribute [clear asset or capability], and I see a simple test we could run together on [specific channel or format]. Open to a 15 minute compare-notes call next week, or would a one page outline be better?
Why it gets replies: You show the overlap, propose one test, and offer two low friction paths.
User research or feedback request
Hi [Name], I’m improving [product or process] used by [their role]. Your recent comment on [issue] was sharp. Could I ask 3 questions by message, totalling under 5 minutes, in exchange for a summary of findings? If that is a hassle, all good.
Why it gets replies: It trades value for time and quantifies the ask.
Make it yours in two minutes
A quick workflow keeps you out of the generic bin:
- Spend 60 seconds on context. Skim their recent post history, role scope, and one recent shift like a hire, launch, or event.
- Write three lines. Line one is their world, line two is your relevance, line three is the question with the easy out.
- Cut any adjectives that could appear in a template. Replace with nouns and specifics from their feed.
- Send when you can reply fast. If they respond in five minutes and you vanish for a day, the momentum dies.
Follow up once, lightly
Hi [Name], looping back on the note below about [topic]. If it is not useful right now, I will close the loop here.
That is enough. A single, polite follow up signals professionalism without nagging.
Common mistakes that kill replies
- Opening with your bio. Lead with their world, not your headline.
- Asking for 30 minutes without a reason. Earn time in small steps.
- Filling space. If a word adds no clarity, cut it.
- Pitching features. Talk in outcomes and problems they have already signalled.
- Forgetting an exit. People reply more when they feel free to opt out.
A final note on tone
Be human, not formal. Write how you would speak to a colleague you respect. Specificity reads as care. Brevity reads as confidence. If your message helps the other person make a low risk decision in under a minute, your reply rate will climb without pushing.
