Most SaaS onboarding fails not because teams don’t care, but because they never had a concrete process to begin with. They have pieces: a welcome email here, a product tour there, a check-in call for big accounts. What they lack is a sequence.
This guide lays out a complete sample onboarding process, step by step from the moment a user signs up through day 30. It covers the mechanics of each phase, how to adapt the process for different product types, which metrics to watch at each step, and where AI fits into the picture. Take this as a starting template, not a prescription. Every product has a different aha moment and a different user. The structure here is meant to be adapted, not copied.
Hyper is an AI onboarding agent for SaaS that does 1-on-1 screen-sharing calls with users, seeing their screen, controlling their browser, and guiding them via real-time voice. We publish this guide as part of our ongoing analysis of the onboarding problem.
The Logic of a 30-Day Onboarding Process
Before the steps: why 30 days?
Most B2B SaaS onboarding runs 14 to 30 days, depending on product complexity. Thirty days is the right outer boundary for most products: long enough to move a user through setup, first value, and early habit formation, short enough to maintain momentum before attention drifts.
The process breaks into four phases:
- Day 0: Signup and immediate orientation
- Days 1-3: First value (activation)
- Days 4-14: Habit formation and feature expansion
- Days 15-30: Consolidation and success signal
The goal of each phase is different. Day 0 is about removing friction. Days 1-3 are about delivering proof that the product works. Days 4-14 are about making the product part of the user’s regular workflow. Days 15-30 are about confirming that it stuck.
A Complete Sample Onboarding Process
Day 0: The First Five Minutes
The user has just signed up. They are at peak motivation and zero context. Everything in the first five minutes should convert that motivation into a completed action.
What happens:
- Welcome email delivers immediately. Not a newsletter. Not a product overview. A single, specific next step: “Complete your profile” or “Connect your first data source” or “Create your first project.” One action, clear link.
- In-app welcome screen acknowledges the signup and asks one or two questions to personalize the experience. Role, use case, team size: enough to route the user to the relevant onboarding path, not enough to slow them down.
- The product opens on a state that makes the next action obvious. Empty states have prompts. The first screen is not a blank dashboard.
What you are measuring: Time from signup to first in-app action. If the median is longer than 5 minutes, something in the signup-to-setup funnel is causing drop-off before onboarding even starts.
The most common failure: Sending a welcome email that describes the product instead of directing the user to one specific thing to do.
Days 1-3: The First Value Moment
The aha moment is the specific action where the user first understands why the product exists. For a collaboration tool, it might be “first task assigned.” For an analytics product, “first dashboard built.” For a communication platform, “first message sent to the team.”
The best SaaS products get users to first value within their first session. The outer boundary for most B2B tools is 7 days. Beyond that window, the motivation gap between “I signed up for this” and “I should actually use this” becomes a chasm most users don’t cross.
What happens:
- Day 1: A short onboarding checklist (3-5 items maximum) appears inside the product, showing the user exactly which steps lead to first value. Each step is a verb and an outcome: “Connect your calendar,” “Invite a teammate,” “Run your first report.” Progress is visible.
- Day 2: A follow-up email to users who haven’t reached the activation milestone. Not a “Did you forget about us?” nudge. A concrete “Here’s the one thing to do next” message, with a direct link to the step they haven’t completed.
- Day 3: Users who have activated get a brief confirmation: “You’ve completed setup. Here’s what to explore next.” Users who haven’t get a second follow-up, optionally with an offer to help (a call link, a guided session, a help resource).
What you are measuring: Activation rate (percentage of new signups who complete the aha moment action). Industry average: 37.5%. Target for a well-tuned process: 40-50% by day 3.
Days 4-14: Building the Habit
Activation is not retention. A user who completes setup once and never returns has not been successfully onboarded. This phase is about moving from “I tried it” to “I use it.”
What happens:
- Days 4-7: In-app prompts introduce secondary features, timed to user behavior. If the user has only used feature A, show them how feature B connects to what they’ve already done. Context-aware, not a generic feature tour.
- Day 7: Check-in email for all users. For active users: a “here’s what you’ve accomplished” summary with a natural next step. For inactive users (no session since day 1-3): a re-engagement message framed around value, not around the product itself.
- Days 8-14: For products with team or collaborative components, prompts to add teammates or share work. Social hooks are among the strongest retention signals in this window because they create external accountability and product stickiness.
- Day 14: For high-touch products or high-value accounts, a scheduled check-in call from the Customer Success team. Not to sell. To confirm that the user has reached their first goal and to surface anything blocking further adoption.
What you are measuring: 7-day and 14-day retention rates. Feature breadth (how many distinct product areas has the user engaged with). Session frequency. If a user has only opened the product once, they are at high churn risk regardless of what they did in that session.
Days 15-30: The Consolidation Phase
By day 15, the pattern is set or it isn’t. Users who are active and returning have started forming a habit. Users who haven’t returned are unlikely to without intervention.
What happens:
- Days 15-20: Advanced feature introduction for active users. Not a checklist this time: contextual, triggered by what the user has already done. “You’ve used X 10 times. Here’s how to automate it.” Behavior-triggered guidance scales better than scheduled tours.
- Day 21: Segment active users from inactive users. Active users: a brief win-summary email, a natural nudge toward expansion (connecting an integration, upgrading, inviting more teammates). Inactive users: a re-engagement sequence with low-friction return options, or a Customer Success outreach for accounts above a revenue threshold.
- Days 22-30: Finalize onboarding milestone tracking. Define a “successfully onboarded” event: the specific combination of actions that correlates with 90-day retention in your product’s data. Mark it. Every user who reaches it exits onboarding. Every user who doesn’t gets a follow-up plan.
What you are measuring: Month 1 churn rate. If Month 1 churn exceeds 15%, onboarding is the first thing to audit. The percentage of new users who hit the “successfully onboarded” milestone. Expansion signals: integrations connected, seats added, features unlocked.
Adapting the Process by Product Type
The 30-day template above is a starting point. Three variables change the shape of the process significantly.
Simple, single-player tools
If your product delivers value in a single session and the aha moment happens in minutes, compress the process. Day 0 does the heavy lifting. Days 1-3 are about confirmation and a follow-up prompt. Days 4-30 shift from onboarding to retention. The activation window is short; if a user doesn’t reach first value in their first session, the probability of return drops sharply.
Multi-user or collaborative products
The team adoption problem is layered: the admin who signed up and the teammates who need to join are different people with different motivations. Build a parallel track for admin setup (days 1-7) and team member invitation plus activation (days 3-14). The account is not activated until more than one user is using it. Design for that.
Complex or configurable products
Longer onboarding is justified when configuration is genuinely required to reach value. But “complex” is often used as an excuse to delay the aha moment. Audit ruthlessly: what is the minimum configuration that lets a user experience the core product? Make that the Day 0-3 goal. Save the rest for Days 4-30.
Enterprise accounts
Add a pre-onboarding phase: the handoff from Sales to Customer Success. Define the success criteria before the first onboarding session. Set a timeline with the account stakeholder. The 30-day clock starts from the handoff, not from the contract date. Build in a formal milestone review at day 30 with the economic buyer, not just the end users.
Measuring Each Step
The process above maps to a small set of metrics. Track these and you’ll see exactly where users fall off.
| Phase | Metric | What it tells you | |---|---|---| | Day 0 | Signup-to-first-action time | Friction in setup before onboarding starts | | Days 1-3 | Activation rate by day 3 | Whether users are reaching first value fast enough | | Days 4-14 | 7-day and 14-day retention | Whether activation is turning into a habit | | Days 4-14 | Feature breadth | Whether users are exploring beyond the initial action | | Days 15-30 | Month 1 churn rate | Whether the full onboarding process is working | | Days 15-30 | “Successfully onboarded” milestone rate | Percentage of users who hit the combination of actions that predicts retention |
One metric often missing from standard dashboards: the percentage of signups who never take any action at all. If that number exceeds 20%, the problem is not in onboarding. It’s earlier, in the signup flow or in the expectations set during acquisition.
See the onboarding checklist for a full list of measurable milestones to build into your tracking setup.
Where AI Fits Into This Process
Walk through the process above and count the moments where a human would do a better job than automated guidance: the user is stuck on a setup step, confused about which feature to use, running an unclear workflow, or unsure whether what they’ve done is right.
Those moments are scattered through every phase. Day 0 through day 30. They’re the reason high-touch onboarding works: a human who can see the user’s screen and talk them through the problem is categorically more effective than a tooltip pointing at a button.
The constraint has always been scale. High-touch works. It doesn’t scale.
That constraint no longer holds.
AI agents can now join a user in a live screen-sharing session, see exactly what’s on their screen, control the browser, and guide them through the product via real-time voice. The moments in the process above where a human call would help most, these agents cover at software scale.
Hyper takes this approach directly. Instead of building tour content, Hyper’s AI joins each new user in a 1-on-1 session, deployed with one line of JavaScript, available in any language, 24/7. The agent adapts to what’s actually on the user’s screen, not to a pre-scripted sequence.
In practice, this means the Days 1-3 activation phase, typically the highest drop-off window in the process, can include an AI-guided session instead of relying on a checklist and a follow-up email. The user who would have clicked “skip” on a product tour now has an agent that can walk them through the exact step they’re stuck on.
The rest of the process still applies: the email sequences, the milestone tracking, the Customer Success check-ins for high-value accounts. AI covers the guided, interactive moments. The rest of the infrastructure stays the same.
For more on how AI changes the onboarding model, see onboarding workflow examples and the SaaS user onboarding guide.
The One Thing to Verify Before Optimizing
Before adjusting email timing, A/B testing checklist copy, or evaluating new onboarding tools: confirm you have defined the aha moment.
Not “users explore the product.” Not “users feel engaged.” The specific, measurable action that correlates with 90-day retention in your data. That one thing determines whether every other part of the process is pointed in the right direction.
Once defined, the 30-day process above gives you the scaffolding. Build the specific steps around that moment. Measure the four core metrics. Iterate on the phases where users fall off.
If you’re at the stage where you’re evaluating whether an AI onboarding agent belongs in your process, talk to Hyper. We’ll show you exactly where AI guidance fits into your current flow.
Part of Hyper’s editorial guide to SaaS onboarding. We’ve studied 46+ tools in the onboarding, adoption, and Customer Success space. March 2026.