---
title: "Write a Product Demo Script From a Help Article | FoxCue"
description: "Rebuild one help article as a 60 to 90 second demo script: open on the problem, keep two or three actions, split voiceover from screen, cut the rest."
url: "https://foxcue.com/software-to-video/help-article-demo-script/"
type: "Guide"
published: "2026-11-11"
updated: "2026-11-11"
author: "Jeel Patel"
---

# How do you write a product demo script from a help article for YouTube?

By Jeel Patel, Founder, FoxCue · Published 2026-11-11 · Updated 2026-11-11

Don't read the help article aloud. Pick one article, find its result, and rebuild it as a story: the viewer's problem, what they'll get, two or three actions, the finished result, one next step. Write the voiceover and the on-screen action in separate columns, aim for 60 to 90 seconds, and leave everything else in the article.

## Why can't you read a help article aloud as a demo?

A help article is built to be complete. A demo is built to get one viewer to one result. MakeMyDemo puts it bluntly: a demo without a script becomes a feature tour.[^2] Typecast says the same about short demos: cover one primary use case, because showing every screen and setting leaves viewers with information but no takeaway.[^3]

| The help article | The demo script |
| --- | --- |
| Lists every setting and edge case | Shows only the path to the result |
| Covers a whole feature | Follows one task |
| Starts with login, setup and navigation | Starts on the viewer's problem |
| Names buttons and fields | Says why each action matters |
| Is written to be scanned | Is written to be spoken |
| Saves the result for the last line | Promises the result early, then shows it |

The article stays the reference. The demo's job is to make someone want the result and see that it's reachable.

## Is this a demo script, a how-to script or a talk track?

Decide before you write, because the same help article can feed three different scripts.

| Script | Viewer | What it does |
| --- | --- | --- |
| Demo script (this page) | Hasn't reached the result yet | Opens on the problem, shows the shortest path, ends on the result and one next step |
| How-to answer script | Searched the task and needs every step | Opens on the answer, then prerequisites, numbered steps, the common failure, one next step |
| Sales talk track | A rep before a call | Turns the doc into a line the rep can say, plus the likely objection |

