SaaS Customer Onboarding Checklist (Free 30-Day Template)

A new user signs up, logs in, and lands on an empty dashboard. They don’t know what to do next. Three days later, they’re gone, and your team never finds out why.

This happens more than most teams think. In a Wyzowl survey, 63% of people said the support they expect after buying is an important part of deciding to buy at all. And 86% said they’d stay more loyal to a business that welcomes and teaches them after they sign up.

Below is the full checklist first, ready to copy. After it, we explain each phase and the design mistakes that stop users from getting started.

SaaS Customer Onboarding Checklist Template (Free)

Use this checklist as your team’s to-do list for every new account. Copy the tables below, or grab the free Google Sheet at the end of this section, which fills in due dates for you and tracks progress as you go.

Phase 1: Before Day 1 (Setup)

Phase 2: Days 1 to 3 (First Win)

Phase 3: Days 4 to 14 (Feature Adoption)

Phase 4: Days 15 to 30+ (Success Milestones)

Copy this into Google Sheets, Notion or Asana and run it for every new account. Change the owners to match your team. The tasks stay the same for most products. What changes is your first-win action and your Day 30 goal. A construction SaaS and a healthcare scheduling SaaS can both run this list, but their first win looks completely different. If you sell to one industry, see how vertical SaaS products change this.

Get the free Google Sheets template →

What a SaaS Customer Onboarding Checklist Actually Covers

A SaaS customer onboarding checklist is a structured, phase-by-phase task list that defines who does what, when they do it, and how the team confirms completion. It covers everything from pre-login account configuration to the Day 30 health score that predicts renewal.

Without that structure, onboarding becomes whatever the last sales call promised, followed by a welcome email, followed by silence. That silence is where trial churn lives. If you want the why behind each step first, our SaaS customer onboarding guide covers it.

"A checklist without phases is a to-do list. A phase-gated checklist is a retention system."

Here is how the four phases break down:

Each phase feeds the next. A broken pre-setup means users arrive at a blank screen. A skipped adoption phase means users activate once and never return. The checklist is what stops each handoff from turning into a drop-off. This page is the hands-on task list. For the strategy and design thinking behind each phase, read our SaaS customer onboarding guide.

Phase 1: Pre-Onboarding Setup Checklist (Before Day One)

The pre-onboarding phase is everything your team completes before the user sees the product. New customers should never arrive at an unconfigured workspace. They signed up to experience value, and your job is to make sure value is ready on the other side of login. This phase is invisible to the user, but it determines whether Day 1 feels smooth or confusing.

Account Configuration

Before the first login, complete every item in this block:

• Create the account with the correct role and permissions

• Pre-populate demo data or a starter project matching their stated use case

• Connect integrations confirmed during sales (CRM, Slack, SSO)

• Configure default views and workspace settings for their team size

• Set up role-based access if the account includes multiple team members

Every skipped item here shows up as friction in the user's first session. They do not know your team skipped it. They only know the product feels incomplete.

Welcome Asset and Segmentation Routing

Sorting accounts before Day 1 means every user gets the right path from the first email. Assign every new account to the right track before the welcome email goes out:

• Assign to the correct onboarding track: self-serve, sales-assisted, or enterprise

• Tag with industry, use case, and expected time-to-value

• Route to the right CSM or onboarding specialist based on deal size

• Schedule the Day 3 automated check-in or CSM call

• Prepare a personalized welcome email with the first three steps only, not ten

Tip: One welcome email, three steps, one clear first action. Every extra link cuts click-through rates. That constraint alone improves Day 1 activation.

"The pre-onboarding phase sets the ceiling for every metric that follows. Whatever you configure here is the best experience the user can have."

The SaaS landing page design guide shows how pre-signup clarity also reduces setup friction. When users arrive having already seen clear product framing, the pre-onboarding phase runs faster because expectations match reality.

Pre-setup shapes the ceiling. The next phase is where users actually experience it.

Phase 2: Welcome and Activation Checklist (Days 1–3)

Activation is the moment a user reaches their first real value inside the product. In product-led SaaS, this moment does most of the selling, because users decide to stay based on what happens in their first session.

The welcome and activation phase has one job: move the user from login to first value in under five minutes.

Hitting that window consistently is rarely accidental - it's usually the result of deliberate SaaS onboarding flow design, tested against real activation data.

First Login Experience

The first session is the highest-stakes UX moment in the product. Every element on screen points toward the core action or away from it:

• Trigger a welcome modal with three clear next steps, not ten
• Show an in-product setup progress bar or completion checklist
• Surface the core feature first, keeping everything else behind it
• Ask one onboarding question on entry: "What are you trying to do first?" and route based on the answer
• Suppress advanced features until the user completes the core use case setup

