All articles|
EthumEthum Knowledge Base
Log in
SOP

EXP – Sales – Acq – Social Outreach – Social – First DM Engine

GROWTH AND SALES - LEAD GEN

═══════════════════════════════════════════════════════════════════════════════

EXP – Sales – Acq – Social Outreach – Social – First DM Engine

Social Channel DM Conversation Creation Test

═══════════════════════════════════════════════════════════════════════════════

Document Type: LOSER SOP (Archived Learning)

Department: Sales / Growth

Business Function: Sales (Acquisition)

Created: [Date]

Owner: [Operator Name]

Status: ❌ FAILED — DO NOT REPEAT AS-IS

═══════════════════════════════════════════════════════════════════════════════

EXECUTIVE SUMMARY

═══════════════════════════════════════════════════════════════════════════════

WHAT WE TESTED:

Three DM messaging variants on social channels to increase conversation rates:

- Variant A: Question-led approach

- Variant B: Pattern insight approach

- Variant C: Micro-value offer approach

TARGET METRIC:

DM → Conversation Rate: 15-25%

ACTUAL RESULT:

[Fill in actual conversation rate achieved: X%]

VERDICT:

❌ Failed to meet minimum threshold of 15% conversation rate

═══════════════════════════════════════════════════════════════════════════════

EXPERIMENT DETAILS

═══════════════════════════════════════════════════════════════════════════════

HYPOTHESIS:

If we test different DM approaches (question-led, pattern insight, micro-value)

on social channels, then we will increase the conversation rate because these

tailored messages will better engage our audience.

APPROACH TESTED:

Variant A — Question-Led

Message: "Quick question — how are you currently generating pipeline?"

Execution: Sent within 24h after connection accepted

Tracking: LI_DM_01

Variant B — Pattern Insight

Message: "We're seeing a lot of SaaS teams struggle with outbound efficiency

lately — curious if that's the case for you?"

Execution: Sent within 24h after connection accepted

Tracking: LI_DM_02

Variant C — Micro-Value

Message: "Quick idea on pipeline generation for SaaS teams — want me to share?"

Execution: Sent within 24h after connection accepted

Tracking: LI_DM_03

EXECUTION PARAMETERS:

- Timeline: [Start date] → [End date]

- Sample Size: [Total DMs sent]

- Distribution: [X per variant]

- Channel: Social Platform (LinkedIn assumed)

- Timing: Within 24 hours of connection acceptance

═══════════════════════════════════════════════════════════════════════════════

WHY IT FAILED — ROOT CAUSE ANALYSIS

═══════════════════════════════════════════════════════════════════════════════

PRIMARY FAILURE REASONS:

1. GENERIC MESSAGING (Most Likely)

- All three variants are sales-forward

- No personalization mentioned in execution notes

- "Quick question/idea" patterns are overused in LinkedIn outreach

- Pattern insight assumes pain point without validation

2. TIMING ISSUE

- 24-hour window may be too slow

- Prospects already receiving other DMs in that timeframe

- Lost window of immediate engagement

3. LACK OF CONTEXT

- No mention of WHY we're reaching out

- No reference to prospect's specific activity/content

- Messages could apply to anyone

4. VOLUME/QUALITY MISMATCH

- If audience size undefined, may have targeted wrong ICP

- No signal scoring mentioned

- Potentially low-quality connections

5. WEAK VALUE PROPOSITION

- Variant C offers "idea" but doesn't specify what kind

- Variant B uses fear-based pattern ("struggle")

- Variant A is pure interrogation

SECONDARY FACTORS:

- No A/B testing methodology documented

- Kill switch criteria not defined

- No mention of follow-up sequence

- Unclear if messages were tested individually or simultaneously

═══════════════════════════════════════════════════════════════════════════════

WHAT WE LEARNED

═══════════════════════════════════════════════════════════════════════════════

✅ VALIDATED LEARNINGS:

1. Generic DM frameworks don't work at scale

- Even "good" templates need personalization layer

- Question-led ≠ automatically engaging

2. 24-hour delay likely too slow

- First-mover advantage matters on social

