What Are the Components of a Top-Tier SaaS Onboarding Experience?

Everything else on this page is in service of one event, and the company has to name it. Slack's founder Stewart Butterfield told First Round in 2015 that the line was 2,000 messages exchanged by a team, and that "after 2,000 messages, 93% of those customers are still using Slack today." The number matters less than the shape: a behaviour, in the product, on the customer's own work, past which retention flattens.

Set this first. A team without a defined moment measures attendance and completion instead, the failure covered in why customers churn after completing onboarding. The method for finding your own moment from your data is on improving product adoption during initial use.

The same tour bores an expert and loses a beginner. Duolingo's fix is a placement test at signup: in its own words, "we use a placement test to determine where they should begin within a course." Zapier's version is choice rather than testing. Its quick start guide offers several routes to a first Zap, including "Using Zapier's pre-built Zap templates" and "Using the AI-powered Copilot tool to help you create your Zap", so a person who already knows what they want does not sit through the tutorial.

For a B2B product the placement test is two questions on the kickoff form: what are you replacing, and what should have happened in 30 days. Those answers pick the path.

Superhuman is the clearest published example of concierge onboarding at scale. Rahul Vohra described it in 2019: "we do in-person onboardings typically over a Zoom video call. They're about half an hour in length each." Gaurav Vohra, who ran the program, wrote in 2025 that sessions had run up to 90 minutes before the team "pared onboardings down from 90 minutes to 30 minutes".

Two things to take from that: every user got a session, not only the buyer, and the session got shorter as the team learned what needed a human. If your kickoff runs 60 to 90 minutes, the call is carrying work a checklist, a template or a sandbox should carry.

When the product replaces a system of record, free onboarding is a false economy for both sides. HubSpot's marketing pricing page states that the cost shown "does not include the required, one-time Professional Onboarding for a fee of $3,000" and, on the Enterprise tier, onboarding "for a fee of $7,000". The services page scopes what that buys: "Marketing Hub Onboarding is designed for new customers using Marketing Hub software for the first time."

The lesson is the pairing: a fee, and a written scope saying what it covers (in HubSpot's case the data model, lead capture, automation and CRM migration). A fee without a scope is a tax; a scope without a fee gets deprioritised, because unpaid work is optional work.

Intercom describes checklists as "a new type of in-product message that allow you to deliver contextual and personalized lists of tasks to customers using your product". Its best-practice article gives the design rules: "make them look manageable by using between 3-7 tasks in your checklists" and, because "customers only see the first 4-5 tasks before they have to scroll", the order matters.

Shopify runs the same idea in its help centre for a much larger setup: a general checklist that "outlines all the steps that you need to take to get started with Shopify", ending in test transactions. Whichever surface you use, put the task that produces first value in position one or two and cut anything that is about your product rather than the customer's outcome.

Three flexible products, three identical decisions. Airtable's introduction tells first-time builders "If it's your first time building, we recommend that you consider using a template." Notion puts templates at the two moments a new user is most likely to stall: "Add a template to your workspace via the Templates button in the sidebar, or when creating a new page." Figma's Get started hub offers starter projects because "These starter projects are the perfect way to get some hands-on experience in the editor."

For B2B, the template is a pre-built workspace for the customer's segment, filled during implementation with their names and data, so the first login is not an empty state.

A quick start should end with something that exists. Loom's Chrome extension guide ends with "Once you're satisfied with your recording settings, go ahead and select Start Recording." One video. Calendly's learning hub sets out a four-lesson getting-started path, about 17 minutes long, that ends in a first bookable meeting, and frames it as understanding "how everything fits together before we start clicking around".

The test: can you name the noun the user holds at the end? A recording, a booking link, a paid invoice. If the answer is "a configured account", it is a setup guide, not a quick start.

Any product that moves money, sends messages or changes records needs a place to be wrong safely. Stripe offers "test card numbers and test API keys so you can simulate real transactions without moving money". Shopify's setup checklist ends with test orders for the same reason: the customer proves the flow before a real buyer hits it.

Without a formal sandbox, the equivalent is a dry-run step in the plan: send the first campaign to the customer's own team, run the first report against last month's closed data, route the first ticket to the champion.

The live session covers the first week; everything after it has to scale without a calendar. Atlassian announced in May 2024, "Today, we're introducing 100% free and flexible on-demand courses at Atlassian University." Asana made the same move in 2018: "Asana Academy is free", and, as the post adds, "all you need is an Asana account".

Both companies concluded that training is part of the product rather than a service line. A small team does not need an academy: six recorded 8-minute videos, one per job the product does, linked from the checklist, does the same work.

The buyer and the admin get the kickoff. The person invited in week three gets nothing, and decides whether adoption spreads. Slack keeps a separate "Getting started for new members" page, covering profile, notifications, channels and direct messages, written for someone who joined a workspace that already exists: "If you need to communicate with a group of people, send a message in a channel."

Write yours as one page in the second user's situation (someone set this up, you were added, here is the first ten minutes) and send it automatically on invite, because nobody on the customer side will.