Slack does this well. Its setup pushes you to invite a teammate before anything else, because Slack is useless without one. The lesson: narrow the path, and the first win comes faster.

For the interface-level decisions behind this kind of activation design, the SaaS UX design guide covers how information hierarchy controls whether users find the core action or wander through the dashboard.

Day 3: The Critical Check-In

Day 3 is the highest-risk point in the trial. Users who have not returned by Day 3 are unlikely to activate at all. This check-in is not a follow-up: it is the last reliable intervention point before the user goes dark:

• Send a Day 3 email: "Did you [activation event]? Here is what is next."
• Trigger a single-question pulse survey if the user completed activation: "How was setup?"
• Flag non-activated users for immediate CSM outreach
• Log activation status in the CRM or health score dashboard

"Day 3 is where you convert the users who were undecided, not just the ones who would have converted anyway."

A short, timely nudge on Day 3 reaches users while they still remember why they signed up. That lift compounds across every cohort.

Before you redesign your first-login flow, check it against these common SaaS UX mistakes. Most activation problems start there.

Phase 3: Feature Adoption Checklist (Days 4–14)

Feature adoption is the phase where onboarding checklists stop being used. The pre-setup was clean. Activation went fine. Then the user comes back on Day 6, opens the product, and finds nothing guiding them toward a second action. By Day 10, they have opened the app twice and quietly decided it is not worth the effort.

The adoption phase covers the two weeks after activation. Its job is to build a second habit, then a third.

Product-Side Adoption Nudges

These items live inside the product experience itself. Each one surfaces value the user has not found yet:

• Trigger a contextual prompt for the second core feature once the first is used
• Design empty states that show a completed state, not just "No data yet"
• Add a progress tracker: "You have set up 3 of 5 features your team type typically uses"
• Build a session-based nudge for any key feature unused after 5 logins
• Show a "teams like yours use this for..." prompt during the second session

Notion's empty page state shows a template gallery above the fold. Airtable fills new workspaces with a demo project matching the user's stated use case. Both products replace "nothing here" with "here is what this could look like." That design choice is what drives sessions two and three.

The SaaS dashboard design complete guide breaks down how empty states, defaults, and progressive disclosure work together in the first-session product experience.

Communication Sequence

The email side of adoption matters as much as the product side:

• Day 7 email: one specific use case the user has not tried yet, not a feature roundup
• Day 10 email: a real customer story from a similar company
• Day 12 flag: if fewer than 3 sessions logged, move account to at-risk segment
• CSM personal email to at-risk accounts: a specific offer to help, not a demo invitation
• Push or Slack notification for mobile users when a feature is relevant to recent activity

"A Day 7 email showing one real use case outperforms a feature roundup email every time. Specificity is the conversion driver, not comprehensiveness."

Emails tied to what the user actually did in the product beat a fixed schedule. Contextual beats generic every time.

Users who reach their aha moment in these first two weeks are the ones most likely to still be around at Day 90.

Phase 4: Success Milestones Checklist (Days 15–30+)

Onboarding does not end at Day 14. A user who has adopted core features still needs a structured milestone review to confirm they are getting real, measurable value from the product. This is the phase where churn is either reversed or locked in permanently.

The success milestone phase has two outputs: a health score and a renewal signal. Both sit at the retention stage of the B2B SaaS customer journey, and every item below feeds one of them.

Health Scoring and At-Risk Flags

Define what healthy usage looks like before building the score:

• Define the activation event: the one action that predicts 90-day retention
• Define the success milestone: the event that predicts renewal
• Build a health score from three inputs: logins per week, core feature usage, team seats filled
• Flag any account scoring below 60 for CSM intervention within 48 hours
• Send an automated intervention message to at-risk accounts: one specific resource, one specific offer

The point of a health score is timing. It lets you catch at-risk accounts before they cancel, not after. That improvement is the compounded effect of catching at-risk accounts before they churn instead of after they cancel.

Day 30 Renewal Signals

The Day 30 review is not a formality. It is the moment you prove ROI before the renewal conversation starts:

• Send a 30-day usage summary: "Here is what your team accomplished with [Product]"
• Request a testimonial or case study from high-engagement accounts
• Book a quarterly business review for enterprise accounts
• Share the product roadmap and invite active users to a feedback session
• Review the three core renewal signals: weekly active users growing, over 50% of seats filled, core feature used at least 3 times per week

"A 30-day summary email is not a thank-you note. It is proof of ROI delivered before anyone asks for it."

The mobile app retention guide shows how the same Day 14 and Day 30 milestone checkpoints apply to mobile SaaS products, where return windows are shorter and the cost of missing them is higher.

