The Sales Execution Gap

Client Onboarding Template: Copy It, Then Run It

A complete, copy-pasteable client onboarding template with phases, owners, kickoff-relative due dates, and exit criteria, filled in for a real services engagement, plus how to adapt it by deal size, migration vs net-new, and team count.

A client onboarding template is a reusable plan for bringing a new client live: the phases, steps, owners, due dates set relative to kickoff, and exit criteria a team copies onto each new account so the first 90 days run the same way every time.

You searched for a client onboarding template because you want the structure without rebuilding it. Fair. Below is a complete one, filled in for an agency engagement, with a kickoff agenda and a 30/60/90 review block attached. A client onboarding template is a reusable plan for bringing a new client live: the phases, steps, owners, due dates set relative to kickoff, and exit criteria a team copies onto each new account so the first 90 days run the same way every time.

Take it. Then stay for the argument around it, because a template is the floor of good onboarding, and the floor is the part most teams already have. In our State of Sales Enablement survey of 198 leaders, 89 percent had a defined process and 36 percent saw their teams follow it. Structure was never the missing piece. The run is.

What should a client onboarding template include?

Six fields per row: the phase the step belongs to, the step itself (one action, one verb), one named owner, a due date written relative to kickoff, an exit criterion, and a client-visible flag.

Two of the six do most of the work. Kickoff-relative dates make the plan reusable: a template with calendar dates dies the day after you write it, while one dated K-5 to K+60 (five days before kickoff to sixty after) pastes cleanly onto any account. And exit criteria make a step true. A checked box records that somebody said the work happened. An exit criterion names an observable state: not “kickoff done” but “success metrics agreed in writing, and the client named one decision-maker.”

Anatomy of one client onboarding template row: phase, step, one named owner, a due date relative to kickoff (K+7 means seven days after the kickoff call), an exit criterion naming the verifiable state that makes the step true, and a client-visible flag.
One row, six fields. One named owner, a K-date so the template survives copying, and the exit criterion that makes the step true.

A building inspector already works on this principle. He does not ask the electrician whether the wiring is finished; he opens the panel and looks. Atul Gawande’s surgical checklist ran the same way: its 19 items named verifiable states (antibiotics given, instruments counted), and in-hospital deaths across eight hospitals fell from 1.5 percent to 0.8 percent, a 47 percent drop (Haynes et al., New England Journal of Medicine, 2009). The checklist added no skill to the room. It made “done” checkable.

Why a client onboarding template needs exit criteria: a checked box records the builder's word that the wiring is done, while an exit criterion is the inspector opening the panel and verifying the state; checklists built on verifiable states cut in-hospital deaths from 1.5 percent to 0.8 percent (Haynes et al., NEJM 2009).
The builder’s word versus the open panel. Verifiable states cut surgical deaths from 1.5% to 0.8%; the same field turns your onboarding plan template from a claim into a standard.

The client-visible column earns its place too. Onboarding is the first product the client experiences, and marking which rows they see forces a decision, per step, about the experience you are producing. It also leaves you a shareable plan with no last-minute redacting.

The client onboarding template (copy this)

The example values below are for a marketing agency bringing a retainer client live: paid media plus a site refresh. Swap the deliverables for yours and keep the fields. K0 is the kickoff call.

Phase 1: pre-kickoff (K-5 to K0)

StepOwnerDueExit criteriaClient-visible
Sales-to-delivery handoffAccount directorK-5Delivery team can state the client’s goal, scope, and both promises made during the sale without opening the contractNo
Access requests sent (ad accounts, analytics, CMS, brand assets)Project managerK-4Request list sent and acknowledged by the client contactYes
Kickoff agenda and welcome packet sentAccount directorK-2Client confirms attendees and agendaYes

Phase 2: kickoff and requirements (K0 to K+10)

StepOwnerDueExit criteriaClient-visible
Kickoff call run to the standing agendaAccount directorK0Success metrics agreed in writing; client names one decision-makerYes
Access verifiedProject managerK+3Team logs in to each system on the access listNo
Requirements doc reviewed and signed offProject managerK+7Client signs off in writing; open questions logged with ownersYes
Internal build plan lockedDelivery leadK+10Tasks scheduled with owners through launchNo

