# Draft Outreach — Research-First Personalized Messaging

Research a prospect first, then craft personalized email and LinkedIn outreach. Works standalone or integrates with the lead_pipeline's EmailComposer for AI-powered generation.

## When This Skill Activates

Trigger phrases: "draft outreach to [company]", "write email to [prospect]", "outreach for [lead]", "cold email to [company]", "message [person]", "follow up with [company]"

## Three-Step Process

### Step 1: Research (Never Skip)
Before writing a single word, gather context:
1. Run prospect-research skill or check existing lead data
2. Identify the best personalization hook from:
   - **Trigger event** (best): funding, hire, product launch, expansion
   - **Shared connection**: mutual contacts, events, communities
   - **Content engagement**: blog post, podcast, social media post
   - **Company initiative**: strategic direction, public goals
   - **Role-based pain point** (fallback): challenges common to their role

### Step 2: Draft the Message

**Email Structure (AIDA Model):**
```
Subject: [Specific, relevant, under 50 chars — no clickbait]

[Opening hook — reference the research finding, 1 sentence]

[Interest — connect their situation to our value prop, 2-3 sentences]

[Proof point — brief evidence: metric, case study, or social proof, 1 sentence]

[Clear ask — specific, low-commitment CTA, 1 sentence]

[Signature]
```

**LinkedIn Message Structure:**
```
[Connection note — why connecting, reference shared context]

[1-2 sentences on relevance]

[Soft ask — no hard sell on first touch]
```

### Step 3: Create Follow-Up Sequence

If requested, generate a multi-touch sequence:

| Touch | Timing | Channel | Purpose |
|-------|--------|---------|---------|
| 1 | Day 0 | Email | Initial outreach with research hook |
| 2 | Day 3 | LinkedIn | Connection request with context |
| 3 | Day 7 | Email | Follow-up with new value angle |
| 4 | Day 14 | Email | Breakup email with final offer |

## Style Requirements

- **Plain text only** — no markdown, bold, italics, or formatting that breaks in email clients
- **Short paragraphs** — 2-3 sentences max per paragraph
- **Conversational tone** — professional but human, not robotic
- **Under 150 words** for initial cold email
- **No generic openers** — never use "hope this finds you well", "I'm reaching out because", "I noticed that your company"
- **Specific CTA** — "15-minute call Thursday or Friday?" not "let me know if you'd like to chat"

## Integration with Lead Pipeline

When the lead exists in the pipeline:
1. Use `Lead.company` data for personalization context
2. Use `Lead.contact` for verified email/LinkedIn
3. Pass the draft to `EmailComposer.compose()` for AI refinement if desired
4. Update lead status to `EMAIL_DRAFTED` after approval
5. Optionally trigger `EmailSender.send()` for delivery

**Composer Config Alignment:**
- Match the `ComposerConfig.tone` setting (professional/casual/formal)
- Include `ComposerConfig.value_proposition` as the core pitch
- Use `ComposerConfig.sender_name`, `sender_company`, `sender_role` for signature
- Respect `ComposerConfig.language` (en/ar) for bilingual outreach

## Templates by Scenario

### Cold Outreach (No Prior Relationship)
- Lead with trigger event or research finding
- Establish credibility in one sentence
- Propose specific value exchange

### Warm Introduction (Referral/Event)
- Name the connection or event immediately
- Reference the specific conversation or content
- Suggest continuing the dialogue

### Re-engagement (Gone Dark)
- Acknowledge the gap without guilt-tripping
- Offer new value (not just "checking in")
- Give an easy out alongside the ask

### Post-Event Follow-Up
- Reference specific session or conversation
- Share a relevant resource or insight
- Propose next step within 48 hours

## Key Rules
- NEVER draft without researching first — generic outreach is worse than no outreach
- NEVER use email formatting (HTML, markdown) — plain text only
- ALWAYS include a specific, time-bound CTA
- Personalization must be SPECIFIC — "loved your recent Series B" not "congrats on your success"
- Match the language to ComposerConfig.language when set
- Log outreach to GDPR audit trail via lead_pipeline
