Customer onboarding checklist
Onboarding sets up everything that follows. This checklist covers the major steps from handoff to first value, which you can adapt to your product.
Quick answer — What should a customer onboarding checklist include? Handoff review, kickoff, implementation, training, first-value milestone, and a transition to ongoing management.
Before kickoff
- Receive the sales handoff: goals, stakeholders, promises made, timeline. See handoff.
- Review the contract, scope, and technical requirements.
- Identify the executive sponsor, champion, and admin.
- Prepare a draft success plan.
- Send a welcome email with next steps.
Kickoff
- Confirm goals and success criteria in the customer's words.
- Agree on timeline, milestones, and responsibilities on both sides.
- Confirm data, access, security, and integration needs.
- Set the communication cadence.
- Document risks and dependencies.
Implementation and configuration
- Complete setup, integrations, and data migration.
- Test with the customer.
- Track progress against the plan; escalate blockers.
- Keep stakeholders updated.
Training and enablement
- Train admins and users, in role-based sessions.
- Provide quick-start guides and recordings.
- Set up office hours or a community channel.
- Check understanding rather than assuming it.
First value and adoption
- Define and celebrate the first-value milestone. See time to value.
- Review early usage and fix gaps.
- Plan the first business review.
- Collect initial feedback via a short survey. See CSAT and CES.
Test: If the customer cannot tell you what success looks like and how they will know they have reached it, onboarding is not done.
Closing onboarding
- Confirm completion with the customer.
- Transition to the ongoing cadence.
- Set health score inputs. See health score.
- Plan the path to renewal and expansion.
- Review what could be automated. See digital CS.
A kickoff email template
Subject: Welcome to [Product]: what to expect in the first 30 days. Body: thank them, restate their goal, list three milestones with dates, name the owners on both sides, and propose a kickoff time. Keep it under 150 words.
Adapting the checklist by segment
| Segment | Adjustment |
|---|---|
| Enterprise | Add security review, executive sponsor session, phased rollout |
| Mid-market | Standard checklist with a defined 30-60-90 plan |
| SMB / digital | Automated email and in-app sequence with a human check at risk points. See digital CS |
The onboarding principles behind the checklist
A checklist helps consistency, but the principles matter more than any single item. First, onboarding is about the customer's outcome, not your setup process. Every step should move the customer closer to the result they bought the product to achieve. Second, momentum matters: long gaps between kickoff and visible progress make champions anxious and give competing priorities time to creep in. Third, ownership on both sides must be explicit, because many onboarding delays come from tasks the customer owes and has quietly forgotten.
Teams that onboard well also learn from each cohort. They track how long each stage takes, where customers stall, and which accounts reach first value quickly. Over time, the data shows which steps can be automated, which need more support, and which expectations set in sales cause trouble. Feeding those insights back to sales and product turns onboarding from a one-off project into an engine for improving the whole customer journey.
Key takeaways
- Anchor every step to the customer's outcome.
- Keep visible momentum from kickoff to first value.
- Make responsibilities explicit on both sides.
- Track stage durations and feed learnings back to sales and product.
Frequently asked questions
See what CSMs really earn
Compare your pay against real CSM submissions — free, anonymous, takes 2 minutes.