Email Draft & Polish

Use This Skill When

• Writing cold outreach or pitch emails
• Replying to important messages requiring the right tone
• Drafting status updates or reports for stakeholders
• Escalating issues professionally
• Condensing long messages into summaries
• Uncertain about tone (formal vs. casual vs. direct)
• Want multiple versions to choose from
• Need to ensure calls-to-action are clear

When NOT to Use

• Mass emails or bulk campaigns (different skill focus)
• Highly sensitive legal correspondence (consult lawyer)
• Complex negotiations with multiple stakeholders
• Marketing copy (use marketing-specific skills)

Context: Email Clarity Maturity

Undeveloped: Long rambling emails, unclear CTA, inconsistent tone.

Target: Concise drafts with clear CTA, consistent tone, multiple variants if tone unclear.

Optimized: A/B tested variants, sentiment analysis, delivery optimization, integration with email platforms.

Core Principle

Every email should have one clear purpose and one clear action. Clarity comes from structure, brevity, and consistent tone — not length or eloquence.

Instructions

Step 1: Gather Email Requirements

Ask for key information:

Element	Questions	Why Needed
Goal	Inform? Persuade? Apologize? Escalate? Negotiate?	Determines structure & tone
Audience	Who are you writing to? (peer, manager, customer, prospect?)	Shapes formality level
Context	What's the situation? Is this a reply or new thread?	Explains urgency & tone
Length	How long should it be? (3 lines, 3 paras, 1 page?)	Disciplined brevity
Must-Include	Any specific points, data, or disclaimers?	Ensures completeness
Tone	Formal, warm, direct, apologetic, celebratory?	Sets voice & style
CTA	What action do you want? (approval, response, meeting?)	Makes ask explicit

Capture in brief:

# Email Brief

**Goal**: Get Q2 budget approval
**Recipient**: Finance Director (busy, data-driven)
**Context**: Follow-up to our discussion last week
**Must-include**: Budget breakdown, ROI projection, timeline
**Length**: Concise (3-4 paras)
**Tone**: Professional, confident, not pushy
**CTA**: Approval by Friday for Monday rollout

Step 2: Create Email Outline

Map key points before drafting:

## Email Structure

**Subject Line**: [Working title—refine later]

**Greeting**: [Name, formality appropriate to recipient]

**Hook/Opening** (1-2 sentences):
- What's this email about?
- Why should they care right now?

**Context** (if needed):
- Background they might have missed?
- Relevant previous discussion?

**Main Points** (3-4 bullets or short paragraphs):
- Point 1 + evidence/data
- Point 2 + evidence/data
- Point 3 (objection handling, if applicable)

**Call-to-Action** (explicit & single):
- What do you want them to do?
- By when?
- How should they respond?

**Closing**:
- Warm/formal/neutral depending on tone
- Optional: offer for discussion

Example outline for budget request:

# Q2 Budget Approval Email

**Subject**: Q2 Budget Approval Needed — $45K Initiative

**Hook**: Following up on our conversation about hiring contractors

**Main Points**:
1. Budget breakdown: Dev ($25K), Design ($15K), Tools ($5K)
2. Expected ROI: 30% faster delivery, 15% quality improvement
3. Timeline: Need approval by Friday for Monday contractor onboarding

**CTA**: Can you approve by Friday? Happy to discuss Thursday if needed.

**Closing**: Thanks for considering — this will help us hit our Q2 goals

Step 3: Draft Email

Write first draft with discipline:

Rules:

• Keep paragraphs to 2-3 sentences max
• Avoid hedging ("I think maybe could possibly")
• Replace jargon with clear language
• Subject line under 50 characters
• Make CTA the last substantive line

Example draft:

Subject: Q2 Budget Approval — $45K Initiative

Hi [Name],

Following up on our conversation last week about accelerating Q2 delivery.

We'd like to bring on contractors in three areas:
• Development: $25K (core feature build)
• Design: $15K (UX refinement)
• Tools & infrastructure: $5K (productivity)

This investment should accelerate our delivery by 30% and reduce defects by ~15%, directly supporting our Q2 targets.

Can you approve this by Friday? We'd like to onboard Monday so we don't lose momentum. Happy to discuss details Thursday if helpful.

Thanks,
[Your name]

Step 4: Create Tone Variants

If the tone is unclear, offer 2-3 versions:

Variant A: Formal & Confident

