SaaS Customer Onboarding Checklist (Free Template)

A customer onboarding checklist is the simplest version of an onboarding process: the ordered set of tasks that has to happen between a signed contract and a customer who is live and getting value. For a B2B software implementation, that means everything from confirming success criteria and collecting data to configuration, training, go-live, and the handoff to customer success. The value of writing it down is that nothing gets skipped and both sides can see what's next.

A checklist is the task layer inside the five stages of customer onboarding – the concrete to-dos, not the framework around them. The version below is copy-ready for SaaS and software implementations, organized by phase with the owner each task usually belongs to. Keep it static and it sits in a doc; run it as something the customer can see and it actually gets worked.

Checklist vs. plan vs. stages – what's the difference?

These three words get used interchangeably, but they're different layers of the same thing:

• Stages are the phases the process moves through – kickoff, data collection, implementation, go-live, adoption. They give onboarding its shape and exit criteria.
• A checklist is the concrete tasks inside those stages – "send intake form," "grant SSO access," "run go-live readiness check." It tells you what to actually do next.
• A plan combines both: the stages as a backbone, the checklist tasks nested under each, plus owners and dates.

So a good onboarding checklist isn't a flat to-do list – it's grouped by phase, with a named owner and a target date on every line. That's the version below. If you want the fuller planning artifact with milestones and dependencies, start from our customer onboarding plan template instead.

The customer onboarding checklist (by phase)

Here's the checklist for a typical B2B SaaS or software implementation. Treat it as the 80% that's the same for every customer and trim or add for your product. Each line names the owner who usually holds it.

Phase 1 – Pre-kickoff (before the first call)

There's almost always a lag between closed-won and the kickoff call. The best teams use it instead of waiting, so the customer arrives with momentum already started.

• Confirm the deal details and success criteria from sales – what they bought, what they said success looks like, who was in the room (owner: onboarding lead / CSM)
• Draft the setup before you ask them for anything. Use what sales already learned to pre-fill company details, contacts, purchased modules, and a proposed configuration. The customer's first job should be correcting a draft, not filling in a blank form – approving is fast, producing is what stalls (owner: CSM)
• Set up the customer's onboarding space or workspace and personalize it to their branding (owner: CSM)
• Send the draft plan and a short "who's involved" prompt before the call, so the kickoff is spent on decisions rather than data entry (owner: CSM → customer)
• Schedule the kickoff and target go-live date (owner: CSM)

Done when: the customer has a personalized space, a draft plan waiting for their input, and a kickoff booked.

Phase 2 – Kickoff and alignment

• Confirm the outcome the customer actually bought and agree what "live" and "success" mean (owner: CSM)
• Map every stakeholder, including decision-makers and users who weren't in the sales process (owner: shared)
• Walk through the plan and timeline together, so both sides own the same dates (owner: CSM)
• Assign the first customer-side tasks and confirm who owns what (owner: shared)
• Agree how you'll communicate and where the plan lives (owner: CSM)

Done when: kickoff complete, plan agreed, stakeholders mapped. For a full agenda, see how to run a customer onboarding kickoff call.

Phase 3 – Implementation and configuration

• Collect only the data you couldn't pre-fill, via structured forms rather than email attachments – and where their data is the blocker, start with sample data instead of waiting for theirs (owner: customer)
• Grant system access – credentials, SSO, admin rights (owner: customer IT)
• Complete any security or compliance review (owner: customer / your security lead)
• Configure the product to the customer's chosen modules (owner: your implementation lead)
• Connect integrations – CRM, SSO, other systems (owner: your team)
• Run internal QA before showing the customer (owner: your team)
• Post a progress update so the customer sees momentum during the build (owner: CSM)

Done when: the product is configured, integrated, QA'd, and ready for training.

Phase 4 – Go-live

• Deliver training – live sessions plus self-serve videos and guides (owner: CSM / enablement)
• Run a go-live readiness check – users, data, and integrations all confirmed (owner: CSM)
• Go live on the first real use case (owner: shared)
• Confirm the first-value milestone is reached – the outcome the customer bought (owner: CSM)

Done when: the customer is live and has hit their first real outcome. Time to value is the metric that most predicts renewal – see how to reduce time to value in SaaS onboarding.

Phase 5 – Adoption and handoff

• Confirm sustained usage, not just a single login (owner: CSM)
• Collect onboarding feedback – a quick CSAT or NPS (owner: CSM)
• Hand off to ongoing customer success with context, goals, and open items (owner: onboarding lead → CSM)
• Schedule the first post-onboarding check-in (owner: CSM)

Done when: adoption is sticking and the account is cleanly handed to success.

How to adapt the checklist

The list above is a starting point, not a straitjacket. A few adjustments make it fit your product:

• Match the touch level. A low-touch, self-serve product can collapse phases 2–4 into a single week and drop the formal training session. A complex enterprise rollout might split configuration across several milestones with its own data-migration sub-checklist.
• Show only what they bought. If a customer didn't buy a module, its tasks shouldn't appear. Cutting irrelevant lines keeps the checklist honest.
• Put a date on every item, not just an owner. A task with an owner but no date drifts. Anchor the checklist to the target go-live and work backward.
• Name the segment. The wording differs slightly for a marketing agency onboarding a retainer client, a fintech running a security-heavy implementation, or an HR SaaS setting up payroll – but the five phases hold across B2B software.

