What Makes a Good Marketing Video for Software? Nine Things We Check Before a Walkthrough Is Published

Ask what makes a good marketing video and most answers describe production: pacing, music, colour, a strong hook in the first three seconds. Those matter for an advert competing for attention in a feed. For a software walkthrough, watched by someone who went looking for it, they are close to irrelevant.

What matters is whether the video is true, complete and still true next quarter. These are the nine checks we run before publishing, each with the specific failure it prevents.

1. The version is stated

On screen and on the page. Without it, nobody can tell whether the footage is current, including you. A video with no version is a video nobody can ever confidently retire, so libraries fill up with recordings that might be wrong and nobody dares delete.

2. Prerequisites appear before anything is clicked

Account type, permissions, dependencies that must already exist, free space or quota. Thirty seconds up front.

This prevents the most common failure of published walkthroughs: a viewer follows along, hits a wall the video never mentioned, and concludes the product is broken rather than that their account lacked a role.

3. The environment is clean and disposable

Not a demo tenant groomed for two years, and never production. A viewer needs to believe the starting state resembles theirs, and you need take two to start where take one did.

4. One task, with a nameable finish

If you cannot say the moment the job was done, there is nothing to verify and nothing satisfying to watch. "Show the reporting module" fails this. "Export last quarter's revenue by region as a CSV" passes.

5. The result is checked against the product's own evidence

Not the narrator saying it worked. Something the product produced independently of the screen being clicked: the file in the bucket with a matching checksum, the alert in an inbox, the machine that boots, the record in an API response.

Four seconds of evidence is the difference between showing a button being clicked and showing a job being done.

6. Failed attempts are kept, with the fix

Whatever went wrong before it went right, listed with what resolved it. This is the section your users search for, and cutting it is how a walkthrough becomes a demo.

It is also the check most often skipped internally, because the person recording wrote the confusing step and does not experience it as confusing.

7. Captions are corrected by hand

Auto-generated captions mangle every product noun that matters, and captions are the only part of a video a search engine or a language model can read. If you kept a run log while recording, correcting them takes five minutes because the vocabulary is already written down.

8. A written guide sits beside the video

Some people read rather than watch, and the written version is what gets found in search and cited in answers. A video with no text beside it is invisible to half your audience and to every machine.

9. A refresh trigger is set

The video is bound to the version it ran against, so when a release touches that task, it re-runs. Without this the library decays silently and you find out from a ticket that starts "your video says".

What is deliberately not on the list

• Music. A walkthrough is watched for information; a soundtrack under a terminal is noise.
• A presenter on camera. Nobody needed to see a face to learn whether the restore worked.
• A three-second hook. The viewer arrived from a search or a support reply. They are already committed.
• Length limits. It takes as long as the task takes. Cutting the pause where the product was thinking misleads someone planning a migration.

How to use this

Run it as a publish gate, not a review meeting. Nine yes-or-no checks take two minutes and catch the things that make a video quietly useless a quarter later.

Checks one, five, six and nine are the ones almost everyone fails, and they are also the four that separate a walkthrough from a demo. The recording process that produces them is in how to make a marketing video for a software product, and a worked example with its failures intact is the Proxmox VE 9.2 install walkthrough.