Project Kickoff Email to a New Client: 10 Templates

The kickoff email is the first thing a client reads after they've paid you or signed the contract, and it sets the tone for every email after it. Get it right and disputes later ('that wasn't in scope', 'who approves this?') have a paper trail to point back to. Get it wrong — vague, late, or missing a name for who signs off — and you're re-litigating scope in week three.

Below are ten templates you can copy, edit the bracketed fields, and send: the full kickoff agenda, the roles-and-owners note, the access request, the communication-rules note, the milestone summary, the recap, and four variants for trickier situations. Each one exists because a specific gap in the standard kickoff caused a specific problem downstream.

When to send this#

Send the kickoff email within 24 hours of the contract or purchase order being signed — before the first call, not after it. If the kickoff call happens first and the email comes a few days later as a 'recap', you've already had a verbal conversation where scope, dates and expectations could drift without anyone writing them down.

Send it even if you also plan to have a live kickoff call. The email is the artifact; the call is the conversation. If the client's internal team changes six weeks in, the new person reads the email, not a transcript of the call.

• Right after the contract or deposit is signed, before any work begins
• Before, not after, the first working session or kickoff call
• As a written record, even when you also do a live kickoff meeting

What a good one contains#

The Project Management Institute's guidance on kickoff meetings centers on the same handful of elements regardless of methodology: confirmed scope, named roles, a shared timeline, and an agreed communication cadence. An email version needs the same four things, written down instead of said out loud.

PlainLanguage.gov's federal guidelines are worth borrowing from here too — write to the person who will act on the email, not the file. One sentence per instruction, the ask stated before the justification, and no paragraph that could be a bullet list instead.

The templates#

Ten templates below. Use the first for a standard kickoff, and pull the others as the situation calls for them — most projects will use three or four of these across the first two weeks, not all ten at once.

1. The full kickoff email#

This is the one to send first. It covers scope, roles, dates and access in one message, so the client has everything in one place before the first call.

2. The roles-and-owners note#

Use this when more than one person on the client side will be involved, and you need one name for who actually approves things.

3. The access-and-assets request#

The single most time-wasting gap in a kickoff is asking for access piecemeal instead of all at once. Ask for everything on day one.

4. The communication-rules note#

Send this separately when the full kickoff email would be too long, or when a client's team is large enough that channel sprawl is a real risk.

5. The milestone summary#

Send this once dates are confirmed, as a standalone reference the client can forward internally without the rest of the kickoff context.

6. The kickoff recap#

Send this after a live kickoff call, within a few hours, while the room's memory of what was agreed is still fresh.

The hard version of this situation#

The trickiest kickoff isn't the one with a difficult client — it's the one where the person you're emailing hasn't actually gotten sign-off from whoever controls the budget. This shows up as vague answers to direct questions, a decision maker who keeps saying 'let me check', or scope that shifts between the sales call and the kickoff call.

The kickoff email is the right place to surface this, because it forces a written answer before you've spent a week of billable time on a project that might get re-scoped or cancelled once the actual sponsor sees it.

What to do if there's no reply#

A kickoff email that goes unanswered for more than your stated SLA is a signal, not just an inconvenience — something changed on their end, or the project wasn't as prioritized as it seemed at signing.

1. 1

   Wait one full SLA period

   If you promised [RESPONSE SLA], hold yourself to it before following up — chasing early reads as anxious, not diligent.

2. 2

   Send a short, specific follow-up

   Reference the exact open item: "Following up on the access list from [DATE] — we're ready to start as soon as we have it." Not a general check-in.

3. 3

   Set a real deadline on the second follow-up

   "If we don't have access by [DATE], we'll need to push the [MILESTONE] deadline by the same number of days." Make the cost of silence concrete.

4. 4

   Escalate to a second contact if one exists

   If the kickoff contact goes fully dark, a polite note to whoever signed the contract is reasonable — that's what the signature is for.

Where AI Emaily fits#

Most of the friction in a kickoff isn't writing the first email — it's tracking whether the client actually replied to the access request, whether the decision maker confirmed, and whether the milestone follow-up got sent on time. AI Emaily's agent can draft the kickoff variant you need from a short instruction, using a Personal Context brain and per-client profiles you set yourself — not by reading your past sent mail — and it can flag threads that have gone past your stated response SLA so a follow-up doesn't slip. We build AI Emaily; it's a 7-day free trial on the Pro plan, card required, $0 if you cancel before day seven.