Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Client Workspace

SaaS onboarding flow design: activation paths and drop-off analysis

Design a SaaS onboarding flow backwards from one activation event, the first action that shows a new account got value, then measure every step towards it and fix the step that loses the most people with the cheapest lever. Netbase JSC treats removing a step as the first fix, and tours or emails as the last.

Book a solution review See product discovery and roadmapping

By Netbase Commerce and Platform Engineering Desk · Reviewed by David (CEO) · Updated · 11 min read

star

This guide is for founders, product owners and product managers whose sign-ups do not turn into active accounts. It belongs to Netbase's software product engineering work and complements our SaaS development service, where the first-run experience is built together with billing, tenants and permissions.

In this guide

What counts as activation in a SaaS product?

Activation is the first moment a new account does the thing the product exists for, not the moment it finishes a setup wizard. For a project tool it may be a first task shared with a colleague; for an invoicing tool, a first invoice sent. Pick one event, write it down and make every onboarding decision serve it.

The best candidate comes from your own retained accounts: look at what the accounts that stayed did in their first days and what the accounts that left did not. With too few accounts, choose the event that best matches your product's promise and revisit it later. A good activation event is observable in your event data, happens early, and is something the user would recognise as useful.

Keep sign-up, setup and activation apart. Many flows report a high setup completion rate and still lose accounts, because finishing setup was never the same as getting value.

How do you find where new users drop off?

You find drop-offs by measuring each step on the path to activation as a funnel and reading the loss between steps, not the overall rate. First check the funnel itself: a missing or mislabelled event looks exactly like a drop-off.

Product analytics tools give you the controls you need. PostHog's funnel documentation describes a conversion window, how long a user has to complete the funnel after the first step, and breakdowns by event properties, person properties and cohorts. Google Analytics distinguishes open funnels, where users can enter at any step, from closed funnels, where they must enter at the first step. For onboarding, use a closed funnel that starts at sign-up, so a returning user who skips ahead does not inflate a later step.

Then read the funnel three ways:

  • Step loss. The share of users who reach one step but not the next. The largest relative loss is the first candidate, not the step with the most traffic.
  • Time between steps. A step that people complete but slowly is friction even when the loss looks small; PostHog notes that steps with a long time to convert are likely harder than others.
  • Breakdown by source and role. A drop that appears only for one acquisition channel or one user role is a fit or messaging problem, not a flow problem.

Numbers show where people leave, not why. For the why, watch a handful of real sessions at the losing step, read support tickets from the first week and run a short usability round on the step itself; our guide to usability testing without a research team covers how to run one.

Drop-off patterns, their likely cause and the lever that fits

Where the loss happens Likely cause Evidence that confirms it Lever to pull first
Between sign-up and the first screen Email verification, slow provisioning or a broken redirect Error logs, verification emails not opened, time gap before first screen Let users in before verification; fix provisioning speed
At a required setup or profile step The product asks for information it does not need yet Sessions stop on the form; fields left blank or filled with junk Remove the step or defer it until the data is needed
At an empty first workspace Users see nothing to act on and do not know what to do next Long time on the empty screen, no first action, quick exit Sample data, a template or one clear first action
At an integration or data import The step needs access, files or a colleague the user does not have Many starts, few completions, tickets asking for help Offer a skip path, a manual alternative and an invite link
After a first value moment, with no return Value was shown once but the habit or team adoption never started Activated accounts with no second session or no invited colleague Prompt the next use and the first invite at the point of value

How to fix an onboarding flow, step by step

  1. Write the activation event and the path to it

    List every screen and action between sign-up and the event, and mark which ones the product truly needs at that moment.

  2. Check the instrumentation

    Confirm that each step fires one event with a clear name, set a conversion window that matches how people actually use the product, and use a closed funnel from sign-up.

  3. Find the losing step

    Read step loss, time between steps and the breakdown by source and role, and pick one step to work on.

  4. Confirm the cause

    Watch sessions, read first-week tickets and run a short usability round on that step before you design a fix.

  5. Pull the cheapest lever first

    Remove or defer the step, then prefill or template what the user sees, then add guidance; tours and checklists come last.

  6. Ship the change to new sign-ups and compare cohorts

    Compare the funnel of accounts that saw the old and the new flow over the same conversion window, and keep the change only if activation, not just step completion, improves.

The order in step 5 matters. Nielsen Norman Group advises avoiding app onboarding wherever possible and spending the effort on making the interface more usable, and warns that instructional onboarding should not patch poor design. Its guidance on empty states points the same way: an empty screen should explain the system status, teach in context and give a direct path to the key task. Progressive disclosure, showing only the most important options first and the rest on request, keeps setup short without hiding what experienced users need.

Which design levers work best, and when should you not use them?

  • Removing or deferring a step fits any step the product does not need yet. Never remove a step that protects data, billing or permissions; move it instead.
  • Templates and sample data fit an empty first workspace. They backfire when sample data is hard to delete.
  • A role or goal question at sign-up fits a product with clearly different first tasks for different users. One question is enough; a long survey before value is itself a drop-off step.
  • Checklists fit products that genuinely need several setup tasks. They do not fit a product with one core action, where a checklist only adds noise.
  • Product tours fit a new interaction pattern that users cannot guess. They do not fix a confusing screen, and users often skip them.
  • Emails and in-app nudges fit users who left with a clear next step still open. They do not bring back users who never understood the value.

