Video Marketing

SaaS Product Video Examples: 14 Videos by the Part They Show

Introduction

A SaaS product has no box

A SaaS product has no box. Nobody can pick it up, turn it over or feel its weight.

So a SaaS product video has to choose which part of the product stands in for the whole. The screen your user works in? The result it hands back? The connections behind it? The plan the buyer signs?

Show all four in 90 seconds and the video proves none of them. A screen tour won't move the finance lead. A cost slide won't move the engineer.

The short answer: the SaaS product videos that work show one part of the product, picked for the person watching. Cockpit shows the screen your user will work in. End Result shows what the product hands back. Pipework shows how it connects to systems the buyer already runs. Order Form shows the cost case or the plan that fits. The 14 examples below are sorted by the part they show.

Planning a SaaS product video?

Talk to the Advids team about style, budget and timeline before you write the script. Start with the one part of your product the video has to show.

Let’s talk

14 examples

SaaS Product Video examples

Part 1 · Cockpit

If buyers can't picture using it, show the screen they'll work in.

A pilot doesn't judge a plane by a photo of its engine. They ask to sit in the cockpit. Your buyer judges your software product the same way: by the screen they'll face every day.

I call it the Cockpit: the real interface, doing real work, with the buyer's own inputs. Four examples.

nCino Banking Advisor product feature video

nCino's Banking Advisor puts AI inside a banker's daily screens. In 41 seconds, the video shows the actual interface, not a metaphor for it.

What works here:

  • A policy question goes in. A structured answer with numbered points comes back, exactly as the banker will see it.
  • Documents are dragged in and their data is pulled out. Progress bars and success marks show each step finish.
  • The last screens carry the decision: a covenant breach flagged from financial statements, a credit use graph, then a drafted credit memo.

The move: Record the 3 screens your buyer will open most in week one. If a screen won't be opened in week one, cut it.

Vectary interactive 3D design video

Vectary shows its 3D design tool through one real object: a racing shifter part imported from CAD software. Every feature is a click on that part.

What works here:

  • Hotspots do the explaining. Click one and the part shows its size options, with dimensions that adjust to the chosen size.
  • Technical details float beside the object. Hover over the part, its shape lights up, and a click changes the material.
  • It names 3 groups who use the same file: manufacturing teams, account managers and external partners.

The move: Pick one real object or record your buyer works with, and run every feature on it. If a feature needs a second example, save it for a second video.

Fractal Kalaido.ai software walkthrough video

Kalaido.ai by Fractal turns text prompts into images. The video stays on the two things a user touches: the prompt box and the picture it returns.

What works here:

  • Prompts arrive in several Indian languages, not only English. A buyer in that market sees their own words on screen.
  • A “Prompt Enhanced” feature refines a rough request before the image is made, so the viewer sees the tool help them.
  • Every result fits one theme, imagining India: a vintage Kolkata taxi, traditional dancers, a futuristic cityscape.

The move: Show the input and the output side by side, in your buyer's own language. If the input needs your jargon, rewrite it.

Ericsson Telecom Software product video

Ericsson's video sells AI for the OSS/BSS software telecom operators run. It puts the operator's view on screen: a city map and a chat window.

What works here:

  • A city map shows network insights in real time. That's the view a network team watches all day.
  • A chatbot interface takes questions in plain language. That's how generative AI shows up for the operator.
  • Behind the screens sits one named idea, the Cognitive loop, in 5 steps: Measure, Assure, Propose, Evaluate and Actuate.

The move: If your product runs on AI, show the screen where a person talks to it. Then name the loop behind it in 5 words or fewer.

Part 2 · End Result

If the work happens out of sight, show what comes out.

A screen is only worth showing if someone works in it. Some products do their work in a pipeline, a sensor or a model, and the buyer only sees the result.

A bakery window shows the bread, not the oven. Your buyer pays for the output too: a heatmap, a dashboard, a summary. I call it the End Result: what your product hands back, shown before anything else. Three examples.

Folium Smart Sensor Network video

Autogrow's Folium is a wireless sensor network for greenhouses: hardware plus data. The video spends its best seconds on what the data becomes, a heatmap of the greenhouse.

What works here:

  • The unit is taken apart in CGI first. 6 readings, from air temperature and humidity to CO2 and light, come from one compact sensor.
  • Then the output. Humidity, light and temperature gradients sit on the greenhouse layout as color-coded heatmaps.
  • On-screen questions tie the map to grower worries: microclimates, CO2 loss and the effect of climate on beneficial insects.

The move: Show the one view your buyer couldn't see before they bought you. If it looks like any other chart, label it with their question.

Chronosphere Animated software demo

