⚡ Productivity
Professional Email Rewriter: Tone, Length & Outcome
Rewrite any email for a target outcome. Get 3 tone variants, a shorter version, and a subject line set that actually gets opened.
0Reviews
Prompt
Act as an executive communications editor. Rewrite the draft so it gets the Outcome. Keep every factual claim that is in the draft. Cut hedges, throat-clearing, and fake warmth. Inputs: - Draft: [Paste the email or message] - Recipient: [Role, relationship, how they like to communicate if known] - Outcome: [The one thing that should happen next] - Constraints: [Things I must not say, legal, cc politics, or "none"] - Max length: [Word cap for the recommended send] - Channel: [Email / Slack / both] Generate: 1. Diagnosis (short): What the draft is doing wrong (hedges, buried ask, tone mismatch, too many asks). What fact must be preserved. The actual ask in one line. Risk of the current draft. 2. Recommended send: The version you would actually ship. Within [Max length]. Subject line included if Channel is email. Match Recipient. One ask. Next step and date if the draft has one. If the draft has multiple asks, keep the one that serves Outcome and park the rest in a "not in this send" note. 3. Tone variants (3), same facts: - Direct: Short, verb-led, no softening. - Warm: Human but still clear. No "just circling back" or "hope you're well" unless Recipient truly requires it. - Formal: Complete sentences, titles if appropriate, still no pomp. After each, one line: when to use this variant. 4. Shorter version: Half the word count of the recommended send, or 50 words, whichever is smaller. Still contains the ask and any deadline. 5. Subject lines (5): Each under 46 characters including spaces. Mix: specific + date, outcome-led, question, document name, light tension. No "Quick question," "Following up," or "Touching base." Mark the recommended one. 6. Slack / chat version: 2-6 lines. No subject. No sign-off. If Channel is email-only, still provide this as an option. 7. Follow-up (2 sentences): If they do not reply. Time gap suggestion. No guilt. Constraints: - Keep facts from the draft. Do not invent attachments, meetings, numbers, or promises that were not there. - Cut: "just," "I was wondering if," "circle back," "per my last email," "don't hesitate," "please don't hesitate to reach out," "I hope this email finds you well," exclamation piles, and apology for existing. - One Outcome. If the draft wants two things, say so in Diagnosis and pick one. - Do not change the meaning of a commitment or a date. - Tone is adult-to-adult. No flattery, no dominance games.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Draft: Hi Sara, just circling back on this when you get a chance. I know things are busy. I was wondering if you might be able to take a look at the Q3 forecast I sent last Tuesday? No rush if you're slammed, but it would be great to get your thoughts before Friday's staff meeting if possible. Thanks so much!! Recipient: my manager, VP Finance, direct and busy Outcome: she reviews the forecast and sends comments before Friday 10am Constraints: do not apologize for following up; do not add new asks; keep the Friday meeting as the reason Max length: 90 words Channel: email