If the viewer already searched for the steps, use the [five-part answer video script](https://foxcue.com/youtube-ai-overviews/answer-video-script-template/). If the script is for reps, see [product docs into sales enablement videos](https://foxcue.com/docs-to-video/product-sales-enablement/). The rest of this page is the demo.

## How long should a demo script from a help article be?

Draft for 60 to 90 seconds. MakeMyDemo says a 60 to 90 second demo starts at about 130 to 190 spoken words, and the pauses for the interface fill the rest.[^1] Its timings are a budget, not a law: if the workflow needs 55 seconds, give it 55 and trim the setup.[^1]

| Beat | MakeMyDemo (90 s) | Typecast (60 s) | Where it comes from in the help article |
| --- | --- | --- | --- |
| Problem | 0-10 s | 0-5 s | The symptom, or the question the article answers |
| Promise | 10-20 s | 5-15 s | The article's title or stated purpose |
| Proof | 20-70 s | 15-40 s | The two or three steps that change the outcome |
| Result | Inside the proof | 40-52 s | The last lines, or the 'you should now see' passage |
| Next step | 70-90 s | 52-60 s | The related article or the next task |

The beat names and the help-article column are our working template. The timings are MakeMyDemo's four beats[^1] and Typecast's 60-second template,[^3] side by side. Neither is a YouTube rule.

## How do you turn the help article into a script?

Work backward from the result, because the result decides what stays.

1. Pick one article people already ask about. In your Search Console Performance report, the queries tab groups clicks and impressions by what people typed.[^4] Start where a query matches the article's task closely.
2. **Find the result.** Mark the line where the reader can see it worked. That's your result beat.
3. Write the problem in one sentence, in the viewer's words, not your product's. That's your opening line.
4. **Keep two or three actions.** Typecast's template shows two or three actions that move the viewer toward the outcome.[^3] Login, setup, navigation and anything that doesn't change the result come out.
5. **Rewrite each kept step as speech.** Say why the action matters and put the click in the on-screen column. MakeMyDemo says narration should explain why the action matters, not read the interface back to the viewer.[^1]
6. **Read it aloud and time it.** If it runs long, cut a step. Don't talk faster.
7. **Check each line against the article.** MakeMyDemo's checklist asks that every product claim is visible on the source page or verified by the product owner.[^1] Note the passage behind each line, and rewrite or remove any line that has none.

## What does a two-column demo script look like?

Put what is said beside what is shown. The split stops the voiceover from describing the screen, and Typecast's checklist asks that every narrated step matches something visible.[^3] The example below is illustrative: a fictional analytics app and its help article, "Schedule a weekly report email".

| Time | Voiceover | On-screen action |
| --- | --- | --- |
| 0-10 s | Still exporting the same report every Monday and pasting it into an email? Set it once instead. | An inbox of manual report emails |
| 10-20 s | By the end of this, the report lands in your team's inbox on its own. | The finished scheduled email, preview only |
| 20-45 s | Open the report and choose Schedule. This is the setting that ends the Monday export. | Open the report, zoom in on Schedule |
| 45-70 s | Pick weekly, add the team's list and save, so everyone gets the same numbers. | Select Weekly, add recipients, click Save |
| 70-80 s | That's it. Next Monday's report is already queued. | Schedule list showing the next send |
| 80-90 s | Schedule one report today. The other options are in the article linked below. | Help article link on screen |

A script line beside the passages it came from, and the grounding check that flags a claim they don't support.

## What do you cut from the help article?

Most of it, and the video loses nothing. MakeMyDemo's own worked example leaves out templates, permissions, every publishing destination and a tour of the settings screen, because they don't help a short demo prove its one claim.[^1] The rows below use the same fictional article.

| Help article passage (illustrative) | In the script? | Why |
| --- | --- | --- |
| "You need the Editor role to schedule reports." | No | A prerequisite. It stays in the article and the link. |
| "Go to Reports, then open the report you want." | On screen only | Navigation. The viewer sees it, nobody needs to hear it. |
| "Choose Schedule, then pick daily, weekly or monthly." | Yes, as one choice | The demo shows weekly. The other intervals stay in the article. |
| "Scheduled emails send at 9:00 in the report's time zone." | No | A detail. True, but it doesn't change the result on screen. |
| "Your schedule appears under Scheduled." | Yes, as the result | This is the finished state, so it becomes the result beat. |
| "If emails don't arrive, check your spam filter." | No | Troubleshooting. It belongs to a how-to or a fix video. |

## How do you package the demo for YouTube?

- **Captions:** make the demo work with the sound off. MakeMyDemo notes many viewers begin with sound off, so the visuals and captions should make sense on their own.[^2]
- **Transcript:** your voiceover column is already the transcript. Save it as a plain text file and leave a blank line where a new caption should start.[^6] YouTube synchronizes transcript text to the video automatically, as long as it is in the language spoken.[^5] More on this in [accessible captions](https://foxcue.com/docs-to-video/accessible-captions/).
- **Chapters:** only if each beat is long enough. YouTube needs the first timestamp at 00:00, at least three timestamps in ascending order, and chapters of 10 seconds or more.[^7] A 5-second opening can't be its own chapter, so fold it into the next one. The [description and chapters template](https://foxcue.com/youtube-ai-overviews/description-chapters-template/) has the format.
- **Description:** link the full help article in the first lines, since that's where the cut steps live.

## Where does FoxCue fit?

FoxCue is the video OS for SaaS, the AI video OS for B2B and product teams, built to show up in AI answers. It writes the script from your docs and shows the passages the script used, and a grounding check flags a claim those passages do not support. You record on the teleprompter with your screen in its studio recorder, or make a narrated slide video. Your team still reviews each script and uploads each video.

Making the demo itself, from the help article behind a feature, is in [product demo videos from your docs](https://foxcue.com/docs-to-video/product-demos/). Recording the script on screen and camera is in [record a software walkthrough](https://foxcue.com/software-to-video/record-screen-camera/), and choosing between a walkthrough, a demo and a tour is in [walkthrough vs demo vs tour](https://foxcue.com/software-to-video/walkthrough-demo-tour/). The hub is [software to video](https://foxcue.com/software-to-video/).

## Questions

### How long should a product demo script be?

For a 60 to 90 second demo, start at about 130 to 190 spoken words, then read it aloud and time it. Screen pauses take time, so a script that looks short on the page can still fill the video.

### Should the voiceover read the button names?

No. Show the click on screen and use the voiceover for why it matters. Say a label out loud only when the viewer can't find it without hearing it.

### What's the difference between a demo script and a how-to script?

A how-to script is for someone who searched the task and needs every step, so it opens on the answer. A demo script is for someone who doesn't have the result yet, so it opens on the problem and shows only the shortest path.

### Can one help article become more than one video?

Yes. The demo shows the shortest path to the result. The steps you cut can become a how-to video, and a common failure can become a short fix video. Keep each video to one job.

## Sources

[^1]: [MakeMyDemo, Product demo video script: Template and examples](https://makemydemo.com/guides/product-demo-video-script), updated Nov 2026, checked 11 Nov 2026
[^2]: [MakeMyDemo, How to create a product demo video](https://makemydemo.com/guides/how-to-create-product-demo-video), checked 11 Nov 2026
[^3]: [Typecast, Product Demo Script: 60-Second Template and Example](https://typecast.ai/learn/product-demo-script/), 16 Oct 2026, checked 11 Nov 2026
[^4]: [Search Console Help, Performance report (Search results)](https://support.google.com/webmasters/answer/7576553), checked 11 Nov 2026
[^5]: [YouTube Help, Add subtitles & captions](https://support.google.com/youtube/answer/2734796), checked 11 Nov 2026
[^6]: [YouTube Help, Tips for creating a transcript file](https://support.google.com/youtube/answer/2734799), checked 11 Nov 2026
[^7]: [YouTube Help, Video Chapters](https://support.google.com/youtube/answer/9884579), checked 11 Nov 2026

---

Write the demo script from the article you already have: https://foxcue.com/waitlist/. More in Software to Video: https://foxcue.com/software-to-video/