Write a LinkedIn InMail to [PROSPECT NAME], [PROSPECT ROLE] at [COMPANY]. I am [SENDER ROLE] at [MY COMPANY], and my relevant offer is [OFFER AND PROOF]. The public, current information I can responsibly reference is [PROSPECT RESEARCH]. My desired next step is [CALL TO ACTION], and the relationship context is [CONNECTION CONTEXT]. Create three distinct versions, each 85-120 words, with a subject line of six words or fewer. Version 1 should lead with a business trigger; version 2 should lead with a role-specific problem; version 3 should lead with a concise relevant insight. Use one concrete detail from the research only when it clearly connects to the prospect’s likely priorities. Do not praise the prospect generically, claim to know their priorities, imply a personal connection that does not exist, or use sensitive personal information. Each message must follow this sequence: relevant observation, plausible problem or opportunity framed as a hypothesis, specific proof or outcome from my offer, and one low-friction call to action. Keep the CTA to one option, such as a 15-minute conversation or permission to send a one-page example. Avoid attachments, calendar links, long company descriptions, and more than one question. Do not make performance, savings, or customer claims unless supplied in my proof. After the three drafts, provide a one-line personalization note explaining the research detail used in each version. Ask up to three clarifying questions only if a required input is missing. Before answering, flag unsupported claims and check that every draft can be understood without clicking a link.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROSPECT NAME] | Enter the prospect's name as shown on LinkedIn. | Dana Ruiz |
| [PROSPECT ROLE] | Enter the prospect's current job title and responsibility area. | Director of Revenue Operations |
| [COMPANY] | Enter the prospect's company name. | Clearpoint Logistics |
| [SENDER ROLE] | State your role and why you are a relevant person to contact them. | Account executive focused on revenue operations teams |
| [MY COMPANY] | Enter your company or organization name. | ForecastLane |
| [OFFER AND PROOF] | Describe the offer and only verified proof points, customer results, or examples you may use. | Pipeline-quality software; a published case study showed a 22% reduction in stale opportunities at a mid-market SaaS company |
| [PROSPECT RESEARCH] | Paste one or two recent public facts about the prospect, company, or role. | Clearpoint posted three RevOps roles this quarter and Dana shared a public post about forecast consistency |
| [CALL TO ACTION] | State the exact, low-commitment next step you want. | A 15-minute conversation next week |
| [CONNECTION CONTEXT] | State any real shared context, referral, prior interaction, or say none. | None |
How to use
- Choose one credible public trigger and verify that it is current before pasting it into the prompt.
- State only proof points your company can substantiate in a customer conversation or on request.
- Read each draft as the prospect: remove any sentence that assumes an internal problem or sounds like surveillance.
- Follow up with: “Make version 2 70 words and replace the meeting request with permission to send a two-sentence example.”
Variations
Recruiting InMail
Use this when contacting a candidate about a specific role.
Write a LinkedIn InMail to [CANDIDATE NAME] about the [ROLE] position at [COMPANY]. Their public experience relevant to the role is [RELEVANT BACKGROUND]. The accurate role facts are [ROLE FACTS], and the next step is [NEXT STEP]. Draft two messages of 90-120 words with a short subject line. Explain why their experience may fit without claiming they are looking. Include location, work arrangement, and compensation only if provided. Do not infer personal circumstances or use protected characteristics. Ask up to 3 questions only if required inputs are missing. Check that each claim about the role and candidate is supported.
Warm introduction
Use this when a real mutual contact has made an introduction.
Draft a LinkedIn InMail to [PROSPECT] following an introduction from [MUTUAL CONTACT]. The contact authorized this context: [INTRODUCTION CONTEXT]. I work at [MY COMPANY] and can help with [RELEVANT OUTCOME], supported by [PROOF]. Write one 100-word message with a six-word subject line and one specific CTA: [CTA]. Do not overstate the mutual contact's endorsement or assume a pain point. Ask up to 3 questions only if needed. Check that the message explains why the introduction is relevant within the first two sentences.
Event follow-up
Use this when the prospect attended the same event or engaged with its public content.
Write a LinkedIn InMail to [PROSPECT] after [EVENT OR WEBINAR]. The specific public event context is [EVENT DETAIL]. I am [SENDER ROLE] at [COMPANY], offering [OFFER] with verified proof [PROOF]. Create two 80-110 word drafts: one for an attendee and one for someone who posted about the event. End each with [CTA]. Do not claim they attended unless confirmed. Ask up to 3 questions only if inputs are missing. Check that each draft provides value beyond repeating the event topic.
Tips
- Use a company event, role change, hiring pattern, or published priority only if it has a real connection to your offer.
- Limit personalization to one relevant detail; several scraped facts feel intrusive and take attention away from the reason to reply.
- Make the proof comparable to the prospect's context, and state the customer type or conditions behind a result when you have them.
- Test the CTA separately from the opener; a useful InMail can fail if it asks for too much commitment too early.
FAQ
How long should a LinkedIn InMail be?
Around 85-120 words is enough for a relevant observation, credible proof, and one clear next step. Cut anything that reads like a company brochure.
Can AI research the prospect for me?
Use verified public research you can check yourself, and follow your company's privacy and platform policies. Do not use sensitive personal data or invent a connection.
Should every InMail ask for a meeting?
No. Permission to send a relevant example or question can be a better first step when the offer needs context.