New Customer Onboarding Checklist | 42 B2B SaaS Steps

This new customer onboarding checklist runs 42 items across five phases, from signed contract to adopted product. Every phase has an owner, a timebox and an exit criterion, so you can tell the difference between a completed task and a customer who is actually moving. The full checklist is on this page and the interactive version lets you jump to each phase and track progress in your browser. Scope: sales-assisted B2B SaaS deals.

Scope first: sales-assisted B2B SaaS onboarding, from signature to adoption. Somebody on your side owns the account. Somebody on theirs signed the contract. That is the world this new customer onboarding checklist assumes.

For self-serve signup flows, use the user onboarding checklist. When onboarding happens inside the product, the real work is empty states, tooltips and activation events. That checklist looks nothing like this one.

Customer onboarding is complete when the customer reaches first value and repeats it without help from your team. Not when the kickoff happened. Not when everyone thanked you on the training call.

Activities need completion criteria. “Send the welcome email” records an action; “kickoff accepted by the required participants” records a verified state. Include both the work and the outcome needed to advance.

You tick "send welcome email" when the message leaves your outbox. You tick "kickoff booked with the sponsor on the invite" only when it is true. One is a to-do list. The other is a definition of done, which is why teams finish on time while their customer sits still.

Copy the new customer onboarding checklist per account. Paste it into whatever you run onboarding in: Notion, Asana, Linear, HubSpot tasks, a spreadsheet with one tab per customer. The tool matters less than the copy-per-account habit, because one shared master list becomes a graveyard by the fourth deal.

Assign owners in the kickoff, by name. "CS" does not send anything. Anna sends things. An item with a team name in the owner column is an item nobody agreed to do.

Then timebox each phase, not the whole journey. An eight-week onboarding without phase deadlines slips one quiet week at a time. In week eleven the sponsor asks why nobody uses the product.

Seven owner labels appear below. Yours: Sales, Onboarding lead, Solutions engineer, Enablement, CSM. Theirs: Sponsor and Admin. In a ten-person company one person plays four of those roles. Keep the labels anyway, because a label makes a missing owner visible.

The timeboxes below are an illustrative plan, not a universal benchmark. Adjust them to the agreed scope and customer dependencies. Two common adaptations:

• Simple implementation: combine kickoff and setup if prerequisites are ready. Keep the security, privacy and purchasing checks that apply to the data and contract, regardless of customer size. Mark other items not applicable with a reason.
• Complex implementation: confirm security review, SSO, data-processing terms and procurement with their owners before committing to go-live. Start required approvals before signature or data access when appropriate; allow time for dependencies.

Agree the onboarding commitments during the sale so that the delivery plan matches what the customer expects. The customer onboarding framework helps separate stage ownership from individual tasks.

The five phases at a glance

The five phases below each have a suggested timebox and an exit criterion.

Owner: Sales owns the handoff. Onboarding owns the rest. Timebox: 5 business days from signature. Exit criterion: the kickoff sits on the calendar with the sponsor invited, and a success plan draft exists.

• Write the handoff document: business goal in the customer’s words, stakeholders, promised outcomes, known risks. (Sales)
• Hold a 15-minute handoff call, so the onboarding lead can ask what the document missed. (Sales, Onboarding lead)
• Provision the account: CRM record, product instance, plan, seat count, contract and renewal dates. (Onboarding lead)
• Assign a named onboarding lead and introduce them by name, never by shared inbox. (CSM)
• Draft the success plan skeleton from the deal notes before the kickoff, never during it. (Onboarding lead)
• Send the welcome email within 24 hours of signature: one owner, one link, one action. (Onboarding lead)
• Book the kickoff inside the first week, then put the executive sponsor on the invite. (Onboarding lead)
• Flag the risk internally if the deal has one champion, no sponsor, or an over-promised outcome. (Onboarding lead)

Use the handoff to summarize what sales and the customer agreed, then confirm whether anything has changed. That is practice 10 in customer onboarding best practices.

Owner: the onboarding lead runs it. The sponsor signs it. Timebox: week 1. Exit criterion: the customer sponsor signs off on the success plan in writing. Attendance is not sign-off.

