DEV Community

Lisa Sakura
Lisa Sakura

Posted on • Originally published at agencyonboardingos.com

The 7 Client Emails Every Agency Needs Written Before a Project Starts

The agency that has these 7 emails written before a project starts just pastes, adjusts two lines, and sends. The one that doesn't scrambles to find the right words in the middle of a stressful moment — and usually says something defensive, apologetic, or accidentally binding.

Most agency problems aren't scope problems. They're communication timing problems: the delay notice that came too late, the scope change that got handled verbally instead of in writing, the project completion email that never got sent so the client didn't know they had to stop sending feedback.

Here are the 7 emails to have ready before day one.

Here are the 7 emails every agency should have ready on day one.


1. The weekly status update

Send every Friday, even when there's nothing dramatic to report. Clients who hear nothing assume things are going wrong.

Template structure:

  • What got done this week (3 bullets max)
  • What's happening next week
  • Any open items you're waiting on from them
  • Any risks on the horizon

Keep it under 150 words. The goal is reassurance, not a report. Clients who feel informed don't send "just checking in" emails.

Example:

Subject: [Project Name] — Week 2 update

Hi [Name],

Quick update from this week:
— Completed homepage wireframes (3 variations, sent to your Dropbox)
— Locked in the nav structure based on your feedback Tuesday
— Started on the about page

Next week: mobile designs + a first pass at the contact page.

Still waiting on: the team photo and bio copy for the about section. Can you get that across by Thursday?

On track. Talk soon,
[Your name]


2. The scope change request

Before you do any work that isn't in the contract, send this. Not after. Not verbally. In writing, before.

Template structure:

  • What was requested (one line, their words)
  • What's in scope vs. what this is
  • The impact: time, cost, or both
  • What you need from them to proceed

This email protects you legally but more importantly it protects the relationship. Most clients don't realise they're asking for something out of scope — this email surfaces it without making them feel accused.


3. The delay notice

Send this the moment you know a deadline is at risk — not when it's already missed. Early communication on delays is one of the highest-trust signals a client ever sees from an agency.

Template structure:

  • What's delayed and why (brief, no over-explaining)
  • The revised timeline
  • What you're doing about it
  • What, if anything, you need from them

Do not bury the lede. Say "we expect a 3-day delay" in the first sentence.


4. The waiting-on-client unblocking email

When you're blocked because a client hasn't sent assets, reviewed copy, or approved a milestone — send this. This email is not passive. It names the blocker, the deadline it creates, and what happens if it slips.

Template structure:

  • What you're waiting on (exact item)
  • When you need it to stay on schedule
  • What will be affected if it's late
  • One clear ask with a specific date

"Waiting on feedback" is not a status update. This email converts a vague delay into a written, dateable moment you can refer back to.


5. The project completion / handoff email

When a project ends, mark it explicitly. Clients who don't receive a clear close signal keep sending feedback and changes indefinitely. The handoff email draws the line.

Template structure:

  • Confirm what was delivered (list each item)
  • Any handoff instructions (login details, access, documentation)
  • The support window if you offer one
  • The feedback / sign-off ask

This email also sets up the testimonial ask. You can follow up 48 hours after sign-off with a short "would you be willing to share a sentence or two about working with us?"


6. The re-engagement email (send 90 days after project close)

Most agencies lose repeat business not because clients didn't want more — but because nobody followed up. A simple 90-day check-in recovers more revenue than any cold outreach campaign.

Template structure:

  • Brief personalised opener (reference the project)
  • How things are going / what's changed for them since
  • One low-pressure offer or question
  • No hard sell

Write it to feel like a genuine check-in, not a sales email. Because it is.


7. The difficult conversation email

For when something goes wrong and you need to address it in writing before it becomes a relationship problem. Missed expectations, payment delays, repeated scope violations.

Template structure:

  • Name the issue directly (first sentence)
  • Impact on the project or relationship
  • What you need from them
  • What happens next

The instinct is to soften difficult conversation emails until they're unreadable. Resist it. A clear, calm, firm email is more respectful than a vague one that makes the reader guess what you actually mean.


Why writing these before you need them matters

When you're in the middle of a delay or a scope dispute, you don't have the headspace to write a good email. You write something defensive, or something apologetic, or something that accidentally commits you to things you don't mean.

Having these written and ready flips that. The email sends faster, sounds more professional, and doesn't carry the emotional charge of the moment.

The full set of copy-paste templates — including subject lines and adaptable copy for each situation — is at Agency Onboarding OS. Free, no sign-up.

Top comments (0)