1. The Writing Bottleneck
Most professionals spend 30–40% of their workday writing. Emails, Slack messages, reports, proposals, presentations—it adds up. Not because writing is hard, but because we over-edit.
The typical flow: think → write → rewrite → rewrite → polish → send. This takes forever, especially for high-stakes communication.
Claude flips this: think → bullet points → Claude drafts → you refine → send. You save the middle steps.
What AI Writing Can Do
- Draft from bullets: Turn your notes into full paragraphs
- Edit for clarity: Remove jargon, simplify sentences, fix tone
- Adapt tone: Formal → casual, angry → diplomatic, brief → detailed
- Translate: Make technical content accessible, or vice versa
- Fix common issues: Passive voice, redundancy, missing structure
⚠️
The Rule: Claude drafts, you refine. Never send AI output without reading it first. Claude can be wordy, miss nuance, or misunderstand context. Your job: make it yours.
2. Emails That Get Responses
Most emails get ignored because they're unclear about what the recipient should do. Claude can fix this. Here are three critical email types:
Type A: Cold Outreach
You're contacting someone who doesn't know you. Key: establish credibility and make the ask crystal clear.
Bad Prompt (Vague)
"Hi, I wanted to reach out about a potential collaboration. Let me know if you're interested."
Write a cold email to {recipient name}, {title} at {company}. Here's what I want to achieve: {your goal}.
About me: {your background}
Why I'm reaching out: {specific reason}
What I'm asking for: {specific request - call, meeting, advice, intro, etc.}
Key points to hit:
- Establish I've done my homework
- Show I understand their specific situation (not generic)
- Make the ask so specific they can say yes/no immediately
- Keep it under 150 words
Write in the style of: {formal/casual/friendly}
Type B: Internal Escalation
You need to escalate something to your manager or leadership. Key: lead with business impact, not complaints.
Bad Prompt (Complaining)
"I'm frustrated with the current process. It's slowing us down and no one listens to my concerns."
Write an escalation email to my manager about {issue}.
Business impact: {specific metrics: cost, time lost, risks}
Root cause: {what's actually going wrong}
What I've tried: {steps you've already taken}
What I need: {specific decision, resource, or support}
Frame it as a problem-solver, not a complainer. Use BLUF (bottom-line-up-front):
- Start with the ask
- Then explain the impact
- End with next steps
Tone: {professional/collaborative/urgent}
Type C: Follow-Up After No Response
They didn't respond. Key: don't sound hurt. Sound helpful and remove barriers to response.
Bad Prompt (Passive Aggressive)
"I wanted to follow up on my previous email. Still waiting for your response."
Write a follow-up email to {recipient} about {original topic}.
Original ask: {what I originally asked}
Time since: {how long it's been}
New angle (optional): {why I'm reaching out now - urgency, new info, lower stakes}
Make it easy for them to say yes by:
- Offering multiple options or paths
- Removing any implied urgency
- Showing I understand they're busy
- Making the ask smaller/easier if possible
Tone: {helpful/understanding/light}
💡
The "Voice Match" Technique: Paste a previous email you wrote into Claude and ask it to write the new email in your exact style. This ensures the output sounds like you, not generic AI.
3. Proposals, Reports, and Business Cases
High-stakes documents need structure. Claude can build a skeleton in minutes. You fill in the details.
Template 1: One-Page Business Case
Write a one-page business case for {project/decision}.
Problem: {What's broken or missing?}
Solution: {What are you proposing?}
Impact: {Quantify: revenue, cost savings, risk reduction, speed, quality}
Investment: {Time, budget, resources required}
Timeline: {When will this be done?}
Risks: {What could go wrong?}
Format as:
- 1 paragraph executive summary (lead with impact)
- Problem statement (1-2 paragraphs)
- Solution (1-2 paragraphs)
- Business case (1 table: costs, benefits, timeline)
- Risks & mitigations (bullet points)
- Recommendation (1 sentence)
Template 2: Executive Summary
Write a 1-2 page executive summary for {report/project}.
Key findings: {What's the most important thing people need to know?}
Context: {Why does this matter? Who cares?}
Recommendation: {What should we do?}
Trade-offs: {What's the cost? What are we giving up?}
Timeline: {When?}
Use BLUF structure:
- Bottom line first (1 paragraph: the ask + why it matters)
- Supporting details (2-3 key findings)
- Recommendation (1 sentence)
- Next steps (action items + DRI)
Template 3: Project Proposal
Write a project proposal for {project name}.
Vision: {What will this deliver?}
Scope: {What's in, what's out?}
Timeline: {Start → milestones → ship date}
Budget: {Resource request}
Success metrics: {How will we know it worked?}
Risks: {What could derail this?}
Stakeholders: {Who needs to be involved?}
Format:
- Title & elevator pitch
- Problem statement
- Proposed solution
- Scope & timeline (Gantt or table)
- Budget & resources
- Success criteria
- Risks & mitigation
- Team & DRI (directly responsible individual)
ℹ️
Structure Matters More Than Length: A messy 10-page report gets skimmed and ignored. A crisp 2-page proposal with clear headings gets read and acted on. Claude is great at structure—use it.
4. Editing, Tone, and Style
Claude is a world-class editor. Use it to refine clarity, tone, and style.
Six Editing Prompts
1. Make it more concise
Edit this to be 30% shorter without losing meaning. Remove jargon and filler words:
[PASTE TEXT]
2. Make it more confident
Rewrite this to sound more confident and authoritative. Replace hedging language ("may," "might," "possibly") with stronger claims:
[PASTE TEXT]
3. Convert to bullet points
Convert this paragraph into a bulleted list. Keep the key points, drop the narrative:
[PASTE TEXT]
4. Make it more empathetic
Rewrite this to sound warmer and more empathetic. I'm trying to build trust, not just deliver bad news:
[PASTE TEXT]
5. Plain language version
Rewrite this for a 12-year-old. Remove jargon, use short sentences, explain anything technical:
[PASTE TEXT]
6. Academic to casual
Rewrite this in casual, conversational English. Remove academic tone and make it sound like I'm talking to a peer:
[PASTE TEXT]
ℹ️
Plain Language Guide: Check out
plainlanguage.gov for government best practices on clarity. Claude knows these principles and can apply them.
🖥️HANDS-ON EXERCISE⏱ 35 min
Hands-On: Write 3 Real Work Pieces
In 35 minutes, use Claude to draft three real documents you've been putting off.
- Exercise 1: Write a professional email you've been procrastinating on (cold outreach, escalation, or follow-up)
- Exercise 2: Turn messy meeting notes into a clean summary email
- Exercise 3: Write a one-paragraph executive summary of a recent project or initiative
- For each exercise, paste the Claude output into your email client or doc and read it out loud
- Make 2-3 edits to match your voice (replace AI jargon, adjust tone, personalize)
- Send or save the refined version
Exercise 1: Professional Email Template
Use this prompt for the email you've been putting off:
Write an email to {recipient name}.
Goal: {What do you want them to do or know?}
Context: {Why you're writing now}
Key points: {2-3 bullet points of what matters}
Call to action: {Specific next step}
Style: {formal/friendly/urgent}
Length: {short/medium/detailed}
Use the voice of a {your profession}. Keep it under 200 words.
Exercise 2: Meeting Notes to Summary Template
Paste your meeting notes and use this prompt:
Convert these meeting notes into a clean summary email.
Include:
- Key decisions made
- Action items (who, what, by when)
- Open questions
- Next steps
Format it like a professional email you'd send to stakeholders who weren't there.
[PASTE MEETING NOTES]
Exercise 3: Executive Summary Template
For a recent project, use this prompt:
Write a one-paragraph executive summary for {project name}.
What it delivered: {brief description}
Impact: {metrics: time saved, revenue, cost reduction, risk, quality}
Outcome: {what's the status now?}
One sentence that captures: "{project name} {achieved outcome} by {method}, resulting in {impact}."
Keep it under 100 words.
Quick Reference: Copy-Paste Writing Prompts
Cold EmailInclude: recipient role, your credibility, specific ask, why them, next step
Internal EscalationLead with business impact → then problem → then ask → offer solutions
One-Page Business CaseExecutive summary → problem → solution → impact (quantified) → risks
Executive SummaryBLUF: bottom-line-up-front → key findings → recommendation → next steps
Voice MatchPaste a previous email you wrote and ask Claude: "Write this in my style"
Final RuleClaude drafts, you refine. Always read aloud before sending.