Phase 3: implementation (K+10 to K+45)

StepOwnerDueExit criteriaClient-visible
Weekly status cadence runningProject managerK+14Two consecutive status notes sent on scheduleYes
First deliverable shipped (audit plus roadmap)Delivery leadK+20Client reviewed it on a call; feedback captured in writingYes
Campaigns and site build complete in stagingDelivery leadK+38Client walkthrough done; punch list agreedYes
QA against the launch checklistProject managerK+42Zero open blockers on the punch listNo

Phase 4: launch and handoff (K+45 to K+60)

StepOwnerDueExit criteriaClient-visible
Go-liveDelivery leadK+45Work live in production; client confirms in writingYes
Handoff to the ongoing account teamAccount directorK+50Ongoing owner introduced to the client; first monthly review bookedYes
First results readoutAccount directorK+60Client sees the metric agreed at kickoff, with a number against itYes

The kickoff agenda (60 minutes, attach it to the K0 row)

SegmentTimeExit criteria
Introductions and roles5 minClient knows who owns what on your side
Goals and success metrics15 minTwo or three metrics agreed and written down
Scope walkthrough and what we need from you15 minClient dependencies listed with dates
Ways of working (cadence, channel, who to call)10 minOne communication channel and one escalation contact agreed
Timeline to first value10 minClient can say what they will see by K+20
Next steps and owners5 minEach open item leaves the call with a name on it

The 30/60/90 review block

ReviewWhat you inspectExit criteria
Day 30Plan vs actual against the K-dates; any step past due and whyDrifting steps re-dated or escalated; client asked how the start feels
Day 60First deliverable’s outcome vs the kickoff metric; scope changesChanges logged and re-scoped in writing, or explicitly declined
Day 90Results vs the success metric; which template steps got skippedRenewal or expansion conversation opened; template updated with what the run taught you

That last cell is the template maintaining itself: day 90 tells you which steps got skipped, and folds the lesson back in.

How do you adapt the template to your engagement?

The fields stay. The rows flex along three axes.

  • Deal size. For a small engagement, collapse phases 2 and 3 and pull go-live to K+30: fewer ceremonies, same exit criteria. For a large one, add an executive-sponsor row to phase 1 and a biweekly steering call to phase 3, both client-visible on purpose.
  • Migration vs net-new. A migration adds a parallel track: export and verify the old system’s data before touching the new one, with an exit criterion of “record counts match, spot-checked by the client.” Net-new work moves that weight into phase 2, because requirements carry the risk data carries in a migration.
  • Single vs multi-team. When delivery crosses teams, keep one named owner per step anyway, and add an explicit handoff row at each boundary: “build handed to media; media confirms inputs received.” The handoff is a step with its own exit criterion, because the boundary is where multi-team onboardings drop the baton.

Why doesn’t a client onboarding template guarantee the onboarding happens?

Because a template is a map, and a map has never once driven the route. Someone still has to drive it, on the hundredth account as carefully as on the second, with the client in the passenger seat watching how you take the corners.

A client onboarding template is a map and the onboarding is the drive: the planned route runs clean from signature to a live account, while the route the team drives drifts, skips a stop, and arrives late; the gap between the lines is the run, and no template field fixes it.
The map and the drive. The distance between the two lines is where onboarding is won or lost, and it never shows up in the document.

The numbers say the map is already common. Across the 198 leaders in the State of Sales Enablement, 89 percent had a defined process and 36 percent saw their teams follow it: a 53-point gap that is pure adherence. Write the finest customer onboarding template in your industry and you have moved yourself into the 89 percent. The engagement is decided in the 36.

Bar chart showing why a client onboarding template is the floor: 89 percent of teams have a defined process, 36 percent see their teams follow it, a 53-point adherence gap, from The State of Sales Enablement 2026 survey of 198 leaders.
89 percent defined, 36 percent followed. The template closes none of the 53 points; the run closes all of them.