Onboarding Screens Checklist: What New Users Should See

The checklist above is what your team does. This part is what your user sees. Most onboarding problems show up on these screens first, so check each one in your own product.

Keep the setup list short. Userpilot’s benchmark report found the average onboarding checklist completion rate is just 19.2%. Fewer steps, each one a real win, is how you beat that number.

Fix these screens in order, from the top. A broken signup form makes every screen after it matter less.

The Onboarding Design Mistakes That Kill Activation

Three design patterns cause the same activation failures across SaaS products. They are invisible to the product team building them and obvious to every user who churns in week one.

Mistake 1: The 10-Step Feature Tour

A product tour covering 10 features on Day 1 is not onboarding. It is a feature dump. Users watch it politely and retain almost nothing, because passive exposure does not build product habits. Most users click “Next” until the tour ends, then start from zero.

Fix it: replace the tour with a three-step setup wizard. Three steps, three specific outcomes, and the user reaches the first value at step three.

Mistake 2: Empty States That Give No Direction

An empty dashboard tells your product team "the user has not added data yet." It tells the user "I have no idea what to do here." Figma shows a blank canvas with three starter templates on first open. Airtable fills new bases with a demo project. Every SaaS product with strong trial conversion turns the empty state into a demonstration of what value looks like.

For teams rebuilding their first-session experience, the B2B SaaS dashboard design examples guide shows how dashboard structure at the interface level drives or kills first-session activation.

Mistake 3: Treating Activation as a One-Time Event

A user who activates on Day 1 but receives no Day 7 check-in churns quietly around Day 20. They do not cancel. They just stop logging in. The product team sees a login metric drop and runs another activation campaign, but the problem was never activation: it was adoption.

"The fix is never a prettier onboarding screen. It is a shorter, clearer path to first value, followed by a system that keeps users coming back after they find it."

These are design problems as much as process problems. The interface decisions made in sessions one through five determine whether there is a session six. That is where product design does more work than any email sequence.

For SaaS teams reviewing their product's current design patterns, the SaaS product design trends guide covers how leading products are restructuring their onboarding flows in 2026, moving away from feature tours and toward outcome-based activation journeys.

Acquiring a new customer can cost 5 to 25 times more than keeping an existing one, according to Harvard Business Review. Every activation failure in week one is not just a lost trial: it is a full acquisition cost with zero return.

Frequently Asked Questions

What should a SaaS customer onboarding checklist include?

A SaaS customer onboarding checklist should cover four phases: setup before Day 1, the first win in Days 1 to 3, feature adoption in Days 4 to 14, and success milestones from Day 15 onward. Each task needs an owner, a due day and a clear “done when” check, so nothing gets lost between teams.

Is there a free SaaS customer onboarding checklist template?

Yes. The template at the top of this page is free to copy. It has 24 tasks across four phases, each with an owner, a due day and a “done when” check. Copy it into Google Sheets, Notion or Asana and change the owners to match your team.

How long should SaaS customer onboarding take?

Plan for 30 days for standard accounts and 60 to 90 days for enterprise. Users should reach their first real win within the first three days. For self-serve products, aim for that first win in under five minutes.

Who should own the SaaS customer onboarding checklist?

One named person per account, usually a customer success manager. In self-serve products, a product or growth manager owns the in-app steps and marketing owns the emails. Without one clear owner, tasks fall through the gaps between teams.

What is the difference between a customer onboarding checklist and an in-app checklist?

A customer onboarding checklist is your team’s task list for every new account: setup, emails, calls and health checks. An in-app checklist is the short list of steps a user sees inside the product. You need both, and the in-app list is one task on the team checklist.

How do you measure SaaS onboarding success?

Track four numbers: time to first win, Day 14 retention, health score at Day 30, and trial-to-paid conversion. Measure them for each onboarding track (self-serve, sales-assisted and enterprise), because one blended average hides where users drop off.

How do you reduce churn during SaaS onboarding?

Flag at-risk users early: any account with fewer than 3 sessions by Day 12. Send them a personal email with a specific offer to help, not a demo link. Replace empty screens with examples, and review a health score at Day 15 so you catch at-risk accounts before they cancel.

Final Thoughts

A SaaS customer onboarding checklist works when it is treated as a four-phase system, not a series of one-off emails. Each phase has an owner. Each milestone has a done state. The gap in your current checklist is the churn you cannot explain.

Copy the free template at the top of this page and map your current onboarding against it. Find the first phase where nobody owns the outcome. That is the fix that moves your conversion rate.

Ready to design the product experience behind your onboarding system? See how Orbix Studio approaches SaaS design ->