Chronosphere sells observability for cloud-native systems. Its 80-second explainer turns a messy pile of metrics into the screens an engineer actually reads.

What works here:

  • The problem is drawn as sprawl: data and costs growing out of control across microservices and containers.
  • Raw data streams pour through a “C” shape and come out as clean, organized dashboards. One motion explains the product.
  • Then the payoff: dashboards and a metrics profiler that help engineers spot issues faster.

The move: Draw your input as a mess and your output as the screen a buyer reads. If your video turns into a dashboard tour, keep only the screen that changes a decision.

Amazon Bedrock Data Automation video

Amazon Bedrock Data Automation turns documents, images, video and audio into usable data for developers. The animation names exactly what comes out.

What works here:

  • It starts on the input most companies already have: unstructured content in files, and a manual process to make it usable.
  • Then the outputs, one by one: video summaries of key moments, detection of inappropriate image content and automated document analysis.
  • Trust is part of the output. Results carry confidence scores and are grounded in the original content.

The move: Name the outputs your product returns, in the order a buyer uses them. If you can't name 3, your video is showing the engine instead.

Part 3 · Pipework

If IT asks how it fits, draw the connections.

A result is only half the sale. Next, someone in IT asks where the data comes from and what it has to plug into.

A plumber's drawing shows the pipes behind the wall, because that's where leaks start. Your buyer's tech stack is that wall. I call it the Pipework: the systems your product connects, drawn as one simple picture. Four examples.

Five9 Workflow Automation video

Five9 Workflow Automation connects a contact center's systems so agents stop doing busywork. The video draws those connections instead of touring the interface.

What works here:

  • It opens on one agent buried in manual tasks and too many screens. Anyone who runs a contact center has seen that desk.
  • Animated flowcharts link marketing, service and sales systems through pre-built connectors. The plumbing is the product, so the plumbing is the picture.
  • It ends back on the agent, calm and focused on the customer, with real-time data in front of them.

The move: Draw your connectors as lines between systems your buyer already pays for. Then return to the person the lines were built for.

State Street Alpha software explanation video

State Street Alpha for Post Trade sells one front-to-back platform to asset managers. The video turns invisible back-office plumbing into a road trip.

What works here:

  • Trading volume is a delivery truck overflowing with money blocks on a winding road. Failed trades and settlement backlogs become traffic signs.
  • Manual reconciliation desks give way to one glowing cloud holding the Alpha platform, front to back, from a single provider.
  • Trade matching and settlement run automatically in real time. Then a world map lights up with new asset classes and regions.

The move: If your product lives in the back office, give the flow one physical picture, a road or a pipe, and keep it for the whole video.

Amdocs Software explanation video

Amdocs sells the software that lets telecom operators charge for 5G services. The video shows where its product sits: between the network and the money.

What works here:

  • Network terms become services. Latency, edge and slices map to smart parking, telesurgery and connected cars.
  • The product gets one name, the 5G Value Plane, and 3 parts: cloud-native charging, policy functions and network analytics.
  • Its center is drawn as a “5G brain”: a central catalog that joins business, IT and network operations.

The move: Draw your product as the layer between two things your buyer already owns. Then name what passes through it.

Microsoft Dragon Copilot feature video

Microsoft's Dragon Copilot clip covers one feature: partner apps and agents from Microsoft Marketplace, running inside clinical workflows. The example task is revenue cycle management.

What works here:

  • It starts from what buyers already know the product does, then adds the new layer: “Beyond automating notes.”
  • Partners plug in. Revenue capture help comes from “numerous different partner providers,” so customers choose the guidance that suits them.
  • The payoff is named for the clinician: accurate, timely reimbursement for care delivered.

The move: If partners extend your product, show one partner task running inside your screen. Then say who gets paid, or saves time, because of it.

Part 4 · Order Form

If finance has to sign, show the cost case and the plan that fits.

Fit settles IT. Then the deal lands on a desk that never watched the video: finance.

A menu prints the price next to every dish, so nobody orders blind. I call it the Order Form: the cost case, or the plan your buyer would pick, shown on screen. Three examples.

Thinfinity VDI cost video

Thinfinity sells virtual desktop software on Oracle Cloud. Its 2-minute video is a cost sheet in motion: 4 savings levers, added up at the end.

What works here:

  • The levers are numbered: licensing, cloud infrastructure, hypervisor costs and autoscaling. A finance reader can follow the math without a sales call.
  • Each lever names who it helps. Concurrent licensing means paying only for sessions in use, which matters for call centers, seasonal staff and rotating shifts.
  • The close adds it up. Thinfinity claims a total cost of ownership “up to 60% lower,” with orchestration built in and no extra subscription.

