Product Demo Script Template with Three Examples ================================================ Original fictional products, controls, and behaviors. Copy and adapt for your own verified product. These samples do not describe tested real features or claim customer outcomes. Keep spoken copy separate from visual and editor directions. Prospect demo: complete a software handoff ------------------------------------------ You have a lesson ready for review, but the next person needs the script, the audio, and a clear note about what changed. In this Mossline Tasks demo, we'll put that handoff in one review card. Open the Review board and choose New card. Name the card Lesson three, pronunciation update. Attach the script and the audio file shown in this sample workspace. In the note, write: the speaker name has been corrected in the second paragraph. Choose Assign and select the reviewer. Now open the card preview. The reviewer can see the two sample files and the change note together. This demonstration covers preparing the card. It does not show the reviewer approving the lesson or prove that every upload format is supported. If this is the handoff you need, open the example workspace and make a card with your own non-private sample files. Editing note: The job is a complete handoff, not a tour of every menu. Show the two files, the note, the assigned reviewer, and the final card in the same capture. The limit sentence prevents the audience from mistaking a prepared card for a completed review. A real demo needs the labels and behavior of the actual build; the fictional controls are a writing example. Physical product demo: open, adjust, and pack a stand ----------------------------------------------------- This is the Foldwell travel stand in this product demonstration. We'll show how this sample opens, how the screen position changes, and how it packs away. Place the stand on the table. Hold the base, lift the support, and seat it in the marked position. Here is the support from the side so you can see where it rests. Set the sample laptop on the stand. The next shot shows the screen position before and after the adjustment. We are demonstrating this sample combination, not claiming compatibility with every laptop. Remove the laptop before changing the stand position. Fold the support back into the base. The final shot shows the closed stand beside the same bag used at the beginning. Before choosing a stand for your own setup, check the actual product dimensions, device compatibility, and instructions. Editing note: The physical example needs a sequence the camera can prove: open, seat, show, remove, fold. Do not hide a difficult assembly step behind a cut. The narration deliberately avoids an invented weight rating or ergonomic benefit. For a real product, follow its manufacturer instructions and state only supported compatibility. The viewer should see the mechanism clearly rather than hear a generic claim about portability. Existing-user feature demo: see what changed -------------------------------------------- If you've used Mossline Tasks to send a review card before, this update changes where you check who can open the link. The card content stays in the same place. Open the card and choose Share. The Share settings panel now shows the selected audience above the link. In this sample workspace, it is set to Invited reviewers. Choose Preview access. The preview names the people selected for this card. Read that list before copying the link. Then return to Share and choose Copy link. The preview shown here covers this sample card. It is not an audit of every card in the workspace, and it does not establish your organization's sharing policy. For your next handoff, check the audience for the actual card you are sending. If you do not recognize a reviewer, resolve that choice before sending the link. Editing note: The purpose is adoption by existing users, so it starts with what changed rather than explaining the product from scratch. Screen labels carry the sequence, and the narration states the scope of the preview. In a real access-control demo, verify the behavior with the actual account types before making a claim. Do not turn a small UI preview into a promise of security or compliance. Blank narration --------------- [Audience task and starting situation.] [Demo scope.] [Action one, using an exact label or movement.] [Action two.] [Observable result.] [Relevant scope boundary or condition.] [One suitable next step.] Two-column planning worksheet ----------------------------- For each beat, fill in: Narration: [ ] Visual or action: [ ] Fact or behavior to verify: [ ] Product/build version: [ ] Review owner: [ ] Beats: audience task; scope; action one; action two; visible result; boundary; next step. Review checklist ---------------- Confirm actual product behavior and labels. Use clean sample data. Show the result the voice describes. Keep claims limited to verified scope. Check narration, captions, descriptive text, and the final export together. Record actual duration after production. SCRIPT LENGTH ESTIMATES ======================= Whitespace-separated spoken words, excluding leading speaker labels. Assumed 150 words per minute. Not measured. Pauses, music, effects, turn changes, and visual action time excluded. Prospect demo: complete a software handoff: 145 spoken words; 58.0 estimated seconds. Physical product demo: open, adjust, and pack a stand: 137 spoken words; 54.8 estimated seconds. Existing-user feature demo: see what changed: 141 spoken words; 56.4 estimated seconds.