Skip to content

HomeArticles

SaaS

SaaS Product Videos

Most software companies need four videos over time: a homepage explainer, a product demo, feature launches, and training or onboarding. Making all four at once is how nothing ships. The homepage gets the explainer. Sales gets the demo and the feature cut. Internal and in-app get training. Start with the page or email that already has traffic and a weak conversion. One done video beats four unfinished ones. Sequence is the strategy. Jude and AccessGrid are the videos we actually made.

By Jonathan Maynard, Content Yard

Updated August 26, 2026 · 6 min read

The SaaS product video stack

Most software companies need four videos over time: a homepage explainer, a product demo, feature launches, and training or onboarding. Making all four at once is how nothing ships. The stack is a map of jobs, not a sprint to produce everything this week.

SaaS product videos are not one asset with four names. Each video has a job, a length, and a page. How we produce them — script, UI-accurate animation, voice, revisions — lives on SaaS video production. This page is the map of which video belongs where.

The SaaS product video stack: job, length, and surface
VideoJobTypical lengthSurface
Homepage explainerWho it is for, what changes30–90sHomepage, ads
Product demoThe product doing the workAs long as askedFeature page, sales email
Feature launchOne new capabilityUnder 40sLaunch page, announcement
Onboarding / trainingA step someone will rewatchAs short as the stepHelp center, in-app

A brand reel is optional. A recording of the whole product is not a strategy. Wyzowl 2026 found 63% of people would most like to learn via a short video — ahead of text, decks, and calls. Short only helps if the video names one job.

What goes on the homepage vs in sales vs internal

The homepage gets the explainer. Sales gets the demo and the feature cut. Internal and in-app get training. Put the wrong video on the wrong surface and a good script still looks like the wrong hire. Match the job to the page.

Put the SaaS explainer on the homepage. Cold traffic has not sat a demo. They need who it is for and what changes — not a tour of modules. Feature lists belong in the page body.

Put the demo behind a “see it in action” click or in a sales email. Put the feature video on the launch page and in the announcement. Keep training where people work — help center, in-app, internal. Do not hide the homepage video in a resource library nobody opens.

Jude is a legal-tech product story — prompt to finished document — the kind of video that can sit where a first-time viewer has to understand the workflow. AccessGrid is a 31-second feature launch. Both are in the work section. Watch them for the job, not the decoration.

  • Jude · 1:48Conference explainerA full product story that walks a legal-tech workflow from prompt to finished document.
  • AccessGrid · 0:31Credential Pools launchShort launch video for AccessGrid’s credential-pool feature — how newly issued passes get credentials automatically.

What to make first

Start with the page or email that already has traffic and a weak conversion. A homepage explainer beats a brand reel. A feature video beats a recap of the whole product. One done video beats four unfinished ones. Sequence is the strategy.

Order of operations we use on the audit:

  1. Where does intent already exist — homepage, pricing, a launch email, a sales loop?
  2. What is the one sentence a stranger should leave with?
  3. Is the interface the proof, or the confusion? That decides explainer vs demo.

If sales repeats a five-minute preamble on every call, make the explainer. If people book demos and then get lost in the UI, make the demo. If you just shipped one capability and need it to travel, make the feature video. Humans direct every video; most videos deliver within 3 days once the brief is clear.

Book a free 15-minute Video Strategy Audit with Content Yard if you want the shortlist of which SaaS product videos are worth making first — not a pitch for a monthly plan.

Frequently asked questions

What is the SaaS product video stack?

Four jobs over time: a homepage explainer, a product demo, feature launches, and training or onboarding. The stack is a map of jobs, not a sprint to produce everything this week. Making all four at once is how nothing ships.

Which SaaS product video goes on the homepage?

The explainer. Sales gets the demo and the feature cut. Internal and in-app get training. Put the wrong video on the wrong surface and a good script still looks like the wrong hire. Match the job to the page.

What SaaS product video should we make first?

The page or email that already has traffic and a weak conversion. A homepage explainer beats a brand reel. A feature video beats a recap of the whole product. One done video beats four unfinished ones.

Which of your videos are SaaS product videos?

Jude and AccessGrid. Jude is a product story for a legal-tech workflow. AccessGrid is a capability launch. Watch those two on this page. We do not invent SaaS logos we did not work with.

Do you sell monthly SaaS video plans on this page?

No. The smallest start is one done-for-you video. Book a free 15-minute Video Strategy Audit if you want a shortlist of which video is worth making first.

We’ll tell you which video will actually solve something. Then we’ll make it.

Free 15 minutes. The audit finds the problem. Then we make the video in 3 days.

A direct call. Not a form. Not a 40-page deck.