The move: Number your savings and name the buyer each one helps. If finance can't repeat the levers after one viewing, you have too many.

BarTender User adoption video

BarTender by Seagull Scientific sells labeling software to companies of every size. The video ends where a buying decision starts: which edition fits.

What works here:

  • The workflow comes first, in 3 verbs: create, automate, manage. Design happens in the interface, and automation runs on a conveyor belt.
  • Then the plans. Professional, Automation and Enterprise editions are laid out, so a small team and a global company can each find theirs.
  • A world map closes the enterprise case: print from anywhere to anywhere, with security and management in one place.

The move: Name your plans on screen and match each one to a buyer size. A viewer who finds their plan in the video reaches pricing ready to pick.

Comarch Animated software demo

Comarch's video sells AI for telecom operations on one argument, written into its title: lower long-term costs. The product is Comarch AI Control Desk.

What works here:

  • Scattered colored blocks stand for expert knowledge spread across people. The AI stacks them into one knowledge base.
  • Roles are clear. The AI takes the repetitive tasks, and experts verify its work and supervise.
  • The close is the cost case: continuous improvement, higher efficiency and lower operating costs over time.

The move: If your price pays back over years, not weeks, put the long-term cost in your title and end on it. Then show who stays in charge.

Pick your part

Which part should your SaaS product video show?

The short answer: ask who has to say yes after watching. The daily user, the buyer of the result, IT or finance? The answer picks the part. One part per video. If two people sign off, make two short videos instead of one long one.

If your viewer isUseDo thisExample to copy
The person who'll use it dailyCockpitThe real screen, doing their tasknCino
Buying a result, not a toolEnd ResultWhat comes out, named and shownAmazon Bedrock
IT, checking the fitPipeworkThe connections, drawn as one pictureFive9
Finance, checking the costOrder FormThe savings, or the plan that fitsThinfinity

Now go back to the box nobody can hold. A video can't hand your product over. But it can hand over the one part your viewer came to check.

The move: list who signed off on your last 5 closed deals: users, IT, finance or the executive who wanted the result. Make your next product video show the part the most common signer needs.

Show everything and the product looks big. Show one part and it looks real.

FAQ

SaaS Product Video Examples FAQ

What is a SaaS product video?
A SaaS product video is a short video that shows one part of a software product to the person who has to say yes. That part is the screen, the result, the connections or the cost. nCino's Banking Advisor video, for example, shows the real screens a banker will use in 41 seconds.
What part of a SaaS product should a video show?
The part your viewer has to approve. A daily user needs the screen. A buyer paying for an outcome needs the result. IT needs the connections, and finance needs the cost case or the plan. Pick one per video.
How is a SaaS product video different from a SaaS demo video?
SaaS demo videos follow one task to answer a buyer's doubt. A SaaS product video decides which part of the product stands in for the whole. A demo is often the Cockpit version of a product video.
How is a SaaS product video different from a promo or a launch teaser?
A SaaS promo video sells the brand and the offer, often in under a minute. A SaaS launch teaser builds interest before release and hides most of the product. A product video shows a real part of the product, in enough detail to judge it.
How long should a SaaS product video be?
Most of the examples here run 41 seconds to 1:30. 12 of the 14 come in under 1:30. The longest is Thinfinity's at 2:00, because it walks finance through 4 cost levers. Cut anything that doesn't serve the one part you chose.
Should a SaaS product video use the real interface or animation?
Use the real interface when the buyer will work in it, the way nCino and Vectary do. Clean screen capture matters here. Use animation when the work is invisible, like State Street's back-office flow. Many SaaS UI videos mix both.
How do you show a SaaS product that has no interface?
Show what goes in and what comes out. Chronosphere pours raw data into dashboards. Amazon Bedrock Data Automation names each output, from video summaries to document analysis. Technical animation videos use the same approach for systems nobody can see.
How many features should a SaaS product video show?
As few as the chosen part needs, usually 2 or 3. Vectary runs every feature on one shifter part. Tie each feature to a benefit, and give feature depth its own product features videos.
Should a SaaS product video mention pricing?
Only when finance is the viewer. BarTender names its Professional, Automation and Enterprise editions. Thinfinity walks through 4 savings levers. Both give the viewer a plan or a cost case without quoting a price.
How do you show an AI feature in a SaaS product video?
Show the screen where a person talks to the AI, and say who stays in charge. Ericsson shows a chat window. Comarch has experts verify the AI's work. Fractal's “Prompt Enhanced” feature shows the tool improving the user's request.
Should a SaaS product video use a voiceover?
Usually, yes. A voiceover lets the screen show the product instead of filling it with text. Add captions either way, because many viewers watch with the sound off.
Which buyer should a SaaS product video speak to?
One. Write a short buyer persona for the person who signs off, then pick the part they need. Vectary names manufacturing teams, account managers and external partners. Thinfinity names call centers, seasonal staff and rotating shifts.
How do you measure whether a SaaS product video works?
Pick the goal first: trial sign-ups, demo requests or a pricing page visit. Track clicks on the call to action against it. Then check where viewers drop off. That second is the next thing to fix.

