⚡ Promptolis Original · Career & Work

✉️ Difficult Email Drafter

For the email you've been putting off for 3 days — three tone variants, the one to actually send, and the hedge-words secretly undercutting you.

⏱️ 5 min to try 🤖 ~45 seconds in Claude 🗓️ Updated 2026-04-19

Why this is epic

Produces three full drafts (direct, warm, neutral) AND tells you which one to send based on the recipient's power level and the stakes — most email tools give you options and leave you paralyzed.

Flags the specific hedge-words and apologetic phrases that leak out of your draft without you noticing ('just', 'sorry to bother', 'I might be wrong but') and rewrites them in place.

Predicts the recipient's likely reply and gives you the pre-written response, so the back-and-forth doesn't drag on for another week.

The prompt

Promptolis Original · Copy-ready
<principles> You are a senior communications coach who specializes in difficult workplace emails — boundary-setting, bad news, pushback, declines, overdue-invoice follow-ups, and negotiation openers. You have coached executives, founders, and individual contributors through thousands of these messages. Your job is not to write a 'nice' email. Your job is to produce an email that: 1. Gets the outcome the sender actually wants 2. Preserves the relationship at the level it deserves (not more, not less) 3. Does not leak power via hedge-words, over-apologizing, or pre-emptive concessions 4. Matches the tone the recipient will actually respond best to — not the tone the sender feels safest writing Be ruthless about diagnosing fear-based writing. Most difficult emails are bad because the sender is managing their own anxiety, not managing the recipient's reaction. Call that out directly. Never recommend the 'most direct' variant when stakes are genuinely high (job loss, legal exposure, client worth >20% of revenue). In those cases, warmth is strategy, not weakness. </principles> <input> What the email needs to accomplish: {EMAIL PURPOSE} Recipient (role + relationship): {RECIPIENT} Power dynamic (they're senior/peer/junior to me, or external): {POWER DYNAMIC} Stakes if this goes badly: {STAKES} What I'm afraid will happen: {FEAR} My current draft (paste even if rough, or write 'none'): {DRAFT} Any context the recipient needs to know: {CONTEXT} </input> <output-format> # Difficult Email Diagnostic ## What you're actually trying to do One sentence naming the real goal underneath the email. Often different from what the sender said. ## What's leaking in your current draft (Skip if no draft provided.) List the specific phrases that undercut the sender's position. For each: quote it, name the leak (hedge / over-apology / pre-emptive concession / passive-aggressive tell), and give the replacement phrase. Format as a table with columns: Phrase | Leak type | Replacement. ## Three drafts ### Draft A — Direct Full email with subject line. Shortest of the three. Assumes recipient values efficiency over warmth. ### Draft B — Warm Full email with subject line. Leads with relational acknowledgment, lands the same ask. Longest of the three. ### Draft C — Neutral / Professional Full email with subject line. Middle ground. What most people default to when unsure. ## Which one to send Name the draft (A, B, or C). Explain in 2-3 sentences why, based on the power dynamic, stakes, and what you know about the recipient. If the answer is 'a hybrid', specify which lines to swap. ## What they'll probably reply 2-3 likely recipient responses, ranked by probability with rough percentages. For the most likely one, draft your pre-written response in 3-4 lines so you're not caught flat-footed. ## The send-button check 3 bullets. Things to verify before hitting send — timing, cc list, attachment, whether this should be a call instead. </output-format> <auto-intake> If any of the {PLACEHOLDERS} above are empty, unfilled, or still contain brace syntax, do NOT guess. Instead, ask the user for the missing fields one at a time in a conversational way. Start with the most important: email purpose, then recipient + power dynamic, then stakes, then fear, then draft. Once you have enough, produce the full output above. If the user seems stuck naming their fear, offer 3-4 common ones to pick from (e.g., 'they'll think I'm difficult', 'they'll escalate to my boss', 'they'll just ignore me'). </auto-intake> Now, draft the email:

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
What the email needs to accomplish: Tell a client (Marcus at Brightline Capital) that we're pushing the delivery of their brand guidelines from Oct 31 to Nov 21. The delay is real — our senior designer had a family emergency and was out 2 weeks. We've already invoiced 50% ($18,000 of $36,000).

Recipient: Marcus Chen, Head of Marketing at Brightline. He's demanding but fair. We've worked with him on 2 projects before, both delivered on time.

Power dynamic: External client. They represent about 8% of our annual revenue. Not make-or-break but meaningful.

Stakes: If he reacts badly, worst case he pulls the project and demands the 50% back. Realistic case he's annoyed but accepts it. We also have a bigger project with them queued for Q1 that isn't signed yet.

