Kickoff is a bad time for delivery to learn the deal. Before the client joins, the team should know what they bought, what sales promised, who can approve the work, and which early result matters.
If the first part of the call is spent piecing that together, onboarding has already slipped. The client is paying to repeat information your company already has.
This client onboarding checklist starts with the internal handoff, then covers setup, training, a live use case, and the move into the ongoing relationship. Each of its 25 steps has one owner and a completion rule.
This 25-step client onboarding template is built for high-touch B2B customer onboarding: SaaS implementations, agency and consulting engagements, and managed services. It is not an employee checklist or an in-app product tour.
Throughout the checklist, “customer success lead” means the person who owns the post-sale relationship. An agency may call that person an account, project, or engagement lead.
Client onboarding checklist at a glance
| Phase | Default timing | The phase is complete when |
|---|---|---|
| Internal handoff | Before kickoff | Delivery knows what was sold, why it matters, and where the risks are |
| Client kickoff | Days 1–3 | Both sides agree on the outcome, scope, roles, first-value event, and immediate next steps |
| Setup and training | Days 4–14 | The core workflow works and the right people can use it |
| First value | Days 15–30 | The client completes a real use case and both sides record the result |
| Adoption and review | Days 31–90 | Remaining work has a destination and the ongoing plan has owners and dates |
These timings are a starting point. Adjust them to match the client’s approvals, dependencies, and committed dates, while keeping the phases in order.
Write down what first value means
Describe first value as something the client will actually do. For example: “The client publishes its first campaign through the approved workflow.” That is easier to confirm than “implementation complete.”
Copy the full 25-step checklist
| # | Phase | Timing | Task | Default owner | Done when |
|---|---|---|---|---|---|
| 1 | Internal handoff | Before kickoff | Write down the outcome the client bought | Account executive | The expected change is stated in one sentence using the client’s language |
| 2 | Internal handoff | Before kickoff | Reconcile the agreement with the sales notes | Account executive | Delivery has reviewed the scope, exclusions, dates, services, and material promises |
| 3 | Internal handoff | Before kickoff | Map the people who can move or stop the work | Account executive | The team knows the sponsor, working lead, technical contacts, and approvers |
| 4 | Internal handoff | Before kickoff | Put the risks in the open | Implementation lead | Every known risk has a next action and owner |
| 5 | Internal handoff | Before kickoff | Prepare the shared client home | Customer success or project lead | The agenda, plan, resources, contacts, and first actions are available through one link |
| 6 | Kickoff | Days 1–3 | Send a one-page kickoff brief | Customer success or project lead | The client has the goal, agenda, participants, preparation request, and shared workspace |
| 7 | Kickoff | Days 1–3 | Reconfirm the outcome and the evidence | Customer success lead | The sponsor agrees on the result, evidence, and first review date |
| 8 | Kickoff | Days 1–3 | Walk through boundaries and change control | Implementation lead | Both sides understand the scope and how changes will be handled |
| 9 | Kickoff | Days 1–3 | Replace departments with names | Customer success lead | Every workstream has a named owner and a backup where needed |
| 10 | Kickoff | Days 1–3 | Choose the communication and escalation path | Customer success lead | Both sides know where questions, decisions, status, and escalations belong |
| 11 | Setup and training | Days 4–14 | Collect the next required inputs | Implementation lead | The current stage’s required files, details, and decisions are received and checked |
| 12 | Setup and training | Days 4–14 | Clear security, legal, and access gates | Client technical or security lead | Required reviews and permissions are approved or have a dated resolution plan |
| 13 | Setup and training | Days 4–14 | Configure the narrowest useful workflow | Implementation lead | The core path works end to end with representative client data or content |
| 14 | Setup and training | Days 4–14 | Make the client lead test it | Client project lead | The client completes the core path, records issues, and approves the setup |
| 15 | Setup and training | Days 4–14 | Split training by role | Enablement or customer success lead | Each audience has training built around the work it will perform |
| 16 | Setup and training | Days 4–14 | End training with work in the live system | Enablement or customer success lead | Required users complete one role-relevant task and can find the reference material |
| 17 | Setup and training | Days 4–14 | Document the support path | Customer success lead | The client knows the support channel, required context, expected response time, and status location |
| 18 | First value | Days 15–30 | Prepare the first-value run | Customer success lead | The live use case, client participant, prerequisites, date, and evidence are confirmed |
| 19 | First value | Days 15–30 | Run a real use case | Client project lead | The client completes the critical path with live work and records friction |
| 20 | First value | Days 15–30 | Turn every blocker into a decision | Implementation lead | Every blocker is fixed, accepted, or deferred with an owner and date |
| 21 | First value | Days 15–30 | Record first value and the remaining gap | Customer success lead | Both sides record the result, evidence, remaining gap, and next review |
| 22 | Adoption and review | Days 31–90 | Review adoption by role and workflow | Customer success lead | The review identifies usage, blockers, and the response each role needs |
| 23 | Adoption and review | Days 31–90 | Give every open item a destination | Implementation lead | Every task is completed, transferred, or removed from scope |
| 24 | Adoption and review | Days 31–90 | Hold the first business review | Customer success lead | The sponsor and working team review the goal, evidence, gaps, and next plan |
| 25 | Adoption and review | Days 31–90 | Document the ongoing operating rhythm | Customer success lead | The client has an owner, support path, review cadence, priority, and decision date |
Before kickoff: give delivery the whole story
Complete these five steps before the first client-facing meeting. Delivery should not need the client to fill gaps that sales already captured.
1. Write down the outcome the client bought
- Owner: Account executive
- Done when: The handoff states the expected business or operational change in one sentence, using the client’s language.
Write the outcome in the client’s terms and include the constraint that matters. For a team launching in September, that could be: “The revenue team uses one approved proposal workflow before launch.”
2. Reconcile the agreement with the sales notes
- Owner: Account executive
- Done when: The delivery lead has reviewed the included work, exclusions, dates, services, and material promises made during evaluation.
Link the signed agreement or approved order form in the handoff. Add the relevant sales context beside it, but do not rewrite the commercial terms.
3. Map the people who can move or stop the work
- Owner: Account executive
- Done when: The team can name the executive sponsor, day-to-day lead, technical contact, security or legal contact, and final approver where each role matters.
Mark unknown roles instead of guessing. Put those gaps on the kickoff agenda.
4. Put the risks in the open
- Owner: Implementation lead
- Done when: Every known integration, deadline, access issue, staffing gap, and unresolved requirement has a next action and an owner.
For every risk, record the next action and owner. For example: “Mina sends the security pack to the client’s IT lead by Friday.”
5. Prepare the shared client home
- Owner: Customer success lead
- Done when: The kickoff agenda, current plan, key resources, contacts, and first client actions are available through one link.
Keep private risk notes and staffing details in the internal system. The shared space is for the work both sides need to see or do.
Days 1 to 3: make the kickoff produce decisions
Use the kickoff to confirm the outcome, settle scope questions, assign the first actions, and agree on how progress will be reviewed.
6. Send a one-page kickoff brief
- Owner: Customer success or project lead
- Done when: The client receives the meeting goal, agenda, participant list, preparation request, and shared workspace at least one working day before the call.
Ask only for information needed in the meeting. A 40-field intake form can wait until the client understands why those inputs matter.
7. Reconfirm the outcome and the evidence
- Owner: Customer success lead
- Done when: The sponsor agrees on the intended result, the evidence that will show progress, and the first review date.
Track setup milestones and client results separately. A configured workspace means the system is ready; it does not show that the client has used the new workflow.
8. Walk through boundaries and change control
- Owner: Implementation lead
- Done when: The client understands what onboarding covers, what sits outside it, and how either side will raise a scope change.
Review the places where scope usually slips: data migration, access for another team, custom training, or an integration shown during the demo.
9. Replace departments with names
- Owner: Customer success lead
- Done when: Every workstream has one named owner on the side responsible for the next action, plus a backup where continuity matters.
Assign tasks to named people, not departments. Use “Ravi, client technical lead” instead of “IT.” If you do not have a name yet, assign someone to find the owner by a specific date.
10. Choose the communication and escalation path
- Owner: Customer success lead
- Done when: Both sides know where routine questions go, where decisions are recorded, how often status is reviewed, and what qualifies as an escalation.
Work can happen across email, chat, meetings, and a project board. Choose one system of record for decisions when those channels disagree.
Days 4 to 14: build the smallest workflow that can deliver value
Optional configuration can consume most of the setup period. Ask only for the inputs needed now, configure the core workflow, test it, and train each role on the tasks it will perform.
11. Collect the next required inputs
- Owner: Implementation lead
- Done when: The implementation lead has received and checked the brand files, user list, process details, content, or configuration choices required for the current setup stage.
Send each request to a named client owner and tie it to the work it unlocks. A single giant list makes every missing item look equally urgent and leaves the client guessing where to start.
12. Clear security, legal, and access gates
- Owner: Client technical or security lead
- Done when: Required reviews, permissions, domains, accounts, and data-handling decisions are approved or have a dated resolution plan.
Formal questionnaires and approvals should stay in the channel the client requires. The onboarding checklist points to that record and shows the next move.
13. Configure the narrowest useful workflow
- Owner: Implementation lead
- Done when: The core path works end to end with representative client data or content.
Configure and test the core path before discussing optional settings. Add secondary customization only after the client has completed a real task.
14. Make the client lead test it
- Owner: Client project lead
- Done when: The client lead completes the core path, records issues, and approves the setup for training or launch.
Have the client run the same test after internal QA. They will catch missing context and permission issues that the delivery team may not see.
15. Split training by role
- Owner: Enablement or customer success lead
- Done when: Each audience has a short agenda and material built around the work it will perform.
An administrator needs configuration and exception handling. An occasional end user needs the three actions they will take next Tuesday. They do not need the same 60-minute tour.
16. End training with work in the live system
- Owner: Enablement or customer success lead
- Done when: Required users complete one role-relevant task and can find the recording and reference material afterward.
Set aside the end of each training session for attendees to complete a live task while the trainer is present.
17. Document the support path
- Owner: Customer success lead
- Done when: The client knows where to ask for help, what context to include, the expected response time, and where to check status.
Keep the support channel, response time, and status link in the shared client space so the client can find them after kickoff.
Days 15 to 30: do real work and record the result
By this point, setup and training should be complete. The next test is whether the client can use the workflow for an actual job and record the result.
18. Prepare the first-value run
- Owner: Customer success or project lead
- Done when: The event agreed at kickoff is scheduled, its prerequisites are ready, and both sides know what evidence to record.
Confirm the client participant, the live work they will use, the date, the prerequisites, and where the result will be recorded.
19. Run a real use case
- Owner: Client project lead
- Done when: The client completes the critical path with live work and records where the process slowed down or broke.
During the first live run, ask where the client had to stop and what caused the delay. Record each answer as a task, decision, or known limitation.
20. Turn every blocker into a decision
- Owner: Implementation lead
- Done when: Each launch blocker is fixed, accepted as a known limitation, or moved to a later phase with an owner and date.
If a blocker is still marked “in progress,” add the person responsible and the next action. If there is no next action, decide whether to accept the limitation or move it out of onboarding.
21. Record first value and the remaining gap
- Owner: Customer success lead
- Done when: Both sides have recorded what happened, the evidence, the gap against the intended result, and the next review date.
If the event did not happen, record the cause and set a new date. Do not move the milestone without noting why.
Days 31 to 90: turn a first result into a working rhythm
After the first live run, check whether the team can repeat it without implementation support. Close or transfer the remaining onboarding work, then agree on the owner and review cadence for the next quarter.
22. Review adoption by role and workflow
- Owner: Customer success lead
- Done when: The review identifies who is using the workflow, who is blocked, and which role needs training, access, or a process change.
Use the operational and product data available to you. A document-view event shows that the document was opened in a viewer. Time spent and pages viewed add context, but none of those signals proves that the reader completed the process or adopted the workflow.
23. Give every open item a destination
- Owner: Implementation lead
- Done when: Each remaining task is completed, transferred into the ongoing success plan, or removed from scope with the decision recorded.
Review every open item before the final meeting. Complete it, transfer it to the ongoing success plan, or remove it from scope and record the decision.
24. Hold the first business review
- Owner: Customer success lead
- Done when: The sponsor and working team have reviewed the original goal, evidence, gaps, decisions, and the proposed next-quarter plan.
Send status and completed work before the business review. Use the meeting for unresolved gaps, decisions, and next-quarter priorities.
25. Document the ongoing operating rhythm
- Owner: Customer success lead
- Done when: The client has a named relationship owner, support path, review cadence, next priority, and next decision date.
This is the handoff from onboarding into the working relationship. Write it down even when the same person owns both phases.
Copyable 30-60-90-day customer onboarding plan
Use this 30-60-90-day client onboarding template in a document, spreadsheet, project tool, or client onboarding workspace. Replace every bracketed prompt before you share the plan.
Days 0–30: set up and prove first value
- Outcome:
[The first observable result] - Client owner:
[Name] - Our owner:
[Name] - Required inputs:
[List] - Critical tasks:
[List] - First-value event:
[Event] - Target date:
[Date] - Done when:
[Evidence]
Days 31–60: repeat the workflow and close adoption gaps
- Outcome:
[The workflow repeated by the intended team or in the intended process] - Client owner:
[Name] - Our owner:
[Name] - Adoption gap:
[Role, team, or process step] - Response:
[Training, access change, resource, or process fix] - Measure:
[Operational measure] - Review date:
[Date] - Done when:
[Evidence]
Days 61–90: review the evidence and agree on the next plan
- Outcome:
[Result to review with the sponsor] - Client owner:
[Name] - Our owner:
[Name] - Evidence:
[Report, example, or recorded result] - Open decision:
[Decision] - Next-quarter priority:
[Priority] - Business review date:
[Date] - Done when:
[Agreed plan with owners and dates]
Build a checklist people can actually run
The table above is a reference checklist. When you turn it into a live operating plan, add enough information for someone to take the next action without reconstructing the project from email. The downloadable Word and Excel versions already include these fields.
| Field | What to write |
|---|---|
| Task | A verb plus the specific output: “Approve tracking plan,” not “Analytics” |
| Owner | One person or role accountable for the next action |
| Due date | A real date when timing or sequence matters |
| Dependency | The input, approval, or prior task that unlocks the work |
| Done when | The evidence that closes the task |
| Visibility | Client-facing or internal |
| Context | The current file, link, decision, or instruction needed to act |
| Status | Not started, in progress, blocked, or complete |
Replace a row named “Training” with a specific action, such as “Customer administrator completes the live setup exercise by August 14.”
Use one accountable owner per row. Other people can contribute, review, or approve, but the Owner field should answer a simple question: who makes the next move?
Run the customer-facing plan from one Room
Keep internal delivery detail out of the client plan.
The internal system can hold staffing, time, cost, private risks, and technical detail. The client needs the portion of the plan that asks them to act, decide, review, or understand something. Publish that layer in a persistent HummingDeck customer onboarding Room:
- Organize Welcome, Setup, Training, and Reviews with content tabs or section labels.
- Group the customer-facing actions into phases in the Room’s action plan.
- Add the accountable owner, due date, and dependencies. Put the completion rule in the task description.
- Put the current guide, video, form link, or decision material in the same Room.
- Choose an access mode that fits the sensitivity of the material.
Every HummingDeck Room can include one mutual action plan. Identified client contacts can complete buyer-visible tasks assigned to the same email without creating a HummingDeck account. Pro and Business add contextual Discussions and Restricted sharing for exact email addresses or eligible company domains. Restricted recipients verify inbox access before entering.
HummingDeck is our product. Email verification proves inbox access; it does not prove legal identity or create an electronic signature. HummingDeck does not replace resource planning, billing, native intake forms, legally binding e-signature or contract-management workflows, or a full implementation-management system. Its role is narrower: give the client one place to find the current plan, the material behind it, and the next decision.
If the shared plan is only one part of a longer relationship, see the broader client portal and Rooms workflows. If you are still choosing the internal system, compare customer onboarding software by job before you buy a portal, a project platform, or an intake tool.
Client onboarding checklist FAQ
How long should client onboarding take?
Use the shortest timeline that safely reaches the agreed first-value event and establishes an ongoing owner. Use a 30-60-90-day customer onboarding plan only when that structure helps sequence the work; extend or compress the phases to match the real dependencies.
Who owns client onboarding?
One internal lead should own the overall onboarding outcome. Individual steps can belong to sales, implementation, customer success, technical teams, and client stakeholders, but every action still needs one accountable owner.
What is the difference between client onboarding and customer onboarding?
The terms often describe the same post-sale process. Agencies and professional-services firms tend to say “client,” while SaaS and product companies tend to say “customer.” Use the term your buyers and account teams already use.
What should a customer onboarding checklist include?
A customer onboarding checklist should include the internal handoff, scope, stakeholders, risks, kickoff decisions, required inputs, setup, validation, training, support path, first-value event, adoption review, remaining work, and the transition into the ongoing relationship. Every row also needs an owner and a clear definition of done.
Should the sales rep join the kickoff?
The sales rep should join when their context or relationship will improve the handoff. Their presence should save the client from repeating goals and commitments, not turn the kickoff into another sales call.
What happens after the first 90 days?
Move open work into an ongoing success plan, confirm the relationship owner, and set the next review around a real decision or outcome. Keep the resources the client still uses and archive setup material that has finished its job.
By kickoff, delivery should already know why the client bought, what was promised, and what needs a decision. At the end of onboarding, both sides should have a record of the result, the open work, its owners, and the next review date.
Related:
- Customer onboarding software: 10 tools compared: Choose a portal, project platform, intake tool, or in-app onboarding product based on the work you need to run.
- Digital sales rooms for small teams: See when a shared Room is enough and when a larger system earns its cost.
- What is a digital sales room?: Understand the workspace model behind shared plans, content, and recipient activity.
- Five ways teams use digital sales rooms beyond sales: Explore customer success, agency, consulting, and other post-sale use cases.