Claude Prompts for Writing Better Emails in Half the Time

The short version: Claude can draft a solid first version of almost any email in under a minute, but the time you save only counts if you stop re-writing from scratch and start feeding it better instructions. The prompts below are built from the structure Claude needs: context, tone, length, and a clear job for the email to do.

I've spent five years rebuilding a business in public, which means I write a stupid number of emails every week. Pitches, follow-ups, apologies for late replies, client updates, the lot. I used to think using AI for email would make me sound like everyone else. It doesn't, if you give it the right input. It makes you sound like you had an extra twenty minutes you didn't have.

Why most people get slower, not faster, with Claude

Here's the bit nobody tells you: if you type "write me an email about the delay" into Claude, you will get a generic, slightly waffly draft, and then you'll spend ten minutes fixing it. That's not faster than writing it yourself. It's slower, because now you're editing someone else's bad first draft instead of writing your own decent one.

The fix isn't a magic prompt. It's giving Claude the same information you'd give a new assistant on their first day: who the email is for, what happened, what you want them to do, and how blunt or soft you want to be. Skip that and you're gambling on the model guessing your intent correctly, which it won't, because it can't read your inbox or your relationship with the person.

The five-part structure that saves time

Every good email prompt has five pieces. Miss one and you'll be rewriting:

• Recipient and relationship - client, boss, cold prospect, supplier you're annoyed with
• Situation - what's happened, in two or three plain sentences
• Goal - what you want to happen after they read it
• Tone - formal, warm, firm, apologetic, no-nonsense
• Length - a number, not "short." Say "under 120 words"

Put those five things in and Claude's first draft is usually 80 percent there. You're editing a sentence or two, not restructuring the whole thing.

A worked example

Say you run a small marketing consultancy and a client's invoice is three weeks overdue. You're annoyed but you still want the account. Here's a prompt that does the job:

"Write an email to a client whose payment is three weeks late on a £2,400 invoice. We have a good relationship and I want to keep it that way, but I need the money and I'm tired of chasing. Tone: friendly but firm, no apologising for asking. Goal: get payment within five working days or a concrete date. Length: under 100 words. Don't mention late fees, just ask for a clear timeline."

Compare that to "write a payment reminder email" and you'll see the difference immediately. The first gives Claude a job. The second gives it a vague topic, and vague topics produce vague emails full of phrases like "I hope this finds you well" and "just following up," which is exactly the sludge you were trying to avoid writing in the first place.

Prompts for the emails everyone dreads

These are the ones people sit on for days because they don't know how to start. Steal the structure and swap the details.

Declining a meeting without sounding rude

"Write an email declining a meeting request from a colleague about a project I'm not involved in anymore. Keep it warm but clear, redirect them to the right person (Sarah in operations), under 60 words, no over-explaining."

Chasing someone who's gone quiet

"Write a follow-up email to a prospect who went quiet after a proposal three weeks ago. Don't be needy. One short paragraph, one direct question, give them an easy out if they've gone with someone else. Under 80 words."

Saying no to a discount request

"Write an email declining a 20 percent discount request from a potential client. Be respectful of their budget but firm on price. Offer a smaller scope instead of a lower rate. Tone: confident, not apologetic. Under 120 words."

Notice none of these say "make it sound professional." That instruction means nothing to Claude. It already defaults to professional. What it needs is your actual boundary, which is the thing you'd normally soften into mush when writing under pressure.

The uncomfortable bit people skip

Here's what most advice on this topic won't say out loud: the fastest way to write emails with Claude is to stop trying to sound like yourself on the first draft. Ask for the plainest, most direct version possible, strip out the hedging, and then add your own voice back in afterwards with two or three small edits. People do it backwards. They ask Claude to "sound like me," get a draft full of their own verbal tics exaggerated back at them, and then spend ages trying to tone it down. Ask for plain and blunt first, then warm it up yourself. It's quicker and the result is better.

If you want more on getting Claude to match your actual writing voice rather than a generic AI voice, the piece on Claude prompts for editing your own writing covers that in more depth than I can here.

Reusable templates worth saving

Save these in a notes app so you're not retyping the structure every time:

• "Write a [type] email to [who] about [situation]. Tone: [tone]. Goal: [what you want to happen]. Length: under [X] words."
• "Rewrite this email to be more direct and 30 percent shorter, keep the key ask, cut the hedging: [paste draft]"
• "Give me three subject line options for this email, one neutral, one urgent, one curious: [paste email]"

The rewrite prompt is the one I use most. Write your own messy first draft, then hand it to Claude purely to tighten, not to rewrite from scratch. You keep your voice, it removes the fat. That one habit alone probably saves more time than any fancy prompt.

Where the time goes

If you're writing ten emails a day and each one used to take six minutes, that's an hour. With a real prompt structure, most of those drop to two or three minutes, because Claude's first draft needs a tweak, not a rewrite. That's roughly 30 minutes back, every single day, which over a working month is about ten hours. That's not a small number. That's a free afternoon a week.

For longer, more detailed messages, say a project update with several sections, the shorter prompt structure above won't be enough on its own. That's a different skill, and I've written about it separately in Claude prompts for writing long emails fast, which covers how to get Claude to handle structure and sections without losing the plot halfway through.

A note on tone and model choice

Not every email needs the same model. For quick, low-stakes replies, a faster lighter model does the job fine. For anything with nuance, a tricky client situation, a difficult no, a sensitive update, it's worth using a stronger model and giving it more context. If you're not sure which is which, the breakdown in Claude Sonnet vs Haiku is worth five minutes of your time.

And if you're building these prompts into templates your whole team uses, rather than just your own shortcuts, it's worth reading up on how Anthropic itself recommends structuring business prompts, which I've broken down in Claude prompt engineering.

What this doesn't fix

Claude won't fix a relationship you've let go cold, and it won't make a difficult conversation easy just because the wording is tidy. If you're sending a redundancy email or anything with real emotional weight, use it to tighten your structure and tone, not to decide what to say. The judgement is still yours. The same goes for customer-facing replies where the stakes are reputational rather than just time-related; there's a separate set of considerations for those, covered in Claude prompts for customer support replies.

If writing emails faster is one small piece of a bigger push to use AI across your business, it might be worth getting outside eyes on it rather than guessing prompt by prompt. That's the kind of thing I help with through AI implementation coaching, building habits and templates that stick rather than one clever prompt you'll forget by Friday.

Frequently asked questions

What's the single most useful Claude prompt for emails?

The one that forces you to name recipient, situation, goal, tone and word count before you ask for a draft. Without those five pieces, Claude guesses, and guessed emails need more editing, not less.

Can Claude sound like me instead of sounding like AI?

Yes, but not on the first attempt. Ask for a plain, direct draft first, then edit it into your own voice with a few small changes, rather than asking Claude to mimic you from the start.

How much time does this really save?

If you write around ten emails a day, cutting each one from roughly six minutes to two or three saves about 30 minutes daily, which adds up to roughly ten hours a month.

Should I use Claude for sensitive emails like complaints or bad news?

Use it to tighten tone and structure, not to decide what you're saying. Judgement calls on sensitive or emotional situations should still be yours, with Claude as the editor rather than the author.