Act as a crisp business-writing editor who hates inbox theater. The task is writing a short email that needs a reply from a busy stranger. Context: [who they are and why them, my single ask, shared context if any, deadline if real].
1. Subject line that names the point, not the topic.
2. First sentence proves this is for them specifically.
3. One ask, formatted so yes or no is easy.
4. Under 100 words total, PS used only for genuine value.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is writing an escalation email about a blocked issue. Context: [the issue and impact, what I have tried, who is cc'd and why, what decision I need].
1. Lead with the decision needed and by when.
2. State facts and attempts without blame adjectives.
3. Quantify the impact in cost, time or risk.
4. Offer the two options so the reader chooses, not investigates.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is writing an apology email for a professional mistake. Context: [what happened, who was affected and how, what I have done since, what changes now].
1. Name the mistake plainly in the first sentence.
2. Acknowledge the specific impact on them.
3. State the fix and the prevention, both dated.
4. No "if you were offended" hedging anywhere.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is writing a recurring project status email. Context: [project state, milestones hit or missed, blockers, decisions pending, audience].
1. Lead with overall state in one word plus one sentence.
2. Structure: done, next, blocked, decisions needed.
3. Make every blocker a named ask with an owner.
4. Keep it scannable in 20 seconds with bolded leads.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is declining or shrinking a meeting invitation. Context: [the meeting and organizer, why it may not need me, what I can offer instead, my relationship to the organizer].
1. Decline with a reason framed around value, not busyness.
2. Offer the async alternative: a note, a doc comment or a delegate.
3. Write the version for my boss and the version for a peer.
4. Include when I genuinely should attend instead.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is writing a follow-up to an unanswered email. Context: [the original email gist, how long ago, why it matters now, what happens if no reply].
1. Reference the original in one clause, not a re-paste.
2. Add one new piece of value or urgency that is real.
3. Make the ask smaller if the first one was big.
4. Set the internal limit: how many follow-ups before I stop.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is writing a handover email before time away. Context: [my open threads, who covers what, dates away, what counts as urgent].
1. List each open item with owner, state and next action.
2. Define the one channel and trigger for true emergencies.
3. Write the out-of-office reply that routes people correctly.
4. Send-ready in under 250 words.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is requesting honest feedback by email. Context: [who I am asking and why them, the project or period, what I will do with it].
1. Ask two specific questions instead of "any feedback".
2. Include one question that invites criticism safely.
3. State exactly how long it takes and why their view matters.
4. Promise and script the no-defensiveness follow-up.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is writing a double opt-in introduction. Context: [person A and why, person B and why, what each gains, who asked me].
1. Check consent wording I send to each side first.
2. Write the intro email with one line of context per person.
3. Make the suggested next step tiny and optional.
4. Keep my own role to one sentence then exit the thread.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is replying to an angry customer email. Context: [their complaint verbatim, what actually went wrong, what I can offer, policy limits].
1. Acknowledge the feeling and the fact in the first two lines.
2. Explain briefly without excusing.
3. State the concrete remedy and its timeline.
4. Give a named human and direct channel for the next step.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is writing post-meeting notes and action recap. Context: [attendees, decisions made, action items with owners, open questions].
1. Open with decisions, not discussion.
2. Every action has one owner and a date.
3. List parked topics so they do not resurface as new.
4. Under 200 words, sent same day.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is writing the email that opens a compensation conversation. Context: [my role and tenure, three concrete results with numbers, market signal if known, what I am asking for].
1. Request the meeting with the topic stated plainly.
2. Attach or preview three results with numbers.
3. Anchor the ask to scope and impact, not need.
4. Keep it short; the case is made live, the email earns the slot.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.