SaaS onboarding and activation: designing the first session

A signup is not a customer yet. Between the sign-up form and the moment someone gets what they came for, there is a first session of a few minutes, and that’s where most trials are won or lost. This guide is how we design that session for SaaS and AI products: what to decide first, what to cut, and what to put on the screens nobody thinks about.

Why don’t trial users activate?

It’s rarely a missing feature. The usual causes are less dramatic:

• 01Too many steps before anything useful happens: verify the email, name a workspace, invite the team, connect an integration, pick a plan.
• 02An empty product with no obvious start. The dashboard loads, every chart says “No data yet”, and the person leaves to come back later.
• 03A tour that explains the interface instead of getting a job done.
• 04Value that depends on setup the user can’t do alone, like data from another tool or an admin’s approval.
• 05Follow-up emails that ignore what the person did, so they read as noise.

All five have the same root. The first session was designed around how the product is built, not around the moment the person signed up for.

What is the activation moment?

The first time a new user gets the value you sell: a first report, a first automation, a first answer. Write it down, because everything in onboarding serves it.

Write it as one sentence with a verb and a result: “A new user has activated when they connect a data source and see their first weekly report.” A good activation moment passes four checks:

• 01It’s something the user does, not something they see. “Viewed the dashboard” doesn’t count.
• 02It produces a result they’d miss if it disappeared.
• 03It can happen in the first session, at least in a smaller form.
• 04You can log it as a single event and count it.

If the honest answer is that the full value only arrives after a week of data, the first-session target is a smaller version of it: a preview built on sample data, an import that finishes, a first rule that will run tonight. Design for that, and say plainly when the full result will arrive.

If the team can’t agree on that sentence, it isn’t an onboarding problem yet. It’s a positioning question, and drawing the onboarding is often how it surfaces. We wrote about that in Strategy is a design material.

How should a SaaS sign-up flow work?

Ask less. Email or SSO, then straight in. Ask for team size and role later, when you need them.

Every field before the product has to justify itself. For each one, ask: does the first session change based on the answer? If it doesn’t, it moves later.

• 01Offer SSO with the provider your buyers already use, next to plain email.
• 02Don’t block the product on email verification if you can avoid it. Verify in the background and gate only what needs it, like inviting others or sending from their domain.
• 03Ask one question only if it changes what they see first, such as their role or use case, so you can pick the right template. Let them skip it.
• 04Don’t ask them to invite teammates before they’ve seen anything worth inviting anyone to.
• 05Move questions you need for sales or segmentation to the second session, or to a moment where answering them helps the user.

Why are empty states part of onboarding?

An empty dashboard is a dead end. Offer sample data, a template or a single obvious first action.

For a new user, the first screen is the emptiest the product will ever be. Most teams design the full state with care and leave the empty one to a default “Nothing here yet”. Three patterns work better:

• 01Sample data: a realistic demo workspace that shows what the full state looks like, clearly labelled and easy to clear.
• 02Templates: a starting point that matches the role or use case they gave you, so the first edit is a change, not a blank page.
• 03One obvious action: a single primary button that leads toward the activation moment, with one line explaining what happens next.

Pick one per screen. An empty state with three equal buttons is a menu, and a menu asks the user to choose before they know enough to choose. Write the copy as a next step, not an apology.

Product tour or guided task?

Product tours get skipped. A checklist of three steps that each do something real works better.

A tour explains the interface: this is the sidebar, this is where settings live. People click through it and remember little, because nothing happened. A guided task gets something done, and the interface is learned on the way.

A tour shows people the product. A first task lets them use it.

How we design the checklist:

• 01Three steps, four at most. Each one is an action in the product, not “watch a video” or “read the docs”.
• 02The last step is the activation moment.
• 03Steps tick themselves off when the action happens, wherever the user did it.
• 04It’s visible but dismissible, and it goes away once it’s done.
• 05If a step needs someone else, like an admin or an API key, offer a way around it: sample data for now, a reminder later, or an invite with a message already written.

How should onboarding follow up?

With emails and in-app nudges based on what people did, not a fixed sequence.

A day 1, day 3, day 7 sequence sends the same message to someone who already activated and to someone who never came back. Trigger on behaviour instead:

• 01Signed up but never finished the first step: one short email with the single next action and a link straight to it.
• 02Reached the activation moment: point to the next most useful thing, not to the upgrade page.
• 03Stuck on a step that needs a colleague: a message they can forward as it is.
• 04Went quiet after activating: show what happened since, like the report that ran or the results waiting for them.

Fewer messages, each tied to something the person did, beat a long sequence. Write the email and the in-app version in the same voice, and give one person ownership of them, because follow-up drifts out of date faster than the product does.

What changes for AI products?

Show an example prompt or task that works the first time, and set honest expectations about limits.

An empty input box is the AI version of an empty dashboard. People don’t know what to ask, and the first thing they try is often not what the product is best at. A weak first answer is hard to recover from, because it sets the user’s idea of what the product can do.

• 01Offer a few starter prompts or tasks, chosen for the user’s role and tested so they reliably produce a good result.
• 02Show what a good input looks like: the files, context or detail that make the answer better.
• 03Say what the product doesn’t do yet, near the input, in plain language.
• 04Make the first output easy to edit, rerun or correct, so a weak answer is a step and not the end.
• 05Show progress for anything that takes more than a few seconds, so waiting doesn’t look like failure.

How do you know the first session works?

Log the activation moment as an event and look at the path to it: how many people start each step, where they stop and how long it takes. Watch a handful of real first sessions, recorded or live. The problem is usually visible in the first few. Then change one thing at a time, so you know what moved the number.

A checklist before you ship a new first session:

• 01The activation moment is written as one sentence and logged as one event.
• 02Every sign-up field changes the first session, or it has moved later.
• 03Every empty state has one primary action, a template or sample data.
• 04The guided task ends at the activation moment.
• 05Follow-up is triggered by behaviour, not by the calendar.
• 06For AI features, starter tasks are tested and the limits are stated.

Where we fit

Core product flows, onboarding included, are part of a Launch sprint: about 4 weeks, from US$12k, with positioning and the first screens designed side by side. For a product that’s already live, Partner, from US$6k/mo, takes on the first session as one focus, then moves to the next. If you’re still deciding who should do this kind of work, read In-house, agency, or AI: who should design your product.

If your signups aren’t turning into active users, send your brief.

• Product
• Onboarding
• SaaS