How to Make Customer Onboarding Videos for SaaS: A 4-Video Plan

Most SaaS teams make one onboarding video: a long product tour that walks through every menu. New users rarely finish it. A tour shows them where everything is, but it doesn't help them get the one thing done that made them sign up.

Customer onboarding videos work better as a small set, with each video tied to a specific moment in the user's first week. Here's the plan this guide follows:

The word budgets come from an average US English speaking rate of about 150 words per minute, per the National Center for Voice and Speech.

The 2–3 minute cap on the quick start has a source too. In a study of 6.9 million video sessions on edX, Guo, Kim and Rubin (2014) found that learners watched only 2 to 3 minutes of each tutorial video on average, however long the video was. Anything after that point mostly goes unwatched.

The rest of this guide covers how to pick each video's one job, script it, place it, keep it accurate when your UI changes, and check whether it's helping.

Start with your activation event, not your feature list

Before you script anything, write down your activation event: the first action that shows a new user is getting real value. Examples:

• A project tool: the user creates a project and assigns a task to a teammate.
• An analytics tool: the user connects a data source and sees their first chart.
• A video tool: the user exports their first finished video.

Every onboarding video should move someone closer to that event. If a video explains a feature that doesn't help with it, that video belongs later, in the help center or a feature announcement.

Then list the setup steps that stand between signup and that event. Cut any step a new user can skip. Whatever's left is the script for video 2.

Decision rule: if you can't name the activation event in one sentence, fix that first. Without it, you'll end up making another full product tour.

Video 1: the welcome video (30–60 seconds)

The welcome video has one job: tell a new user what to do first and why it's worth doing. It is not a product tour.

A 45-second script has room for about 110 words. Use them like this:

1. The outcome (1 sentence). "By the end of today, you'll have your first report shared with your team."
2. The first step (2–3 sentences). Show the exact screen they'll land on and the button they'll press first.
3. Where help lives (1 sentence). Point to the checklist, docs or chat.

Leave out the company history, the founder's story and the full feature list. The user has already signed up, so there's nothing left to sell. A welcome video that starts pitching makes people wonder whether they made the right choice.

Takeaway: if your welcome video runs past 60 seconds, it's trying to do the quick start's job. Cut it and move that content into video 2.

Video 2: the first-win quick start (2–3 minutes)

This is the most important video in the set. It walks a new user from an empty account to the activation event, one step at a time.

Keep it at 2–3 minutes and one task. The edX data shows people skim and jump around in tutorials instead of watching straight through. The same study found tutorials were re-watched more often than lectures. Its authors recommend visual signposts that make skimming easier.

For an onboarding quick start, that means:

• Number every step on screen ("Step 2 of 4: Connect your data") so people can find their place again after pausing.
• Add chapters if your video player supports them, with one chapter per step.
• Show the finished result first, in the opening 10 seconds, so viewers know what they're working toward.
• Use real, current product screens, with your own sample data rather than a customer's.

One honest caveat: the edX study looked at online course learners, not SaaS users. When it came out, it was the largest study of video engagement to date, and the pattern fits how people use onboarding videos. Still, check your own retention graph before you treat 2–3 minutes as a hard rule.

For the step-by-step production process (outline, script, record, edit), see our guide on how to make a tutorial video.

Takeaway: if the setup genuinely needs more than 3 minutes, split it into two videos at a natural break, such as "set up your workspace" and "create your first report".

Video 3: contextual clips next to the feature

Nielsen Norman Group's research supports this kind of help. Its analysis of mobile-app onboarding found that up-front tutorials "didn't improve task performance". It recommends showing tips in context instead, at the moment a user actually needs them.

A short clip placed beside a feature does exactly that. The best place is usually the feature's empty state: the blank screen a user sees before they've created anything. NN/g's guidelines for empty states recommend using that space for learning cues and a direct way to start the task.

A good contextual clip:

• Runs 30–90 seconds and covers that one feature only.
• Sits next to the primary button ("Create your first automation"), not in place of it.
• Shows a thumbnail with a play icon and doesn't autoplay with sound.
• Can be dismissed, and stays dismissed.

Make clips for the 3–4 features your activated users rely on most, not for every screen.

Takeaway: a clip in the right empty state answers the question at the moment the user asks it. That beats any up-front tour.

Video 4: the next-step video (after the first win)

Once a user hits the activation event, the next goal is a second habit. Usually that's something that makes the product stick: inviting a teammate, connecting an integration, or setting up a recurring workflow.

Trigger this video from that event, not from a fixed day count. A user who activated in 10 minutes and one who took 5 days are ready for it at different times.

Script it the same way as the welcome video: one outcome, one first step, one reason. "Invite your team so new requests stop landing only on you" gives the step a reason. "Invite your team" on its own is just another task.

Takeaway: event-based triggers keep this video relevant. Day-based drip emails often send it to people who aren't ready for it, or who already did it.

Captions, sound and accessibility

Onboarding videos often get watched at a desk, in an open office, with the sound off. Write every video so it still makes sense on mute:

• Captions are required. WCAG 2.1 success criterion 1.2.2 (Level A) requires captions for all prerecorded audio in synchronized media.
• Put the key instruction on screen as text, not only in the voiceover.
• Don't autoplay with sound. Let the user choose to press play.

For more on why muted viewing changed video strategy, see how auto-captions changed silent viewing.

Takeaway: do the mute test before you publish. If a viewer can't complete the step with the sound off, add on-screen text until they can.

Keep onboarding videos accurate when the UI changes

An out-of-date onboarding video does more harm than having none. A user follows it, can't find the button it shows, and decides the product is confusing.

A simple maintenance system:

1. Keep a video inventory. For each video, list the screens it shows, its owner and the date it was last checked.
2. Check the inventory before every release. If a release changes a screen on the list, that video gets updated in the same sprint.
3. Re-check everything every quarter, even if nothing seems to have changed.

This is where the way you make the video matters. A hand-recorded screencast has to be fully re-recorded after a UI change. Poko Motion builds walkthrough videos from your product's code repository, website URL or existing docs, with narration and captions. When the product changes, you regenerate the video instead of re-recording it, and you can make edits by typing instructions like "zoom in on the Invite button". See how to make a product walkthrough video with AI for that workflow.

Takeaway: if nobody owns a video's accuracy, it will go stale. Give every video in the inventory a named owner.

How to tell if your onboarding videos are working

View counts won't tell you much. Track these instead:

• Play rate on each placement: how many people who see the video press play.
• Engagement on the quick start: the share of the video watched, and where people drop off.
• Activation rate for viewers vs. non-viewers: the share of each group that reaches the activation event within 7 days.
• Time to activation: how long it takes viewers vs. non-viewers to get there.
• Support tickets about the steps the video covers, before and after it goes live.

Be careful with the viewer vs. non-viewer comparison. Motivated users are more likely both to watch and to activate, so a gap between the two groups shows a link, not proof that the video caused it. To test for cause, show the video to a random half of new signups and compare activation rates.

Our guide to demo video metrics covers the formulas and how to set up tracking in Google Analytics 4.

Takeaway: judge each video by whether it moves people toward activation, not by how many times it's played.

Your next step

Write down your activation event and the steps that lead to it. That list is the script for your quick-start video. Make that one first. Add the welcome video next, then contextual clips for your 3 most-used features, and keep the inventory up to date as your product changes.