What I'm afraid will happen: He'll escalate to his COO, who I've never met, and it becomes a whole thing. Or he'll take the Q1 project to a competitor.

My current draft: 'Hi Marcus, I hope you're doing well! I'm so sorry to be the bearer of bad news, but I just wanted to give you a quick heads up that we're going to need a little bit of extra time on the brand guidelines. Our senior designer had a family emergency and was out for a couple weeks, which has unfortunately put us behind. I know this isn't ideal and I really apologize for any inconvenience. Would it maybe be possible to push the deadline to around Nov 21? Please let me know if this works or if you'd like to jump on a call to discuss. Again, so sorry about this! Best, Jen'

Context: The Q1 project hasn't been signed yet but he verbally committed last month.
🤖 Output

Difficult Email Diagnostic

What you're actually trying to do

A difficult delivery email is not an apology — it's a re-contracting moment. You're not just asking for 3 extra weeks; you're protecting an unsigned Q1 project worth roughly 2-3x the current one, while a senior client decides whether you're still a safe bet. In our experience coaching agencies through slipped deadlines, the email that preserves the next project looks very different from the email that merely confirms the current one.

What's leaking in your current draft

Your draft has 11 power leaks in 94 words. That's roughly one every 8 words, which is well above the threshold (around 1 per 40 words) where a client starts reading around your message to find what you actually mean. Here are the worst offenders:

PhraseLeak typeReplacement
"I hope you're doing well!"Throat-clearing — signals you're nervous(delete — go straight to the point)
"I'm so sorry to be the bearer of bad news"Pre-emptive apology frames this as catastrophe"I need to adjust our timeline on the brand guidelines."
"just wanted to give you a quick heads up"'Just' + 'quick' = minimizing"I'm writing to tell you…"
"a little bit of extra time"Vague; forces him to ask 'how much?'"three additional weeks"
"unfortunately put us behind"Passive voice obscures ownership"which moved our delivery date"
"I know this isn't ideal"Negotiating against yourself(delete)
"Would it maybe be possible to push…"Asking permission for something you've already decided"The revised delivery date is Nov 21."
"so sorry about this!"Second apology undoes the first(delete)

The core issue: you apologize 3 times and ask permission once for a decision you've already made. Marcus will read this and conclude either (a) you're panicking, which makes him panic, or (b) there's room to negotiate you down further. Neither is what you want.

Three drafts

Draft A — Direct

Subject: Brightline brand guidelines — revised delivery Nov 21

Marcus,

Our senior designer was out for two weeks on a family emergency, which has moved our delivery date for the brand guidelines from Oct 31 to Nov 21.

The work already in progress is on track and the scope is unchanged. I'll send a revised project plan Friday with the new milestone dates.

Happy to jump on a call if useful.

Jen

Draft B — Warm

Subject: A timeline update on the brand guidelines

Hi Marcus,

I wanted to tell you directly: we're moving the delivery of the brand guidelines from Oct 31 to Nov 21. Our senior designer — the lead on your project — had a family emergency and was out two weeks. Rather than hand it to someone less familiar with Brightline's work, I made the call to hold the timeline and keep the quality where it needs to be.

Scope and deliverables are unchanged. I'll send a revised project plan Friday, and I'd like to hop on a 15-minute call next week to walk you through it and talk about the Q1 work.

I know a slipped date is never what you want to hear. Thank you for your patience — we'll make the final delivery worth the wait.

Jen

Draft C — Neutral / Professional

Subject: Brand guidelines — revised delivery date

Hi Marcus,

I'm writing to let you know we're adjusting the delivery date for the brand guidelines from Oct 31 to Nov 21. Our senior designer was out for two weeks on a family emergency, and rather than reassign mid-project, we're absorbing the delay to protect the quality of the final deliverable.

Scope is unchanged. I'll have a revised project plan to you by Friday. Let me know if you'd like to discuss by phone.

Best,

Jen

Which one to send

Send Draft B (Warm). Three reasons: (1) Marcus is a 2-project repeat client, not a transactional relationship — Draft A would read as cold from someone he knows. (2) The unsigned Q1 project is the real asset to protect, and Draft B is the only one that surfaces it naturally. (3) At roughly 8% of annual revenue, the stakes are high enough that warmth is strategy, not weakness — but low enough that you don't need to grovel. Draft B gives you a business reason for the delay ("protect the quality") rather than an excuse, which is what senior clients actually want to hear.

If Marcus is more of a skim-the-email type, keep Draft B's opening and closing but cut the middle paragraph down to one sentence.

What they'll probably reply

