DreamJuiceAI logo
Back to blog

SaaS Onboarding Video: What to Make, Where to Place It

Isometric path of onboarding cards toward first value

A SaaS onboarding video is a short, task-focused clip that takes a newly signed-up user from their first session to a first useful result, such as a finished setup or a first completed task. The ones that work are narrow (one step each), show real product screens, and appear at the moment the user needs them: in the app, in the help center, or in a welcome email. This guide covers what to make, how to script it, where to place it, how to keep it current and how to tell whether it works.

Dreamjuiceai
Make Your SaaS Easier to Understand
DreamJuiceAI creates clear product demonstrations and explainer videos for SaaS startups, with each project led by founder Flávio Narciso.
Explore DreamJuiceAI

TL;DR

  • Make a small set of videos, one per activation moment: welcome, first value, milestone, feature deep-dive, troubleshooting. Don’t make one long tour.
  • Keep each video to a single job. Most tutorials work best in the 1 to 5 minute range, and many single-step clips are shorter.
  • Show real screens with realistic data, add captions, and put written steps next to the video.
  • Place each video at the point of need, and judge it by activation and support tickets, not views.
  • Build for change: short, step-based chunks and editable project files let you replace one outdated segment instead of re-recording everything.

Table of Contents

What a SaaS onboarding video is (and what it is not)

An onboarding video serves people who have already signed up. A marketing demo serves prospects who are still deciding. The two can share footage, but the job differs: a demo persuades, an onboarding video gets someone to do something in the product.

That difference shapes everything else. A demo can open with a big promise and a brand sting. An onboarding video should open with the outcome the user is about to reach and get to the first click within seconds. If you want the prospect-facing side, our guide to product demo video best practices covers it.

Common formats, as Vidyard’s guide to customer onboarding videos lays them out, include welcome videos, product walkthroughs, feature tutorials and FAQ or troubleshooting clips. They work as a sequence, not as a single asset.

The five videos most SaaS products need

Think in terms of activation moments rather than a video count. For most products, five slots cover the journey.

Moment Job of the video Where it lives What to watch
Welcome Set expectations, point to the first step Welcome email, first in-app screen First-login conversion
First value (the “aha”) Walk through the one action that proves the product works In-app, at the empty state Activation rate
Milestone Introduce the next capability once the first is done In-app prompt, milestone email Feature adoption
Feature deep-dive Teach a more advanced workflow Help center, linked from the product Retention of users of that feature
Troubleshooting Fix a known failure Help center, error states Ticket volume on that topic

Start with the first-value video. If you can only afford one, it is the one that decides whether a trial user becomes an active user. Then add the welcome clip, then the troubleshooting clips for the questions your support team answers most often.

Welcome video

Keep it human and brief. Say who you are, what the user will achieve first, and where to click. Resist the urge to tour every menu. A welcome video that tries to explain the whole product teaches nothing and gets skipped.

First-value video

This is a screen-led walkthrough of the shortest path to a result. Pick the one action your best retained users all took early, and build the video around it. Show the starting state, every step at a followable pace, and the finished result so the user knows what success looks like.

Troubleshooting videos

These are the least glamorous and often the most useful. Take the top support questions, record the fix in under two minutes, and link the clip from the error message or help article where the problem occurs.

How long should an onboarding video be?

Short, and scoped to a single step. Wistia’s analysis of its own viewing data found that educational and tutorial videos of one to five minutes typically hold viewers for more than half the video, with engagement generally declining after five minutes. Wistia’s broader data also reports that educational videos draw the highest engagement, probably because viewers arrive wanting to learn.

A workable rule of thumb for one activation step is 30 to 90 seconds, and up to a few minutes for a feature deep-dive. If your script needs more, split it into two videos that link to each other. Longer “retain or train” content has its place in a help center for committed learners, but it shouldn’t be the first thing a new user meets.

A script structure that keeps people watching

A simple four-beat structure works for nearly every step-level onboarding clip:

  1. Promise the outcome (5 to 10 seconds). “In the next minute you’ll connect your first data source.”
  2. Show the exact action (30 to 60 seconds). Real screens, cursor visible, one step at a time.
  3. Prove the result (10 to 15 seconds). Show what the finished state looks like.
  4. Say what comes next (5 to 10 seconds). Point to the next video or the written steps.

