Write a SaaS demo script the screen can prove.

A short SaaS demo script should help someone follow a task, not list everything your product does. Start with a question such as “Where do I find the decisions from a client call?” Then show the answer. If a sentence has no visible action or supported fact behind it, rewrite it before you record.

This worksheet is for a short social demonstration. It is not a sales-call script or a customer testimonial. The example and timings below are original editorial illustrations, not measured engagement results or UGC Pilot generation settings.

Copy the script worksheet

Paste this into your notes. Fill in the product action first, then write the opening. This prevents a dramatic hook from promising a result the demonstration cannot show.

Viewer and situation:
Question this video answers:
One supported product action:
Starting screen / safe sample data:
Opening words:
Action words -> exact screen action:
Result words -> visible result:
Next step -> actual destination:
Claim or sensitive detail to check:
Rehearsal length / revision needed:

Use the screen labels that actually appear in your app. “Choose Call notes” is easier to follow than “unlock your team’s knowledge.” Leave pricing, account creation and unrelated features out of the sequence unless they are necessary to answer this viewer’s question.

A 30-second example: find a client-call decision

Imagine a fictional project-notes app that stores call notes under each project. These are assumed capabilities for this example, not claims about UGC Pilot or a customer. Replace both the words and screen actions with your verified workflow.

Read it aloud while performing the clicks. If a screen loads slowly, record the wait honestly and decide whether an indicated edit is appropriate. Do not speed up a process and present the edited duration as proof of how fast the product works. If the words or actions do not fit, shorten the message or allow more time.

Make a shorter cut by removing a beat

For an illustrative 15-second version, keep the same task and show less context. Try: “Need the decisions from your last call? Open the project, choose Call notes, and select the call. The next steps are here. Try a sample project.”

Remove the extra discussion of preparing a follow-up. Keep the project selection, the note selection and the result. Rehearse the actual recording; if the viewer cannot read the controls at that pace, the shorter version is not ready. A duration target is an editing choice, not evidence that it is the best length.

Check every line against the product

Can the viewer see the claimed outcome?

“Here are the decisions” can be supported by the displayed note. “Never lose a decision again” cannot be demonstrated by one clip. “This saves ten hours a week” needs separate credible measurement. Replace unsupported promises with the observable action.

Does the next step match the audience?

A person who has never used the app may need an explanation or sample workspace. An existing user may need to open a specific feature. Pick one destination and verify it works for that audience. Do not promise a free account, trial or credit amount without checking your current offer.

Does it work without the narrator?

Watch the recording muted. Add concise labels where an essential action would otherwise be unclear. When speech is present, review captions against the actual audio. The readable video text guide covers contrast, placement and reading time.

Use AI for an opening, not for product evidence

If you want a creator-style introduction, choose words that lead directly into the task. The Reaction Hook Library offers starting lines to adapt. A direct question is often enough; a surprised face is optional.

Generated performance is not a genuine customer endorsement. Use your real screen recording to demonstrate the software, and add exact words in an editor. UGC Pilot’s video workflow can help with creative footage; check the current supported features before requesting generation or an export. The finished demo still needs your review.

Before recording

• Write the single question the video answers.
• Confirm each named feature and control exists.
• Prepare safe sample data and the result you will show.
• Pair every script line with an observable screen state.
• Rehearse words and actions together, allowing time to read.
• Check that the closing link or action is available to the intended viewer.

Next, record readable source footage. Once that is ready, follow the product-demo editing guide to assemble the opening, demonstration and review.