Write a personalized LinkedIn outreach email to a prospective client. The goal is to earn a relevant conversation, not to force a product pitch into the first message. Use only the research and facts below; do not invent mutual connections, company initiatives, results, pain points, or compliments. Inputs: - Prospect and company details: [PROSPECT AND COMPANY] - Verified personalization signal: [VERIFIED PERSONALIZATION SIGNAL] - Relevant problem and offer: [RELEVANT PROBLEM AND OFFER] - Proof or example I can substantiate: [APPROVED PROOF] - Desired next step and sender context: [NEXT STEP AND SENDER CONTEXT] Write three email options, each 80-120 words, with distinct opening angles: one based on the personalization signal, one based on a role-specific operational problem, and one based on a timely business trigger. For each option, provide a subject line of no more than six words. Each email should: open with one specific observation; connect it to a plausible, non-assumptive issue; state one concise way I may help; include one relevant proof point only if it is supplied; and end with a low-friction call to action such as a 15-minute conversation or permission to send a useful resource. Use short paragraphs. Avoid “just checking in,” false urgency, flattery, jargon, feature lists, and requests for a meeting without a reason. If the personalization signal is weak, say so and use a neutral role-based opening rather than stretching it. Ask up to three clarifying questions only if a required input is missing. Before answering, check that the message could not be sent unchanged to ten unrelated prospects, and flag every claim that lacks direct support in my inputs.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROSPECT AND COMPANY] | Enter the prospect’s name, role, company, industry, and any verified scope of responsibility. | Maya Chen, VP of Revenue Operations at Cedarpath, a 240-person B2B payments software company; owns forecasting and sales process |
| [VERIFIED PERSONALIZATION SIGNAL] | Enter a recent post, public announcement, job opening, interview, or other verifiable signal. | Cedarpath posted three sales operations roles this month and Maya shared a post about improving forecast consistency across regions |
| [RELEVANT PROBLEM AND OFFER] | Describe the role-specific problem you help solve and the service or outcome you can offer. | We help RevOps teams identify where CRM stage definitions and handoffs distort forecast accuracy through a two-week diagnostic |
| [APPROVED PROOF] | Enter one client result, case study, or experience claim you can accurately support. | For a B2B SaaS client, our diagnostic found duplicate pipeline stages and reduced weekly forecast reconciliation time from 6 hours to 2 hours |
| [NEXT STEP AND SENDER CONTEXT] | State who you are, why you are reaching out, and the specific next action you want. | I am Jordan Patel, principal at Fieldmark Ops; ask for a 15-minute call next week to see whether the diagnostic fits |
How to use
- Paste a real public signal and remove any detail you cannot verify or explain if challenged.
- Select the opening that best matches the prospect’s role, then confirm the proof point is approved and accurately framed.
- Keep the message in plain text and send it from the account the prospect can verify.
- Follow up with: “Create a 55-word LinkedIn connection note that uses the same signal and asks only for permission to share a resource.”
Variations
Connection request
Use this when you need a LinkedIn connection note before sending a longer message.
Write three LinkedIn connection notes of 250 characters or fewer for [PROSPECT], using [VERIFIED SIGNAL], [ROLE-RELEVANT PROBLEM], and [SENDER CONTEXT]. Each note should contain one genuine reason to connect and no meeting request unless [NEXT STEP] explicitly calls for it. Do not claim shared interests, mutual contacts, or knowledge not supplied. Avoid compliments that could apply to anyone. Ask up to three questions only if necessary. Check that the note is specific to this prospect and fits the character limit.
Warm introduction
Use this after a mutual contact has agreed to introduce you.
Draft a follow-up email after an introduction from [INTRODUCER] to [PROSPECT]. Use [INTRODUCTION CONTEXT], [PROSPECT PRIORITY], [RELEVANT OFFER], [APPROVED PROOF], and [REQUESTED NEXT STEP]. Write one 100-130 word message with a subject line. Thank the introducer only if they remain copied; otherwise do not make them the focus. Explain relevance in one sentence and make a specific, low-pressure ask. Ask up to three questions if needed. Check that the proof is supportable and the prospect’s priority is not overstated.
Breakup email
Use this after several unanswered, relevant outreach attempts.
Write a 70-100 word final outreach email to [PROSPECT] after [NUMBER OF PRIOR TOUCHES] attempts about [OFFER]. Refer only to [VERIFIED CONTEXT OR PRIOR MESSAGE], state a clear close-the-loop choice, and offer [USEFUL RESOURCE OR NEXT STEP] if appropriate. Use a respectful subject line and do not manufacture urgency, guilt, or scarcity. Do not claim the prospect saw earlier messages. Ask up to three questions if required inputs are missing. Check that it can stand alone and does not repeat the prior message verbatim.
Tips
- A company hiring plan is a useful signal only when your offer relates directly to the capability being hired; otherwise it reads like scraped research.
- Use a proof point with a comparable situation, but state the actual scope and result instead of implying the same outcome is guaranteed for the prospect.
- A 15-minute call works better when the recipient knows what they will learn or decide during it.
- If you cannot identify a specific signal, lead with a narrow role pattern and give the prospect an easy way to say it is not relevant.
FAQ
How long should a LinkedIn outreach email be?
For a first email, 80-120 words is usually enough to establish relevance and make one request. Connection notes need to be much shorter because LinkedIn limits characters.
Can AI research the prospect for me?
AI can organize research you provide, but verify every statement before sending. Public data can be outdated, incomplete, or misinterpreted.
Should I include a case study in the first message?
Include one compact, comparable proof point only when it strengthens the relevance. Save a full case study or attachment for after the prospect shows interest.