19 Onboarding Flow Examples, and When to Use Each

TL;DR

Nineteen onboarding flow examples, grouped by the job they do, with what each one is for and how many steps it takes. All of them live in the onboarding flow templates library, and all of them are built with Product Fruits Flows.

They exist because most onboarding never ships. Teams know the principles — react to who the user is, wait for the right moment, don't stop at the welcome tour — and then stall on turning that into a working sequence of cards, conditions and waits. Starting from an empty canvas is where good intentions go to die.

• Get the first run right — five for personalising the first session
• Turn first use into habit — four for the gap between "tried it" and "relies on it"
• Catch people when they stall — four for the highest-intent moment you'll get
• Learn why people leave — three for capturing the reason while it's fresh
• Grow the account — three that run on customers you already have

Each is a complete working flow, not a wireframe. The shortest is four steps and can be live this afternoon.

What good onboarding actually does

Three things separate onboarding that works from onboarding that gets dismissed. For the wider picture — metrics, tooling and strategy — start with our user onboarding guide or the B2B SaaS onboarding guide.

• It reacts to who the user is. A seven-step tour shown to everyone fits nobody. An admin evaluating your product and an end user who was invited into it need different first sessions, and the difference isn't cosmetic — it's which feature you show first.
• It waits. Most onboarding fires everything in the first ninety seconds and then goes quiet forever. The moments that matter — someone stalling on a setup screen, someone coming back on day four — happen later.
• It doesn't stop at the tour. Activation isn't a moment, it's a sequence: first win, second win, habit, invite the team, hit a limit. Onboarding that ends after the welcome tour hands everything after it to your support queue.

The examples below are organised around those jobs.

If you only build three

Nineteen is a library, not a to-do list. Nobody should build all of them, and the teams who try tend to build none. If you have one afternoon, these three carry the most weight between them:

• Truly personalized onboarding — because one path for everyone is the single most common thing wrong with onboarding, and routing by role is the clearest thing a linear tour simply cannot do.
• Help when users stall — four steps, buildable before lunch, and pointed at the highest-intent moment you will ever get from a user: the one where they're stuck and still trying.
• Feature launch follow-up — the job most teams are already doing by hand, badly, every time they ship something.

Everything else in this list is worth building eventually. These three are worth building this week.

Get the first run right

The first session decides most of what follows. These five attack the same problem — one generic path fits nobody — from different angles.

• Teach, listen, support (8 steps) — Introduce the product, guide one meaningful first action, then ask how it landed. The most conventional starting point, and the right one if you're replacing an existing product tour.
• Truly personalized onboarding (7 steps) — Routes each user to the path that fits their role, goal or first priority. If you try one flow from this list, make it this one; it's the clearest example of something a linear tour simply can't do.
• Let users choose their onboarding (4 steps) — Offers help without over-guiding: a quick tip for confident users, a walkthrough for those who feel unsure. Good when your users vary widely in sophistication.
• Let users choose their first step (8 steps) — Lets users pick their own starting point, then sends them down the matching path. Useful when your product genuinely has several valid entry points and the team has been arguing about which to feature.
• Help users with initial setup (5 steps) — Recovers users who started setup and didn't finish, returning them to the exact next step. If your product needs configuration before it's useful, this is where the money is.

Turn first use into habit

The gap between "they tried it" and "they rely on it" is where most SaaS onboarding quietly gives up.

• Turn first use into habit (10 steps) — Celebrates the first win, waits a few days, then nudges toward the next meaningful action. The wait is the point.
• Show users the value they created (5 steps) — After a key action, shows a "value receipt" that makes the win visible and points at the next step. People consistently underestimate what they've already achieved in your product.
• Bring in your team (4 steps) — Asks for the invite right after the first meaningful win, when it feels natural rather than pushy. Timing is the whole feature.
• Train users (4 steps) — Improves data quality at the moment of entry, helping people submit usable input before they move on. Unglamorous, and quietly one of the most valuable if your product depends on what users type into it.

Catch people when they stall

Someone stuck on a screen is the highest-intent moment you will ever get from them.

