# Product Demo Video Script Builder

Create a product demo video around a realistic user task, visible proof, and precise screen direction instead of a feature-by-feature tour.

## Prompt

You are a product video director who specializes in task-centered software demonstrations and clear on-screen proof.

Inputs:
1. Product, target viewer, and buying or adoption stage: {{product_context}}
2. User problem and demonstration scenario: {{scenario}}
3. Features, workflow, sample data, and proof points: {{demo_material}}
4. Length, channel, presenter style, and call to action: {{format}}
5. Product limitations, claim rules, and production constraints: {{constraints}}

Do the following:
1. Define the single viewer question the demo must answer and select one realistic user workflow that proves the answer from starting state to outcome.
2. Map each spoken claim to visible product evidence, sample data, or an approved proof point, excluding features that do not advance the scenario.
3. Write a time-coded script with narration, exact screen action, cursor or focus behavior, zoom or callout guidance, transitions, and breathing room for viewers to follow.
4. Include loading, prerequisite, privacy-safe sample-data, and failure-recovery notes, and label simulated integrations, edited timing, or unavailable functionality transparently.
5. Produce the final script, capture checklist, sample-data plan, shot sequence, on-screen text, accessibility notes, backup shots, and a version trimmed by 30%. Avoid vague phrases such as seamless or powerful unless the screen demonstrates them.

## Best for

Product marketing, sales, and onboarding teams creating software demos that must prove a user outcome clearly and accurately.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Choose one complete user task.
- Provide approved claims and realistic sample data.
- State which integrations or timings are simulated.
- Record the workflow before finalizing narration timing.

## Customization tips

- Show the product proving each claim.
- Keep cursor movement deliberate and slow.
- Use synthetic data that still looks operationally credible.
- Prepare static backup shots for unstable steps.

## Example input

Product: Purchase-order approval app for mid-sized manufacturers. Viewer: finance managers evaluating the product. Scenario: review a EUR 24,800 equipment request that exceeds budget and needs a second approver. Proof: policy warning, budget context, approval routing, audit trail, and mobile approval. Length: 2 minutes for a landing page, calm voice-over, CTA to book a workflow review. Constraints: use synthetic supplier data, mobile segment is prerecorded, and do not claim ERP sync is real-time.

## Example output

The script follows one purchase request from warning detection through budget inspection, second-approver routing, mobile approval, and audit confirmation. Every narration line has a corresponding screen action and approved claim. ERP data is described as periodically synchronized rather than real-time, and the mobile capture is labeled consistently with the desktop sequence. The output includes a 120-second script, privacy-safe fixture data, cursor choreography, fallback stills, captions, and an 84-second cut.