The quality of your work doesn't set the tone of a new engagement — the first email does. Clients form an opinion about how organized you are before you've delivered anything, based entirely on whether the logistics feel handled or improvised. Three emails cover the first week: a welcome note, a kickoff-call confirmation, and a first-week check-in. Here's the full text of each, adapt the bracketed parts and send.
1. The welcome and logistics email
Send this within a few hours of the contract being signed, not the next morning. It does three things: confirms the engagement is officially starting, sets expectations for what happens next, and requests the access you'll need before the kickoff call so that call isn't spent waiting on IT tickets.
Subject: Welcome aboard — next steps for [Project Name]
Hi [Client First Name],
Excited to get started. Here's what happens between now and our kickoff call:
1. I'll send a calendar invite for kickoff within the next day — let me know if [proposed date] doesn't work.
2. To make that call as useful as possible, could you set up access to the following before then?
- [Shared drive / project folder]
- [Slack or Teams channel]
- [Analytics or platform access, if relevant]
3. If there's anyone else on your team who should be looped in before we start, send their name and I'll add them to the invite.
Looking forward to it.
[Your Name]
2. The kickoff-call confirmation with agenda preview
Send this one to two days before the call, once it's on the calendar. An agenda sent ahead of time does two things a bare calendar invite doesn't: it lets the client flag anything missing before you're live on the call, and it signals that the call has a purpose beyond introductions.
Subject: Kickoff call Thursday at 2pm — quick agenda
Hi [Client First Name],
Confirming our kickoff call for [Day, Date] at [Time]. Planning to cover:
1. Quick round of introductions and roles
2. Confirming scope and timeline out loud, against what's in the agreement
3. How we'll communicate — preferred channel, expected response times, backup contact
4. Setting the date for our first check-in
Should take about 30 minutes. Let me know if there's anything you'd like to add before then.
See you Thursday,
[Your Name]
3. The first-week check-in
Send this three to five business days after kickoff, before the client has to reach out first. The goal isn't to report progress — a week in, there usually isn't much to report yet. It's to confirm nothing is stuck: access that hasn't come through, a stakeholder who hasn't responded, an assumption from the kickoff call that turned out to be wrong. Catching one of those in week one is a two-line email. Catching it in week three is a scope conversation.
Subject: Quick check-in — one week in
Hi [Client First Name],
One week in — wanted to check a few things before we get further into the work:
1. Access to [item] is still pending on my end — could you follow up with [name] if that's an easy nudge?
2. I'm planning to have [first deliverable or milestone] ready by [date] — flagging now in case that timeline needs to shift on your end.
3. Anything from the kickoff call you'd like to revisit or clarify now that the team's had a week to sit with it?
No need for a call unless something above needs one — happy to keep this async.
Thanks,
[Your Name]
All three take under five minutes to send and each one closes a specific gap — access, expectations, drift — before it turns into a bigger problem later in the engagement. If the proposal that led to this engagement wasn't this specific about scope and deliverables in the first place, the free Consulting Proposal Generator is worth using on the next one, so the kickoff-call agenda has something concrete to confirm against.