Users Sign Up but Never Activate: The SaaS Onboarding Video Playbook
A generic product tour cannot repair unclear value or a broken workflow. Define activation by segment, diagnose the drop-off, and test a contextual micro-video at the moment of need.
The short answer: Show each new user the exact next step to first value, with your real product on screen and a clear reason that step matters. Golpo is built to be the complete AI explainer workflow for that moment. Start from the current product guide, an approved script, or a short recording of the click path. Golpo drafts a segment-specific narration, plans the scenes, and renders the video after you approve the script.
Logged in is not activation. A marketer, an administrator, and a developer can reach first value through different actions. Define the event, the qualifying conditions, the time window, and the evidence that it predicts value. Then use one video only where a visual explanation removes a specific knowledge or confidence barrier.
Who this is for
Product and lifecycle teams who can see signups stall before a defined activation event. The artifact is one contextual video at the step immediately before first value, plus a measurement plan in the analytics you already run.
Diagnose the drop-off
| Barrier | Signal | Best response |
|---|---|---|
| Value | User does not see why to continue | A short outcome example for that segment |
| Knowledge | User cannot complete the step | The real screen and the next click |
| Confidence | User fears a destructive action | A safe preview and the recovery |
| Access | Permissions or data are missing | An admin path, in its own video |
| Product | Flow is broken or excessive | Fix the product. A video should not narrate around it |
What to set on the activation video
The useful hybrid is an explanation of the permission model plus the actual publishing UI. A generated picture of your product is not evidence of how publishing works.
| Control | What changes at the stuck step | Plan |
|---|---|---|
| Prompt Mode, then Script Mode if needed | Golpo drafts a segment-specific script from the approved product guide. Edit script before creating video. When the permission sentence must be spoken exactly, render that wording in Script Mode and put shot directions in Video Instructions. About 1,050 characters fit in one selected minute. | All plans, with length and controls varying. On Pay As You Go, script review bills 10% after the script and 90% after the video. |
| Custom Scenes | Give the safe preview, the permission choice, and the success state their own scenes. You can split or combine sentences inside the engine limit. The map does not rewrite the narration. | Growth and higher, and Pay As You Go. |
| Own Media | Insert the real publishing screenshot or a short recording of the success state. Keep the capture current after UI changes. Generated interface art does not prove the click path. | Business and higher, and Pay As You Go. |
| AI Presenter | An optional welcome can sit beside the explanation in a side-by-side or circle layout, or on Auto so a busy screen gets more room. Keep the presenter off full-screen while the interface is the point. A presenter is a generated performance, not a recording of your founder. Presenter API access is still described as coming soon, so build this in the dashboard. | Creator and higher, and Pay As You Go. |
Worked example: analysts who never publish
This scenario is hypothetical. A reporting product sees analysts connect data and then stop before they publish a dashboard. Interviews point to uncertainty about the preview, who can view the dashboard, and what “published” looks like. The video belongs on the publish step. It shows the safe preview, the permission choice, and the success state, using the current product guide and the real UI.
- Source. Attach the current “publish a dashboard” guide for the analyst segment. In Prompt Mode, ask for a one-minute explainer of preview, permission, and success. Approve any legal or permission sentence and, if it must stay verbatim, supply it in Script Mode.
- Settings. Select 1 minute. Map the three beats with Custom Scenes. Insert the publishing footage with Own Media, including the success state. If you want a brief welcome, add a stock AI Presenter beside the screen so the interface stays visible. The presenter rate applies to the whole selected minute, including a welcome that lasts only a few seconds.
- Script review. Confirm the narration names the preview, the permission choice, and the success state your product actually shows. Then render.
- Result and placement. You should have one clip that can sit immediately before the publish control. Embedding it, and deciding who sees it, happens in your product. Golpo does not ship an in-app player or a funnel report.
- One correction. When the publish button label changes, replace that frame with frame editing if the spoken steps are still right. Frame editing charges the selected duration. On this 1-minute standard video that is 1 credit. Frame editing does not change the soundtrack. If the permission rule changed in the script, revise the narration and render again. Retire screenshots that no longer match the UI.
- One reuse. Build the admin video from the same guide: the person who grants the permission the analyst is unsure about. Keep the scene pattern. Swap the audience, the screen, and the decision. That second video is a different job, not a renamed copy of the analyst clip.
A measurement plan you can actually run
Record the activation baseline for this segment before the video ships. For the hypothetical reporting product, the primary event is “published a dashboard,” with permission errors and dashboard use seven days later as supporting measures. Compare a group that sees the clip at the publish step with a comparable group that does not, when you can hold the rest of the flow steady. Read the result in your product analytics. A finished video does not create an uplift, and completion of the video is not the activation event.
- Record the activation baseline by segment.
- Choose one diagnosed knowledge or confidence barrier.
- Create the smallest reviewed asset from the current guide.
- Place it at that step, with a comparable control when you can.
- Measure activation, time, errors, help requests, and later value.
- Remove or revise the video if it distracts, or if it is covering a broken step.
Plan, duration, and credits
The analyst video in this walkthrough is 1 selected minute. A standard render is 1 credit. One frame-edit version is charged again at the rate of that version. The real UI insert requires Business or higher, or Pay As You Go, which also covers a presenter. Custom Scenes require Growth or higher, or Pay As You Go. Amounts are on pricing. The Free plan is not a downloadable publishing workflow.
Review before you ship it
- Activation is defined for one segment, with a time window and a qualifying event.
- The clip uses the current guide and a current, authorized capture of the real UI, including the success state.
- Preview, permission, and success are each visible. The presenter does not cover the interface.
- The product control and the path to help stay available outside the player.
- Placement and the baseline comparison live in your product, not in Golpo.
- You will read activation, errors, and later use. You will not treat plays as activation or promise a lift.
Use the broader customer education playbook and the support-to-video loop when the same step also generates tickets. Keep the guide current with the release-note and help-doc workflow.
Frequently asked questions
What is SaaS activation?
The earliest qualifying behavior that demonstrates meaningful value for a defined user segment. Video completion is not that event.
How long should onboarding videos be?
As short as the single next action permits. The publish-step walkthrough on this page is 1 selected minute, which is 1 credit for a standard video.
Where should onboarding videos appear?
Immediately before or at a diagnosed knowledge or confidence barrier, inside your product. Golpo does not embed the player or read your product analytics.
Should every onboarding step have video?
Use video when it improves comprehension or confidence at one step. A broken flow, a missing permission, or a value gap still needs a product or access fix.
How should activation video be tested?
In your own analytics, measure the target behavior, time, errors, help requests, and downstream value against a baseline or comparison. Do not treat a higher play rate as activation, and do not assume the video caused a lift.
Build the video for the step before first value
Pick one segment and the step immediately before their first value. Build one contextual video from the current product guide, with the real screen and the success state, and decide in advance which activation event you will read in your own analytics.
Create the activation video · See Business and Pay As You Go
Tags
