Brent Haskins / Applied AI
Onboarding Is Not One Flow: Why Your Activation Metrics Are Lying to You
Most SaaS onboarding flows treat all new users as if they have the same goal. In reality, two fundamentally different populations exist: doers who want to get something done, and demonstrators who want to prove the product works. Designing for the wrong group inflates activation metrics and delays time-to-value. This post explains how to segment by intent, adapt flows using AI and behavioral signals, and measure what actually matters. Written June 2026 from a product engineer’s perspective who has shipped onboarding systems across SaaS and AI products.
The short answer
Your onboarding flow is probably designed for the wrong user. Most SaaS products treat every new signup as if they have the same goal: learn the product, then use it. In reality, two fundamentally different populations exist. One group — the doers — shows up to get something done. They want to send a message, create a project, import data, ship an automation. The other group — the demonstrators — shows up to prove the product works. They invite teammates, configure dashboards, export reports, and complete every step of your product tour.
Both groups generate activity metrics that make your dashboard look healthy. But only doers drive retention and revenue. If your onboarding is optimized for demonstrators, you'll see high activation rates and low long-term engagement. The fix is not a better tour or a smarter empty state. It's segmenting by intent from the first click.
Key takeaways
- Segment by intent, not role or company size. A founder who signs up alone is a doer. A team lead who invites 10 people before touching the product is a demonstrator. Use signup source, first action, and behavioral signals to classify.
- Measure time-to-first-value for doers only. Ignore demonstrator metrics for activation. If doers take longer than 5 minutes to reach the core action, your onboarding is adding friction.
- Kill the product tour for doers. Replace it with contextual hints that appear only when they pause or make an error. For demonstrators, a short guided first action is more effective than slides.
- Design empty states for action, not explanation. An empty state that says "Invite your team" is for demonstrators. An empty state that says "Create your first project" with a one-click button is for doers.
- Use AI to adapt flows invisibly. Detect intent from clickstream and dynamically adjust the onboarding sequence. The user should feel understood, not "personalized to death."
- Audit your onboarding for the wrong user. Go through your flow as if you only wanted to get one thing done. Count how many steps are unnecessary. Then remove them.
The Two Users Every SaaS Actually Serves
Most products treat two fundamentally different user populations as one: users who show up to get something done (take an action, see a result, come back) and users who show up to demonstrate they're getting something done (configure, invite, build dashboards, export reports). Both groups complete onboarding and generate activity metrics that make a dashboard look healthy. But they have opposite motivations.
Doers are impatient. They have a job to do and will abandon your product if they can't do it in under two minutes. Demonstrators are patient. They will click through every tooltip, invite 15 teammates, and fill out their profile — then never return. If your onboarding is designed for the patient user, you're optimizing for churn.
Why Most Onboarding Flows Fail
The classic onboarding pattern — welcome modal, product tour, empty state with "Invite your team" — is built for demonstrators. It assumes the user wants to learn before doing. But doers want to do before learning. They'll skip the tour, close the modal, and look for the action button. If they can't find it in 10 seconds, they leave.
I've seen this pattern in every SaaS product I've shipped. The team celebrates high activation rates because 80% of users complete the tour. But retention at 30 days is below 20%. The tour completers were demonstrators. The doers who bounced never made it into the metric.
How to Segment by Intent
You don't need a complex ML pipeline to start. Use three signals:
- Signup source. A user who comes from a referral link sent by a power user is likely a doer. A user from a trade show or content download is more likely a demonstrator.
- First action. If the first click is on a core action (create, send, import), classify as doer. If it's on settings, help, or invite, classify as demonstrator.
- Time to first action. Doers act within seconds. Demonstrators browse.
Once classified, serve different flows. Doers get a minimal interface with a single call-to-action: the core action. Demonstrators get a guided setup with team invites and configuration. Reclassify after each session — intent can shift.
What Activation Metrics Should Actually Measure
Stop measuring "onboarding completion." That's a vanity metric for demonstrators. Instead, measure time-to-first-value for doers: the time from signup to the moment they perform the core action that defines your product. For a messaging app, it's sending the first message. For a project management tool, it's creating the first project. For an AI automation platform, it's shipping the first automation.
Track this separately for doers and demonstrators. If doers take longer than 5 minutes, your onboarding is broken. If demonstrators take 10 minutes, that's fine — they're not your activation target.
The Role of AI in Onboarding
AI can detect intent from early behavior and dynamically adjust the onboarding sequence. It can also power contextual tooltips that answer the exact question a user has, rather than showing a generic walkthrough. The key is to keep the AI invisible: the user shouldn't feel "personalized to death," just that the product understands them.
For example, if a doer pauses on the data import screen, an AI-driven hint could say "Most users import a CSV first" with a one-click button. If a demonstrator is clicking around settings, the AI could offer to invite teammates. This is not about flashy chatbots — it's about reducing friction at the exact moment it matters.
Closing
Your onboarding is not one flow. It's two flows serving two different users. If you design for the demonstrator, you'll get high activation and low retention. If you design for the doer, you'll get lower activation numbers but higher long-term engagement. The smartest product teams I've worked with start by auditing their onboarding for the wrong user. They remove every step that doesn't get a doer to first value. Then they add back optional paths for demonstrators. Try it. Your retention curve will thank you.
FAQ
Questions people ask about this topic.
How do I identify whether a new user is a doer or a demonstrator?
Look at the first action they take after signup. Doers typically jump straight to core actions: creating a record, sending a message, importing data. Demonstrators click through product tours, invite teammates, or configure settings. You can also use signup source — referral from a power user often signals a doer — and machine learning to classify intent from initial clickstream.
Should I completely remove product tours for doers?
Yes, for the first session. Doers want to see results, not slides. Replace tours with a contextual hint system that appears only when they pause or make an error. For demonstrators, a short tour can be useful, but even then, a guided first action is more effective. The key is to adapt the flow based on detected intent, not force everyone through the same funnel.
What activation metric should I use instead of 'completed onboarding'?
Measure time-to-first-value for doers: the time from signup to the moment they perform the core action that defines your product (first message sent, first project created, first automation run). Track this separately for doers and demonstrators. If doers take longer than 5 minutes, your onboarding is adding friction. Ignore demonstrator metrics for activation — they'll complete any flow you put in front of them.
How can AI improve onboarding without adding complexity?
AI can detect user intent from early behavior and dynamically adjust the onboarding sequence — showing a data import prompt to a doer, or a team invite prompt to a demonstrator. It can also power contextual tooltips that answer the exact question a user has, rather than showing a generic walkthrough. The key is to keep the AI invisible: the user shouldn't feel 'personalized to death,' just that the product understands them.
Sources