Create LinkedIn outreach for [PROSPECT NAME AND ROLE] at [COMPANY]. Their verified context is [PROSPECT AND COMPANY SIGNALS]. I sell [OFFER AND IDEAL CUSTOMER], and the problem we can credibly help with is [RELEVANT PROBLEM]. Evidence or outcomes I am allowed to use are [APPROVED PROOF]. The desired next step is [CTA]. My constraints are [MESSAGE FORMAT AND COMPLIANCE RULES]. First, decide whether the supplied signals support outreach. If there is no clear relevance, say “do not send yet” and name the information needed; do not invent research, mutual connections, business priorities, or results. If the signal is strong enough, write a three-touch sequence: 1. Connection request: 250 characters or fewer, no pitch, one relevant observation or context point. 2. First message after acceptance: 70 to 110 words. Open with the prospect's likely business context, state a narrow problem, give one approved proof point, and ask one low-pressure question or meeting request. 3. Follow-up: 45 to 75 words, sent only if there is no reply. Add a useful angle, clarify the reason for reaching out, and make it easy to decline. Tailor by role: executives need commercial or strategic relevance; operators need workflow, risk, or implementation relevance. Do not use flattery, fake urgency, “just bumping this,” or a calendar link before the prospect shows interest unless my constraints allow it. Do not claim results for a similar company unless the approved proof identifies a defensible comparison. Self-check: map each personalized sentence to a supplied signal, and flag any claim about savings, revenue, compliance, or outcomes that lacks approved proof. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROSPECT NAME AND ROLE] | Enter the prospect's name, role, and decision-making or operating area. | Dana Wu, VP of Customer Operations |
| [COMPANY] | Enter the prospect's company and relevant business context. | LedgerLoop, a 140-person accounts-payable software company |
| [PROSPECT AND COMPANY SIGNALS] | Enter verified public facts, such as a job post, launch, hiring pattern, interview, or stated initiative. | LedgerLoop posted three implementation specialist roles and Dana discussed reducing onboarding handoffs in a public webinar |
| [OFFER AND IDEAL CUSTOMER] | Describe what you sell and the types of customers it fits. | OnboardMap, workflow software for B2B SaaS teams with complex implementation handoffs |
| [RELEVANT PROBLEM] | State the narrow operational or business problem your offer can address. | Reducing missed ownership changes between sales, implementation, and customer success |
| [APPROVED PROOF] | Enter only results, case studies, credentials, or examples you are authorized to claim. | A named case study: Arcview reduced incomplete handoff checklists from 31% to 12% in six months |
| [CTA] | Enter the precise next step you want, such as a 15-minute discovery call or a reply to one question. | Ask whether this is an active priority and, if so, offer a 15-minute conversation |
| [MESSAGE FORMAT AND COMPLIANCE RULES] | Enter length limits, industry rules, approved language, and any outreach restrictions. | Standard LinkedIn limits; do not mention competitors or make savings claims |
How to use
- Collect one or two verifiable signals that relate to the prospect's role before filling in the prompt.
- Use only proof your company has approved, especially for metrics and customer names.
- Reject a draft if the first sentence could be sent unchanged to ten other prospects.
- Follow up with: “Create role-specific versions for a VP of Operations, an implementation director, and a CFO using only these approved facts.”
Variations
Account research
Use before writing messages for several people at one target company.
Build a LinkedIn account-outreach brief for [COMPANY] based only on [VERIFIED RESEARCH]. Our offer is [OFFER], and our qualification criteria are [QUALIFICATION CRITERIA]. Identify up to four likely stakeholder roles, the role-specific problem each may own, evidence that would justify contact, and a safe opening angle. Separate verified facts from assumptions. Do not name individuals unless I supplied them, infer budget, or state that a company has a problem without evidence. End with the research gaps that must be filled before outreach.
Event follow-up
Use after a prospect attended or participated in an event.
Write LinkedIn follow-up messages for [PROSPECT NAME] after [EVENT]. The verified interaction is [SPECIFIC DETAIL]. My offer is [OFFER], relevant to [PROBLEM], with approved proof [PROOF]. Draft a connection note under 250 characters and a 90-word post-acceptance note. Reference the event only if the supplied detail makes it relevant, avoid pretending we spoke if we did not, and ask [CTA]. Flag each sentence that is not anchored to a supplied fact.
Referral request
Use when an existing contact may introduce you to a buyer.
Draft a LinkedIn message to [CONTACT NAME] asking for guidance or an introduction regarding [TARGET ROLE OR COMPANY]. My relationship with this contact is [RELATIONSHIP CONTEXT]. The value proposition is [OFFER AND PROBLEM], and proof I may use is [APPROVED PROOF]. Write 90 to 120 words that gives the contact an easy way to decline, makes the target fit understandable, and offers a forwardable two-sentence summary. Do not presume they know the buyer or pressure them to endorse us. Check that the request is specific and respectful.
Tips
- Treat a job post, earnings statement, product launch, or stated operational goal as a possible opening signal, not proof that your product is needed.
- Use a proof point only when the comparison is honest; a result for a large enterprise may not transfer to a small company.
- A connection request should earn acceptance, not contain a compressed product pitch.
- If a prospect declines or does not reply after a restrained follow-up, stop the sequence and record the outcome instead of escalating pressure.
FAQ
How personalized should LinkedIn outreach be?
Personalize the reason for contact and the problem hypothesis, not every sentence. One verified, relevant signal is stronger than decorative references to a prospect's profile.
Can I use AI to research LinkedIn prospects?
Use it to organize research you provide, but verify every factual statement before sending. Do not let it invent company priorities or personal details.
What is a good LinkedIn call to action?
Ask a small question tied to the stated problem, or offer a brief conversation if it is a priority. A clear, low-pressure CTA usually outperforms a vague request to connect.