Email Drafter

Overview

This skill produces clear, purposeful emails calibrated to the right tone, length, and structure for the situation—whether you're reaching out cold to a potential partner, nudging a slow-to-respond client, or delivering difficult feedback to a colleague. It applies proven subject line formulas, places calls to action where they land hardest, and keeps emails as short as they need to be and no shorter. The goal is emails that get opened, read, and acted on.

When to Use

• Cold outreach to prospects, journalists, collaborators, or employers
• Follow-up emails after meetings, proposals, or no-reply situations
• Internal communication: project updates, feedback, requests
• Client-facing messages: onboarding, status updates, difficult news
• Professional introduction or networking emails
• Declining requests or delivering bad news diplomatically
• Responding to complaints or sensitive situations

When NOT to Use

• Bulk email marketing sequences (use copywriter skill for campaign copy)
• Legal notices, contracts, or compliance communications requiring specific phrasing
• Transactional system emails (order confirmations, password resets)
• Personal/casual texts or messages to close friends

Quick Reference

Instructions

1. Clarify the email's single purpose. Every email should do exactly one thing: make an ask, share information, confirm something, or respond to something. If you have two asks, send two emails. Identify: who is the recipient, what is the relationship, and what is the single desired outcome?

2. Write the subject line. The subject line determines whether the email gets opened.

   • Personalized: "Quick question about [their company/project]"
   • Benefit-led: "How we helped [similar company] cut onboarding time by 40%"
   • Direct ask: "30-minute call this week?"
   • Re: trick for follow-ups: "Re: [original topic]" (implies conversation continuity)
   • Numbers: "3 ideas for your Q4 content calendar"
   • Avoid: "Following up", "Checking in", "Just wanted to…"

3. Choose the right tone.

   • Formal: C-suite executives, legal/finance contexts, first contact in conservative industries. Use "Dear [Full Name]", avoid contractions, use complete sentences.
   • Professional-casual: Most business contexts. Use first name, contractions fine, conversational but precise.
   • Casual: Colleagues you know, creative industries, startups. Use first name, relaxed language, emojis if culturally appropriate.

4. Structure the email.

   • Opener: Something real (not "hope you're well"). Reference a shared connection, recent event, or their work.
   • Body: State your purpose in the first or second sentence. Give just enough context. Don't bury the ask.
   • CTA: One clear, specific, low-friction action. "Reply with a yes or no" beats "Let me know your thoughts."
   • Sign-off: Match the tone. "Best," or "Thanks," for professional; "Cheers," or "Talk soon," for casual.

5. Calibrate length.

   • Cold outreach: 75–125 words (shorter = higher response rate)
   • Follow-up: 50–75 words (shorter than the original)
   • Meeting recap or detailed request: 150–250 words max
   • If it needs more than 250 words, consider whether an attachment or a call is better

6. For reply emails: Start by briefly acknowledging their message—one sentence. Then make your point or ask. Don't restate everything they said.

7. For difficult or sensitive emails: State the situation factually. Acknowledge impact. Offer a path forward. Avoid over-apologizing (it undermines the message) and avoid defensiveness.

8. Proofread for these specifics: Correct recipient name (check spelling), accurate subject line, working links if included, no "sent from my phone" auto-signatures if the email is formal.

Examples

Example 1: Cold Outreach Email

Input: "Write a cold email to a product manager at Stripe asking for 20 minutes to discuss a UX research tool I'm building. I don't know them personally. Keep it short and genuine."

Output:

Subject: Quick question about Stripe's onboarding UX

Hi [Name],

I came across your talk at Config 2024 on reducing payment friction—the friction-mapping framework you described is exactly the kind of thinking I'm trying to support with a tool I'm building.

I'm developing a lightweight UX research platform that helps PM teams track friction points across user flows without drowning in session recordings. Given your focus on onboarding, I thought you'd either find it interesting or immediately tell me why it's a bad idea—either would be valuable.

Would you have 20 minutes in the next two weeks for a quick call?

Thanks for considering it, [Your Name]

Why it works:

• Subject is specific and doesn't oversell
• Opens with genuine reference to their actual work
• States the tool's value in one sentence
• Frames the ask as low-stakes (willing to hear "no")
• Single CTA with timeframe
• Under 100 words

Example 2: Follow-Up Email (No Reply After First Outreach)

Input: "I sent a proposal to a client last week and haven't heard back. Write a follow-up that's not annoying or pushy."

Output:

Subject: Re: Proposal for Q4 Campaign

Hi Sarah,

Just wanted to resurface this in case it got buried—no worries if the timing isn't right.

I'm happy to adjust the scope, timeline, or budget if anything in the proposal gave you pause. Otherwise, if you're still reviewing, I'll check back in another week.

Thanks, [Your Name]

Why it works:

• Extremely short—respects their time
• "No worries" immediately lowers pressure
• Offers a concrete reason they might not have responded (objections)
• Sets a clear next touchpoint
• Zero guilt-tripping or passive aggression

Example 3: Internal Feedback Email

Input: "Write an email to a junior team member letting them know their last report had unclear structure and needs revision. Be direct but kind."

Output:

Subject: Feedback on the Q3 Market Analysis Report

Hi Jamie,

Thanks for getting the Q3 report in on time—I know the data collection was a heavy lift.

I want to give you some direct feedback before we share it with the wider team: the current structure makes it hard to follow the main argument. Specifically, the executive summary doesn't match the conclusion, and the methodology section appears before context that would help readers understand why it matters.

I'd suggest:

1. Rewrite the executive summary to reflect the report's actual findings
2. Move the methodology section to an appendix or after the key findings
3. Add a one-paragraph "so what" to each major section

Happy to walk through it together if that's helpful—just let me know. Revised version needed by Thursday EOD.

Thanks, [Your Name]

Best Practices

• Write the CTA before writing the rest of the email—it keeps the whole message focused
• Use the recipient's name once in the greeting; more than once feels like a sales script
• Avoid hedging phrases: "just wanted to", "I was wondering if maybe", "sorry to bother you"
• Front-load key information—assume they may only read the first two sentences
• Match the formality of the context, not your own preference
• For important emails, wait 10 minutes before sending—re-read once cold

Common Mistakes

• Weak subject lines: "Follo