When a client engages us across multiple service lines at once, the kickoff is where the engagement is won or lost. This is the day-by-day structure we used to onboard a client across three service lines — a client who had previously juggled four vendors — delivering a unified workspace, named teams, baseline reporting, and an approved sprint plan by day fourteen.
Why fourteen days, not seven and not thirty
Seven-day kickoffs treat onboarding as purely administrative: access granted, meetings booked, no baseline metrics, no tangible output. Thirty-day kickoffs mimic large consultancies and usually deliver a deck that arrives too late to matter.
The deliverable of a kickoff is not a deck. It is a set of decisions the client and the pod have made together, written down, and agreed.
Fourteen days is enough for real discovery while keeping momentum toward the first visible sprint.
The 14-day schedule
| Day | Phase | Owner | Artifact |
|---|---|---|---|
| 1 | Discovery call (90 min) | Engagement Lead | Discovery notes, open questions |
| 2 | Access provisioning | Ops + Client | Access matrix, credentials vaulted |
| 3 | Tooling audit | Pod Leads | Tooling inventory, gap list |
| 4 | Baseline metrics pull | Analyst | Baseline report (last 90 days) |
| 5 | Pod assembly | Engagement Lead | Pod roster, RACI v1 |
| 6 | Roles and ownership review | Pod Leads | RACI v2, escalation path |
| 7 | Internal pod sync | Engagement Lead | Cross-line dependencies logged |
| 8 | First sprint scoping | Pod Leads | Sprint backlog draft |
| 9 | Brief review with client | Engagement Lead | Sprint backlog v2 |
| 10 | Brief sign-off | Client | Approved sprint plan |
| 11 | Workspace provisioning | Ops | Notion/Linear set up, access granted |
| 12 | Dashboards live | Analyst | Live KPI dashboard, baseline locked |
| 13 | Kickoff working session (3 hr) | All | Decision log, action register |
| 14 | Week 1 sprint kickoff | Pod Leads | Active sprint, standup cadence set |
Days 1 to 2: Discovery and access
The ninety-minute discovery call follows a structured agenda — business model, operational strengths, problem areas, quarterly commitments, constraints — shared forty-eight hours in advance so the client side arrives prepared.
Day two is access provisioning, the single most common failure point in any kickoff. A standardized matrix specifies required access per service line, credentials go into a shared vault rather than email, and a named client-side owner handles access requests.
Days 3 to 4: Baseline metrics and tooling audit
The tooling audit documents every system in scope — accounting stack, marketing stack, website infrastructure, CRM, analytics, data warehouse — with version numbers, seat counts, renewal dates, and whether it is actually used. Roughly thirty percent of the tools we inventory turn out to be unused.
The baseline report covers ninety days of history (twelve months for accounting records) and compresses to a single page suitable for a board deck. It becomes the benchmark every later result is measured against.
Days 5 to 7: Pod assembly and ownership
By day five, the engagement has a named pod and a drafted RACI matrix. We enforce strict RACI discipline: one accountable owner per task, no shared accountability.
Day seven is an internal sync where service line leads surface cross-functional dependencies — marketing needs conversion tracking exposed on the website, bookkeeping needs clarity on which entity owns which bank account. Finding these on day seven prevents them from stalling sprints on day thirty.
Days 8 to 10: First sprint scoping and sign-off
The first sprint launches on day fifteen and runs two weeks, deliberately loaded with work that produces visible deliverables — not just foundations. Day nine's review emphasizes the deferred list: everything mentioned in discovery that is explicitly postponed, with the reason documented. Written sign-off lands on day ten, timestamped in the shared workspace. If sign-off slips, it escalates to the client's executive sponsor.
Days 11 to 12: Workspace and dashboards
The workspace is built once, for the life of the engagement. Our defaults are Notion for documentation, Linear for sprint tracking, and Slack for communication — with flexibility to work inside the client's existing systems instead.
The dashboard has three layers: business-level KPIs, service-line metrics, and sprint-level outputs. The client reaches all three through a single URL.
Days 13 to 14: The kickoff working session
Day thirteen is a three-hour working session — in person when possible — with the pod, the client's executive sponsor, and service line owners. It walks the baseline report, the first sprint plan, and the decision log, and builds an action register with names and dates. Day fourteen: the pod's first internal standup, cadence set, and a one-page summary delivered to the client.
What the client owns on day fifteen
- 1A discovery summary and decisions log from kickoff
- 2An access matrix and vaulted credentials
- 3A tooling inventory with gap recommendations
- 4A ninety-day baseline report
- 5A named pod with RACI and escalation path
- 6A signed-off first sprint plan
- 7A live KPI dashboard
- 8A scheduled weekly standup cadence
When it has been worth it
On a recent vendor consolidation engagement, the client had not been able to produce a unified spending report across their vendors in two years. Day fourteen of the kickoff delivered the first one — a single document. If you are evaluating a multi-line provider, ask them for their day-by-day kickoff structure. A vague answer tells you what the first month will feel like.