The template
Present a proposed solution as a focused visual walkthrough tailored to a prospect's needs.
Use this scene sequence as an editable outline. Replace sample wording with verified details; the sequence is a planning aid, not a fixed duration or a platform specification.
| Beat | On screen | Narration | Review check |
|---|---|---|---|
| 1. Prospect context | Show a generic view of the agreed workflow. | Restate the prospect's requirement. | Has the account owner approved it? |
| 2. Proposed path | Start where the prospect would begin. | Connect the workflow to one requirement. | Is this within proposed scope? |
| 3. Product steps | Show the proposed product actions. | Describe what is configurable or standard. | Are integrations and roles accurate? |
| 4. Expected outcome | Reveal an illustrative end state. | Label sample data and assumptions. | Could this be mistaken for a guarantee? |
| 5. Agreed next step | Close on the project or contact path. | State the next step from the proposal. | Does it match the written proposal? |
How to fill it in
- Hook: state the viewer's problem or the outcome they want.
- Context: show only the setup the viewer needs to understand the workflow.
- Main action: focus on one or two meaningful product steps.
- Outcome: show what changed, using only claims you can support.
- Next step: give viewers one specific action to take.
Customize it for your audience
Start with the prospect's own words for the workflow and requirements, then agree on what the video is meant to clarify. Use a clean workspace and synthetic data that resembles the agreed use case without copying confidential records. Separate existing capability from configuration, services or future work, and label any illustrative screen. Tailor the route to the prospect's role: an administrator may need setup and permissions, while an end user may need the task outcome. Have the account owner compare the finished video with the written proposal, scope, pricing and next step before sending it.
Prepare the final handoff
Send the video with a note describing which requirements it addresses and which screens use illustrative data. Keep the approved scope and written proposal as the authoritative commitment, and store a recipient-specific copy securely if it includes account context. Remove or replace that copy when access should end.
Production and approval checklist
Before recording or animation, confirm the viewer, destination, desired next action and product version. Replace every illustrative name, number and screen with approved material, or label it as sample content. Check that each scene advances the story and that voiceover fits the time available on screen. Review the draft once for product accuracy, once for audience comprehension and once for permissions, accessibility and destination requirements. Make the final reviewer and approval date explicit; recheck volatile facts such as pricing, availability, release status, event details and platform rules just before publishing. Keep the script, source assets and approved export together so an update can be made without guessing which version is current.
Who it serves
A prospect should recognize the workflow they described and see how the proposed approach could fit. Build the story around the agreed use case, not a generic product overview.
Evidence and review
Confirm requirements, integrations, price and next steps with the proposal owner. Use a clean demo workspace and synthetic records; distinguish an illustration from a committed implementation.
Do not show other customers' information or imply that a feature, date or commitment is part of the proposal unless it is approved in writing.
A worked example
Illustrative scenario, not a customer story: Open with the prospect's stated workflow, show the proposed product path using sample data, then list the agreed next step. Do not imply a commitment or capability the proposal does not include.
Make it automatically
DemoVexa can use your product code and project context to draft a brief, script, and scene plan. Review every screen, claim, permission, and recording before publishing.
Frequently asked questions
How is a proposal video different from a product demo?
A proposal video is tailored to one prospect's stated needs and proposed scope. A general demo explains a product to a broader audience. Keep the tailored version aligned with the written proposal.
Can I personalize it with a prospect's name?
Only when you have permission and the name is appropriate for the recipient-only asset. Remove confidential records and label sample workflow details that are illustrative rather than agreed scope.
Can I use this template for free?
Yes. The outline is page content you can copy without an account. Adapt it to your product, check the destination's current requirements, and verify every claim, date, permission and third-party asset before publication.
Make your next product video with DemoVexa
Download the app to make a video from your code, or start a free trial with 15 renders.