Onboarding flow best practices: progress, skip and auto-advance

By Screenrove editorial · 22 October 2026

Onboarding flow best practices from 325 real screens: who shows progress, how 95 products word skip, when a click should advance, and live previews.

Half of the onboarding screens we captured tell you where you are, and a third let you leave. Across 325 onboarding screens from 95 SaaS products, 162 show a progress indicator and 108 offer a way to skip, but the skips are not spread evenly: 9 of the 11 invite screens can be skipped, against 39 of the 139 questions about you. That split, and a few other patterns in how people move through setup, are the onboarding flow best practices you can actually see in shipped products rather than read about in theory.

Every screen is on the onboarding screens wall. Our earlier piece on what onboarding asks after sign-up covers the questions themselves. This one covers the mechanics: progress, skip, when a click should advance, sentence-style forms, previews that fill in as you type, and two products that run onboarding as a chat.

Progress: half the screens, and the short flows say so

162 of 325 screens (50%) carry a progress indicator, and 60 of the 95 products show one somewhere in their flow. Where it appears depends heavily on layout:

• Full-bleed steps: 19 of 24 (79%).
• Split screens with a visual: 49 of 80 (61%).
• Centered forms: 64 of 147 (44%).
• Modals over the product: 30 of 74 (41%).

Plan pickers almost never show progress (1 of 12).

The styles fall into four groups:

• A time and step estimate up front. Postman opens with “1 min” and “2 steps” above the title. Typebot’s terms bubble promises “It won’t take more than a minute.” Voiceflow’s assistant offers a first agent “in under 2 minutes”.
• Labelled counts. Sanity shows “Step 1 of 8” beside a thin coral bar. Product Hunt reads “Step 2 of 2” on a step it labels “Optional”. SurveyMonkey uses a small grey “4 of 5” pill.
• Unlabelled bars and dots. Zapier draws a thin purple bar, Duolingo a thick green one, folk five pager dots, Wrike eight.
• Progress that adapts. Deepnote shows five dashes on its first question; pick “I’m working alone” and the bar drops to four, because the team step no longer applies.

“Step 1 of 8” is honest but announces a long road. Postman’s estimate makes a short flow look short before you type anything.

Skip: where it appears and how it is worded

108 screens (33%) from 59 products offer a skip. The share climbs on the steps that ask you to do work outside the form:

On the 9 skippable invite screens, 5 defer (“Do this later”, “I’ll do this later”, “Remind me later”), 3 say a bare “Skip” (Linear, Cap, Jitter) and one, folk, words it as a choice. Some of the variants:

• Jira: “Do this later” beside “Go to Jira”.
• monday.com: “Remind me later”, bottom left, opposite a greyed “Invite your team”.
• Mermaid Chart, which folds its invite into a question modal: “Or skip - you can always invite later.”
• Plasmic: “Do this later” as a full-width outlined button, the same size as “Send invites”.
• folk: “No, I prefer to work solo”, which turns the skip into a statement about how you work. Its extension step uses “I’ll do this later”.

Two products go further. folk adds friction where it cares most: skip the account sync and a modal asks “Continue with fewer features?”, lists four things you will lose, and puts a red “Yes, I’m sure” next to Cancel. The folk buttons we captured elsewhere in the flow are black.

Jotform does the opposite and makes skipping the default. On “Which tools do you use?” the primary blue button reads “Skip” while nothing is picked, under 12 tool chips, a “None of them” chip and “See more”. Grafana Cloud names the destination: “Skip to dashboard” for people who already have data connected.

One answer advances, many answers need a button

119 question screens use cards or chips. On 49 of them, from 26 products, there was no Continue or Next button when we captured the screen: picking an answer is the click that moves you on. Gamma’s 11 role tiles, Lovable’s 8 role cards, Zapier’s 10 role chips and 5 company-size chips and SurveyMonkey’s cards all work this way.

Jira shows the rule inside a single dialog. “What kind of work do you do?” lists 14 rows and has no button at all. The next question, “How does your team plan to use Jira?”, uses six checkbox cards, and there Back and Continue reappear, because you might tick three.

