LinkedIn Outreach DM Pack â€” 3 Connection + 3 A/B Post-Acceptance DMs

One-shot prompt template that produces short, personalized LinkedIn connection requests and post-acceptance A/B DMs (â‰¤200 chars) with required personalization fields and a singl...

What You'll Get

3 Connection Request variants labeled CR-1 to CR-3 (each â‰¤200 chars, no CTAs, includes mutual signal/profile-hook).

3 Post-Acceptance pairs labeled PA-1A/1B, PA-2A/2B, PA-3A/3B (A = soft nudge, B = includes the single CTA; each â‰¤200 chars).

Personalization Fields checklist with exact labels and placeholders (Prospect name, Company, Role, Mutual signal, Profile-hook sentence, Trigger line).

Follow-up cadence recommendation (â‰¤4 touches) and 2 fallback no-reply lines.

3 ultra-short objection-handling snippets (â‰¤200 chars) tied to provided objections and referencing supplied proof points.

KPI suggestions and one implementation note for A/B testing cadence.

Assumptions flow: prompt asks up to three targeted clarifying questions if required inputs are missing.

How to Use

1Provide required inputs before running: offer, target_role (seniority/department), funnel_stage, channel, one-line primary_benefit, proof_points (bullet list), objections (top 3), single CTA text, mutual signal or profile-hook, optional follow-up cadence.

2Run the one-shot prompt in ChatGPT; if any required input is missing the prompt will ask up to three focused clarifying questions and wait for answers before generating messages.

3Use the generated A/B pairs to test reply and booking rates; keep the single CTA identical across B variants to isolate CTA impact.

4Copy messages verbatim into LinkedIn sequences; populate the Personalization Fields checklist for each prospect to ensure consistent personalization.

Prioritize concise, verifiable proof

Supply proof_points as exact, non-identifying phrases (e.g., 'case study with similar client' or verbatim allowed text). If you can't share client names, use 'peer in your industry' to avoid inventing metrics.

Works Best With

Best used by B2B revenue teams running LinkedIn-first outbound sequences

LinkedIn outreach where a clear mutual signal or profile-hook exists

Teams that need short, testable A/B variants for connection + post-acceptance stages

Use when you have at least conservative proof points (case studies or trial reports) to cite

Prompt Template

## Goal
- Create a LinkedIn outreach DM pack that generates 3 short, personalized connection request messages and 3 post-acceptance DM variants (A/B rows) under 200 characters each, optimized to elicit a reply or schedule a quick call/resource request consistent with the {{funnel_stage}} stage on {{channel}}.

## Inputs
- Offer: {{offer}}  
- Target audience / role: {{target_role}}  
- Funnel stage: {{funnel_stage}}  
- Channel: {{channel}}  
- Primary benefit (one-line): {{primary_benefit}}  
- Proof points (bullet list): {{proof_points}}  
- Common objections (bullet list): {{objections}}  
- Single CTA (schedule quick call or send resource): {{cta}}  

If any of the following are missing, the prompt must ask targeted clarifying questions before generating outreach: prospect role specifics (seniority/department), a mutual signal (shared group, connection, event, interest), a one-line value hook tailored to the prospect, a short profile-hook (obs. about prospect profile to personalize), and an optional follow-up cadence (days & count).

## Prompt
You are a senior B2B outreach copywriter. Produce a LinkedIn DM Pack for outbound prospecting using the exact inputs below. If any required detail in Inputs is missing, ask up to three targeted clarifying questions and wait for answers. Use only the provided inputs and the prospect-specific details that the user supplies in answers.

Context to use:
- Offer: {{offer}}  
- Target role/ICP: {{target_role}}  
- Funnel stage: {{funnel_stage}} on {{channel}}  
- One-line primary benefit: {{primary_benefit}}  
- Proof evidence to reference (use exactly as provided, cite conservatively): {{proof_points}}  
- Known objections to pre-handle: {{objections}}  
- Only CTA to use: {{cta}}

Required deliverables (strict order). Do not add extra sections or CTAs. Keep every message â‰¤ 200 characters and human (no corporate buzzwords). Use natural punctuation and contractions.

1) Connection Requests â€” produce 3 variants (label CR-1, CR-2, CR-3). Each message must:
   - Be personalized with a brief profile-hook or mutual signal (use prospect-specific inputs or prompt the user to provide them before generation).
   - Contain no pitch or pricing. No CTA to book in the connection request.
   - Use a curiosity or relevance line tied to {{primary_benefit}} or the mutual signal.
   - Maximum 200 characters.

