SaaS Onboarding: Process, Best Practices, Checklist and Examples
by GainHQ Editorial Team | Jun 4, 2026 | SaaS | Editorial policy
Table of Contents
SaaS onboarding is the process that takes a new user or customer from sign-up (or contract signature) to the first moment the product delivers real value, and then on to regular use. Good onboarding shortens that path, removes setup work the customer should not have to do, and makes the next step obvious at every stage.
This guide explains what SaaS onboarding covers, how the process works for self-serve and enterprise products, the best practices that hold up against research, a 30-day checklist, the metrics to track and examples taken from real products' own documentation. It is about onboarding customers and users of software, not employee onboarding.
What is SaaS onboarding?
SaaS onboarding is everything a software company does to help a new account start getting value from its product: sign-up, setup, first use, guidance and follow-up. Its goal is activation, meaning the customer completes the action that shows the product working for them, followed by repeat use. If you need a refresher on the delivery model itself, see what SaaS is.
Onboarding matters because buyers weigh it before they buy. In a Wyzowl survey of 216 people in early 2020, 63% of customers said that onboarding, meaning the level of support they are likely to receive after the sale, is an important consideration in whether they decide to buy in the first place, and 86% said they would be more likely to stay loyal to a business that invests in onboarding content that welcomes and educates them after they have bought. The survey is consumer-wide and from 2020, so treat it as directional rather than a SaaS benchmark. Retention is where onboarding pays off: research by Frederick Reichheld of Bain & Company, reported in Harvard Business Review, found that increasing customer retention rates by 5% increases profits by 25% to 95%.
User onboarding vs customer onboarding
User onboarding is about one person learning the product: the first login, the first task, the first result. Customer onboarding is about the whole account: contract handover, configuration, data migration, integrations, training and a go-live date. In self-serve products the two are often the same person. In B2B the buyer, the admin and the daily users are usually different people, so you need a plan for each.
| User onboarding | Customer onboarding | |
|---|---|---|
| Who | An individual user | The account (buyer, admin, team) |
| Goal | First personal success, then habit | Account live and adopted across the team |
| Typical owner | Product and design | Customer success or implementation team |
| Main tools | In-app guidance, empty states, emails | Kick-off call, onboarding plan, migration, training |
| Done when | User completes the activation event | Account reaches agreed go-live and adoption targets |
Self-serve, high-touch and hybrid onboarding
Self-serve (low-touch) onboarding relies on the product, emails and help docs, with no human required. High-touch onboarding assigns people to guide each account and is common in enterprise B2B, where setup involves SSO, permissions, data migration and several teams. Most growing B2B products end up hybrid: self-serve for small accounts and human help for large or complex ones.
| Factor | Self-serve | High-touch (enterprise) | Hybrid |
|---|---|---|---|
| Account size and value | Small, many accounts | Large, fewer accounts | Mixed |
| Setup complexity | Low: works in minutes | High: SSO, roles, migration, integrations | Varies by plan |
| Who drives progress | The user | A named onboarding or CS manager | Product by default, people on trigger |
| Success measure | Activation rate, time to value | Time to go-live, seat adoption | Both, split by segment |
| Real-world example | Notion starter templates | HubSpot paid onboarding plans | Stripe sandboxes plus partner access |
The SaaS onboarding process: 6 stages
The SaaS onboarding process runs in six stages: handover or sign-up, welcome, setup, first value, adoption, and review. Each stage has one job and one signal that it is done. Defining the activation event up front, ideally in your product requirements document, keeps product, design and customer success aiming at the same moment.
- Handover or sign-up. For self-serve, this is the sign-up form. For sales-led B2B, it is the handover from sales to the onboarding team, including what the customer was promised and why they bought.
- Welcome. Confirm the account, set expectations and ask one or two questions (role, main goal) that let you tailor what comes next.
- Setup. Import data, connect integrations, invite teammates and configure permissions. This is where most friction lives, so remove every step you can.
- First value (activation). The user completes the action that proves the product works for them, such as sending a first invoice, resolving a first ticket or running a first test payment.
- Adoption. Repeat use and wider use: more teammates, more features, a weekly habit. In B2B, this is where seat adoption is measured.
- Review. Check results against the goals set at the start. For enterprise accounts this is often a 30, 60 or 90 day review; for self-serve it is a cohort review of your metrics.
SaaS onboarding best practices
The best practices below share one principle: get each user to their first real result as fast as possible, then guide the next step only when it is needed. They are drawn from usability research and accessibility standards rather than opinion, and they apply to self-serve and enterprise products alike.
1. Define one activation event per segment
Pick a single, observable action that predicts long-term use, and set a time window for it (for example, "creates and shares a first report within 7 days"). Different segments can have different events. An admin's first success may be "SSO configured"; an end user's may be "first task completed". Without this, onboarding work cannot be measured.
2. Shorten sign-up and setup
Ask only for what you need to create the account, and defer everything else until it is needed. Import existing data so users do not start from nothing. WCAG 2.2, published in October 2023, sets rules that apply directly here: Redundant Entry (3.3.7) means not asking for information the user already gave in the same process, and Accessible Authentication (3.3.8) means login must not depend on a cognitive test, such as memorising or transcribing, without an alternative.
3. Prefer contextual help over up-front tours
Nielsen Norman Group's review of onboarding tutorials vs contextual help found that tutorials interrupt users, are often skipped and quickly forgotten, and are "dramatically overused". Contextual help that appears when the user reaches a feature works better. Keep tours for genuinely new interaction patterns, make help easy to dismiss and recall, and skip the obvious.
4. Design empty states as starting points
The first screen a new user sees is usually empty. Nielsen Norman Group's empty state guidelines recommend using empty states to show system status, teach what the area is for, and give a direct path to the key task, such as a button to create the first item, import data or explore sample data.
5. Personalise with a short welcome question
One or two questions about role and goal let you route users to the right first task, template or checklist. Ask only what you will actually use, and tell users why you are asking.
6. Segment human help by account value and complexity
Reserve calls, kick-offs and migration help for accounts where setup is complex or the account value justifies the cost. Use behaviour triggers (for example, "invited no teammates after 5 days") to bring a person in for self-serve accounts that stall.
7. Keep help in one predictable place
WCAG 2.2's Consistent Help criterion (3.2.6) requires help mechanisms that repeat across pages, such as a help link, chat or contact details, to appear in the same relative order. Users who get stuck during setup should never have to hunt for help.
8. Use email to bring users back to the next unfinished step
Onboarding emails work best when triggered by behaviour, not by a fixed calendar. Each email should point to one next step the user has not yet done.
9. Build onboarding into the product, not on top of it
Onboarding is a product decision as much as a marketing one. Sample data, templates, sensible defaults and import tools are built into the product, so plan them alongside core features. Our guides to B2B SaaS product development and the role of UX in reducing SaaS churn cover how these decisions affect retention.
10. Do not skip security setup for enterprise accounts
For B2B accounts, SSO, roles and permissions are part of onboarding, not an afterthought. Getting admins through them quickly, and safely, unblocks everyone else. See our SaaS security best practices for what to cover.
SaaS onboarding checklist (first 30 days)
Use this checklist as a template for the first 30 days of a new account. Each row has an owner and a "done when" test, so you can tell whether it is finished rather than just started.
| When | Task | Owner | Done when |
|---|---|---|---|
| Before launch | Define the activation event and time window per segment | Product | Written down and tracked as an event |
| Before launch | Instrument each onboarding step as an event | Engineering | Every step appears in your analytics funnel |
| Before launch | Record baseline activation rate and time to value | Product / data | Baseline numbers saved for comparison |
| Day 0 | Short sign-up; no repeated fields; accessible login | Product / design | Form asks only what account creation needs (WCAG 2.2 3.3.7, 3.3.8) |
| Day 0 | Welcome message plus one or two routing questions | Product / marketing | Answers change what the user sees next |
| Day 0 | Empty states with a direct path to the first task | Design | Every empty screen has a primary action |
| Days 1–7 | Data import or sample data available | Product | User can see their own (or sample) data on first login |
| Days 1–7 | Prompt to invite teammates (team products) | Product | Invite flow reachable from the first-value screen |
| Days 1–7 | Behaviour-triggered emails to the next unfinished step | Marketing / CS | Each email maps to one missing step |
| Days 1–7 | Enterprise only: kick-off, SSO, roles, migration plan | Customer success | Admin setup complete; go-live date agreed |
| Days 8–30 | Contextual help for second-tier features | Product / design | Help appears when the feature is first used |
| Days 8–30 | Human outreach for stalled accounts | Customer success | Trigger rules defined and running |
| Day 30 | Review metrics by cohort and segment | Product / CS | Activation, TTV and retention compared with baseline |
| Day 30 | Ask one feedback question about onboarding | Product / CS | Responses reviewed and logged |
SaaS onboarding metrics
The core SaaS onboarding metrics are activation rate, time to value, onboarding completion rate, early retention and early support load. Track them by sign-up cohort and segment, because an average across all users hides the segments that are struggling. A custom dashboard that shows these by cohort makes weekly review practical.
| Metric | Formula | What it tells you |
|---|---|---|
| Activation rate | Users who complete the activation event within the window ÷ new sign-ups in the cohort × 100 | Whether onboarding gets people to first value |
| Time to value (TTV) | Time from sign-up (or contract signature) to the activation event; report the median | How long first value takes |
| Onboarding completion rate | Users who finish all onboarding steps (or checklist tasks) ÷ users who started or saw onboarding × 100 | Whether the guided path is followed to the end |
| Early retention | Users from the cohort still active in week 4 (or month 1) ÷ cohort size × 100 | Whether first value turns into a habit |
| Early support load | Support tickets from new accounts in the first 30 days ÷ new accounts | Where users get stuck |
| Enterprise: time to go-live | Contract signature to agreed go-live | Whether high-touch onboarding stays on schedule |
Worked example (illustrative, not GainHQ data). A product gets 400 sign-ups in one week. 148 complete the activation event within 7 days, so the activation rate is 148 ÷ 400 = 37%. Of 1,000 users shown a 5-task checklist over a month, 190 complete it, a 19% completion rate. In a sample of ten activated users, time to value is 0.5, 1, 1, 2, 3, 3, 4, 6, 9 and 14 days: the median is 3 days, while the mean is 4.35 days because two slow users pull it up. That is why TTV is best reported as a median. If 92 of the 400 users are still active in week 4, early retention is 23%. If 120 new accounts raise 66 tickets in their first 30 days, the support load is 0.55 tickets per account.
What good looks like: published benchmarks
Benchmarks vary widely by product and definition, so your own baseline matters more than any industry number. One published benchmark gives a useful reference point for activation:
- Activation rate: Userpilot's SaaS product metrics benchmark, based on data from 62 B2B companies, reports an average of 37.5% and a median of 37%, with wide gaps by industry (54.8% for AI and ML, 42.6% for CRM and sales, 8.3% for HR).
The data comes from customers of one onboarding vendor, the data period is not stated, and each company defines activation differently. Use it as a sense check, not a target. We have not found a published onboarding completion benchmark with a verifiable source and sample size, so track completion against your own baseline.
How to measure and improve onboarding
Start with a funnel from sign-up to activation, built from the events you instrumented, and find the step with the largest drop. Watch a handful of real users go through that step, or review session recordings, to see why they stop. Change one thing at a time and compare the next cohort against your baseline, ideally with a holdout group that does not see the change. Repeat monthly.
SaaS onboarding examples from real products
The examples below describe what each company documents in its own help centre or service pages, so you can check them at the source. They show different onboarding models rather than one right answer.
- Notion: templates chosen from onboarding answers. Notion's help centre says new workspaces include starter templates in the sidebar, selected from the answers given during onboarding, and users can delete any they do not want. It is a simple form of personalisation that also solves the empty-workspace problem.
- Stripe: a safe place to reach first value. Stripe's sandboxes let teams test payments without real money moving, and let them invite outside users, such as an implementation partner, without giving access to live data. Developers can see the product work before anything is at risk.
- HubSpot: paid, high-touch onboarding. HubSpot sells onboarding services in which it builds a customised onboarding plan with the customer around their goals, the products they bought and their existing tech stack. It is a clear example of high-touch customer onboarding sold alongside the software.
- Slack: teach the core concept first. Slack's quick start guide describes channels as fundamental to working in Slack and walks new users through the sidebar, channels and the message field before tools and automations.
- Gain.io: no empty queue on day one. Gain.io, the CRM and helpdesk built in-house at GainHQ, states on its website that it imports tickets and history as a one-time migration during onboarding, so teams are not starting from an empty queue.
- Payrun: import to get started. Payrun, GainHQ's HR and payroll product, describes on its website a data import that brings in an organisation's previous data to get started quickly.
Common SaaS onboarding mistakes
Most onboarding problems come from asking too much too early or leaving users with nothing to do next. These are the mistakes to check for first:
| Mistake | Why it hurts | Fix |
|---|---|---|
| No defined activation event | Nobody can tell if onboarding works | Pick one event and window per segment |
| Long sign-up forms | Users drop before they see the product | Ask only what account creation needs |
| Long up-front product tours | Skipped and forgotten (NN/g) | Contextual help at the point of use |
| Blank first screen | No obvious next step | Empty state with a direct action, sample data or import |
| Same journey for every user | Admins and end users need different first steps | Route by role or goal |
| Calendar-based emails | Emails ignore what the user already did | Trigger by behaviour |
| Help hidden or moving around | Stuck users give up | Consistent help location (WCAG 2.2 3.2.6) |
| Treating onboarding as finished at sign-up | Adoption stalls after first use | Track week-4 retention and adoption |
How GainHQ can help
GainHQ is a software development company with more than 15 years of experience building software, 13+ products and a team of 30+ people. We build our own SaaS products, including Gain.io (CRM and helpdesk) and Payrun (HR and payroll), so onboarding flows, data import, permissions and analytics are part of the work we do every day. If you are building or rebuilding a SaaS product and want onboarding designed into it from the start, see our services, including SaaS solutions, UI/UX design and MVP development.
Frequently asked questions
What is SaaS onboarding?
SaaS onboarding is the process that takes a new user or customer from sign-up to their first real result with the product, then to regular use. It covers sign-up, setup, data import, in-app guidance, emails and, for larger accounts, human-led training and go-live planning.
What are the stages of the SaaS onboarding process?
A typical process has six stages: sign-up or sales handover, welcome, setup, first value (activation), adoption and review. Each stage should have one job and a clear signal that it is done, such as the user completing the activation event.
What is the difference between user onboarding and customer onboarding?
User onboarding helps one person learn the product and reach first success. Customer onboarding gets a whole account live: contract handover, configuration, migration, integrations and training. In B2B, the buyer, admin and daily users are often different people, so each needs its own path.
What is a good onboarding completion rate for a SaaS app?
There is no reliable universal target, because products define "completion" differently. Measure users who finish all onboarding steps divided by users who started, set your own baseline, and improve it cohort by cohort. Completion only matters if it leads to activation, so track both together.
What is a good activation rate for SaaS?
Userpilot's 2024 benchmark of 62 B2B companies reported an average activation rate of 37.5% and a median of 37%, with large differences by industry. Because each company defines activation differently, improving your own rate cohort by cohort matters more than matching an average.
How long should SaaS onboarding take?
Self-serve onboarding should get users to first value in their first session or first few days; track it as median time to value. Enterprise onboarding is usually planned around an agreed go-live date with 30, 60 or 90 day reviews. Onboarding ends when the account is regularly using the product.
What should a SaaS onboarding checklist include?
It should include a defined activation event, tracked onboarding steps, a short sign-up, routing questions, empty states with clear actions, data import or sample data, teammate invites, behaviour-triggered emails, enterprise admin setup and a 30-day metrics review.
What are some examples of effective SaaS onboarding experiences?
Notion adds starter templates to new workspaces based on onboarding answers. Stripe offers sandboxes to test payments without real money. HubSpot sells guided onboarding plans built around customer goals. Slack's quick start guide teaches channels first. Each matches its onboarding model to its product and customer.