DEV Community

ClawGear
ClawGear

Posted on

Stop Writing the Same Email Twice

Most professionals spend 30–90 minutes every day writing things they've already written before.

A polite email declining a meeting. A weekly status update. A follow-up to a client after a call. These are tasks that happen constantly — and yet most people approach them from scratch every single time.

There's a better way.

The Problem: Repetitive Writing Eats Your Day

Think about last week. How many emails did you write that were essentially variations of something you'd written before?

  • "Thanks for the call — here's what we discussed"
  • "Just following up on my previous email"
  • "I won't be able to make that meeting, but here's what I'd like to cover"

None of these are creative writing challenges. They're communication mechanics. The information changes, but the structure stays the same.

Across a typical 5-day work week, knowledge workers send between 40 and 60 emails. A significant portion of them follow predictable patterns. When you write each one from scratch, you're spending cognitive energy on the structure rather than the substance.

The fix isn't to become a faster writer. It's to stop making writing decisions you've already made.

The 3-Step Prompt Framework That Changes Everything

Here's a simple framework that takes repetitive emails from a blank page to a ready-to-send draft in under 3 minutes.

The framework has three components: Context → Tone → Constraints.

Context: What's the situation? Give the relevant background in 2–3 sentences. Don't try to be comprehensive — just give enough that the output is accurate.

Tone: How should this sound? Professional and warm? Direct and brief? Formal? Naming the tone explicitly produces dramatically better results than leaving it open.

Constraints: What should the output avoid? Common ones: no jargon, under 150 words, no passive voice, don't make promises about timelines.

That's it. Three parts. The more specific you are in each, the better the output.

Three Examples You Can Use Today

Example 1: Declining a Meeting Politely

Without this framework, most people write these emails three times — too brief, too long, too cold — before landing on something that feels right. Here's the prompt:

Context: I've been invited to a weekly sync that isn't relevant to my current project. I want to decline and suggest an async alternative.
Tone: Warm and professional, not dismissive.
Constraints: Under 80 words. Don't imply I'm busy (everyone's busy). Don't leave it open-ended — suggest a specific alternative.

Result: A polished decline email in about 45 seconds.

Example 2: Weekly Status Update to Your Manager

These are chronically bad because people either write too much (a laundry list of activities) or too little (one vague sentence). Here's the fix:

Context: This week I completed [X], started [Y], and am blocked on [Z] pending input from the design team.
Tone: Confident and concise. My manager is busy.
Constraints: Three sections: Done / In Progress / Needs Input. Maximum 120 words total. No passive voice.

The prompt enforces the structure you want rather than letting you invent it each time.

Example 3: Client Follow-Up After a Call

The mistake most people make here: they summarize the entire call. No one wants that. They want the three things that matter.

Context: I just had a 45-minute call with a potential client. The key outcomes were: they need a proposal by end of next week, their main concern is onboarding time, and I promised to send two case studies.
Tone: Warm and professional. I want to keep momentum.
Constraints: Three sections: Quick summary (2 sentences), What I'm sending now, Next step with a specific date. Under 150 words.

What usually takes 15 minutes takes 2.

How to Build Your Own Prompt Library

The real leverage comes when you stop thinking about individual prompts and start building a reusable system.

The simplest version: a Google Doc with one page per scenario. Name each entry by what it produces: "Meeting decline — warm," "Status update — brief," "Client follow-up — post-call."

Every time you write a prompt that works well, paste it in. Every time you get a result you like, save the actual output as an example. Over 2–3 weeks, you'll have a working library of 15–20 prompts that covers 80% of your regular communication.

The payoff: you stop making writing decisions from scratch. You reference a proven prompt, fill in the specifics, and get a draft that's 90% ready.

Time investment to set up: 20 minutes.
Time saved per week: 3–5 hours, depending on your email volume.

What This Isn't

This isn't about generating form letters or sending emails that feel automated. Good prompting produces drafts — you still review, edit, and add the judgment that only you can bring.

The goal is to stop spending your cognitive energy on the mechanics of writing and spend it on the substance: what actually needs to be said, what decision needs to be made, what relationship is at stake.

The structure is the easy part. Let a prompt handle it.

Start Here

If you want a ready-made starting point, grab our free ChatGPT Starter Kit — 10 prompts for professionals, no email required. It includes the frameworks above plus versions for common scenarios in project management, client communication, and internal coordination.

Free download: https://pinzasrojas.gumroad.com/l/mixiz

No fluff. Just prompts you can open and use today.

Top comments (0)