Are these real prompts people used?

Yes. Each prompt is a normalized (PII-removed) version of a real brief submitted to ngram. Product names, company names, and any identifying details have been stripped, but the structure, phrasing, and intent are from actual users.

What's the difference between a walkthrough video and a product demo?

A product demo shows one feature solving one problem, usually for a sales or marketing context. A walkthrough follows a user through a sequence of steps in the product — the full onboarding path, a multi-step workflow, or a feature-by-feature tour. Walkthroughs tend to run longer (60–90 seconds) than demos (15–30 seconds).

Do I need a script before I generate?

No — most prompts in this cluster don't include a script. If you attach a screen recording or URL, ngram writes the script from the product content. If you have a script already, you can paste it and ngram will use it as the voiceover copy.

Which format should I use for a walkthrough shared in Slack or email?

Add captions and background music, and skip the voiceover. Most walkthrough videos in internal channels are watched muted. Captions let the viewer follow the steps without audio.

Can I generate both a 30-second and a 2-minute version of the same walkthrough?

Yes. Generate the short version first, then ask ngram in chat to 'make a longer version that covers the full onboarding flow'. The agent expands the script and storyboard while keeping the same brand style.

How do I keep the video from showing fake product screens?

Add 'use the real UI from my recording — do not generate fake screens' to your prompt. This single instruction routes ngram to use your uploaded material as the source visuals rather than generating synthetic product UI.

What's the typical turnaround for a 60-second walkthrough?

Most 30–60 second walkthroughs render in under five minutes. Longer videos with multiple screen recordings may take a few minutes more.

Can I use a walkthrough video for sales demos and onboarding?

Yes. The same underlying prompt works for both — adjust the tone and CTA for the context. A sales version ends on 'book a demo'; an onboarding version ends on 'here's what to do next'.

Real SaaS Walkthrough video prompts

Seven prompts SaaS teams actually used to build walkthrough videos with ngram. Copy one, swap the product details, and generate.

ngram.com/app/editor

7 real promptssaaswalkthrough30srealisticmarketers

Trusted by teams at

Salesforce

HubSpot

PayPal

Snap Inc.

Rocket Mortgage

Tektronix

Diligent

Times Internet

Fivetran

Demandbase

Salesforce

HubSpot

PayPal

Snap Inc.

Rocket Mortgage

Tektronix

Diligent

Times Internet

Fivetran

Demandbase

Eightfold AI

PingCAP

Quizizz

Apryse

Sandbox VR

Improvado

Taggbox

Matrixport

Glasswall

ContractSafe

Eightfold AI

PingCAP

Quizizz

Apryse

Sandbox VR

Improvado

Taggbox

Matrixport

Glasswall

ContractSafe

The short version

What a SaaS walkthrough video is

A SaaS walkthrough video follows a user through one real workflow in the product — login to first action, feature A to feature B, or the full onboarding path. Teams build them from screen recordings, URLs, or ordered screenshots. Below are the actual prompts teams used in ngram, the patterns that make them work, and a step-by-step breakdown of the strongest one.

30–90s

Typical length

~93%

Attach a recording or URL

Realistic

Top visual style

Prompt gallery

Prompts to start from

Copy one, swap the bracketed parts for your product, and generate.

Location directory dashboard tour

Featured

Step-by-step walkthrough of a data-heavy dashboard UI — stat cards, toolbar navigation, and map view.

screen-recordingurl30s

prompt

Create a 30-second step-by-step walkthrough of a location directory dashboard. The dashboard has stat cards at the top, a filterable data table, and a toolbar for exporting. Walk through each area in order: stat cards first, then the table filters, then the export flow. Use my screen recording as the source. No fake UI. Clear voiceover. End on the logo.

Beta tester onboarding walkthrough

Longer onboarding walkthrough for a consumer SaaS app — screen recordings combined with a scripted voiceover.

screen-recording2min+narrated

prompt

Make a 3-minute beta tester onboarding video for a family scheduling app. Use my screen recordings for each section: (1) creating a family group, (2) adding events, (3) assigning tasks. Write a voiceover script that explains each screen as it plays. Warm, friendly tone. End with a thank-you and a prompt to submit feedback.