Give the customer a reason to prioritize it

A checklist tells the customer what to do. It doesn't tell them why to do it this week – and that gap is where most onboarding time disappears. When teams look closely at where the weeks went, in our experience the large majority of the delay sits on the customer's side: decisions not made, data not sent, people not assigned. It's tempting to read that as the customer not caring. It's usually the opposite. They're afraid of setting something up wrong and having to live with it, and someone who's afraid of deciding wrong decides slowly, or not at all.

So urgency has to be designed in, not chased afterwards. The levers that actually move it:

• Commercial levers – the most underused of the set. Bill from closed-won rather than go-live, sell implementation as a time-boxed package with a fixed start and end, or run onboarding in cohorts. When delay costs the customer something, it stops being free.
• Deadlines that were agreed, not implied. A date in your project plan is a hope. A date both sides said out loud at kickoff and wrote down is a commitment.
• A quick win in the first 48 hours. Enthusiasm peaks at signature and decays every quiet day after, so put something real and visible in front of them before it drops.
• Executive sponsorship, kept aware of risk. A weekly update that names what slips if a blocker isn't cleared reaches the person who can actually clear it.
• Progress the customer's boss can see. Visible momentum is its own motivator, on both sides of the table.

The test: if your answer to a stalled task is another reminder, you're chasing where a default, a deadline or an incentive would have done the work for you.

Where a static checklist falls short

A checklist in a Google Doc, a spreadsheet, or a project board like Monday.com, Asana, or Notion has the same three problems, no matter how good the list is. It's internal-only, so the customer can't see it and you end up re-typing status into emails. It goes stale the moment a task moves, because nobody updates the doc in real time. And it can't chase anyone – the customer-side tasks that stall onboarding (data, access, security review) sit there until someone manually follows up.

That's the real difference between a checklist and a process: the list tells you what to do; the process makes sure it actually happens, on both sides. General-purpose tools coordinate your team well but were never built to be shared with the customer, which is exactly where onboarding gets stuck. For the fuller version of this argument, see how to catch stalled onboardings before they churn.

Run the checklist as a living, shared space

The fix is to run the checklist as something the customer opens and works with you, not a file you email around. That's what a customer onboarding platform does, and if you are still comparing them, our guide to the best customer onboarding software weighs 14 tools across five categories. Valuecase is built around exactly this: you build the checklist above once as a reusable template, then spin up a personalized, branded Space per customer – the single place the customer opens from a link, no login required, that holds the checklist, intake forms, training content, and chat.

From there, the parts a static list can't do happen automatically:

• Tasks are assigned to named people on both sides, including the customer, so nothing belongs to "the team." With several stakeholders in play, each person sees just the tasks they own.
• You can chat directly on a task, with the right stakeholders, instead of a long email thread everyone's copied on. When a customer has a question about the security review or a data upload, the conversation happens on that task – so context stays with the work.
• Automated reminders chase open tasks, so your CSM isn't manually following up on every stalled item.
• Engagement tracking flags at-risk accounts across every active onboarding in one dashboard, so you see which customer went quiet before it becomes a renewal problem.
• Activity syncs to HubSpot and Salesforce, so the checklist status lives in your CRM too.

Because it ships an embedded AI agent (with MCP support, so Claude or ChatGPT can plug in), you can also have AI draft a tailored checklist from your template, add a go-live readiness checklist, build a full customer onboarding hub, or chase customers on open tasks for you – see the full library of AI onboarding use cases.

If you'd rather start from a worked example than build from scratch, the template gallery has ready-made onboarding workspaces – checklists included – by use case, including agency, HR SaaS, hardware, and cybersecurity SaaS.

FAQ

What's on a customer onboarding checklist?

A customer onboarding checklist covers the tasks that take a customer from signed to live, grouped by phase: pre-kickoff (draft the setup, set up the space, book the kickoff), kickoff (confirm success criteria, map stakeholders, agree the plan), implementation (collect data and access, configure, integrate, QA), go-live (train, run a readiness check, go live, confirm first value), and adoption (confirm usage, collect feedback, hand off to customer success). Every item should have a named owner and an agreed date.

Is there a free onboarding checklist?

Yes – the phase-by-phase checklist on this page is free to copy and adapt. You can keep it in a doc or spreadsheet, but it works far better as a shared, customer-facing space the customer can see and act on directly. The template gallery also has free, ready-made onboarding workspaces with checklists built in, by industry.

What are the phases of customer onboarding?

Most B2B software onboarding moves through five phases: kickoff and alignment, data and access collection, implementation and configuration, go-live and first value, and adoption and handoff to customer success. A checklist is the concrete tasks inside those phases; the phases give it shape and exit criteria. For the full framework, see the five stages of customer onboarding.

Want to run this checklist as a shared workspace instead of a doc? See Valuecase for onboarding or start a free trial.