Around that skeleton, a few details separate useful clips from forgettable ones.

  • State the starting point. Tell the viewer what they need before they begin: a connected account, an invited teammate, a file.
  • Use a clean demo account with realistic data. Empty states look broken, and lorem ipsum looks careless. Placeholder names that resemble the user’s own data help them map the video onto their situation.
  • Add callouts and a clear voiceover. Highlight the button or field in question. Keep narration conversational and cut anything that doesn’t change what the viewer does next.
  • Include the common failure. If one step trips up many people, show the error and its fix in the same video.
  • Link the written steps. Some users want to skim. Text next to the video lets them do either.

The point is function over polish. That said, polish matters for the videos that carry your brand most visibly: the welcome film and the first-value walkthrough are the ones every new user sees.

Learning from a real example

One instructive case is Wistia’s own welcome flow, described by Appcues. Replacing a generic loaner video with a 90-second product-specific one lifted the activation metric the team was tracking by 20%. The more useful lesson sits underneath that number: users had been completing the generic video, but meaningful engagement stayed weak until the content demonstrated the customization actions the product actually needed. Completion is not the same as usefulness.

A second example comes from Userpilot’s write-up of Platformly, a product with a complex setup. By pairing feature videos with interactive walkthroughs, the team reported onboarding-flow completion of 40% or more, against a 30% rate the article describes as generally good. Note the pairing: video explained, the interactive layer guided the doing.

Take both lessons together. Make the video about your product’s actual first task, and decide whether the viewer needs to understand something (video) or perform something (an in-product guide, ideally with a video next to it).

Learning from a real example

Where to place onboarding videos

A good video in the wrong place does nothing. Match the placement to the moment.

  • In the app: welcome, first-value, milestone and troubleshooting clips, triggered at the relevant action or empty state, not on a timer.
  • In the help center: feature deep-dives and troubleshooting, searchable and chaptered.
  • In onboarding email: the welcome video and milestone clips. Use a still frame with a play button and a clear promise in the subject line or first line.

Trigger a video when the user reaches the point of need, then let them dismiss it. A modal that blocks the product before the user has done anything is the fastest way to teach them to ignore your videos.

For the marketing-facing counterpart, where the video sits on a page that persuades rather than teaches, see our notes on landing page video.

Perspective

Most SaaS products are hard to explain quickly, and that problem doesn’t disappear when someone signs up. A new user is still deciding, minute by minute, whether this tool is worth their time.

Our view is that onboarding video deserves the same craft as a launch film, just with a different job. The script has to be tight, the screens have to be real, and the message has to come from someone who understands what the user is trying to achieve. That is why we combine human creative direction with AI-backed production: the strategy and the story stay human, and the production moves fast enough to be ready in 10 working days.

We also think the first-value video and the welcome film are worth doing properly, because every new user sees them. Founder involvement on every project is how we keep the message clear. The founder decides what the product’s first win is and makes sure the video gets the viewer there.

flavio

Making videos that survive your release schedule

Product videos age. When a design changes, a recording that was helpful last month can confuse users the next. Teams that ship weekly feel this most. A few habits keep the problem manageable.

  • One step per video. When a release touches one screen, you replace one clip, not the whole library.
  • Chunk and chapter. TechSmith’s guidance on maintaining a video knowledge base recommends recording in small step-based pieces and keeping editable project files so outdated segments can be swapped without re-recording everything.
  • Keep an audit list. Map each video to the screens it shows. When engineering flags a release that touches those screens, the video goes on the update list.
  • Review recordings before publishing. Screen captures can expose real names, emails or account data. Use a demo account, and redact anything sensitive.
  • Decide which videos are evergreen. Concept-level videos (what the product is for, how the workflow fits together) stay valid longer than click-by-click ones. Put your premium production effort there.

If you are comparing ways to produce this work, our comparison of a freelancer, agency or studio for SaaS video lays out the trade-offs, and the video production workflow shows how a project moves from brief to delivery.

Captions and accessibility

Captions are the default way many people watch in-product video, whether in an open office, on a train or with the sound off. They also make steps searchable and help users who are deaf or hard of hearing. Treat them as part of the video, not an add-on.