When not to touch the flow at all: if the breakdown shows that one channel brings sign-ups who never activate, the fix is the targeting or the promise, not the onboarding. If activated accounts still leave, the problem sits after onboarding, in the product or the pricing, and a better first-run experience will not hide it.

To choose how far to prototype a new flow before building it, see our guide on prototype fidelity: a clickable wireframe is usually enough to test the order of steps. Back-end onboarding, creating a tenant, its settings and its first users, is a separate job covered in our SaaS platform engineering guide.

Where AI fits

AI tools speed up the qualitative half of drop-off analysis: clustering first-week support tickets and session notes by theme and drafting hypotheses for the losing step. A product manager still checks every hypothesis against the funnel data and a person watches the sessions, because a tidy summary can point at the wrong step. Netbase works with the major commercial and open-source AI tools and models, chosen per project, under human control.

What delivery record exists, and what does not

Netbase JSC designs, builds, integrates and runs software across technologies and industries. Its delivery teams combine business analysts, project managers, solution architects, developers, QA and UI/UX designers, so the people who design an onboarding flow also own the events that measure it.

Netbase runs SaaS of its own: Cloodo, a Netbase Business Division, is a digital workplace for company profiles, services, projects and team collaboration; the Cloodo workspace record describes it. For a US client that is not named, Netbase works as offshore development partner on a multi-tenant cloud ERP delivered as SaaS to small and mid-sized businesses, covering CRM, team messaging and project management. For ACT Printing, a custom apparel and print shop, Netbase built a guided mobile-first ordering flow that walks buyers through print locations, colours and sizes step by step.

Netbase's delivery lifecycle starts with discovery and strategic alignment, which is where the activation event and the path to it are defined. In custom development, the client owns the IP created for it, including the flows and analytics set-up made for the project.

Netbase does not publish an activation rate, a drop-off figure or an improvement from an onboarding redesign. This guide explains a method; it is not a case study.

Alternatives: other ways to raise activation

  • Assisted onboarding. A person sets up the first workspace with the customer. Fits high-value B2B accounts; it does not scale to low-value sign-ups.
  • A sales-led trial. Fits complex products where the buyer and the user are different people; it moves the problem from the flow to the trial plan.
  • Fixing the product, not the flow. Fits a product where users reach the core screen and still cannot complete the core task; start with product discovery and roadmapping to decide what to change first.

Selection criteria: choose self-serve flow work when sign-ups are many and accounts are small, assisted onboarding when accounts are few and valuable, and product changes when the loss is at the core task rather than before it. Most Netbase projects are delivered on fixed-price contracts; milestone-based and monthly team retainer models are also offered.

Limits of this guide

  • It covers self-serve web SaaS; app stores and enterprise procurement add their own steps.
  • It does not set benchmark rates. Activation and drop-off figures differ by product, price and audience, and published averages rarely match your funnel.

Plan the next step with a Netbase consultant

Frequently asked questions

There is no reliable universal figure, because activation depends on your own event definition, audience and price. Compare your funnel with its own earlier cohorts and judge each change by whether more new accounts reach the activation event.

Usually not. Start by removing steps the product does not need yet and by giving the first screen a clear first action; add a tour only for an interaction users cannot guess.

A funnel needs enough sign-ups per step for a change to be visible, so small products should pair the numbers with watched sessions and short usability rounds. The qualitative evidence tells you why people leave even when the counts are small.

Next step

If new sign-ups are not turning into active accounts, tell us about your product and its funnel and we will reply with a proposal for a drop-off review and the first fixes.

AI-enabled software product engineering from discovery to operation AI-enabled software product engineering from discovery to operation

Netbase provides software product engineering for companies that need a web, SaaS, mobile or custom platform built and kept running, with AI features and AI-assisted engineering where they pay off. We cover the full lifecycle, from discovery to operation, and the same team stays accountable for architecture, delivery and handover, so nothing important gets lost between phases.

Learn More
line
AI-ready SaaS development from a team that runs its own SaaS AI-ready SaaS development from a team that runs its own SaaS

Netbase provides SaaS development for founders and product teams to launch and scale multi-tenant subscription software with AI features customers will pay for. We build and operate our own SaaS platforms, Printcart and the AI-powered Cloodo workplace, and bring that experience to client products. Discovery fixes the MVP scope and schedule.

Learn More
line
Product discovery that validates AI features and ends in a release roadmap Product discovery that validates AI features and ends in a release roadmap

Netbase provides product discovery workshops for founders and product leaders to turn a product idea into validated scope, architecture options and a release roadmap. We test the problem with real users, prototype the riskiest flows, check whether planned AI features have the data and accuracy they need, and agree what the first release must prove before committing a build budget.

Learn More
line
SaaS product accelerator: launch an AI-ready SaaS on proven Netbase modules SaaS product accelerator: launch an AI-ready SaaS on proven Netbase modules

A SaaS product accelerator is a set of reusable Netbase modules for accounts, billing, roles and integrations that helps founders and product teams launch subscription software faster, with room for in-product AI from the first release. Reusing these modules can shorten development time, and the approach is proven on Printcart, Netbase's own web-to-print SaaS.

Learn More
line

Work with Netbase remotely

Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.

Contact Netbase

Discuss a project

Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.
Project enquiries

project@netbasejsc.com

WhatsApp

+84 937 869 689

Office address

91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam

Get in touch

Tell us what you want to build, modernize, or operate.

Tell us what you want to build, modernize, or operate.

Contact Netbase