Most companies treat customer onboarding as a handoff problem. Sales closes the deal, Customer Success picks up the baton, and someone cobbles together a project plan in a shared doc that nobody keeps current. The customer shows up to the kickoff call without having read it. Three months later, they’re barely using the product and the renewal conversation is already difficult.
This guide exists because onboarding done well is one of the highest-leverage investments in the entire customer lifecycle. Not just for churn prevention, but for expansion, referrals, and the speed at which a new customer starts seeing your product as essential rather than optional.
Hyper is an AI onboarding agent for SaaS that does 1-on-1 screen-sharing calls with users, seeing their screen, controlling their browser, and guiding them via real-time voice. We publish this checklist as part of our analysis of what effective customer onboarding actually looks like at every stage.
Customer Onboarding vs. User Onboarding: What’s Different
These two terms get used interchangeably and they shouldn’t be.
User onboarding is the individual experience: a person logging into your product for the first time, learning how to do the thing they came to do. It is product-led, happens inside the app, and is measured by whether that person reaches a meaningful action quickly.
Customer onboarding is the account-level process: a new company, department, or business unit becoming a functioning customer. It spans contract execution, technical integration, team configuration, stakeholder alignment, training, and the moment the account goes live. Customer Success owns it, not the product team.
In B2B SaaS, both happen simultaneously. The distinction matters because they require different owners, different timelines, and different success criteria. A customer can be fully onboarded at the business level while their users are still stuck on first login. The reverse is also true: individuals can activate while the account integration sits unfinished and the renewal hangs on a customer who doesn’t know if the product is actually working.
Both problems are expensive. This checklist addresses the customer-level process. For the user-level version, see User Onboarding Checklist.
The Customer Onboarding Checklist
Six phases, each with a defined set of tasks and a clear exit condition. The exit condition matters as much as the tasks: without a gate between phases, teams rush forward before the previous stage is actually done.
Phase 1: Pre-Sale Handoff
This phase starts before the contract is signed and ends the moment the account is officially handed to the Customer Success team.
Checklist:
- [ ] Sales captures key context in the CRM: use case, success criteria the customer named in the sales conversation, known risks, champion and economic buyer contact details
- [ ] Customer Success joins the final sales call or receives a recorded briefing
- [ ] Internal kickoff completed between Sales and Customer Success before the first customer touchpoint
- [ ] Technical requirements collected: SSO, API access, data import scope, integration dependencies
- [ ] Welcome email sent within 24 hours of contract signature
- [ ] Customer Success introduction made in writing before the kickoff call
Exit condition: Customer Success has full context and the customer has received a warm introduction before the kickoff.
The handoff is where onboarding fails most quietly. When Customer Success learns about the customer’s goals for the first time on the kickoff call, the account starts behind.
Phase 2: Kickoff
The kickoff meeting sets the entire onboarding trajectory. Teams that treat it as a welcome call miss the chance to align on the things that will determine whether onboarding succeeds.
Checklist:
- [ ] Align on the customer’s definition of success (not yours)
- [ ] Document stakeholders on both sides with clear ownership
- [ ] Set a shared project timeline with milestones and a target go-live date
- [ ] Define what “done” means for onboarding
- [ ] Confirm all required technical access and permissions
- [ ] Schedule the next three touchpoints before leaving the call
- [ ] Send a meeting summary with action items and owners within 24 hours
Exit condition: Both parties have signed off on a shared plan with named owners on every open item.
The most important question on a kickoff call is not “what does your team want to use this for?” It is “how will you know onboarding succeeded?” Those are different questions. The first gets you a feature list. The second gets you the actual success criteria the renewal will be judged against.
Phase 3: Implementation
Technical setup, data migration, integration configuration, and account structure. This phase is often the longest and the most likely to stall.
Checklist:
- [ ] Product configured to match the customer’s account structure (teams, roles, permissions)
- [ ] Data import completed and validated by the customer
- [ ] Integrations connected and tested end-to-end
- [ ] Admin users trained on configuration and management workflows
- [ ] Acceptance criteria confirmed: customer has reviewed the setup and approved it
- [ ] All blockers documented with owners and resolution dates
- [ ] Status update sent to customer stakeholders at minimum weekly
Exit condition: Customer has reviewed and accepted the configured environment. No outstanding blockers.
Using a repeatable template for implementation reduces time in this phase and keeps accountability clear: approximately 90% of onboarding tasks are identical from customer to customer. Build the template once and personalize the remaining 10%.
Phase 4: Training
Training is where most teams invest too little and measure too loosely. A training session that ends with “questions?” is not training. Training ends when users can do the job the product was bought to do.
Checklist:
- [ ] Identify which user roles need what training (administrators, power users, occasional users)
- [ ] Run role-based training sessions rather than one generic overview
- [ ] Record sessions and share in a persistent location
- [ ] Confirm post-training: can users complete the core workflow without help?
- [ ] Identify users who are struggling and schedule follow-up
- [ ] Share reference documentation tied to actual workflows, not feature lists
Exit condition: Key users can complete the product’s primary workflow independently.
The gap between “attended training” and “can do the thing” is where most onboarding falls apart. Attendance is not competence. The test is not “did you watch?” but “can you now do it?”
For many SaaS teams, the training step is also where scale becomes a problem. Scheduling live sessions for every user at every customer account is not sustainable. This is where AI-guided onboarding changes the math: instead of blocking live Customer Success time for every training session, an AI onboarding agent joins each user 1-on-1, sees their screen, and walks them through the product in their own session at their own pace.
Phase 5: Go-Live
The transition from onboarding to active use. This phase is often treated as an event rather than a process, which is why customers frequently feel abandoned immediately after launch.
Checklist:
- [ ] Pre-launch review completed: all acceptance criteria met
- [ ] Go-live communication sent to the customer’s team
- [ ] Escalation path communicated: who to contact if something breaks
- [ ] First-week check-in scheduled for 5-7 days after launch
- [ ] Customer Success monitoring product usage data for the first two weeks
- [ ] Any post-launch issues captured and resolved within agreed SLA
Exit condition: Customer is actively using the product and has a clear support path.
Users who experience a smooth go-live, specifically one where their first week is monitored and any issues are resolved quickly, show materially higher engagement at 30 and 60 days than users who launch without active follow-up. Going live is not the finish line. It is when onboarding’s effects start compounding.
Phase 6: First Review
The 30-60 day review is the most underused tool in the Customer Success playbook. It is the first chance to measure whether onboarding delivered on the success criteria set at kickoff.
Checklist:
- [ ] Review product usage data before the call: who is using what, who is not
- [ ] Compare actual outcomes to the success criteria from the kickoff
- [ ] Surface quick wins: specific things the customer has done that prove value
- [ ] Identify at-risk users and propose a plan to re-engage them
- [ ] Identify expansion opportunities without forcing the conversation
- [ ] Document the customer’s stated assessment of onboarding quality
- [ ] Set the cadence for the ongoing relationship
Exit condition: Customer has acknowledged value and both parties have agreed on what success looks like at the 90-day mark.
The review closes the onboarding loop. Without it, the only feedback you get is renewal or churn, both of which arrive too late to act on.
Checklist by Company Size
The phases above apply across the board. What changes is the weight of each phase and the level of structure required.
Small Business (under 50 employees)
The priority is speed. Small-business customers want the product working as fast as possible. Extended kickoffs, multi-week implementations, and elaborate project plans create friction without matching value.
Target go-live: 7-14 days.
Key adjustments: compress Phases 1-2 into a single lightweight kickoff, keep implementation self-serve where possible, make training asynchronous (recorded walkthroughs), and start the first review at 30 days. One Customer Success owner for the account with light-touch check-ins.
Mid-Market (50-500 employees)
The priority is structure with momentum. Mid-market accounts have more stakeholders and more technical complexity than SMBs, but they also have shorter patience for enterprise-style ceremony.
Target go-live: 30-45 days.
Key adjustments: formal kickoff with defined project timeline, implementation managed with a shared project tracker, role-based training required, weekly check-ins until go-live. A named Customer Success manager who tracks milestone completion.
Enterprise (500+ employees)
The priority is governance and coordination. Enterprise accounts often run onboarding as a formal project with internal project management, legal and security review steps, multi-team training, and executive stakeholders who expect status reporting.
Target go-live: 60-90 days, with a defined first-value milestone within the first two weeks.
Key adjustments: dedicated implementation support, change management planning, structured training program for multiple user cohorts, executive business review at 60 days, and a formal handoff to the ongoing Customer Success relationship at the close of the onboarding period.
Automating the Checklist
Most of the project management layer of onboarding (task ownership, timeline tracking, status updates) can and should be automated. Tools like Rocketlane, Dock, and Asana have template-based onboarding plans that auto-generate from a deal closed in Salesforce. That layer is now table stakes.
The harder automation problem is training.
Training is the phase most likely to be delayed, abbreviated, or skipped entirely because it requires live human time at both ends. A Customer Success manager cannot be on a call with every new user at every new account. As the customer base grows, the training backlog grows with it. The options are: hire more people, cut training quality, or find a different model.
The different model is AI-guided training at the user level. Hyper joins each user in a 1-on-1 session, sees their screen, controls their browser, and walks them through workflows in real time via voice. The session adapts to what the user is actually doing, not to a pre-scripted tour that breaks when the user takes an unexpected step.
What this means for the checklist: the training phase no longer requires Customer Success time for every individual user. Customer Success sets up the session triggers, reviews session summaries, and steps in for edge cases. The guided training itself runs at software scale, with every user getting a dedicated walkthrough rather than a recorded video they may or may not finish.
The result is not just cost reduction. Users who receive live guided walkthroughs activate faster and retain more than users who watch recordings or self-navigate. The quality goes up. The cost per user goes down.
See also: What Is Customer Success for how this fits into the broader post-sale motion.
Next Steps
A checklist is a starting point. The teams that consistently run fast, high-quality onboarding treat it as a living system: they review first-review outcomes, identify where phases are stalling, and improve the template each quarter.
The phase most worth investing in first is training. It is the one that takes the most Calendar time, creates the most variability in outcomes, and is most directly responsible for whether users actually use the product after go-live.
If you’re looking at training as a scale problem, book a call with Hyper to see what live AI-guided sessions look like on your product. We’ll run a session on your actual workflow.
See also: Onboarding Checklist for the user-level version, and What Is Customer Success for the broader post-sale framework this checklist fits into.
Part of Hyper’s editorial guide to SaaS onboarding and Customer Success. March 2026.