The Awkward Email Library

The 10 emails every freelancer dreads

Most freelance work is enjoyable. The miserable part is roughly 10 specific emails that come up over and over: telling a client their request is out of scope, pushing a deadline, asking for a refund or accepting one, raising your rates, following up after silence, ending a relationship, asking for a testimonial, declining a project, sending bad news, and disagreeing with feedback on a deliverable.

These all share a common shape: emotional content (frustration, regret, guilt, fear of damage to the relationship) wrapped in a professional medium (email). The library above pre-writes them in three tones each. You fill in the names and specifics; you get a polished message in 30 seconds.

• Scope creep: when "just one more thing" turns into another week of unpaid work.
• Deadline push: the project is going to be late. Sooner is better than later.
• Refund: project fell apart. Clean wrap-up beats lingering resentment.
• Rate increase: annual price update. Standard practice, awkward to write.
• Following up after ghosting: silent client, polite check-in.
• Client breakup: professional ending without burning the bridge.
• Testimonial ask: good projects deserve a follow-up. Most people forget.
• Decline a project: wrong-fit project. Decline gracefully.
• Bad-news status update: a milestone slipped or something broke.
• Dispute on a deliverable: client doesn't like it. You disagree, professionally.

The three-tone framework

Every awkward email should be available in three tones because the right tone depends on context: who the client is, what's already been said, and how close to fire the relationship is.

Gentle: opens with appreciation or sympathy, frames the ask as a question, leaves obvious off-ramps. Use when the relationship is healthy and you want to preserve it. Default for first-time messages of any kind.

Standard: direct but warm. Says the thing without softening, but ends with collaboration language ('let me know' / 'happy to discuss'). Use for most situations — this is the professional default.

Firm: minimal pleasantries, no softening, clear consequences. Use only when gentle and standard already failed, OR when the situation is irreparable (client breakup, pulling out of a project). Firm without prior softer attempts reads as aggressive.

Bad use of firm: as your first message. Bad use of gentle: when the client has been disrespectful. Bad use of standard: when the message is genuinely emotional (firing a client, accepting a refund). Match tone to situation, escalate only when needed.

• Gentle: first contact, healthy relationship, you want to stay close. Always start here.
• Standard: most situations. Direct + warm. Default 80% of the time.
• Firm: after prior softer attempts failed, or relationship is already over.
• Wrong tone = relationship damage: firm-too-early reads as aggressive; gentle-too-late reads as desperate.

Why pre-written templates beat AI for these emails

AI-generated emails for sensitive scenarios fall into a few traps: they over-apologise (the model is trained on conflict-avoidance), they're too long (more text feels safer to a model), they hedge in ways that read as weakness, or they hallucinate specific commitments ("I'll have it by Tuesday" when you didn't say that).

Pre-written templates have none of these issues. They've been edited by hand for the specific tradeoffs in each scenario: how much apology is appropriate, how to frame the ask, what to leave out. Substitute your fields and the message is ready in 30 seconds — and it actually reads like a careful person wrote it, not a model.

We do still use AI for some things (the Invoice Reminder Email Generator is AI; the Cover Email on the Invoice Generator is AI). But for emails where the line between professional and damaging is thin, templates win.

• AI over-apologises: every AI-generated firm reminder reads as 10% softer than you actually feel.
• AI is too long: professional adults write 4-5 sentences. AI defaults to 8-12.
• AI hallucinates commitments: specific dates and promises you didn't make.
• Templates are predictable: you know exactly what the email says before you send it.
• Templates load instantly: no API wait, no rate limit, runs in your browser.

When to call instead of email

Some of these conversations are genuinely too important for email. The general rule: if the client could plausibly read your message and panic, escalate to a phone call. Specific examples: "I need to part ways with you" (use email to set up the call, not deliver the news); "we owe you a refund" if the amount is large (call first, email confirms in writing); "we missed the deadline by a week and you're going to be angry" (call first).

For everything else, email is fine and better — gives the client time to react privately, creates a written record, doesn't put either of you on the spot.

• Call first, email second: breakups, large refunds, major bad news, anything with significant financial impact.
• Email is fine: scope clarifications, rate increases, status updates, small requests.
• Use email to set up the call: don't deliver bad news cold over the phone — schedule it briefly first.
• Always follow up calls in writing: protects both of you. The email becomes the record.