---
name: email-mastery
description: Write effective professional emails using AIDA framework, subject line formulas, and follow-up cadences. Use when crafting cold outreach, negotiation emails, or follow-ups.
domain: mindset
---

# Email Mastery

Professional email writing framework covering cold outreach, follow-ups, escalation, and negotiation emails. Based on copywriting principles and high-response-rate patterns.

## When to Use

- Cold outreach to prospects, partners, or investors
- Follow-up sequences after meetings or proposals
- Negotiation or escalation emails requiring persuasion
- High-stakes internal communication to executives
- **When NOT to use**: Urgent matters (call instead), highly sensitive topics (meet in person), or casual team communication

## AIDA Framework

**Attention → Interest → Desire → Action**

| Stage | Purpose | Technique |
|-------|---------|-----------|
| **Attention** | Hook them in 5 seconds | Compelling subject line + personalized opening |
| **Interest** | Make it relevant to them | Show you understand their problem/goal |
| **Desire** | Create value proposition | Proof, social proof, or specific benefit |
| **Action** | One clear next step | Single CTA with low friction |

## Subject Line Formulas

| Formula | Example | Use Case |
|---------|---------|----------|
| **Question** | "Quick question about your Q2 roadmap" | Cold outreach |
| **Personalization** | "[Mutual connection] recommended I reach out" | Warm intro |
| **Value prop** | "How [Company] cut deployment time by 60%" | Case study share |
| **Curiosity gap** | "The mistake costing you 20% in ARR" | Content marketing |
| **Urgency** | "Friday deadline: [Topic]" | Follow-up |

**Rules**:
- Keep under 50 characters (mobile preview)
- Avoid spam triggers: "FREE!!!", "ACT NOW", all caps
- Personalize when possible (their company, role, recent event)

## Cold Email Structure

**Template** (150 words max):

```
Subject: [Personalized hook]

Hi [Name],

[Attention: 1 sentence showing you did research]
I noticed [specific thing about them/their company].

[Interest: 1 sentence on their problem]
Most [their role] struggle with [pain point].

[Desire: 1-2 sentences of value]
We help [similar companies] [achieve specific outcome]. 
[Social proof or result]: [Company X] saw [metric].

[Action: Single CTA]
Would a 15-min call next week make sense? 
[Link to calendar] or suggest a time.

Thanks,
[Your name]
```

**Example**:
> Subject: Quick question about Acme's API rate limits  
>   
> Hi Sarah,  
>   
> I saw Acme launched a public API last month—congrats on the traction.  
>   
> Most eng teams hit rate-limit issues around month 3 as usage spikes.  
>   
> We help API companies (Stripe, Twilio, etc.) scale rate limiting without rewrites. Our customers handle 10x traffic surges with zero downtime.  
>   
> Worth a 15-min call to share what we learned? [Calendar link]  
>   
> Best,  
> Alex

## Follow-Up Cadence

**The 3-7-14 Rule**: Follow up on days 3, 7, and 14 after initial send.

| Follow-up | Angle | Example |
|-----------|-------|---------|
| **#1 (Day 3)** | Bump with new value | "Forgot to mention: here's a case study from [similar company]" |
| **#2 (Day 7)** | Different angle or question | "Curious: is rate limiting even on your radar this quarter?" |
| **#3 (Day 14)** | Break-up email | "Haven't heard back—should I close your file?" |

**Break-up email** (highest response rate):
> Subject: Should I close your file?  
>   
> Hi [Name],  
>   
> I haven't heard back, so I'm guessing this isn't a priority right now.  
>   
> Should I close your file, or is there a better time to revisit?  
>   
> Thanks,  
> [Your name]

## Reply-All Etiquette

| Situation | Do This | Don't Do This |
|-----------|---------|---------------|
| **Internal update** | Reply-all if everyone needs the info | Reply-all with "Thanks!" (noise) |
| **Someone asks a question** | Reply-all if answer benefits the group | Reply privately if only the asker cares |
| **External clients CC'd** | Be cautious—clients see everything | Vent or discuss internally on that thread |
| **Large group (>10 people)** | Move to Slack/separate thread | Keep replying-all (inbox spam) |

## Common Rationalizations

| Rationalization | Reality |
|-----------------|---------|
| "Longer = more thorough" | Emails >200 words get skimmed or ignored. Brevity shows respect. |
| "I'll just wing it" | Effective emails follow structure. Use templates. |
| "They'll figure out the next step" | One clear CTA or you'll get no response. |
| "Following up is pushy" | 80% of sales require 5+ follow-ups. Persistence ≠ pushy if you add value. |

## Red Flags

- Subject line is generic ("Following up", "Quick question")
- First sentence is about you, not them ("I'm the founder of...")
- No clear CTA or multiple CTAs ("Let me know if you want to chat, or I can send a deck, or...")
- Email is >250 words (too long for cold outreach)
- You apologize for emailing ("Sorry to bother you...")
- Tone is passive-aggressive in follow-ups ("Per my last email...")

## Verification

- [ ] Subject line under 50 chars and personalized
- [ ] First sentence shows research or relevance
- [ ] Value proposition clear and specific (not vague)
- [ ] Single, low-friction CTA (calendar link, yes/no question)
- [ ] Email under 200 words for cold outreach (or 300 for warm)
- [ ] Follow-up cadence planned (days 3, 7, 14)