Subject: Q2 Budget Approval Required — $45K Initiative

Dear [Name],

Per our discussion, I'm seeking approval for a $45K contractor budget across development, design, and tools to meet our Q2 delivery targets. This investment will accelerate feature delivery by an estimated 30% while reducing defects.

Detailed breakdown:
• Development: $25K
• Design: $15K  
• Infrastructure: $5K

I require your approval by Friday, April 30th, to proceed with Monday onboarding. Please confirm at your earliest convenience.

Best regards,
[Your name]

Variant B: Warm & Collaborative

Subject: Quick Favor — Q2 Budget Approval 🚀

Hi [Name],

Hope you're having a good week! Following up on our chat about contractors—I think bringing on the team we discussed could be a real game-changer for Q2.

Quick recap:
• Dev ($25K): Heads down on core features
• Design ($15K): Polishing the UX
• Tools ($5K): Dev productivity stuff

We're thinking 30% faster delivery + fewer bugs. Would really help us crush our goals.

Could you approve by Friday? We're eager to get started Monday. Let me know if you want to chat it through—always happy to jump on a call.

Thanks so much!
[Your name]

Variant C: Direct & Data-Driven

Subject: Q2 Budget Request: $45K (Expected 30% Velocity Improvement)

[Name],

Requesting $45K approval for Q2 contractor team:

**Budget**: Dev $25K | Design $15K | Tools $5K
**Expected Impact**: +30% delivery velocity, -15% defect rate
**Timeline**: Approval by Fri 4/30 → Onboard Mon 5/3

Details in attached spreadsheet. Need your sign-off by EOD Friday.

[Your name]

Guidelines for variants:

• Show 1-2 versions unless tone is highly ambiguous
• Label each clearly (Formal, Warm, Direct)
• Keep structure consistent; vary tone through word choice
• Recommend one based on relationship with recipient

Step 5: Quality Assurance Checklist

Before sending, verify:

Check	Questions	Fix If Needed
Clarity	Could a 3rd party understand the ask?	Remove jargon, simplify sentences
CTA	Is ONE action crystal clear? When?	Add deadline, method (reply/click/call)
Tone	Does it match the audience & goal?	Adjust formality, warmth level
Length	Is it concise? Could you cut 20%?	Delete filler, combine short sentences
Names/Links	Are all names spelled right? Links working?	Proofread carefully; test links
Emoji/Formatting	Appropriate for recipient/channel?	Remove if in doubt; use sparingly
Promises	Are you over-committing?	Ensure you can deliver on commitments
Tone Match Reply	Does it match their style?	If they're formal, don't be overly casual

Example QA review:

## QA Checklist ✓

✓ Clarity: "Approve $45K budget by Friday for Monday onboarding" — crystal clear
✓ CTA: Single ask (approve by Friday), method (reply to this email)
✓ Tone: Professional but warm; matches recipient's communication style
✓ Length: 4 short paragraphs; could cut 0 words without losing clarity
✓ Spelling/Links: All correct; no links needed for this email
✓ Promises: Budget confirmed with accounting already; realistic timeline
✗ Emoji: Removed the rocket emoji (too informal for Finance Director)

**Ready to send!**

Step 6: Optimize Subject Lines

Subject line impacts open rate. Make it:

Criterion	Good	Avoid
Specific	"Q2 Budget Approval — $45K Initiative"	"Budget Request"
Urgent (if true)	"Urgent: Q2 Approval Needed by Friday"	"Please read this"
No clickbait	"Q1 Results + Q2 Forecast"	"You won't believe Q1 numbers"
Under 50 chars	"Q2 Budget OK? — $45K, Need Fri Approval"	"We're requesting a rather significant budget for the second quarter"

Subject line variants for same email:

✓ "Q2 Budget Approval — $45K (Need Fri)" ✓ "Quick Decision Needed: $45K Q2 Investment" ✓ "Q2 Initiative — Approval Request by Fri" ✗ "Budget" (too vague) ✗ "URGENT!!!!" (overused, reduces credibility)

Output

Deliver:

1. Email Draft(s)

   • Subject line
   • Greeting, body (structured, concise), closing
   • 1-3 tone variants if tone was ambiguous

2. QA Summary

   • Clarity, tone, CTA verification
   • Any flags or suggestions

3. Optional Enhancements

   • Alternative subject lines
   • Follow-up timing (if no response by X date)
   • Message for other channels (Slack summary, etc.)