A client signs the contract on a Friday. By the following Friday, either there is shared access to four systems and a draft sprint plan, or there is silence and a calendar with one “intro call” on it. The first outcome leads to a renewal. The second leads to a churn conversation in month four.
We run the same kickoff for every engagement, regardless of service line. The structure below is what we hand to our pod leads on day zero. Steal it, adapt it, or use it to evaluate whether a vendor you are about to sign actually has a delivery muscle.
Days 1-3: Access and baseline
The first 72 hours are about removing every blocker before the work starts. If we are still asking for read access on day eight, the engagement is already behind.
- [ ] Signed MSA and SOW filed in the shared workspace; both sides have countersigned PDFs.
- [ ] Access provisioned to the four primary systems for this engagement (e.g., GA4, Search Console, ad accounts for marketing; Xero/QBO, bank feeds, payroll for accounting).
- [ ] A single shared Slack or Teams channel created with the client pod, our pod, and one named escalation contact on each side.
- [ ] Baseline snapshot exported and timestamped: traffic, MRR, AR aging, ticket volume — whatever the engagement is meant to move.
- [ ] Day-1 kickoff brief sent to the client (one page: pod members, working hours, response SLA, weekly cadence).
Days 4-7: Pod assembly and scope sign-off
By the end of week one, the client should know every person on their delivery pod by name and face, and they should have signed off on what is — and is not — in scope for sprint one.
- [ ] Pod intro deck delivered: each delivery team member named, with their primary function and one prior engagement they shipped.
- [ ] Scope-of-work sprint plan drafted: 12 weeks of milestones with explicit out-of-scope items listed.
- [ ] Working agreements documented: response times, change-request process, escalation path, holiday coverage.
- [ ] Tool stack confirmed in writing: project tracker (Asana, Linear, ClickUp), file store, dashboard tool.
- [ ] Sprint-one scope explicitly signed off by the client lead in writing (email or Slack thread, archived).
Days 8-11: First sprint plan and working dashboards
Week two is when the engagement stops feeling like onboarding and starts feeling like delivery. The signal that we have crossed that line: a dashboard the client opens on their own.
- [ ] Sprint-one tickets created, estimated, and assigned in the tracker with due dates.
- [ ] First dashboard live: read-only link sent to the client showing the metrics this engagement is accountable for.
- [ ] Weekly status template agreed and the first one sent (what shipped, what is in flight, what is blocked, decisions needed).
- [ ] Risk register opened with the top three risks and an owner against each.
- [ ] First piece of work shipped or in client review — even a small one. Momentum beats polish in week two.
Days 12-14: Kickoff session and first decisions live
The formal kickoff happens at the end of week two, not the start of week one. That ordering is deliberate — by the time we sit in that room, we have already learned enough to make the conversation substantive instead of theoretical.
- [ ] 90-minute kickoff workshop held with all stakeholders. Agenda covers vision, success metrics, sprint-one demo, and open decisions.
- [ ] First three “decisions needed” resolved in the room and documented in the decisions log.
- [ ] 90-day plan signed off: what success looks like at day 30, day 60, day 90.
- [ ] Standing meeting cadence confirmed (weekly status, biweekly review, monthly executive readout).
- [ ] Retro on the kickoff itself: what worked, what to change for the next 14 days. Notes filed and acted on.
Twenty items. Every one of them is binary — it is either done or it is not. The reason we have the checklist in this form is that “kickoff went well” is not auditable. “Item 14 was signed off on day 11” is.
The two failure modes we see in other vendors’ kickoffs are the same ones, in opposite directions. One is over-documenting: a 60-page onboarding deck that nobody reads while the work stalls. The other is under-documenting: a friendly intro call followed by three weeks of silence. The checklist exists to keep both off the table.
Now what? If you want the full reasoning behind why we built kickoff this way — including what we tried before and why it failed — read our deeper take on the 14-day kickoff playbook, or see what an actual engagement looked like in our healthcare practice case study.