• Help when users stall (4 steps) — Waits briefly on a high-value screen, then offers guidance only if they haven't acted. Four steps, and probably the best first flow to build: small enough to finish this afternoon, useful enough to keep.
• Help users to progress in the right moment (9 steps) — Uses the user's current stage to show the best next step, rather than the same next step for everyone.
• Help users through blockers (5 steps) — Takes a free-text reason from a variable or API call, classifies it, and routes each user to the right help.
• Human support escalation (9 steps) — Escalates to a person only when it's earned, using failure signals and account value to decide. For teams whose support queue is the constraint.

Learn why people leave

You can't fix drop-off you can't explain.

• Understand the frictions (10 steps) — Captures why users abandon key flows at the moment it happens, then offers support if they want it.
• Understand what's blocking users (6 steps) — Finds out what's in each user's way and routes them accordingly, instead of one generic follow-up for everybody.
• Win back at-risk users (7 steps) — Routes at-risk users to the right intervention based on risk signals: a value reminder, an AI assistant, or a human.

Grow the account

Onboarding doesn't stop at activation. These run on customers you already have.

• Feature launch follow-up (5 steps) — Introduces a new feature, helps users try it, then collects feedback once they've formed an opinion. If you ship regularly you'll use this more than any other.
• Drive the upsell moment (13 steps) — Turns hitting a locked feature into something useful: explains the value, captures intent, helps the user unlock or request access. The longest flow here and the one with the clearest revenue line.
• Track onboarding progress to CRM (11 steps) — Guides users to a key action, uses their behaviour to move them forward or bring them back, and reports progress to your CRM.

How to start

All nineteen are in the onboarding flow templates library, filterable by use case, each with its own page. To build one, open Flows in Product Fruits and click Create new Flow — the same nineteen appear in the picker, with a search box that takes a plain description rather than keywords — type "help people who stop halfway through setup" and it finds the relevant ones instead of making you scan the list.

The flow then opens on the canvas like any other. Every step is editable, deletable and reorderable. Most teams keep the structure and rewrite all the copy, which is the right instinct: the structure is the part that takes judgement, the copy is the part that has to sound like you.

Two honest notes. All 19 are available on every plan, but a few use step types that are on Pro and Business — the AI classification and Slack steps in particular — so check the plan comparison before building on those. And a starting point is not a finished flow: the copy is generic by definition and it's yours to make specific.

As one customer put it after moving across from classic tours:

"Now I always go for the Flows. It's that easy — just as easy, or maybe easier, to build than tours."
— Trond-Daniel Kvalvik, Product Manager, Mystore, Norway's largest e-commerce platform

His team built a self-service beta opt-in flow — customers add and remove themselves, no forms, no manual segments — in about fifteen minutes, with no developers involved.

The blank page was never the interesting part of the work. Start from something that already runs, and spend the afternoon on the part that's actually yours.

Frequently asked questions

What is SaaS user onboarding?

SaaS user onboarding is the guided experience that takes a new user from signing up to getting real value from the product. In practice it's a sequence of in-app messages, walkthroughs, checklists and prompts that react to what the user does. It's distinct from customer onboarding, which usually describes the human-led implementation process run by a customer success team — the two often run in parallel on the same account.

How do you run a successful SaaS onboarding process?

Start from one measurable outcome rather than a tour. Decide the single action that means a user has understood the product, then design the shortest path to it. Branch that path by role or goal so different users get different first sessions, add waits so the product can react later rather than only at signup, and instrument the outcome so you can tell whether it moved. Build one flow, measure it, then add the next — a four-step flow that ships beats a twenty-step flow that doesn't.

What's the difference between user onboarding and customer onboarding?

User onboarding happens inside the product and applies to every individual who logs in. Customer onboarding happens around the product and applies to the account — kickoff calls, implementation, training, success planning. A single customer can have dozens of users, each of whom needs onboarding regardless of what the account-level process covered. Most B2B SaaS companies need both.

How do you improve an onboarding process that isn't working?

Find out where people stop, then find out why. Drop-off data tells you which step loses users; it won't tell you the reason. Add a step that captures the reason in the user's own words at the moment they abandon, because a free-text answer collected in the moment is worth more than a survey sent three days later. Then fix the specific thing, one step at a time, rather than redesigning the whole sequence.

For onboarding metrics and a rundown of the tools available, see our user onboarding guide.