Verified against Claude · 2026-07-30
Send a kickoff email that sets expectations before the first status fight
Open a new client engagement with one email that states scope, timeline, communication cadence, and who's responsible for what — so nobody has to guess three weeks in.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are writing the kickoff email that starts a new client project — the first written record either side can point back to if expectations drift later. Context: - Project: Meridian booking site rebuild - Client: Alex - Timeline: 8 weeks, kickoff Aug 10, launch Oct 5 - Deliverables: new booking site, mobile checkout, 3 months hosting - Communication cadence: Friday afternoon email update, live call every other Monday - Point of contact: Sam (project lead), sam@northline.studio Task: Write a kickoff email that: 1. Opens with one brief line of genuine enthusiasm — not three paragraphs of it. 2. Recaps scope and deliverables in a short list, so both sides start from the same written understanding. 3. States the timeline with milestones, not just a total duration. 4. States the communication cadence explicitly — how often, which channel, who sends it — as a commitment, not a suggestion. 5. Lists exactly what you need from the client and by when (approvals, access, content) so blockers surface now, not mid-project. 6. Names the point of contact and how to reach them for anything urgent. Format: email, under 250 words, plain paragraphs and one short list, no corporate filler like "synergy" or "circle back."
Customize the highlighted detailsoptional — the prompt above already works
Why this works
Most client friction mid-project isn't caused by bad work — it's caused by a pace or communication expectation that was never actually agreed on, just assumed differently by each side. Writing the cadence down ("Friday email, call every other Monday") turns a vague hope into a commitment both people can point back to when a week goes quiet. Listing what you need from the client, and by when, does the same job in the other direction — it converts "we're waiting on them" from a surprise three weeks in into something both sides already agreed to watch for.
What you get back
Subject: Kicking off — Meridian booking site rebuild Excited to get started on this. Scope recap: new booking site, mobile checkout, 3 months hosting. Timeline: 6 weeks — design wks 1–2, build wks 3–5, launch wk 6 (Oct 5). You'll get a written update every Friday, plus a 20-minute call every other Monday. What we need from you by Aug 12: brand assets/logo files, and access to your current hosting account. Any urgent questions, reach Sam directly at sam@northline.studio. Looking forward to it.
Verified against
Claude Sonnet 5 · 2026-07-30
Gemini 3 Pro · 2026-06-08
Changelog
- 2026-07-30 — Re-verified, no changes.
- 2026-06-08 — Added the explicit "what we need from you, by when" step after kickoffs kept skipping it.
Need this built into your business?
If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.
EXPLORE CUSTOM SOFTWARE
