PHOENIX STORY WORKS — PRODUCT DEMO SCRIPT KIT ====================================== Before you begin, write down: - Product: [NAME] - Audience: [WHO IT HELPS] - Problem: [THEIR MAIN FRUSTRATION] - Key benefit: [MOST IMPORTANT OUTCOME] - Three features: [FEATURE 1], [FEATURE 2], [FEATURE 3] - Next step: [TRIAL / BUY / BOOK / LEARN MORE] PROMPT ------ Act as a product video strategist. Create a clear [LENGTH]-second demo video for [PRODUCT] aimed at [AUDIENCE]. Build the script around this flow: 1. Show a recognisable problem in the first 5 seconds. 2. Introduce the product as the simplest next step. 3. Demonstrate the three features through actions, not claims. 4. Translate each feature into a real customer benefit. 5. Address this likely concern: [OBJECTION]. 6. End with one direct call to action: [NEXT STEP]. For every scene, include timing, what appears on screen, presenter or voiceover words, on-screen text, and any screen recording needed. Keep the writing specific and believable. Do not use “revolutionary,” “game-changing,” “seamless,” or unsupported superlatives. If a claim needs proof, mark it [PROOF NEEDED]. Also give me: - A 15-second cut-down. - Three alternative opening hooks. - A list of screenshots or product footage to record. DEMO DISCOVERY WORKSHEET ------------------------ Product name: ___________________________________________ What category is it in? _________________________________ Who is the exact viewer? _________________________________ What situation are they in when the problem appears? _____ What do they currently use or do instead? ________________ What does that alternative cost in time, money, or effort? _ What first success can the viewer achieve with the product? _ Which feature creates that success? _______________________ What evidence supports the benefit? _______________________ What concern could stop the viewer taking the next step? __ What single action should they take after watching? _______ FEATURE-TO-BENEFIT TRANSLATOR ----------------------------- Do not stop at what the product has. Show what changes for the customer. FEATURE: What the product contains or does. ACTION: What the viewer actually clicks, enters, holds, or completes. IMMEDIATE RESULT: What visibly changes on screen. CUSTOMER BENEFIT: Why that result matters in the viewer's real situation. PROOF: What demonstrates the benefit without exaggeration. Example: Feature: Automatic transcript search. Action: The user searches a phrase from a one-hour interview. Immediate result: The exact spoken moment appears in two seconds. Benefit: The editor finds useful quotes without replaying the full recording. Proof: A continuous screen capture and an honest timing note. DEMO STRUCTURES BY LENGTH ------------------------- 15 seconds — One problem, one action, one visible result, one next step. 30 seconds — Hook; problem; two-step demonstration; proof; call to action. 60 seconds — Hook; customer context; three connected actions; result; likely objection; call to action. 90 seconds — Short story; problem; product orientation; complete core workflow; proof; secondary benefit; objection; summary; call to action. 2-3 minutes — Audience and outcome; real scenario; setup; guided workflow; mistakes or alternatives; evidence; limitations; next step. Use chapters and allow the viewer to see important actions at a readable pace. MASTER DEMO PROMPT ------------------ Act as a product demonstration director and plain-language script editor. Create a [LENGTH] video for [PRODUCT] aimed at [SPECIFIC AUDIENCE] who currently struggle with [PROBLEM]. The demonstration must show how the viewer goes from [BEFORE STATE] to [FIRST USEFUL RESULT]. Use only these verified facts: [PASTE VERIFIED PRODUCT FACTS] Use this structure: 1. Open on the problem in a recognisable real-world moment. 2. State the outcome the viewer will see, without hype. 3. Demonstrate [CORE ACTION 1], [CORE ACTION 2], and [CORE ACTION 3]. 4. After every action, explain the practical benefit in one short sentence. 5. Show [PROOF OR RESULT] clearly on screen. 6. Address [OBJECTION] honestly, including any real limitation. 7. End with one call to action: [NEXT STEP]. Present a table with TIMING, VISUAL / SCREEN ACTION, PRESENTER OR VOICEOVER, ON-SCREEN TEXT, PROOF NEEDED, and PRODUCTION NOTES. Mark any statement not directly supported by the supplied facts as [VERIFY]. Avoid generic adjectives, invented statistics, fake testimonials, and claims about competitors. SCREEN-RECORDING PLAN --------------------- Before recording: [ ] Create clean sample data that reveals no private customer information. [ ] Close messages, personal tabs, password managers, and notifications. [ ] Increase interface text or zoom so actions remain readable on a phone. [ ] Plan the exact cursor path and remove unnecessary clicking. [ ] Use a test account with the correct permissions and finished setup. [ ] Record at the final aspect ratio or leave space for cropping. During recording: [ ] Pause briefly before and after each important click. [ ] Keep cursor movement deliberate and slow enough to follow. [ ] Record long processes separately so they can be shortened honestly. [ ] Capture clean versions without voiceover for flexible editing. [ ] Re-record mistakes rather than hiding confusing actions with fast cuts. After recording: [ ] Blur or replace any sensitive information. [ ] Confirm that labels and navigation still match the current product. [ ] Add subtle highlights only where the viewer genuinely needs guidance. [ ] Do not speed up a process without making the time change clear. CLAIMS, PROOF, AND TRUST ------------------------ Safer evidence includes: - A continuous real demonstration. - A clearly explained comparison using the same conditions. - A sourced and dated result with relevant context. - A real customer quote used with permission. - A limitation stated alongside the benefit. Review carefully before claiming "fastest," "best," "guaranteed," "secure," "private," "free," specific savings, health outcomes, financial outcomes, or compatibility with third-party tools. Laws and platform requirements vary; seek appropriate professional review for regulated or high-risk claims. WORKED EXAMPLE: SIMPLE PLANNING APP ----------------------------------- Audience: A solo video creator who loses ideas across notes and messages. Goal: Show how to capture an idea and turn it into a three-scene plan. 0-4 sec Visual: Creator searches several open notes for one lost idea. Voiceover: "A good video idea is not useful when you cannot find it." 4-10 sec Visual: Open the product and add the idea in one clearly shown field. Voiceover: "Save the idea once, while it is still fresh." 10-23 sec Visual: Select a short-video template; the three empty scene cards appear. Voiceover: "Choose the format, then shape the opening, middle, and ending." 23-36 sec Visual: Drag a reference image into Scene 1 and add one line of voiceover. Voiceover: "Keep each visual beside the words it needs to support." 36-46 sec Visual: Show the completed three-scene overview without cutting away. Voiceover: "Now the idea is a plan you can film—not another note to rediscover." 46-55 sec Visual: Export button and resulting PDF. Voiceover: "Export the shot list when you are ready to record." 55-60 sec Visual: Product name and honest trial details. Voiceover: "Try the starter plan and build your first three scenes." VERSIONING PROMPTS ------------------ - "Create a silent autoplay version where on-screen text carries the meaning." - "Create a presenter-led version that keeps all product actions visible." - "Cut this to 15 seconds while preserving the problem, action, result, and CTA." - "Expand this into a two-minute tutorial for viewers already evaluating tools." - "Write three hooks: problem-led, outcome-led, and demonstration-led." - "Create a vertical version and flag any screen detail too small for mobile." - "List every claim, the required evidence, and where it appears in the script." FINAL DEMO SCORECARD -------------------- Score each item from 1 (weak) to 5 (excellent): Audience specificity: ___ Problem clarity: ___ Visible product action: ___ Feature-to-benefit connection: ___ Readability of screen details: ___ Quality of proof: ___ Honesty about limitations: ___ Pacing and duration: ___ Single clear call to action: ___ Accessibility and captions: ___ Revise every item below 4 before publishing. Phoenix Story Works — Better prompts. Better videos.