User onboarding guideUser onboarding that gets people to value.
What happens between sign-up and the first real result decides whether a new user comes back. This guide covers the onboarding flow, the kinds of help you can give, the two numbers to watch, and where an in-app AI agent fits.
What user onboarding is for
People sign up because they want a result: a booking page that works, a project with the team in it, a first invoice sent. User onboarding is everything that gets them from the empty account to that result. The product, its first screens, the help it gives and the messages that follow are all part of it.
The moment a new user first gets that result is your activation event. Onboarding works when more of your sign-ups reach it, and reach it sooner. Everything below serves one of those two.
The user onboarding flow, step by step
Most SaaS onboarding flows have the same shape, whatever the product does:
- Step 1Sign upOnly what you need to create the account
- Step 2First screenOne clear first step, not a tour of everything
- Step 3SetupThe minimum the product needs: a project, an import, an invite
- Step 4First resultThe activation event
- Step 5HabitThe next feature, and coming back
Walk through yours as a new user, with a fresh email, and write down every step between sign-up and the first result. Each step is a place someone can stop. The setup step is usually the longest, and it is where most of the work pays off: fewer fields, sensible defaults, sample data, and help right where the question comes up.
Our user onboarding checklist turns this into 21 checks you can tick off for your own product.
The kinds of onboarding help
There are four common ways to help new users through that flow. They suit different moments, and many products use more than one.
Welcome screens and checklists
Good for: setting expectations and showing the handful of steps that matter, with progress a user can see. Where it stops: it lists the steps; the user still does each one.
Product tours
Good for: pointing out where the important things are, on a fixed path you design. Where it stops: it follows the path someone recorded, and needs updating when those screens change.
Help articles and support chat
Good for: answering questions in depth, with a person available for the hard ones. Where it stops: the user reads the answer and then does the steps, or waits for a reply.
An in-app AI agent
Good for: the “how do I” and “set this up for me” moments, in whatever words the user has. It does the steps in the product while the user watches. Where it stops: it moves through real pages, so it takes seconds rather than being instant, and anything that sends, spends or deletes goes back to the user to confirm.
The two numbers to watch
Activation rate is the share of sign-ups who reach your activation event, in a fixed window such as their first 7 days. Time to value is how long that takes. Measure both before and after every onboarding change, against your own previous weeks.
Work out your rate, and what each extra point is worth, with the free activation rate calculator. If your support queue is full of setup questions, the support ticket cost calculator shows what they cost.
Where Stiro fits
Stiro is an in-app AI agent for the setup step. A new user says what they want, such as “set up my first project and invite my team”, and Stiro clicks, types and navigates your product to do it while they watch.
- Nothing to record or train. One script tag in your app’s layout. It reads the live screen, so it keeps working as your onboarding changes.
- The user keeps the final say. Anything that sends, spends or deletes is prepared and handed back for them to press.
- It says so when it can’t. If your product can’t do what was asked, it stops and explains, and the user can message your team from the same panel.
- everyday requests passed, cold, in three apps it had never seen
- 44 of 44
- to set Saturday hours in Cal.com, filmed in real time
- 14 s
See how it works for new accounts on the AI onboarding page, or watch a real request from start to finish.
User onboarding questions.
What is user onboarding?
User onboarding is everything that takes a new user from signing up to getting real value from your product: the first screens, the setup, the help along the way and the nudges in the first weeks. Good onboarding gets more of your sign-ups to that moment, sooner.
What is a user onboarding flow?
The sequence of steps a new user goes through after sign-up: a welcome, the setup that product needs (a profile, a first project, an import, an integration), the first real result, and what comes next. Mapping it step by step shows where people stop.
What is the difference between user onboarding and customer onboarding?
Customer onboarding covers a whole account: kick-off, contracts, data migration and training, often with a person on your side. User onboarding is each user’s own path inside the product. Self-serve products rely mostly on user onboarding; larger accounts need both.
What makes onboarding good?
A short, obvious path to the first result, screens that explain themselves, help at the exact moment someone is stuck, and confirmation before anything with consequences. Then measurement: activation rate and time to value, checked after every change.
What tools help with user onboarding?
Welcome screens and checklists, product tours, help articles and support chat, and in-app AI agents that do the steps for the user. Each suits a different kind of moment; many products use more than one.
How does AI help with user onboarding?
An in-app AI agent lets a new user say what they want set up, in their own words, and does the steps in the product while they watch. It covers the questions nobody scripted a tour for, and it keeps working when the screens change.
Let your users just ask.
Stiro does the steps in your app for your users. One script tag, 50 runs a month free, no card.