2) Post-Acceptance DMs â€” produce 3 A/B pairs (label PA-1A / PA-1B, PA-2A / PA-2B, PA-3A / PA-3B). For each pair:
   - A variant: soft nudge that asks 1 simple question or offers a quick resource (â‰¤ 200 chars). No heavy pitch.
   - B variant: slightly more direct alternative that includes the single CTA ({{cta}}) phrased as an easy next step (keep optional scheduling phrasing lightweight). Also â‰¤ 200 chars.
   - Each DM must include one concrete micro-proof line derived from {{proof_points}} (e.g., "helped X reduce Y by Z%" only if present in proof_points). Do not invent metrics.

3) Personalization Fields â€” output a short checklist of fields to populate for each prospect (exact labels): Prospect name, Company, Role, Mutual signal (group/event/shared interest), Profile-hook sentence (one short sentence), Trigger line used in message. Leave sample placeholders where appropriate.

4) Follow-up Cadence â€” recommend a compact follow-up cadence (days between messages, max 4 touches) and provide 2 short fallback lines for no-reply after the initial PA sequence.

5) Objection Handling Snippets â€” provide 3 ultra-short rebuttals (â‰¤ 200 chars each) tailored to the top 3 items listed in {{objections}}. Each rebuttal must reference a proof point from {{proof_points}} if applicable.

6) KPI & Use Instructions â€” suggest 2 measurable KPIs tied to {{funnel_stage}} (e.g., reply rate, meetings/bookings) and one short implementation note about A/B testing cadence.

Formatting & specificity rules to follow inside the same response:
- Return every deliverable in the order above with clear labels exactly as specified.
- Enforce claim hygiene: if a proof point is vague, convert to language like "case study with similar customer" rather than inventing numbers.
- Ban cliches and hype phrases (e.g., "disruptive", "game-changer", "best-in-class").
- Single CTA only: all messages that include a CTA must use the exact phrasing style in {{cta}}.
- Respect privacy and compliance: do not suggest using scraped personal data beyond public LinkedIn profile signals.
- If any proof_point would require permission to cite (customer name), use generic phrasing: "similar client" or "peer in your industry" unless explicit names are provided.
- If the user did not provide any of the Inputs, output a brief "Assumptions" block (see Output Format) listing the missing items you will assume and then proceed using conservative defaults.

Tone: concise, human, slightly curious, respectful of time.

Output only the deliverables; do not include commentary, apologies, or process notes.

## Output Format
Return the pack exactly in this order and with these headings. Use the labels specified under Prompt. Include an "Assumptions" block only if the user omitted required Inputs; list what was assumed and why (max 2 bullet lines). Each message must be under 200 characters. Headings to include in final output (in this order):
- Connection Requests
- Post-Acceptance DMs
- Personalization Fields
- Follow-up Cadence
- Objection Handling Snippets
- KPI & Use Instructions
- Assumptions (ONLY if needed)

Do not include any other headings or sections.

## Guardrails
- No invented numbers, testimonials, or guarantees. If a metric is necessary, label as "reported" and cite the proof text verbatim from {{proof_points}}.  
- No lengthy pitches in message 1 (Connection Requests).  
- Keep all messages â‰¤ 200 characters. Validate character count roughly by keeping messages short and punchy.  
- One primary CTA only (use {{cta}}). Do not include calendar links or multiple CTAs inside messages.  
- No cliches, no vague superlatives. Use concrete outcomes or conservative phrasing.  
- If inputs are incomplete, ask focused questions before generating copy.

## Examples
Connection Requests (example style)
- CR-1: "Spotted you in the Agile Leaders groupâ€”smart pieces on scaling teams. Mind connecting?"  

Proof block (example style)
- Micro-proof: "Worked with a peer fintech to cut onboarding time by 30% (case study available)."

Variables

Usage Notes

Not for

â€¢ Consumer-facing outreach or bulk spam use

â€¢ Claims that require regulatory/legal verification (clinical, legal, financial regulated claims)

â€¢ Using non-public or scraped personal data for personalization

Do not include

â€¢ Pricing, long sales pitches, or multiple CTAs in any message

â€¢ ClichÃ©s or hype words (e.g., "game-changer", "disruptive")

â€¢ Customer names or metrics that you don't have explicit permission to cite

LinkedIn Outreach DM Pack â€” 3 Connection + 3 A/B Post-Acceptance DMs

Generate 3 connection-request variants and 3 post-acceptance A/B DM pairs under 200 characters each; enforces prospect role, mutual signal, profile-hook, one-line value hook, single CTA, micro-proof usage, personalization checklist, follow-up cadence, and objection rebuttals.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

Auto-fill & personalize from your inputs

AI-assisted edits: tone, structure, constraints

Attach context so outputs stay consistent

Iterate and save versions

What you'll get

Output format

Markdown

Best used when

When working on template or detailed.

Avoid when

Consumer-facing outreach or bulk spam use

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Funnel Stage