Beyond captions, accessibility guidance such as UsableNet’s video accessibility checklist lists accurate synchronized captions, audio descriptions for essential visual content, keyboard-operable player controls, screen-reader support and testing with assistive-technology users. That article is framed around European Union rules, and legal obligations differ by jurisdiction, so check the requirements that apply to where your customers are. One practical habit helps everywhere: if the narrator says “click here,” make sure the screen or captions also say what “here” is.

Captions and accessibility

How to measure whether onboarding videos work

Views are the weakest signal. A user can watch a whole video and still fail to set anything up. Judge each video against the behavior it was meant to change.

Video Primary metric Supporting signals
Welcome First-login to first-action conversion Email click-through, play rate
First value Activation rate Time to first value, drop-off point in the video
Milestone Adoption of the next feature Return visits
Deep-dive Feature usage among viewers Retention
Troubleshooting Ticket deflection Repeat tickets on the same topic

A few practices make the numbers trustworthy:

  • Compare cohorts. Users who saw the video versus those who didn’t, or better, a randomized holdout, so you aren’t just measuring that motivated users watch more.
  • Read the drop-off curve. A sharp fall at 20 seconds usually means the opening promise is wrong. A fall at a particular step means that step needs its own video or a simpler flow.
  • Check support tickets. If tickets about setup don’t drop after you publish a setup video, the video isn’t where users are getting stuck, or they aren’t finding it.
  • Be cautious with headline statistics. Vendor-reported lifts in activation and retention vary a lot by product, audience and how the test was run. Set your own baseline first, then measure your own change.

A simple production plan

If you are starting from nothing, this sequence keeps scope under control.

  1. Map signup to first value. List the steps a user takes from account creation to the first meaningful result.
  2. Write one line per step. Each line becomes a candidate video or chapter.
  3. Pick three videos to start: welcome, first value, and the top support issue.
  4. Script with the four-beat structure above and read it aloud before recording.
  5. Record on a clean demo account with realistic data, in small chunks.
  6. Add captions, callouts and a next-step link, then publish where users get stuck.
  7. Measure after two to four weeks, revise the weakest clip, and add the next one.

Teams often split the work by value. Quick utility clips like troubleshooting fixes can be recorded in-house. The welcome film and the first-value walkthrough, which shape first impressions and the product’s story, often justify a designed, scripted production.

Work with us on your onboarding and product videos

We make launch films, explainers, product demonstrations and social video ads for SaaS and AI startups. Each project covers scriptwriting, creative direction, message strategy, animation of real product screens, voiceover, music and sound design, captions and delivery in multiple formats. Our aim is to deliver within 10 working days, and the founder, Flávio Narciso, leads every project.

Dreamjuiceai

Packages are fixed-price. Our Launch Short starts from $1,500 one-off, the Explainer from $3,500 and the Launch Kit from $7,500. If you need a steady flow of videos as your product changes, the monthly plans are Release at $3,500 per month, Growth at $6,000 per month and Scale from $9,500 per month. See the details on the pricing page, or look at how we handle product tours and demos for software teams.

FAQ

How long should a SaaS onboarding video be?

Aim for 30 to 90 seconds for a single activation step, and no more than a few minutes for a deeper feature walkthrough. Wistia’s viewing data shows tutorials of one to five minutes typically keep viewers for over half the video. If a script runs longer, split it into linked videos.

What is the difference between an onboarding video and a product demo video?

An onboarding video helps someone who has already signed up complete a specific step. A product demo helps a prospect understand the product and decide to sign up. They can reuse footage, but the script, tone and placement differ. If you are weighing formats for prospects, see our comparison of an interactive product demo and an animated demo video.

Where should I put onboarding videos?

Put them where the user needs them: welcome and first-value clips inside the app at the relevant moment, deep-dives and troubleshooting in the help center, and welcome or milestone clips in onboarding email. Trigger by action rather than a timer, and always let the user dismiss the video.

How do I keep onboarding videos from going out of date?

Make one step per video, record in small chunks and keep the editable project files, as TechSmith recommends. Then map every video to the screens it shows so a release that changes those screens triggers an update to just that clip.

How do I know if an onboarding video is working?

Track activation, drop-off points in the video, feature adoption and support tickets on the topic, not view counts. Compare users who saw the video with those who didn’t, ideally with a randomized holdout, so you know the video caused the change.

Sources