SaaS onboarding checklist: how to build one that gets used

By Hasan · November 5, 2026 · 5 min read

A SaaS onboarding checklist is a short list of tasks that moves a new user to their first result. In JustOneCX it is a tour step of type checklist. It shows tasks in a progress widget in the corner of the page, and a task completes when the user clicks it or when your code sends a matching event.

This guide covers what to put in a checklist, how to build one, and how to tell whether it worked.

What belongs in an onboarding checklist?

Start from the result, not from your feature list. Ask what a new user must do to get value. Then list only the tasks that lead there.

A good checklist has these traits:

  • Three to five tasks. Long lists look like homework.
  • Each task is one action the user can finish in a minute or two.
  • Tasks are in the order a person would do them.
  • Each task names the outcome, not the screen. "Invite a teammate" beats "Open the members page".
  • The last task is the one that shows value. That is your activation event. If you have not picked one yet, read how to pick your activation event.

Leave out tasks that only help you, such as "Complete your profile" when nothing in the product needs it. Every task should help the user.

How do you build a checklist in JustOneCX?

A checklist is a step type. A tour can be a checklist alone, or the checklist can be one step among tooltips and modals.

  1. In the dashboard, open Tours and create one, from scratch or from a template.
  2. On the Builder tab, choose Add step, then Checklist.
  3. Write each task as a short label.
  4. On the Settings tab, set targeting. Decide who sees the checklist and on which pages.
  5. Publish.

The SDK fetches published tours on init() and plays the ones that match the visitor. Here is the setup, copied from the docs:

import { init } from "@justonecx/sdk";

await init({
  publicKey: "pk_your_workspace_key",
  apiUrl: "https://api.justonecx.com",
  trackRouteChanges: true,
});

Use trackRouteChanges: true in a single-page app. The checklist stays in the corner while the user moves around, and page targeting is checked again after each navigation.

How does a task get marked as done?

There are two ways, and whichever happens first wins.

The user clicks the task. This is the simplest option. It works for tasks like "Read the quick guide".

Your code sends an event. Bind the task to an event name. When your code calls track("that_event"), the task completes. This is the better option for real actions, because the user cannot tick a task without doing the work.

For example, if a task is "Create your first project" and you bind it to a project_created event, your app sends that event when the project is saved. The docs describe the call under identify and track.

If an event must be proven from your server, JustOneCX also supports steps that only complete on a server event. See server-confirmed steps.

Who should see the checklist?

Show it to new users only. A returning customer does not need a getting-started list.

Targeting has three parts: audience, pages and schedule. Each part is optional, and all of them must match. For a checklist you will often use the audience part with new versus returning visitors, or a segment such as people on a certain plan. Segments need trait data, so call identify after sign-in. See targeting and segments.

Call identify like this:

window.JustOneCX.identify("user-42", { plan: "growth", role: "admin" });

Call reset when the user signs out, so the next person on the same browser does not inherit the first person's state.

How do you know the checklist worked?

Do not judge it by how many people saw it. Judge it by what happened after.

Open the tour's Results tab. It shows:

  • Started, finished, finished with skips and abandoned. Abandoned means no activity for 7 days.
  • The biggest drop-off, with its page.
  • A per-step table: reached, skipped by reason, target missing and median time.
  • A split by any user trait you send with identify(), for example plan.

Read it in this order:

  1. Find the task where most people stop. That task is too hard, unclear or in the wrong place.
  2. Compare traits. If one plan finishes and another does not, the checklist may fit one group better.
  3. Check the activation number in analytics. A checklist that people finish but that does not raise activation is pointing at the wrong tasks.

Change one thing at a time, then read the results again. Tours also support an A/B test, set on the Settings tab, if you want to compare two versions.

What mistakes should you avoid?

  • Listing every feature. Pick the path to value.
  • Making all tasks look equal. Put the value task last and make it clear.
  • Showing the checklist to everyone. Target new users.
  • Never reading the results. The drop-off table tells you what to fix.

For more on tour design, see product tour best practices. For the wider picture, see user onboarding best practices.

Frequently asked questions

Can a tour be only a checklist?

Yes. A tour can be a checklist alone, or the checklist can be one step among other steps.

What completes a checklist task?

A click on the task, or an event your code sends with track("that_event") when the task is bound to that event name. Whichever happens first wins.

Where does the checklist appear?

It appears in a progress widget that stays in the corner of the page.

Can I preview a checklist before publishing?

Yes. The tour builder has a Preview on your site action. It uses the JustOneCX browser extension to play your draft on your own live page.

See how it works in the live demo.

See it working in 2 minutes

Try the live demo

Related