By Touchbase Technologies · Published 2026-11-04

Write a Product Demo Script for a First Sales Conversation

State the buyer problem; Show the starting situation; Complete one useful task; Ask for the next conversation.

A first product demo does not need to explain every feature. It needs to help a relevant prospect understand one useful thing the product does and decide whether that is worth discussing. A complete menu tour can make a simple product difficult to understand, especially when the viewer has not yet agreed that the problem matters.

Start with a buyer situation, choose a task you can show honestly, and end with a clear next step. This guide includes a script structure and a fictional example. The suggested timings are editing choices, not claims about the length that guarantees conversions.

Decide who the recording is for

Write one sentence describing the intended viewer and the situation they recognize. “A founder who needs an easier way to organize first-customer outreach” is more useful than “anyone interested in AI.” A specific viewer helps you choose what to show and what to leave out.

If the same product serves both individual creators and business teams, consider separate demonstrations. The creator may care about completing a personal project. A team may care about the handoff between colleagues. Showing both stories in the same short recording can weaken each one.

Base the situation on research or an actual conversation. If a prospect asked how a particular workflow works, answer that question. Do not invent a private business problem from a public website just to make the introduction sound personalized.

Pick a task with a visible beginning and end

Choose a workflow that exists in the current product. The beginning should make the problem understandable, and the end should show a result the viewer can interpret. For example, a task-planning product could start with an unassigned request and end with a clear owner and next action.

Avoid depending on a feature that is still only planned. If you need a prepared record to keep the recording short, say that it is sample data or that the setup was completed earlier. A staged demonstration can be useful without pretending to be an unedited customer session.

Write down the evidence you will show on screen. That might be an assigned task, a completed export, a reviewed draft or a link ready to share. A claim such as “this saves hours every week” is not an on-screen result unless you have separate evidence for it.

Use a simple five-part script

Treat the script as a guide to the recording rather than something to recite at an unnatural speed. Use the words your intended buyer uses. Explain an action while it happens, and leave enough space for the viewer to see the result.

Part	What the character says	What the screen should show
Situation	Name the task and the person doing it	The starting context
Problem	Explain the friction without exaggeration	The relevant work or input
Action	Describe the one workflow you are demonstrating	The actual product steps
Result	Say what is now available or clearer	The visible output
Next step	Ask one useful question or offer one action	The relevant destination

A rough first cut might spend less time on the opening than on the product action. Adjust that after watching the recording. If the viewer cannot follow the screen, cutting more words may help more than adding background music or faster transitions.

An example script for an outreach workflow

The following script is an editorial example for explaining Touchbase. Verify the exact screens and features available in your account before recording. It does not promise that a prospect will buy or that a campaign will produce a particular result.

“If you have built a product but are still working out who to contact, start with what you actually sell. In Touchbase, I add the website and review the product details, so the research starts with the right context.”

“Next, I open customer research and review the suggested audience. I can inspect potential matches and available contact information before deciding which people belong on my list. A result is a research lead, not a guarantee that someone is ready to buy.”

“For a relevant prospect, I can prepare a personalized email, review the draft and decide what to send. Replies and follow-up stay connected to the conversation. If my team uses an existing CRM, I can use the supported integration to keep the next step in that workflow.”

“The useful part is having product context, research and the next conversation connected. If that is the work you are doing now, you can start with a Free account and see which step helps you.”

Do not show this entire sequence if the recording is meant to answer a narrower question. A prospect asking about demo sharing should see that workflow, not an unrelated introduction to every outreach feature.

Prepare the screen before recording

Use a demonstration workspace or sample records you are allowed to show. Remove private customer information, unrelated browser tabs and credentials. Check that the screen is large enough to read in the format where the video will appear, especially if the final edit will be viewed on a phone.

Write a short shot list: the opening view, each product action, the output and the closing screen. That makes it easier to record a calm explanation instead of searching through menus while speaking. Keep the cursor movement purposeful and avoid narrating every click when the action is already obvious.

Record the actual product with Touchbase's screen-demo tools where available. Review processing and plan capacity in the current interface; do not assume that a feature or allowance shown in an older video still applies. The pricing page describes the available plans and capacity.

Edit for understanding rather than spectacle

Remove waiting time that does not help the explanation, but do not edit a missing capability into an apparent result. If the product takes time to process an action, a clear cut or caption can explain the transition. A viewer should not mistake prepared output for a live process that the product cannot perform.

Use callouts to direct attention to a relevant field, decision or result. Avoid covering the information the viewer needs to see. Captions should support the spoken explanation, not introduce a second sales pitch with different claims.

Watch the finished video without sound and then listen without looking. The first check reveals whether the screen and captions make sense. The second reveals whether the narration is coherent. Neither replaces watching the complete edit as a new prospect would.

Connect the demo to the right next step

A first demo can ask whether the workflow matches the prospect's needs, invite a specific question or link to an account signup. Choose one next step that fits the conversation. Do not end a simple introductory video with several unrelated demands.

When sharing through outreach, keep the email short and explain why the demo is relevant. If the prospect replies with a requirement or objection, preserve that context in the conversation and in your CRM handoff. The CRM checklist can help the receiving teammate continue the discussion accurately.

For an agency selling a service, a short demo may show a deliverable or process rather than software. Pair it with the agency qualification guide so the video supports an understood assignment. A polished recording is useful only when it helps the right person understand the offer.

Questions about demo videos

Should I show all the features in the first video?

Usually choose one useful workflow. Create additional recordings when a different audience or question needs a different explanation. A library of focused demos can be easier to use than one long tour.

Can a better script guarantee more signups?

No. A script can make the explanation clearer. Results also depend on product fit, the audience, the offer and the next experience. Use actual feedback and measured behavior to improve the recording.

Prepared with AI assistance and checked against the sources linked in this guide.