Customer onboarding checklist: every phase, with what to automate
A customer onboarding checklist by phase, with an automation column showing which steps to automate, which to keep human, and how to measure time to value.
On this page
A customer onboarding checklist lists every step between "contract signed" and "customer getting value," grouped by phase with an owner for each step. Use the tables below as a starting point. Automate the repeatable handoffs: data collection, account setup, reminders and status updates. Keep the kickoff, expectation-setting and problem-solving with a person.
How to use this checklist
Onboarding fails in predictable places. Sales promises never reach delivery. Customers send documents in four formats. Tasks have no owner. Then two weeks of silence pass while the team waits on the customer. A checklist only helps if each line has an owner, a due date and a definition of done.
Copy the tables into your project tool, delete what doesn't apply and add the steps unique to your service. Then read the "Automate?" column. It marks where automation usually pays off and where we'd leave a person in charge.
The checklist by phase
Phase 1: Handoff from sales
| Step | Owner | Automate? | How |
|---|---|---|---|
| Closed-won deal triggers onboarding | Sales ops | Yes | CRM stage change creates the onboarding project |
| Deal summary: scope, promises, contacts, dates | Account executive | Partly | Template pulls CRM fields; the AE adds anything promised outside the contract |
| Internal kickoff with delivery team | Delivery lead | No | A short call. Surprises come out in conversation |
| Assign onboarding owner and backup | Delivery lead | Yes | Rules by service line, region or workload |
Phase 2: Paperwork and access
| Step | Owner | Automate? | How |
|---|---|---|---|
| Contract and order form stored in the right place | Sales ops | Yes | E-signature completion files the PDF against the account |
| Collect billing details, tax IDs and purchase order numbers | Finance | Yes | A form that validates fields and writes to billing |
| Create the customer in billing or ERP | Finance | Yes | API call from the form, with a check for duplicates |
| Security questionnaire or data processing agreement | Legal | Partly | Draft answers from an approved answer library; legal signs off |
| Request access, credentials and integrations | Onboarding owner | Partly | Request list with reminders; customers still need to approve access |
Phase 3: Kickoff
| Step | Owner | Automate? | How |
|---|---|---|---|
| Welcome email with named contacts and what happens next | Onboarding owner | Yes | Triggered on handoff, personalized from CRM data |
| Schedule the kickoff call | Onboarding owner | Yes | Scheduling link with the right attendees |
| Agree goals, success measures and timeline | Onboarding owner | No | This conversation sets the customer's expectations |
| Confirm stakeholders and decision makers | Onboarding owner | No | People know who is who in their organization better than any record |
| Send kickoff notes and action list | Onboarding owner | Yes | Draft from the call transcript, reviewed before sending |
Phase 4: Setup and configuration
| Step | Owner | Automate? | How |
|---|---|---|---|
| Create accounts, workspaces and user permissions | Delivery team | Yes | Scripts or API calls from the intake form |
| Import customer data | Delivery team | Partly | Validation checks and error reports; a person resolves bad rows |
| Configure integrations | Delivery team | Partly | Templates for common systems; custom ones stay manual |
| Test with the customer's real data | Delivery team and customer | No | Someone who understands the process has to judge the output |
| Resolve open questions | Onboarding owner | No | People decide |
Phase 5: Training and first use
| Step | Owner | Automate? | How |
|---|---|---|---|
| Role-based training sessions | Delivery team | Partly | Recorded sessions and a help assistant answer repeat questions; live sessions for key users |
| Share documentation and quick-start guides | Onboarding owner | Yes | Sent by role at the right moment |
| First real task completed by the customer | Customer | Track | Detect it from product or system events and notify the owner |
| Check-in after first use | Onboarding owner | Partly | Prompt scheduled automatically; the conversation is human |
Phase 6: Go-live and handoff
| Step | Owner | Automate? | How |
|---|---|---|---|
| Go-live checklist signed off | Delivery lead and customer | No | Both sides confirm in writing |
| Handoff to support or account management | Onboarding owner | Yes | Project closes, summary and configuration notes go to the account record |
| First invoice or billing schedule confirmed | Finance | Yes | Billing runs from the contract terms |
| Satisfaction survey | Account manager | Yes | Sent at a set time after go-live |
Phase 7: First 90 days
| Step | Owner | Automate? | How |
|---|---|---|---|
| Usage and adoption monitoring | Account manager | Yes | Alerts when usage drops below an agreed threshold |
| Check-ins at 30, 60 and 90 days | Account manager | Partly | Scheduled prompts with an account summary; conversation stays human |
| Issue and ticket review | Support lead | Partly | Summary of open issues attached to the check-in |
| Review goals against success measures | Account manager | No | An honest conversation with the customer |
What to automate first
Start where the work is repetitive and mistakes are expensive.
- Handoff from CRM to project. Summary, contacts and scope arrive complete, every time.
- Intake forms with validation. Customers fill in one form instead of answering six emails, and the data goes straight to billing and setup.
- Reminders and status updates. The system chases the customer for missing items so your team doesn't have to.
- Account creation. Scripted provisioning ends copy-and-paste errors.
- Internal notifications. The right person hears about a signed contract, a finished task or a stalled project.
Take a services firm onboarding 30 new clients a quarter. If it spends 90 minutes per client chasing documents, and a form with automatic reminders cuts that to 15, it saves over 35 hours a quarter. Clients also get a clearer experience. Your own numbers will differ, so time the current process before you estimate.
Key point: Automate the handoffs and the chasing. Leave the kickoff conversation, the expectation-setting and the first real test with a person, because that is where trust forms.
Where AI helps and where it doesn't
Language models help with the messy parts. They can read a signed contract and pull out scope and dates, draft kickoff notes from a call transcript, answer a customer's repeat "how do I..." questions from your documentation, or check an uploaded file against the list of what you requested. A person reviews each of these before it reaches the customer or the system of record.
AI shouldn't decide that a customer is ready for go-live, and it shouldn't promise delivery dates. Someone who can be held to the commitment has to make those calls.
Our customer onboarding blueprint shows how handoff, intake, provisioning and follow-up fit into one workflow. For the general approach to connecting these steps, see workflow automation.
Metrics worth tracking
- Time to value: days from signature to the customer's first real outcome. Define "first outcome" per product.
- Time to complete each phase, which shows where projects stall.
- Items waiting on the customer, and for how long.
- Handoff completeness: the share of projects that started with every field filled in.
- Support tickets in the first 30 days. They point at gaps in onboarding.
- Satisfaction at go-live and at 90 days.
Track these for a few months before you set targets. Then pick the one or two that matter most to your business.
Common mistakes
- Building the checklist around your internal tasks instead of what the customer has to do.
- Starting onboarding only after the first invoice is paid.
- Letting a project run without a named owner.
- Automating emails before fixing an unclear handoff from sales.
- Measuring task completion and ignoring time to value.
Get help adapting it
If your onboarding spans many systems or approvals, a generic checklist only gets you part of the way. Book a strategy call and we'll map your current process, find the steps worth automating and tell you which ones to leave alone.
Frequently asked questions
What should a customer onboarding checklist include?
At minimum: handoff from sales, paperwork and billing setup, access and integrations, a kickoff meeting, configuration and data import, training, go-live sign-off and a check-in plan for the first 90 days. Each step needs an owner and a due date.
How do you automate client onboarding?
Connect your CRM, forms, e-signature, billing and project tools so a signed deal creates the onboarding project, customers submit information through one validated form, and reminders go out automatically. People run the conversations and approve anything with commercial or legal weight.
How long should customer onboarding take?
It depends on the product and the customer's own pace. Measure time to first value for your last 10 customers to get a baseline, then look at which phases and which customer-side delays account for most of it.
What is the difference between customer onboarding and client onboarding?
The terms are used interchangeably. "Client onboarding" is more common in services firms, agencies and professional services. "Customer onboarding" is common in software and subscription businesses. The phases are similar.
Can AI run customer onboarding?
It can handle parts of it, such as extracting contract details, drafting notes, answering repeat questions and checking documents. A person should own the relationship and approve key decisions.
Get the next article by email
One practical piece a month on automating real operations. No promotions.