The decay has a mechanism, and it is older than project software. Hermann Ebbinghaus measured in the 1880s how fast people forget what they are taught once: most of it within days, absent reinforcement (the forgetting curve). Walk the team through the template at an all-hands and by the third account the steps are half-remembered and improvised around. The template did not change. The running of it did. And the cost lands on the number that funds a services firm: Frederick Reichheld’s work at Bain found that a five-point gain in customer retention lifts profit 25 to 95 percent (Reichheld, Harvard Business Review), and onboarding is the stretch of the relationship where retention is set.

So the template needs companions. The one-page client onboarding checklist travels into the kickoff itself, and the wider client onboarding guide covers the full first-90-days arc this template runs inside. If you are evaluating tooling, our take on client onboarding software makes the longer case that the plan is the easy half. This is also the job we built Supered’s Action Plans for: the template becomes per-account steps delivered in the flow of work, inside the tools the team already uses, with exit criteria checked and adherence measured account by account instead of assumed.

A quick recap

  • The six fields. Phase, step, one named owner, a due date relative to kickoff, an exit criterion, and a client-visible flag. K-dates make it copyable; exit criteria make it true.
  • Exit criteria over checked boxes. A box records a claim; a criterion names a verifiable state. Checklists built on verifiable states cut surgical deaths from 1.5 to 0.8 percent.
  • The map and the drive. A template is structure, and structure is the floor: 89 percent of teams have a defined process, 36 percent see it followed.
  • The stakes. A five-point retention gain lifts profit 25 to 95 percent, and the first 90 days are where the retention curve gets bent.

What we recommend

Copy the template above this week; the structure costs you an afternoon, and it buys you the floor. Hold one line as non-negotiable from the first account: no step counts as done without its exit criterion met, in writing where the criterion says so. That habit separates a plan that reports progress from one that reports claims.

Then decide where the run will live. A spreadsheet holds the template and decays with attention. A project tool holds a copy per account and tells you what was marked complete. Neither puts the next step in front of the person who owes it, and the 53-point gap is what that absence costs, a system property rather than a discipline problem. Once you run more than a handful of onboardings at a time, put the steps where the work happens and measure whether each account followed them. The template is the map. Book a demo if what you are missing is the drive.

Frequently asked questions

What is a client onboarding template?+
A client onboarding template is a reusable plan for bringing a new client live: the phases (pre-kickoff, kickoff and requirements, implementation, launch and handoff), the steps inside each phase, an owner per step, due dates written relative to kickoff (K-5, K+7, K+45), exit criteria that define when a step counts as done, and a flag for which steps the client sees. The team copies it onto each new account so the first 90 days run the same way every time.
What should a client onboarding template include?+
Six fields per step: the phase it belongs to, the step itself (one action), one named owner, a due date relative to kickoff so the template survives being copied, an exit criterion (the observable state that must be true before the step counts), and a client-visible flag. Attach a standing kickoff agenda and a 30/60/90 review block. Exit criteria and kickoff-relative dates carry most of the load; the rest is bookkeeping.
How long should client onboarding take?+
For a typical mid-market services engagement, about 60 days from kickoff to handoff, with a first deliverable in the client's hands by day 20 and results reviewed at day 90. Small engagements can compress to 30 days by collapsing the requirements and implementation phases. The date that matters most is time to first value: the day the client sees something real, not the day the project board says complete.
What is the difference between a client onboarding template and a checklist?+
A checklist is the one-page version: the steps in order, checked off as they happen. A template adds the fields a checklist drops: owners, due dates relative to kickoff, exit criteria, and client visibility, which is what lets you copy it per account and see where an engagement drifted. Use the checklist for the kickoff meeting itself; use the template to run the 60 days around it. Neither one makes the team follow the steps, which is a separate and harder problem.
Should the client see the onboarding plan?+
Most of it, yes. Onboarding is the first product the client experiences, and a plan they can see (with the internal-only rows filtered out) sets expectations, surfaces their dependencies early, and makes slipped dates a shared problem instead of a surprise. That is what the client-visible column in the template is for: it forces a decision, row by row, about the experience you are producing.

Your process, running itself.

Turn the playbook into rep behavior.

Book a demo Read The State of Sales Enablement