Brett LindenbergCustomer onboarding best practices all serve one goal: get each new customer to the first result they bought your product for, as fast as possible, and then make that result part of their routine. In practice, you define the first result for each type of customer, ask new customers what they came to do, remove setup steps that do not lead there, teach features when customers need them, give larger accounts a named owner and a dated plan, measure activation and time to value, and contact customers who stall before they ask for help. The ten practices below apply to SaaS products, B2B accounts, and client work at service firms. In the demo below, choose a new customer's first goal, then pick the setup step that gives that customer a useful result.
What customer onboarding covers
Customer onboarding is the work between a signup or signed contract and the point where the customer gets value from your product without your help. Several related terms describe parts of that work.
| Term | What it usually means | Onboarding is done when |
|---|---|---|
| Customer onboarding | The whole process for an account, from purchase to first value | The account reaches its first result and keeps using the product |
| User or product onboarding | The in-product experience for each person who signs in | Each user can complete the core task alone |
| Client onboarding | Onboarding at agencies, consultancies, and other service firms: contract, kickoff, access, and a delivery plan | The client approves the first deliverable |
| B2B or enterprise onboarding | A project with several stakeholders, integrations, and a rollout plan | The customer's teams use the product in their daily work |
| Data onboarding | Moving a customer's existing data into your product; in marketing, also matching offline records to online audiences | The data is complete and the customer trusts it |
| Digital onboarding | In banking and insurance, opening an account online, including identity checks | The applicant opens and uses the account |
Onboarding ends when the customer reaches value on their own. For a scheduling tool, that might be the first meeting booked through it. For an agency client, it might be the first approved deliverable. Retention work starts there, and so does customer education, which teaches the deeper skills that keep customers using more of the product. Our guide to building a customer education program covers that next stage.
1. Define the first result for each customer type
Many onboarding problems start with a vague goal such as "complete setup." For each main type of customer, write down the first result the customer can see, and make it an event you can find in your product data. Product teams call this the activation event or the "aha moment." Time to value is the time from signup or contract to that event.
In our own trial, the first result is the first time a viewer outside the customer's team watches the customer's interactive video. Our trial records each stage on the way: building the first video, testing it in preview, sharing it, and then that first outside viewer. We count building and testing as progress toward the result, because a video nobody outside the team has watched has not done its job yet.
To find the right event for your product:
- Compare customers who renewed or expanded with customers who left. List what the first group did in its first weeks that the second group did not.
- Ask recent customers when they first believed the product would work for them. Their answers name the result, and it is often a different thing from the feature you would have guessed.
- Choose an event that has value for the customer, such as a report sent to their manager or a first invoice paid, rather than a login count.
2. Ask each customer what they want to do first
A personalized onboarding path starts with one direct question. Ask for the customer's goal or role at signup or at the kickoff call, then show the path for that answer. Keep the list of answers short and include an "other" option with a text box, because those replies show you which paths to add next.
Our own signup works this way. Before a new account owner creates anything, Mindstamp asks what result they need: capture viewer information, measure knowledge and understanding, drive viewers to a website or form, guide viewers to the right content, or something else. The answer stays with the account, so anyone who follows up later knows what the customer came to do.
Ask instead of guessing from job titles or company size. A declared answer is accurate, and the customer understands why the path changed. A welcome video can ask the same question: in Mindstamp, a button at the start of the video sends each viewer down the matching branch and saves the choice with the viewer's record, as the demo at the top of this page does.
3. Remove setup steps that do not lead to the first result
List every step between signup and the first result: each form field, permission, invitation, and setting. For each one, ask whether the customer needs it before the first result. Move the rest to later, give it a sensible default, or do it for the customer.
- Pre-fill what you already know from the signup form, the contract, or your CRM.
- Offer sample data or a template so the first session produces something real. Our signup offers a sample video and templates next to the upload option, so a new user can build a first interaction before their own footage is ready.
- Leave team invitations, integrations, and branding until after the first result, unless that result depends on them.
- Count the fields and clicks on the path each quarter. They grow back as each team adds one more question.
4. Introduce features when customers need them
Progressive disclosure means you show the few options most people need first and keep advanced options one step away. Jakob Nielsen described the pattern in a 2006 Nielsen Norman Group article, and it applies to onboarding as much as to screen design. A new customer needs the core workflow, and the full feature list can wait.
Nielsen Norman Group's research on onboarding tutorials versus contextual help (Page Laubheimer, 2023) found that tutorials shown at first launch interrupt users, do not necessarily improve task performance, and are quickly forgotten. Help that appears when the user reaches the task avoids those problems.
We follow this in our own editor. A new trial owner who opens a video with no interactions sees one prompt, "Let's add your first interaction," with three choices: a button, a hotspot, or text. The next step asks what should happen when a viewer clicks it. A short guide then points to the controls for timing, click behavior, and style, and to the save button. Questions, branching, and the rest of the editor wait until the customer has made one thing that works.
- Trigger the next lesson from what the customer did, and use the calendar only as a backup. A customer who finished setup gets the next feature tip; a customer who did not gets help with setup.
- Give experienced customers a way to skip the guidance and see every option at once.
5. Teach by doing, with short guided tasks
Customers learn a product by using it for a real task. Guided walkthroughs, checklists, and prompts in empty screens all work when they end in a result the customer keeps, such as a first project built with their own data. A walkthrough that only points at buttons teaches little.
- Use a short onboarding checklist to show the path and the progress. Include only the steps that lead to the first result, and link each item to the help article or video that explains it.
- Let customers complete checklist steps in any order the product allows.
- Decide whether points and badges suit your audience before you build them. In business software, a visible checklist often does the motivating work.
- Ask why customers stall as well as where. Formbricks' guide to user onboarding best practices recommends a short welcome survey and in-app feedback during onboarding, because analytics show where users drop off but not why.
Video helps with steps that are hard to explain in text, such as a setting that spans several screens. Make each video one task, with a question at the point where the customer must decide something and a link to the screen where they do it. In Mindstamp, questions pause the video and can require an answer before playback continues, so a setup video can confirm a decision before it moves on.
6. Coordinate email, in-app guidance, help content, and people
Customers look for help in different places. Decide which channel does which job, so the messages support each other and do not repeat.
| Channel | Best use in onboarding | Typical trigger |
|---|---|---|
| In-app guidance | The next step, on the screen where the customer is working | The customer opens a feature for the first time |
| Reminders and next steps when the customer is away from the product | A setup step is still unfinished | |
| Help center and video | Answers the customer looks for alone | A search, or a link from an in-app or email message |
| People (kickoff, calls, chat) | Decisions, blockers, and accounts with several stakeholders | Kickoff, a missed milestone, or a request |
Base each message on what the customer has done, with a fixed schedule only as a fallback. A day-three email that says "invite your team" is noise to a customer who invited the team on day one.
For client work, agree on channels at kickoff: where questions go, who answers them, how fast, and where you both record decisions. Marlie's list of client communication best practices covers these habits, including response-time standards and written records of what was agreed.
7. Run B2B onboarding as a project with an owner and milestones
Business customers bring more people: the buyer, the admin who sets up the account, the employees who use it, and often IT and procurement. Client onboarding at a service firm and B2B customer onboarding look alike at this point, and both work best when you run them as a project with owners and dates.
- Hand over from sales in writing. Record the goals the customer gave during the sale, the people involved, and any promises made, so the customer does not repeat them at kickoff.
- Name one onboarding owner on your side and one on the customer's side.
- Use the kickoff to confirm the goal, the first result, and the dates.
- Write a short success plan with milestones, owners, dates, and how you and the customer will confirm that each milestone is done.
- Review each milestone when it is due. When one slips, find the cause before you move the date: no named owner, a dependency that is not ready, or no agreed definition of done.
- Plan for change inside the customer's company. Find a champion in each team that will use the product, and give that person access and training before the general rollout.
For service firms, the weeks after the sale often decide whether a client stays. CRM Africa's article on why many businesses lose money after the sale describes how poor handoffs, scope creep, and communication gaps after the deal lead small firms into rework, late payments, and lost repeat business. The demo below practices the milestone diagnosis from the list above.
8. Plan data onboarding and integrations before kickoff
When the first result depends on the customer's own data, data onboarding is part of customer onboarding. Imports, single sign-on, and integrations often depend on people outside the project, such as the customer's IT team, so start them early.
- Ask for a sample of the customer's data before kickoff and test the import with it.
- Write down how each field in the old system maps to a field in yours, and agree on what happens to records that do not fit.
- Run a test import, have the customer check the result, and fix problems before the full import.
- Find out who on the customer's side owns access, single sign-on, and the security review, and put their dates in the success plan.
Where you can, connect to the place the customer's data already lives instead of moving it. Mindstamp, for example, adds interactions to video the customer already has, including video hosted on Vimeo, Wistia, JW Player, or Kaltura, so a new customer can start without re-uploading a library.
9. Measure onboarding and change one thing at a time
Track a few onboarding metrics for each customer type and each signup month, so you can see whether a change helped.
| Metric | How to calculate it | What it shows |
|---|---|---|
| Activation rate | New accounts that reach the first-result event within a set period, divided by all new accounts in that period | Whether onboarding gets customers to value |
| Time to value | Median time from signup or contract to the first-result event | Whether onboarding is getting faster |
| Step completion | Accounts that finish each step, divided by accounts that started it | Where customers stall |
| Early retention | Accounts still active or paying at 30, 60, or 90 days, divided by accounts that started | Whether the first result turns into continued use |
| Tickets per new account | Support tickets from accounts in onboarding, divided by the number of those accounts | Where self-service help is missing |
| Onboarding satisfaction | Survey score at the first result or at the end of onboarding | How the experience felt to the customer |
Use the median for time to value, because a few slow enterprise accounts can pull the average far from the typical customer. When you change the onboarding, change one thing at a time and compare customers who signed up before and after the change. With enough signups, an A/B test gives a cleaner answer. For the retention formula, see our guide on how to calculate retention rate, and for in-product measures, our list of user engagement metrics.
10. Implement Proactive Customer Support
Proactive support means you contact a customer when the signals show they are stuck, before they open a ticket or stop using the product without telling you. In onboarding, it catches the customers that the other nine practices missed.
HubSpot Service Hub Professional and Enterprise let teams create customer health scores using call activity and survey responses. Teams can use these scores to identify customers at risk of leaving and decide who needs support first.
This preemptive strategy shows customers that someone is following their progress and will step in early. It also gives your team a short, ranked list of accounts to contact each week, so help arrives before the customer is frustrated.
Signals that should trigger outreach during onboarding
| Signal | What it often means | What to do |
|---|---|---|
| A setup step is still open days after the customer started it | A permission, a data problem, or an internal decision is blocking it | Offer help with that exact step; for larger accounts, call the onboarding owner |
| No sign-in during the first week after signup or kickoff | The champion is busy, or the project lost priority | Contact the champion and the sponsor, and restate the first result and its date |
| Repeat visits to the same help article | The article does not answer the question | Send the answer, then fix the article |
| A missed milestone in the success plan | No owner, a dependency that is not ready, or no agreed definition of done | Review the milestone with both owners |
| A low score on the first survey | The experience does not match what the sale promised | Read the sales handoff notes, then call the customer |
Make each message specific. Name the step, the problem you can see, and the fix, so the customer can act without a reply.
An onboarding video can collect some of these signals directly. A setup video that asks "Where are you stuck?" records each viewer's answer. With the HubSpot integration on supported plans, Mindstamp writes answers, clicks, branches, and completion to the contact record after the viewing session ends; it needs the viewer's email to find the contact. Webhooks, also on supported plans, send view, interaction, and lead data to other systems during background processing, so allow for a short delay.
Where video fits in customer onboarding
Video helps onboarding in three places: a welcome from the account team, task videos for steps that span several screens, and help-center answers for common problems. It works against you when a long recorded tour takes the place of doing the task in the product.
Keep each task video short. Across 8.07 million views of 18,315 Mindstamp videos recorded from 2018 to October 2026, videos of one minute or less averaged 59.4% of the video watched, the highest of any length group, compared with 39.2% for videos of two to five minutes. Many factors differ between these videos, so treat this as a pattern in Mindstamp data and not a rule for all video.
Ways to use interactive video in onboarding:
- A welcome video that asks each customer's goal and opens the matching setup task through video branching, as in the demo at the top of this page.
- A setup video with a question at each decision point, so the customer confirms a choice before the next step.
- A welcome video that names the customer or company with personalization variables such as {{NAME|there}}, which show the fallback text when a value is missing.
- A troubleshooting video in the help center that asks what the customer sees and opens the matching fix, as described on our customer support page.
Viewers do not need a Mindstamp account to watch, and the report shows each viewer's answers and path. For product training after onboarding, see our customer education page and our guide on driving SaaS customer engagement with interactive video.
Common questions about customer onboarding
What are the steps of customer onboarding?
Most onboarding follows the same order: the sales handoff, the welcome or kickoff, setup and data import, the first result, training on the next features, and a review when onboarding ends. Self-serve products put most of these steps inside the product. Enterprise accounts spread them over weeks, with named owners on both sides.
What is a customer onboarding strategy?
A customer onboarding strategy is the written plan behind the practices above. It names the customer types you serve, the first result for each, the channel or person that delivers each step, which accounts get a named owner, and the metrics that show success. Keep it short enough that the team uses it.
How long should customer onboarding take?
Onboarding should take as long as the customer needs to reach the first result. Set a target time to value for each customer type from your own data: measure the current median, then work to shorten it. A self-serve product can aim for the first session. An enterprise rollout with integrations and security review can take months.
How do you make customer onboarding engaging?
Make it about the customer's goal, and have the customer do something real early. Ask what they want to do, get them to a result they can show a colleague, show their progress, and add a person or a short video where a choice needs explanation. Interactive video makes a welcome video two-way: the customer answers a question and sees the path for that answer.
What can customer onboarding learn from game onboarding?
Well-made games teach through play. The first level introduces one action, lets the player try it where a mistake costs little, gives feedback at once, and adds the next action after the player has used the first. Game teams then judge onboarding by retention. Unity's analytics documentation (checked October 2026) reports day 1, 7, 14, and 30 retention for each install date: the share of players who play on those days after installing. Both habits transfer to business software. Teach one task at a time inside the product, and measure onboarding by how many customers come back.
What is digital onboarding?
In banking, insurance, and fintech, digital onboarding means opening an account online, including the identity checks that regulation requires. In the US, for example, banks must run a Customer Identification Program with risk-based procedures to verify each customer's identity (31 CFR 1020.220). The practices in this guide still apply: ask only for what the checks and the first transaction need, explain why you ask, and show applicants where they are in the process.
How to build or improve your customer onboarding program
Whether you are building a customer onboarding program at a SaaS company or fixing one that loses customers, the work follows the same order.
- List your main customer types and write down the first result for each.
- Map the current path from signup or contract to that result, with every step, email, and handoff.
- Measure the activation rate, the median time to value, and the completion rate of each step, for each customer type.
- Talk to recent customers who stalled or left early, and read their support tickets. They explain why the numbers look the way they do.
- Fix the step where the most customers stop. The fix is usually to remove the step, move it later, or add help at that point.
- Decide which accounts get a named owner and a success plan, and write the playbook for them.
- Set up the outreach signals from practice 10.
- Review the metrics each month and change one thing at a time.
If you do one thing this week, write down the first result for your largest customer type and check how many of last month's new customers reached it. That number shows you where to start.
