Pixel SaaS onboarding role selection template
SaaS
Build this design with AI →Notion onboarding flow: UX breakdown and how to copy it
Notion can do almost anything, and that is its onboarding problem: a blank page scares new users away. Its answer is one of the most copied onboarding patterns in SaaS. Ask one question, then drop people into a workspace that is already filled in for them. Here is how the Notion onboarding flow works, why it works, what to skip, and how to build the same pattern with AI.
The Notion onboarding flow, step by step
A simplified map of the flow, drawn by us. Notion changes it often, and recent versions also show off its AI agent, so this is the pattern rather than every screen.
Sign up and profile
Email, then a name and photo, so the account feels like yours.
One intent question
"How do you want to use Notion?" with three answers: work, personal life or school. Some versions also ask about your team.
A filled-in workspace
Depending on your answer, you land in pages already set up for you, like project boards and meeting notes for teams.
A getting started checklist
A short page of tasks you learn by doing, like typing "/" for commands.
The Notion onboarding pattern: what makes it recognisable
Four choices make this pattern work, and they apply far beyond Notion.
Ask, don't tour
One question replaces a ten step product tour.
No blank page
You never see an empty workspace. Example content shows what is possible.
Learn by doing
The checklist lives inside the product, so learning is using it.
Your answer changes what you see
The question is worth answering because the result is visibly different.
See more patterns like this in our SaaS onboarding design guide.
Why the Notion onboarding flow works
Flexible products lose people at the start. These five decisions keep them.
1. It fixes the blank page problem
Flexible products lose people at the empty state. Notion shows a finished example first.
2. One question is easy to answer
Three clear choices, no typing, no wrong answer.
3. Recognition beats recall
Users pick from examples instead of imagining what to build.
4. Value before effort
You see a useful workspace before you are asked to set anything up.
5. The checklist keeps going after day one
It nudges you towards a second success, not just the first.
The weak spot: one teardown counts five or more screens before you reach the product, including email checks, interests and a desktop app prompt. Upsells like the desktop app arrive before the first win.
Why most onboarding flows that copy Notion fail
Teams copy the question screen and skip the hard part: writing good example content for each answer. A personalisation question that leads to the same empty dashboard is worse than no question at all, because users feel ignored.
What a UX designer would change for your site
Notion's pattern fits a product with many uses. Before you copy it, check that yours has them.
Only ask what changes the experience
If an answer does not change what users see, cut the question.
Pre-fill with real examples
Not placeholder text or "My first project". Show what a good result looks like.
Move upsells after the first win
No app download or upgrade prompt before users get value.
Count your screens
Every screen before the product costs sign ups. Aim for value in the first minute.
Simple product? Skip the question
If your product has one clear job, drop users straight into it.
Is your onboarding losing users?
Ask Mon, the AI design assistant, to review your onboarding flow and tell you which step to cut or fix first.
How to build an onboarding flow like Notion with AI
1
Start from onboarding templates
Pick a role picker, steps and checklist from the templates below.
2
Paste them into your AI tool
Claude Code, Lovable, Bolt, Cursor or Replit. Ask for them in your stack.
3
Write example content for each answer
So nobody lands on an empty page, whatever they choose.
4
Ask Mon to review the flow
Mon tells you which screens to cut before you launch.