Open-source editor feature tour

Two-minute walkthrough built from a reference video, showcasing an open-source developer tool.

url2min+screencast

prompt

Create a 2-minute walkthrough of an open-source code editor. Use my uploaded reference video as the source material. Cover the three main panels: file tree, editor, and terminal. Show how a user opens a file, makes an edit, and runs a command. Developer-friendly tone, no fluff. Add captions.

First-run experience with AI voiceover

Replaces original audio with an AI voiceover to narrate the first-run experience of an AI admin tool.

screen-recording30sai-voiceover

prompt

Take my screen recording of the first-run experience for an AI IT admin tool. Remove the original audio. Add an AI voiceover that narrates each step: account setup, connecting the first integration, and running a test query. Confident, professional tone. 30 seconds.

PDF-narrated product walkthrough

Combines a narration PDF, ordered screenshots, and scripted audio into a 60-second product tour.

urlscreenshots60s

prompt

Build a 60-second product walkthrough video. I'm attaching a PDF with the narration script and 6 product screenshots in order. Use each screenshot as the visual for its corresponding narration section. Add background music. Keep the pacing steady — one screenshot roughly every 10 seconds.

Voice-first AI app speak-to-quote flow

Fast-paced walkthrough showing the core user flow in a vertical AI SaaS product for contractors.

url60sfast-paced

prompt

Make a 60-90 second fast-paced walkthrough of a voice-first job quoting app for contractors. Show the speak-to-quote flow: user taps the mic, describes the job, and the app generates a quote. Use my screen recording. Quick cuts, upbeat background music. No lengthy intro — start on the mic tap.

Mobile-first business app instructional

Instructional walkthrough of a mobile Android SaaS app using a realistic mockup style.

urlscreen-recording90srealistic

prompt

Create a 90-second instructional walkthrough of a record-keeping app for small shops and restaurants. Mobile-first, Android. Use my screen recording. Show the three daily tasks: adding a sale, checking inventory, and running the end-of-day report. Realistic mockup style. Clear English narration, no jargon.

Patterns across SaaS walkthrough prompts

What the data shows across real ngram walkthrough prompts from this cluster.

Most-requested length30s

Briefs that attach a URL or recording~93%

Top visual stylerealistic

Most common authormarketers

Prompts that include a script~36%

Anatomy

Anatomy of a standout

Location directory dashboard tour

prompt

Inputs

One screen recording. The prompt names the three UI areas explicitly so ngram knows what to cover and in what order.

Structure

Explicit scene order — stat cards, table filters, export flow — keeps the walkthrough linear and easy to follow. The viewer always knows where they are in the product.

Tone

'Clear voiceover' with no style adjectives. When the task is informational, plain narration works better than punchy or emotive language.

Guardrail

'No fake UI' is the one constraint that separates a credible walkthrough from a generic AI video. Without it, generated screens can drift from the real product.

Why it works

It names the three sections, sets their order, attaches the recording, and adds one guardrail. That's the whole brief. Every additional sentence would have been noise.

Playbook

What makes a good SaaS walkthrough video

Name the sections in order

Tell ngram which parts of the UI to cover and in what sequence. 'Show X, then Y, then Z' produces tighter cuts than 'cover the main features'.

Attach the recording or URL

93% of walkthrough prompts in this cluster include a real input. A URL or recording means the video follows the actual product — not an AI interpretation of it.

Set a guardrail against fake UI

Add 'use the real UI — no fake screens' to any walkthrough where the product UI is the point. One sentence eliminates the most common credibility problem.

Match length to the workflow depth

A single feature tour fits in 30 seconds. An onboarding sequence needs 2–3 minutes. Set the duration before you generate so the pacing is right.

Choose captions for no-audio contexts

Walkthroughs shared in Slack, email, or LinkedIn feeds are usually watched muted. Captions plus music keep the video useful without a voiceover.

End with the next step

A walkthrough that ends on the logo leaves nothing for the viewer to do. Close with a CTA — 'start your free trial', 'book a demo', or 'read the docs'.

How it works