• Send the agenda 48 hours ahead, with the pre-work list and the names you need present. (Onboarding lead)
• Run the kickoff with the sponsor or an authorized delegate. Demonstrate the agreed workflow only where it helps confirm scope. (Onboarding lead)
• Write the first-value milestone in the customer’s words: the one workflow that proves the purchase. (Onboarding lead)
• Agree the adoption threshold as a number now: active seats, weekly runs, records processed. (Sponsor, CSM)
• Name the people on both sides: sponsor, admin, daily owner, technical contact, your lead, your CSM. (Onboarding lead)
• List every technical prerequisite with an owner and a date: access, credentials, sample data, integrations. (Solutions engineer)
• Confirm that required security review, data-processing terms and vendor approvals are completed before the relevant data access or work begins. (Sales, Solutions engineer)
• Confirm whether SSO and additional procurement steps apply, with a named contact and decision. (Sales)
• Agree the timeline in calendar dates, not durations, because "two weeks" starts drifting immediately. (Onboarding lead)

The success plan itself is six lines. Keep it that short and people actually read it:

1. Business goal, in the sponsor’s words.
2. First-value milestone: the one workflow that proves it, with a date.
3. Adoption threshold: the number that means "adopted," with a date.
4. Owners on our side, by name and role.
5. Owners on your side, by name and role.
6. Known risks and dependencies, each with a date.

Then send it for written sign-off. If sign-off is delayed, establish whether the blocker is scope, authority or availability and resolve it with the named owner.

Owner: the solutions engineer, with the customer admin. Timebox: the example allows two weeks. Replace this with dates agreed with the integration and access owners. Exit criterion: the first-value workflow runs end to end on the customer’s real data.

• Configure the agreed use case only, not every feature the product ships. (Solutions engineer)
• Connect the integrations, then confirm one real record moving in each direction. (Solutions engineer, Admin)
• Import the data, then let the admin spot-check it against a sample they already trust. (Admin)
• Set roles and permissions to mirror how the customer works, not your default template. (Solutions engineer)
• Train the admin on admin tasks only: users, permissions, settings, billing. (Onboarding lead)
• Run the first-value workflow together once, on real data, screen shared. (Onboarding lead, Admin)
• Log every blocker in one shared list with an owner and a due date. (Onboarding lead)
• Write the escalation rule down. After 5 quiet days call the admin, after 10 escalate to the sponsor. (Onboarding lead, Sales)

Setup can stall on either side: unavailable data, a product defect, an access request or an unanswered decision. Track the dependency and agree an escalation interval. The five- and ten-day intervals above are examples to adapt to urgency and contractual commitments.

Owner: Enablement delivers. The onboarding lead tracks. Timebox: 2 weeks after phase 3 closes. Exit criterion: the customer reaches the first-value event, then repeats it without your help.

• Deliver training on separate role paths: admin, daily user, sponsor. Include shared context where useful, then practice the tasks specific to each role. (Enablement)
• Use video for visual workflows and provide captions plus written steps for reference. (Enablement)
• Observe the customer complete the agreed workflow independently, using an approved environment and the required checks for consequential actions. (Onboarding lead)
• Ask a second person to run the same workflow unaided, ideally someone who missed the training. (Customer team)
• Confirm the events fire for this account: first login, setup complete, first-value action, milestones. Verify these before using them to judge progress. (Onboarding lead)
• Email the quick win to the sponsor with a number in it: hours saved, records processed. (Onboarding lead)
• Log every question from activation calls. If a question repeats three times, queue it as content. (Enablement)
• Review the success plan mid-phase. If the first-value date moved, write down what moved it. (Onboarding lead)

If your CS team explains the same setup step on every activation call, that step does not belong in a calendar invite. It belongs in a short video the customer watches before the call, then rewatches afterwards. Count last quarter’s repeats, then multiply by the loaded hourly cost of the person giving them. That number usually wins the argument.

Owner: the CSM, receiving from the onboarding lead. Timebox: 4 weeks. Exit criterion: the account meets the adoption threshold from phase 2, not one invented in week 8.

