Sales demo follow-up video template
Recap a product demo with the audience’s goal, the relevant workflow and a clear next step. Keep the details grounded in the demo and its supporting sources.
See it in action with Supabase Branching demo follow-up.
From this input to this video
A recap of Supabase’s public demo: create a branch, change the schema, review and merge. The closing action is a suggested next step.
Create a 45-second follow-up video after a demo of Supabase Branching for developers who watched Supabase’s public branching demo. Use these approved demo materials, meeting notes or public product sources: the official demo https://www.youtube.com/watch?v=AMQqhHxz5UI and current documentation https://supabase.com/docs/guides/deployment/branching. Recap the audience goal: test database schema changes separately before merging them into production. Show the workflow discussed: in Jon Meyers’s demo, create an add-comments branch, add a comments column to the posts table, review the changes and merge the branch; recap the real demonstrated workflow rather than implying a private customer meeting. Use this verified supporting detail: the demo shows the comments column in the main branch only after the merge completes. Address this open question using only the supplied answer: Does a branch copy production data? No: the demo and documentation describe an isolated branch with the schema but without production data. Keep commercial terms exactly as stated in the source. End with this next step: as a suggested next step, read the current branching guide and evaluate the workflow in a test project; no buyer commitment is recorded. Describe it as agreed only when the source records that agreement; otherwise present it as a suggestion. Use actual product screenshots or recordings from the supplied sources for UI demonstrations. Tone: helpful and practical. Voiceover language: English.
Read the exact input
Prompt
Create a 45-second follow-up video after a demo of Supabase Branching for developers who watched Supabase’s public branching demo. Use these approved demo materials, meeting notes or public product sources: the official demo https://www.youtube.com/watch?v=AMQqhHxz5UI and current documentation https://supabase.com/docs/guides/deployment/branching. Recap the audience goal: test database schema changes separately before merging them into production. Show the workflow discussed: in Jon Meyers’s demo, create an add-comments branch, add a comments column to the posts table, review the changes and merge the branch; recap the real demonstrated workflow rather than implying a private customer meeting. Use this verified supporting detail: the demo shows the comments column in the main branch only after the merge completes. Address this open question using only the supplied answer: Does a branch copy production data? No: the demo and documentation describe an isolated branch with the schema but without production data. Keep commercial terms exactly as stated in the source. End with this next step: as a suggested next step, read the current branching guide and evaluate the workflow in a test project; no buyer commitment is recorded. Describe it as agreed only when the source records that agreement; otherwise present it as a suggestion. Use actual product screenshots or recordings from the supplied sources for UI demonstrations. Tone: helpful and practical. Voiceover language: English.
Selected style
Product spotlight
Read the video transcript
Here's a quick recap of Jon Meyers's Supabase Branching demo. The goal: test database schema changes separately, before they touch production. First, he created a branch called add-comments. On that branch, he added a comments column, type text, to the posts table. Then he reviewed the changes: a diff showing exactly what would run against main. And he merged the branch. The comments column appeared in main only after the merge completed. One open question: does a branch copy production data? No. The demo and the docs describe an isolated branch with the schema, but without production data. A suggested next step: read the current branching guide, and evaluate the workflow in a test project.
Make it yours
Fill in your details here, or continue and finish your brief in ngram.
Help filling in your brief
- [duration]
- Duration.
- [product-name]
- Product name.
- [audience]
- Audience.
- [source]
- Source.
- [buyer-goal]
- Buyer goal.
- [workflow]
- Workflow.
- [proof]
- Proof.
- [open-question-and-answer]
- Open question and answer.
- [next-step]
- Next step.
- [tone]
- Tone.
- [vo-language]
- Vo language.
Trusted by teams at
When to use this template
Send a focused recap after a product conversation: the buyer’s goal, the relevant workflow and one agreed next step.
A clear story to start from
Review the proposed plan to set the final scenes and pacing.
- 1
The buyer’s goal
Restate what the viewer wants to accomplish.
- 2
Relevant workflow
Recap the part of the demo that addresses that goal, with the supplied evidence.
- 3
Follow through
Answer the open question and repeat the agreed next action.
Create your video
Bring the source
Use the material you want the video to explain and fill in the brief for your audience.
Make it yours
Choose your style, add your sources and select a Brand Kit if you want to use one.
Approve the plan
Review the proposed plan containing the script, approve it and watch the resulting video.
Related templates
Explore related video examples
Refine your video in ngram
Create demo follow-ups from your tools
whenYou have the brief and source material for demo follow-ups in an AI assistant
thenUse the ngram connector to create the video with your available credits.
whenYou need to show a real workflow in your browser
thenCapture a screen recording to use as source material for your video.