The multi-select questions we checked keep an explicit button: ElevenLabs (“Select all that apply”, then Continue), GitBook (square checkboxes, then “Create my docs”) and Typebot (“Send”). The reverse is not universal. Duolingo asks a single-choice question and still shows CONTINUE, because the owl first reacts to your pick (“Best thing to pack is the local language!”). Deepnote preselects “Work” and asks you to confirm. Auto-advance screens also keep a way back: Gamma and SurveyMonkey put “Back” bottom left.

Write the questions as a sentence

Three products turn a form into a line you read. Clockify fits three questions into one: “I’m here to [Keep projects profitable and on budget] with my team of [2-10] and our primary billing model is [Hourly billing]”, then a single “START USING CLOCKIFY”. Postman does it with two dropdowns. Smartsheet writes “My company has [number of] people” and “I am in [industry]” beside a skeleton preview labelled “Preview includes data generated by AI.”

Previews that fill in as you type

The most convincing progress is the product taking shape. These flows draw a mock of the app beside the form and update it live:

• Fibery writes your workspace into a mock URL bar (“https://screenrove-research.fibery.io”) and the sidebar.
• GitBook puts the typed name in a docs-site header, with “Docs” appended.
• Jira lets you edit four statuses (To Do, In Progress, In Review, Done) that match the columns of the board beside them; on the invite step the same board gains avatars and @-mention pills.
• monday.com sets your board name in large type over skeleton groups, and Wrike drops three typed tasks into a table with “In Progress”, “New”, “New” and 1d, 2d, 2d.
• TickTick adds a sidebar icon to its mock for each feature you tick; with all six on, the mock shows countdown cards reading 83, 204, 210, 284 and 352.
• Todoist and Zapier redraw the right-hand panel per question: Zapier shows a profile card for role, then a pyramid of person tiles for company size.

Onboarding as a conversation

Typebot builds chatbots, and its onboarding is one. Terms arrive as bubbles, consent is an orange “I agree” reply, and each answer posts back as an orange bubble, so by the company-name question the flow reads as a transcript. It also follows the auto-advance rule: the multi-select bot-type chips end in “Send”, while the single-choice “How did you discover Typebot?” buttons need no Send.

Voiceflow’s assistant, Atlas, greets the account by name and asks for a site. A left rail (Brand, Goal, Skills, Channel, Integrations) is the progress bar. After reading the site it reports “Found 15 key pages for it to answer from”, and the review screen replays every answer as a dark bubble, including a “Skip for now” on integrations, before “Edit brief” and “Build it”. In a chat, even a skip is just another reply.

Onboarding flow best practices to steal

1. Estimate before you count. If the flow is short, say so up front (“1 min · 2 steps”). Save “Step 1 of 8” for flows that really are long.
2. Let the bar shrink. When an answer removes a step, update the indicator, as Deepnote does for solo users.
3. Auto-advance single-choice questions, keep a button for multi-select. Keep a Back link on every auto-advancing screen.
4. Word skip as a deferral on invite and connect steps. “Do this later” tells people the step will still be there.
5. Add friction only where skipping costs features, and list what is lost, as folk does, rather than confirming every skip.
6. Fold small questions into a sentence. Three dropdowns in one line read faster than three labelled fields.
7. Show the product filling in. A mock that echoes the workspace name or typed tasks gives the user progress they can see.

How we counted

We captured these flows in desktop browsers with research accounts in September and October 2026. A vision model recorded each screen’s step type, layout, progress indicator, skip option and choice cards; you can check each attribute on the screen’s own page. Of the 327 screens on the wall, 325 carry a step tag, and that is the base for the counts above. “No button” means none was visible when we captured the screen. These are observations of what each product showed us, not A/B test results, so we make no claims about which pattern converts better.

To pull these references into your own work, connect the Screenrove MCP server and ask your agent for onboarding screens with a skip option, or for question steps that advance on click.