• Run the 30-day review against the success plan, line by line, with the sponsor present. (Onboarding lead, Sponsor)
• Invite the remaining seats, then point each one at its role path, not the whole library. (Admin, Enablement)
• Measure adoption against the phase 2 threshold and give the sponsor the real number. (CSM)
• Transfer the handoff pack: success plan, decisions, open items, unresolved questions and relevant communication preferences. (Onboarding lead)
• Introduce the customer to their CSM on a call before onboarding closes. (Onboarding lead)
• Book the 60 and 90-day check-ins before the handoff call ends. (CSM)
• Collect onboarding CSAT: one rating question, one open field asking what could go faster. (CSM)
• Run an internal retro: which phase stalled, for how long, and what content would prevent it. (Onboarding lead)
• Flag expansion or risk if usage already sits above the plan, or well below it. (CSM, Sales)

Busy teams cut phase 5 first. Then usage flatlines on accounts that "onboarded fine." Understanding does not arrive at go-live. It arrives when customers repeat the value workflow, when a second role adopts it, and when the account can keep moving without the onboarding lead.

All 42 checklist items are available above. You can use them without submitting an email address.

The interactive version turns the same 42 items into a working tool:

• Use the phase links to jump to a section.
• Mark items complete and see progress update immediately.
• Keep progress in this browser when local storage is available. It does not sync across devices or create separate customer records.
• Print or save the checklist as a PDF when you need a shareable snapshot.
• Reset it for the next account without changing the master copy.

Use the checklist above. For several customers at once, copy the items into your own account-level project records; this page stores one checklist state.

Check for four common problems when adapting the template.

It is really a to-do list. Activities without exit criteria let a team tick every box while the customer has not logged in since the kickoff. So every item needs a condition that is true or false, observable by somebody else.

One checklist covers every segment. A simple setup and a complex implementation need different dependencies and timeboxes. Decide which controls apply based on the data, access, contract and workflow rather than company size alone.

Items nobody owns. "Send training" with no name attached does not go out. Owners are people, never teams. Name one accountable lead and identify the people responsible for individual tasks.

The checklist stops at go-live. Setup is phase 3. Adoption is phases 4 and 5. A checklist that ends at configuration can miss the need for repeated, independent use. That is practice 11 in customer onboarding best practices: onboarding ends at adoption, not at setup.

What should a new customer onboarding checklist include?

Five phases, from signature to adoption: pre-kickoff handoff, kickoff and success plan, setup and configuration, activation and first value, adoption and handoff. Each item needs three more things: a named owner, a timebox for the phase, and an exit criterion. Without exit criteria you have a to-do list, and a team can finish one while the customer never activates.

How long should customer onboarding take?

It depends on product complexity, integration depth and the number of people who can block progress. A simple SMB implementation may finish inside a week. An enterprise rollout with security review, procurement and data migration can take much longer. The useful benchmark is your own: how long did each phase take across your last 20 accounts, and which phase consumed the most waiting time?

Who owns the customer onboarding checklist?

One named person per account owns the new customer onboarding checklist. Usually the onboarding lead, or the CSM in a smaller team. Sales owns the handoff and helps resolve commercial commitments or purchasing dependencies. Individual items belong to solutions engineers, enablement and the customer’s own admin. Nobody shares accountability for the whole, because when two people own onboarding, nobody escalates on day 5.

What is the difference between a customer onboarding checklist and a client onboarding checklist?

Customer onboarding checklists cover SaaS products: provisioning, integrations, data import, in-product activation, usage thresholds. Client onboarding checklists cover services and agencies: contracts and scope, intake questionnaires, access to tools and brand assets, communication cadence, first deliverable. The phase structure is nearly identical, but the items are not. If you deliver a service rather than a product, use the client onboarding checklist instead.

If the same phase repeatedly stalls, investigate the cause: guidance, product behavior, access or an unresolved decision. When customers need clearer instruction, a Customer Adoption Pilot can turn one workflow into reusable training with a defined measure of success.

Plan a customer adoption pilot