- Immediate response (1-2 hours) may be critical

3. Pattern insights without validation feel assumptive

- Saying "teams struggle with X" without knowing their reality = turn-off

4. Need stronger connection between acceptance → DM

- Why did they accept? Reference that reason

❌ WHAT DIDN'T WORK:

- Question-led without context

- Pattern insight without personalization

- Micro-value without specificity

- 24-hour timing window

- One-size-fits-all approach across all connections

═══════════════════════════════════════════════════════════════════════════════

SHOULD WE RETRY? ITERATION RECOMMENDATIONS

═══════════════════════════════════════════════════════════════════════════════

🔄 YES — RETRY WITH MODIFICATIONS

Recommended Changes:

1. ADD PERSONALIZATION LAYER (CRITICAL)

- Reference why they accepted connection

- Mention specific post/content they shared

- Use their industry/role in message

Example:

OLD: "Quick question — how are you currently generating pipeline?"

NEW: "Saw your post on X — curious how you're handling [specific challenge]?"

2. REDUCE TIMING TO <2 HOURS

- Send DM immediately after acceptance (if online)

- Maximum 2-hour window, not 24 hours

- Test: Immediate vs 2-hour vs 24-hour

3. IMPROVE VALUE SPECIFICITY

- Replace vague "idea" with concrete offer

- Example: "I have a 3-step framework for X that [specific result]"

4. TEST HYBRID APPROACH

- Personalized opener + question

- Context + pattern insight

- Specific value + curiosity gap

5. DEFINE ICP CLEARLY

- Only send to qualified connections

- Document signal scoring rules

- Track quality → conversation correlation

Suggested Next Experiment:

SALES-EXP-XXX: "Personalized First DM with <2hr Response Window"

- Variant A: [Connection reason] + [Question about their specific challenge]

- Variant B: [Content reference] + [Micro-value specific to their role]

- Variant C: [Immediate response] + [Pattern insight from their activity]

- Target: 20-30% conversation rate

- Timing: <2 hours after connection

═══════════════════════════════════════════════════════════════════════════════

DO NOT REPEAT — ARCHIVED WARNINGS

═══════════════════════════════════════════════════════════════════════════════

🚫 DO NOT:

- Use generic question-led DMs without personalization

- Wait 24 hours to send first DM

- Use pattern insights without validating prospect's reality

- Offer "quick idea" without specifying what it is

- Assume all connections want the same message

🚫 AVOID:

- Sales-forward language in first touch

- Assumptive pain points

- Vague value propositions

- One-size-fits-all messaging

═══════════════════════════════════════════════════════════════════════════════

KNOWLEDGE BASE CLASSIFICATION

═══════════════════════════════════════════════════════════════════════════════

Archive Location: SALES/GROWTH → FAILED EXPERIMENTS → SOCIAL OUTREACH

Reference ID: LOSER-SOP-[XXX]

Related SOPs: [Any related Winner SOPs on DM strategy]

Keywords: first-dm, social-outreach, conversation-rate, linkedin-dm

Department: Sales / Growth

Operator: [Name]

Experiment ID: [SALES-EXP-XXX]

═══════════════════════════════════════════════════════════════════════════════

FINAL RECOMMENDATION

═══════════════════════════════════════════════════════════════════════════════

This experiment revealed that messaging quality matters more than messaging

framework. The core insight — "tailored messages engage better" — remains valid,

but execution was too generic.

✅ RETRY with personalization layer + faster timing

❌ DO NOT repeat as-is with generic templates

⚠️ WATCH: If personalized version also fails, problem may be upstream

(connection quality, ICP targeting)

Next Steps:

1. Document personalization criteria for DMs

2. Test <2hr timing window

3. A/B test: Generic vs Personalized (same framework)

4. If still fails → revisit connection acceptance strategy

═══════════════════════════════════════════════════════════════════════════════

Document Control

Created: 24/03/2026

Last Update: [Date]

Owner: [Operator Name]

Approved by: Pascal Caloc (Sales/Growth Lead)

Status: ARCHIVED — LEARNING DOCUMENTED

═══════════════════════════════════════════════════════════════════════════════