How to write to clients
Writing to clients is an exercise in controlled confidence. You need to sound like you know what you're doing — because you do — without crossing into territory that feels presumptuous, salesy, or dismissive of their expertise. The balance is tricky because the power dynamic in a client relationship is genuinely ambiguous: they pay you, which gives them authority, but they hired you for your expertise, which gives you authority too. Every message you write exists in that tension.
The single most common mistake in client communication is over-apologising. When a deliverable is a day late, one brief acknowledgement is enough: "Sending this a day later than planned — here's the updated draft." You don't need to explain why, unless the reason is relevant to them. Clients don't care that your other project ran over or that you had a dentist appointment. They care that the work is here now and that it's good. Excessive apology erodes confidence — it makes them wonder if they should be more worried than they are.
The second most common mistake is under-communicating. Silence makes clients nervous, and nervous clients micromanage. If a project is on track, say so. A weekly two-line update — "Phase two is on schedule, will have the first draft to you by Thursday" — costs you thirty seconds and saves both of you an anxious check-in call. The best client relationships are the ones where the client never feels the need to ask "how's it going?" because you've already told them.
Tone varies by relationship maturity. Early in a client relationship, err formal. Use their name, avoid slang, spell things out. As the relationship develops and you learn their communication style, you can mirror it. If they send casual one-line emails, you can too. If they write in full paragraphs with bullet points, match that structure. Mirroring isn't mimicry — it's a signal that you're paying attention to how they like to work.
When delivering bad news to a client — a delay, a cost overrun, a problem you've discovered — lead with the impact and your proposed solution, not with the problem itself. "The timeline for launch has shifted to March 15th. We found a data issue in testing that would have caused problems in production, and we've already fixed it. Here's the updated schedule." This is factual, takes responsibility, and demonstrates that you're on top of it. Compare that to: "Bad news — we found a bug and we're going to be late." Same information, completely different emotional response.
Pricing conversations deserve their own rules. Never apologise for your rates. State them clearly, connect them to value, and let the client respond. "The project fee is $12,000, which covers discovery, two rounds of design, and development through launch" is clean and confident. If they push back, ask what's driving the concern rather than immediately offering a discount. Sometimes the issue is budget, sometimes it's scope, and sometimes they just need to hear you explain the value one more time.
Follow-ups with clients should be specific and timeboxed. "Just checking in" is weak — it puts the burden on the client to figure out what you need. "Following up on the brand guidelines — do you have a preferred direction from the three options I sent on Tuesday?" is strong. It reminds them what's pending, references the specific deliverable, and makes it easy to respond.
Finally, know when to pick up the phone. If an email thread has gone back and forth three times without resolution, a five-minute call will sort it out faster than five more messages. Clients appreciate efficiency, and suggesting a call signals that you value their time as much as your own.