When a new engagement starts, the first two weeks decide how the next six months will feel. We run the same 14-day kickoff on every engagement, whether it covers one service line or all three. By day fifteen the client has a named team, a baseline report, a live dashboard, and a signed-off first sprint. This is the full schedule, the twenty-item checklist behind it, and what the client owns at the end.
Three conversations, three different jobs
People often mix up the calls in an onboarding, so here is the order:
- Before signing: a free 30-minute scoping call. We learn your goals, current setup, and constraints, and decide together whether we are a fit. This call leads to a written proposal.
- Day 1: a 90-minute discovery call. This is the first working session after the agreement is signed. It follows a set agenda (business model, what works today, problem areas, quarterly commitments, constraints) that we share 48 hours ahead so your side arrives prepared.
- Day 13: a 3-hour kickoff working session. The formal kickoff happens near the end, not the beginning, so the conversation is grounded in two weeks of real work instead of assumptions.
Why fourteen days, not seven and not thirty
Seven-day kickoffs treat onboarding as paperwork: access granted, meetings booked, no baseline and nothing tangible. Thirty-day kickoffs copy large consultancies and usually produce 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 team have made together, written down, and agreed.
Fourteen days is long enough for real discovery and short enough to keep 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 | Workspace set up, access granted |
| 12 | Dashboards live | Analyst | Live KPI dashboard, baseline locked |
| 13 | Kickoff working session (3 hr) | Everyone | Decision log, action register |
| 14 | Week-one sprint kickoff | Pod leads | Active sprint, standup cadence set |
Days 1 to 4: Discovery, access, and baseline
Day two is access provisioning, the most common failure point in any kickoff. A standard matrix lists the access each service line needs, credentials go into a shared vault rather than email, and one named person on the client side handles access requests.
The tooling audit documents every system in scope (accounting, marketing, website, CRM, analytics) with seat counts, renewal dates, and whether each tool is actually used. Unused subscriptions show up more often than most teams expect.
The baseline report covers ninety days of history (twelve months for accounting records) and fits on one page you could drop into a board deck. Every later result is measured against it.
Checklist for days 1–4:
- Signed agreements filed in the shared workspace
- Access provisioned to the primary systems for the engagement
- One communication channel set up, with named escalation contacts
- Baseline metrics exported and timestamped
- One-page kickoff brief sent: team members, working hours, response commitments, meeting cadence
Days 5 to 7: Pod assembly and ownership
By day five the engagement has a named team (we call it a pod) and a draft RACI matrix that shows who is responsible, accountable, consulted, and informed for each task. We keep one strict rule: one accountable owner per task, never shared accountability.
Day seven is an internal sync where the service-line leads surface dependencies between them. Marketing may need conversion tracking added to the website; bookkeeping may need to know which entity owns which bank account. Finding these on day seven stops them from stalling a sprint on day thirty.
Checklist for days 5–7:
- Pod introductions with names, roles, and relevant experience
- Working agreements documented: response times and escalation steps
- Tool stack confirmed in writing
- Cross-line dependencies logged with owners
- RACI signed off by the client
Days 8 to 10: First sprint scoping and sign-off
The first sprint starts on day fifteen and runs for two weeks. We deliberately load it with work that produces something visible, not only foundations. The day-nine review focuses on the deferred list: everything raised in discovery that is explicitly postponed, with the reason written down. Written sign-off lands on day ten. If it slips, it goes to the client's executive sponsor.
Checklist for days 8–10:
- Sprint-one tickets created, assigned, and dated
- A 12-week plan drafted, with out-of-scope items listed
- Deferred list agreed, with reasons
- Written client sign-off on sprint-one scope
- Risk register started with the top three risks
Days 11 to 14: Workspace, dashboards, and the working session
The workspace is set up once for the life of the engagement. Our defaults are Notion for documentation, Linear for sprint tracking, and Slack for communication, but we are just as happy to work inside the client's existing tools.
The dashboard has three layers: business KPIs, service-line metrics, and sprint output, all behind a single link.
Day thirteen is the three-hour working session (in person when possible) with the pod, the client's executive sponsor, and the service-line owners. It walks through the baseline report, the first sprint plan, and the decision log, and ends with an action register that has names and dates. On day fourteen the pod holds its first standup and the client gets a one-page summary.
Checklist for days 11–14:
- Read-only dashboard published
- First weekly written update sent
- Kickoff working session held, with decisions documented
- 90-day plan signed off, with milestones at days 30, 60, and 90
- Standing meeting cadence confirmed, and a short retrospective on the kickoff itself
Why every checklist item is yes or no
The checklist has twenty items and each has only two states: done or not done. That design prevents two failure modes: over-documentation that stalls the work, and under-documentation that leads to weeks of silence. "Item 14 was signed off on day 11" can be checked. "Kickoff went well" cannot.
What the client owns on day fifteen
- 1A discovery summary and decision log
- 2An access matrix and vaulted credentials
- 3A tooling inventory with gap recommendations
- 4A ninety-day baseline report
- 5A named pod with a RACI and escalation path
- 6A signed-off first sprint plan
- 7A live KPI dashboard
- 8A scheduled weekly standup and written update cadence
Where it has paid off
On a vendor consolidation engagement, the client had not been able to produce a unified spending report across their four vendors in two years. Day fourteen of the kickoff delivered the first one. The full story is in our case study "Mid-market firm consolidated 4 vendors into one operating partner".
If you are evaluating an outsourcing partner, ask them for their day-by-day kickoff plan. A vague answer tells you what the first month will feel like.
Frequently asked questions
How long does client onboarding take?
Ours takes fourteen days from signed agreement to the first active sprint. Work starts on day one: discovery, access, and baseline metrics come before the formal kickoff session.
What should be on a client onboarding checklist?
Access and credentials, a baseline report, named owners for every task, a signed-off first sprint, a live dashboard, and a fixed update cadence. Each item should be a clear yes or no.
Is the kickoff different when we use more than one service line?
The schedule is the same. With more than one line, day seven matters more, because that is when the leads surface the dependencies between marketing, web, and finance.
See it in practice · FinTech
FinTech KYC review cut from 5 days to 4 hours
Curious how your own site scores?
Run our free website audit. Simple report, about 10 seconds, no sign-up.