Patterns from the analysis

SaaS Product Video Best Practices

Four of the videos above were broken down from their full transcripts: Thinfinity, Amazon Bedrock Data Automation, Microsoft Dragon Copilot and Vectary. Four patterns showed up. Four is a small sample, so read each count as what these four did, not as market data.

Named Users

Should a SaaS product video name who uses it?

Observation
Thinfinity names call centers, seasonal staff and rotating shifts. Vectary names manufacturing teams, account managers and external partners. Microsoft names health care organizations, developers and clinicians. Amazon names developers.
Data
4 of 4 named the people who use or gain from the product.
The move
Name your buyer's role or situation in the first half of the video. The right viewer stays. The wrong one leaves early.
Existing Stack

Should a SaaS product video show what the product works with?

Observation
Vectary starts on a part imported from CAD software. Thinfinity runs on Oracle Cloud with orchestration built in. Dragon Copilot brings partner apps from Microsoft Marketplace. Bedrock Data Automation works alone or with Bedrock Knowledge Bases.
Data
4 of 4 showed the product working with something the buyer already has or knows.
The move
Open on a tool or file your buyer already uses. Then show your product picking it up.
Trust Line

How do SaaS product videos make AI output believable?

Observation
Amazon says results carry confidence scores and are grounded in the original content. Microsoft says the feature is built on a responsible AI framework. Thinfinity and Vectary sell no AI output, and say nothing about it.
Data
2 of 4 addressed trust, and both were the AI products.
The move
If your product generates answers, give one line on how the buyer can check them. A score or a source beats a promise.
Hard Number

Should a SaaS product video include a number?

Observation
Only Thinfinity puts a figure on the result: a total cost of ownership “up to 60% lower.” Amazon, Microsoft and Vectary describe benefits without a figure.
Data
1 of 4 gave a number for the result.
The move
If finance will watch, give one number they can check. “Lower costs” is a hope. A percentage is a claim they can test.

How to plan

Where to use your SaaS product video

Put each part where its viewer looks. That one rule decides most placements.

  • Product and onboarding pages. The Cockpit version, for the people who'll use it daily.
  • Landing pages. The End Result version, above the fold, for buyers who pay for outcomes.
  • Integration pages and IT follow-ups. The Pipework version, sent after a security or architecture call.
  • Pricing pages and finance follow-ups. The Order Form version, sent when the deal reaches the budget owner.

How do you create a SaaS product video?

Eight decisions, in order. Each one narrows the next.

  • Viewer. The person who has to say yes after watching.
  • Part. The screen, the result, the connections or the cost.
  • Proof. One real screen, output, diagram or number that shows that part.
  • Script. Write the last line first. Then the first line. Then the middle.
  • Style. Real screens for the Cockpit. Animation for the Pipework. Clear charts for the End Result and the Order Form.
  • Storyboard. One frame per step. If a frame shows a second part, cut it, or the video drifts into a full software walkthrough.
  • Edit. Cut every second that doesn't serve the part you chose.
  • Call to action. Match it to the viewer: a trial for users, a call for IT, pricing for finance.

SaaS product video production process

Every product video runs through the same three stages. Knowing them keeps a project from drifting.

  • Pre-production. Set the viewer, the part and the proof. Then the script, the storyboard, the budget and the timeline.
  • Production. Record clean product screens, or design and animate the interface and diagrams. Record the voiceover.
  • Post-production. Edit, add motion and sound, get feedback in one round, then cut a version for each placement.

About the author

About Jai Ghosh

Jai Ghosh
Video Producer at Advids · LinkedIn

Jai Ghosh is a Video Producer at Advids, where he has planned and produced videos for B2B software and technology companies for 7 years. He works on product demos, explainer videos and brand videos, from the first script to the final cut, for clients from startups to enterprises.

Before Advids, Jai spent over 11 years in freelance media consulting, after starting out in digital journalism. He writes the Advids blog's breakdowns of product and demo videos, sorting real examples by the question each one answers for a buyer.

  • Focus: SaaS product demos, explainer videos and brand videos
  • Experience: 7 years at Advids, over 11 years in media consulting
  • Background: digital journalism

Connect with Jai Ghosh on LinkedIn