Template · Product demo script
Product demo script template (with a worked example).
A demo script template that works for live, video, and interactive demos: outcome, audience, opening screen, six steps as screen → action → what they see, CTA, and what to measure — filled in with an example.
Use when: Before any demo is recorded, captured, or presented. The script is what keeps it to the screens that sell.
The one line
What this demo proves
The buyer sees that they can find the accounts that went quiet this week without building a report.
Stop by stop
6 stops
| # | Screen | Action (hotspot) | Tooltip |
|---|---|---|---|
| 01 | Accounts list, sorted by last activity | Click the 'Quiet this week' filter | Start where the problem is visible: forty accounts, no idea which ones are cooling. |
| 02 | Filtered list: six accounts | Click the first account | Six accounts have gone quiet. No report, no export — one filter. |
| 03 | Account timeline | Click the last email thread | The timeline shows the last touch was 19 days ago and who it was with. |
| 04 | Email thread with a 'Draft follow-up' button | Click Draft follow-up | Draft a follow-up from here — the context is already on screen. |
| 05 | Draft with the account's details filled in | Click Send | The draft knows the account, the contact, and the last topic. Edit or send. |
| 06 | Accounts list, the account marked 'Touched today' | Click 'See the weekly digest' | Back to the list: one down, five to go — and a digest every Monday so you never build this view by hand again. |
Copy
The lines that do the work
- Opening line (tooltip on stop 1)
- Start where the problem is visible: forty accounts, no idea which ones are cooling.
- Lead-form prompt (if gated at stop 4)
- Want the Monday digest for your own accounts? Leave an email and keep driving.
- CTA (last stop)
- Set this up for your pipeline — free, ten minutes.
Take it with you
The template as text
PRODUCT DEMO SCRIPT — TEMPLATE
Outcome: The buyer sees that they can find the accounts that went quiet this week without building a report.
Use when: Before any demo is recorded, captured, or presented. The script is what keeps it to the screens that sell.
01. Screen: Accounts list, sorted by last activity
Action: Click the 'Quiet this week' filter
Tooltip: Start where the problem is visible: forty accounts, no idea which ones are cooling.
02. Screen: Filtered list: six accounts
Action: Click the first account
Tooltip: Six accounts have gone quiet. No report, no export — one filter.
03. Screen: Account timeline
Action: Click the last email thread
Tooltip: The timeline shows the last touch was 19 days ago and who it was with.
04. Screen: Email thread with a 'Draft follow-up' button
Action: Click Draft follow-up
Tooltip: Draft a follow-up from here — the context is already on screen.
05. Screen: Draft with the account's details filled in
Action: Click Send
Tooltip: The draft knows the account, the contact, and the last topic. Edit or send.
06. Screen: Accounts list, the account marked 'Touched today'
Action: Click 'See the weekly digest'
Tooltip: Back to the list: one down, five to go — and a digest every Monday so you never build this view by hand again.
Opening line (tooltip on stop 1): Start where the problem is visible: forty accounts, no idea which ones are cooling.
Lead-form prompt (if gated at stop 4): Want the Monday digest for your own accounts? Leave an email and keep driving.
CTA (last stop): Set this up for your pipeline — free, ten minutes.
Measure: Completion rate over the first two weeks; Where people park — the stop with the biggest drop; CTA click rate; If gated: leads, and the score from the driveCreates a lane with one stop per row above — the screen as the title, the action and tooltip as the body — then opens the editor so you can capture the real screens.
The format
What the finished lane feels like
Measure
What to watch after publishing
- Completion rate over the first two weeks
- Where people park — the stop with the biggest drop
- CTA click rate
- If gated: leads, and the score from the drive
FAQ
Questions
How long should the script be?
Six to ten steps for a website or outbound demo; three to six for a feature launch; the first workflow for onboarding. If the script runs to fifteen, it is two demos.
Does the same script work for a live demo?
Yes — it is the path you follow between the buyer's questions. Skip the steps they do not need.
Related
More templates
Comparing tools?