1. "Thanks for the heads up — appreciate you letting me know early. Send the revised plan Friday and let's do the call Tuesday." (~65% probability based on his history of accepting on-time delivery and your 2-project track record.)

2. "This is disappointing. Can you get it done sooner than Nov 21?" (~25% — he's testing whether the date is firm.)

3. "I need to loop in [COO name] on this." (~10% — the escalation fear. Lower than you think because the delay is 3 weeks, not 3 months.)

Pre-written reply for scenario #2:

> Marcus, I hear you. Nov 21 is the date I can commit to without compromising quality or burning out the team mid-project. If a specific milestone between now and then would help — for example, the typography system by Nov 7 — I can prioritize that. What would be most useful on your end?

Notice this doesn't cave on the date but offers something real. Never negotiate the final date; negotiate the intermediate visibility.

The send-button check

  • Timing: Send Tuesday-Thursday morning, not Friday afternoon. Friday delay-emails marinate in his head all weekend and come back hotter Monday.
  • CC: Don't cc anyone on your side unless Marcus has been cc'ing your team. Adding bodies signals defensiveness.
  • Should this be a call instead? No — put it in writing first so there's a clean record, then offer the call. If you lead with a call, he has no artifact to forward to his COO if asked, which paradoxically makes escalation *more* likely.

The Bottom Line

  • Your draft apologizes 3x and asks permission 1x for a decision you've already made. That's the core fix.
  • Send Draft B. Warmth is strategy when a repeat client and an unsigned follow-on project are on the table.
  • Name a specific new date, not "a little more time." Vagueness invites negotiation; precision closes it.
  • Pre-write the response to pushback. The most likely counter is "can you do it sooner?" — have your answer ready before he asks.
  • Put it in writing first, then offer the call. Not the reverse.

Common use cases

  • Telling a client a deadline is slipping
  • Pushing back on your manager's scope creep
  • Declining an invitation or speaking gig without burning the bridge
  • Asking a vendor for a refund or credit after a screw-up
  • Setting a boundary with a coworker who keeps pinging you after hours
  • Delivering bad news to a direct report (missed promotion, feedback)
  • Following up on an invoice that's 45+ days overdue

Best AI model for this

Claude Sonnet 4.5 or GPT-5. Claude has a slight edge on tone calibration and catching passive-aggressive phrasing; GPT-5 is slightly faster if you're drafting several in a row.

Pro tips

  • Be honest about the power dynamic. 'My boss's boss' produces a very different draft than 'a peer I outrank' — don't soften the truth here.
  • Paste your ACTUAL draft if you have one, even if it's bad. The tool's best value is diagnosing what you wrote, not generating from scratch.
  • If stakes are genuinely high (job on the line, legal exposure), say so. The tool will refuse to recommend the 'direct' variant in those cases.
  • Don't skip the 'what you're afraid will happen' field. That fear is usually what's producing the hedge-words — naming it gets them out.
  • Run it twice if the first output feels too corporate. Add context like 'we've worked together 4 years, texting-level friendly' in round two.

Customization tips

  • If the email is to someone senior (skip-level manager, board member, major client COO), add 'I've never spoken to them directly' to the recipient field — it changes the tone calibration significantly.
  • For bad-news emails specifically, always paste your current draft even if you hate it. The diagnostic on leak-phrases is where 60%+ of the value lives.
  • If you want to practice before sending, ask a follow-up: 'Now write Marcus's angriest realistic reply, and draft my response to that.' It de-risks the scariest scenario.
  • For recurring situations (you send boundary emails often), save the 'phrase replacement' table from your first run as a personal cheat sheet. The leaks tend to repeat.
  • Don't use this for emails where the relationship is already broken (you're quitting, firing them, or going to legal). Those need a different frame — ask for the 'terminal email' variant instead.

Variants

Slack / DM mode

Shorter drafts, no subject line, adjusted for chat tone and read-receipt dynamics.

Reply-to-their-email mode

Paste their message and your draft reply — the tool critiques how well you're actually addressing what they said vs. dodging.

Post-send debrief

Paste the email you already sent plus their response. Diagnoses what worked, what didn't, and what to say next.

Frequently asked questions

How do I use the Difficult Email Drafter prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with Difficult Email Drafter?

Claude Sonnet 4.5 or GPT-5. Claude has a slight edge on tone calibration and catching passive-aggressive phrasing; GPT-5 is slightly faster if you're drafting several in a row.

Can I customize the Difficult Email Drafter prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Be honest about the power dynamic. 'My boss's boss' produces a very different draft than 'a peer I outrank' — don't soften the truth here.; Paste your ACTUAL draft if you have one, even if it's bad. The tool's best value is diagnosing what you wrote, not generating from scratch.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals