Build log/SaaS

B2B SaaS onboarding: getting new accounts to a first useful outcome

Good onboarding gets a new account to one useful result in its first session, then brings the rest of the team in. Sample data, short checklists and helpful empty states do most of the work.

The short answer

  • SaaS onboarding is everything between sign-up and the moment a new account first gets something useful from the product, such as sending its first quote or booking its first lesson.
  • Define that first outcome as a measurable activation event, track the share of new accounts that reach it within a set number of days, and remove steps that don’t lead to it.
  • In B2B products the customer is a team, so onboarding also covers inviting colleagues, importing existing data and completing the few settings that block real use.

SaaS onboarding is the path from sign-up to the first time a new account gets a useful result from your product. In B2B software that result is usually a piece of real work done faster, such as a quote sent, an order placed or a lesson booked. Good onboarding finds the shortest route to that result, uses sample data, checklists and empty states to guide people along it, and measures how many accounts get there.

Define the first useful outcome and clear the path to it

Start by naming the moment when a new account has had value from the product. It should be an action the customer takes, that you can record, and that matters to their business. Some examples from different kinds of product:

  • Construction management software: the first quote sent to a client.
  • A tutoring platform: the first lesson booked.
  • A trade ordering portal: the first order placed by a customer.
  • A reporting tool: the first report shared with a colleague.

For a product like CurioKids, where parents use an app to book, join and follow lessons, the natural first outcome is a booked lesson. Everything in onboarding should either lead to that moment or wait until after it.

Remove steps before the first outcome

List every screen between the sign-up form and the first outcome, then question each one. Products tend to ask for too much, too early.

Ask only for what the first outcome needs. A quote needs a company name and a client. It doesn’t need a VAT number, a logo, bank details or the size of the team. Ask for the VAT number when the user creates their first invoice, and the logo when they first preview a document, where the reason is obvious.

Offer sign-in with Google or Microsoft accounts if your buyers use them, so there is no password to create. Send the email verification message, let people keep working while it waits, and require verification only before they send anything to their own customers.

Sample data and templates

A blank product is hard to judge. Sample data lets a new user see what a finished job, schedule or report looks like before they have entered anything of their own.

Keep sample data clearly labelled, out of real numbering sequences and totals, and removable in one click. A sample invoice that takes invoice number 1, or a demo client that appears in a VAT report, causes real problems later.

Templates are often more useful than samples, because the user keeps them. In construction software, the price book and labour rates decide how quickly a first quote can be built, so a starter price book the user can edit gets them further than an empty one. Imports matter too. Most new B2B customers arrive with a spreadsheet, and a CSV import with column matching and a preview gets their real data in quickly.

Checklists that point at real work

A short checklist shows a new admin what to do next and how far they have got. Keep it to five items or fewer, tick each one only when the action has really happened, and let people dismiss it. A checklist for construction software might read as follows.

  1. Add the company details that appear on quotes.
  2. Add your first client.
  3. Build a quote from the price book.
  4. Send the quote.
  5. Invite a colleague.

Each item links straight to the place where the work is done. Ticking an item because someone opened a page teaches them nothing and tells you nothing.

Invitations and the rest of the team

A B2B account succeeds when the team uses it, so invitations are part of onboarding. Ask the person inviting to choose a role at the same time, using your roles and permissions model, so new users arrive with the right access.

Design the invited user’s first screen separately from the account owner’s. An estimator invited to a job management tool should land on the jobs assigned to them, with the setup checklist left to the admin. Make invitation links expire, let admins resend them, and show pending invitations in the user list. Larger customers will want people added automatically through single sign-on and SCIM.

Empty states that tell people what to do

An empty state is what a screen shows before it has any data. Every new account sees all of them, so they are part of onboarding whether you design them or not.

ScreenUnhelpful empty stateUseful empty state
Jobs“No jobs found.”What a job holds, a button to create one and a link to import a spreadsheet
ScheduleAn empty calendarA note that jobs appear here once they have dates, with a link to the jobs list
ReportsCharts with no dataOne sentence on what each report shows and what data it needs
TeamOnly the owner’s nameAn invite button, with each role explained in a line

A useful empty state says what belongs on the screen, why it matters and the one action that fills it.

Measuring activation

Activation is the share of new accounts that reach the first useful outcome within a set period. Record an event when an account is created and when it first completes the outcome. Then calculate the rate for each monthly group of sign-ups, called a cohort.

For example, if 80 accounts signed up in March and 30 of them sent a quote within 14 days, activation for March is 30 ÷ 80 = 37.5%. Track the median time to that first outcome as well, and the step where accounts that don’t activate stop. That step is where to work next. Activation sits alongside revenue and churn among the metrics an early SaaS should track.

Numbers show where people stop. Conversations show why. Each month, call or email a few accounts that stalled and ask what got in the way.

Emails and human help

Emails triggered by what an account has or hasn’t done, such as a reminder to send a quote they drafted, are more useful than a fixed sequence sent to everyone. Keep them about using the service the customer signed up for. Messages that promote other products or offers count as direct marketing, which has its own rules under PECR and UK GDPR, so keep the two kinds separate. For larger accounts, a short call to help set up the first real job is often the quickest onboarding of all.

Building a product people need to adopt quickly? See how we scope an MVP around the first useful outcome.

Questions people ask

What is activation in SaaS?

Activation is the point at which a new account first gets real value from the product, defined as a specific recorded action such as sending a first invoice. The activation rate is the share of new accounts that reach it within a set number of days. It is one of the earliest signs of whether a product will keep its customers.

Should onboarding include a product tour?

We’d use short hints at the moment a feature is needed in preference to a long tour at sign-up, which people can click through without learning anything. If you use a tour, keep it to a few steps and end it on the action that leads to the first useful outcome.

Should sample data sit in the customer’s real account?

It can, if it is clearly labelled, excluded from totals, reports and numbering, and removable in one click. The alternative is a separate demo account, which keeps real data clean but means the user has to switch back to start their own work.

How do you onboard the rest of a customer’s team?

Make inviting colleagues part of the setup checklist, ask for each person’s role when inviting them, and give invited users a first screen built around their own work. For larger customers, provisioning through single sign-on and SCIM adds people automatically as their IT team grants access.

Written by Flavoureak

We build and run Estimark, CurioKids and CalcStack, and we build web and mobile software for other businesses. Start a project.