Make a sales demo follow-up video from meeting notes
Give a buyer a focused recap of the workflow discussed in a demo. Use meeting notes and approved product material to explain their goal, answer the open question and propose the next step.
See what you can make
A recap of Supabase’s public demo: create a branch, change the schema, review and merge. The closing action is a suggested next step.
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.
How it works
One source. A repeatable workflow.
Start with
Demo notes and product sources
Create in
ngram
Make
Demo follow-up video
Prepare the buyer-specific recap
Select the buyer’s goal, the demonstrated workflow and the unresolved question. Include only approved meeting notes and product material. Use an agreed next step only when the notes record that agreement.
Open the starter in ngram
Choose Open in ngram to carry the starting prompt into your workspace. Sign in if prompted, replace the bracketed details with your own, and add source files. Review the brief and choose your settings before creating.
Create and review your video
Check your selected settings and the total estimate, then choose Create video. If a plan is offered, read it and use Request changes or Approve plan. ngram-flash starts production directly. Keep the same conversation while the video is being made.
Check claims and recipient context
Verify the workflow and answer against the sources. Keep commercial terms unchanged and confirm the audience is correct. Remove confidential material that the intended recipients should not see. Play the full preview and use chat or Make changes for corrections.
Your starting point
Start with the prompt.
Open the starting prompt in ngram, add your source, then review and create your video.
Edit this if you like, or open it in ngram and add your source there. You’ll review the brief and settings before creating.
Review. Then deliver.
A playable video appears in the conversation. Play it and compare it with your source before choosing how to deliver it.
While your video is being made
Read the latest conversation message. Answer a question or approve a plan when asked; otherwise let the active generation finish. You can return to the conversation from Projects.
Share a link
Open Share to publish a public watch link on any plan. Choose an unlisted link on Basic or above when you want access by link without public discovery. Anyone with an unlisted link can watch; check the source is suitable for that audience.
Download the video
On a paid plan, choose Download for the MP4. Wait for Preparing download to finish when shown, then play the downloaded file before delivering it.
If the workflow needs attention
Reopen the same conversation and read the error. Preserve the project link, use an offered retry once for the failed step, and contact Support if it fails again.
- The source cannot be read
- Check the URL and permissions. Provide the relevant text or attach an authorized file in ngram, then ask for the missing source to be used in the same conversation.
- The result misses a fact or step
- Quote the source and identify the exact line or scene to correct. Request a targeted change in the same project, then replay the corrected section and its surrounding context.
- The shared version is out of date
- Open Share and choose Republish when offered. Open the watch link in another tab and verify that it shows the intended version.
Keep the workflow. Change the story.
- 01
Adapt for the next conversation
Replace buyer context and meeting notes for each follow-up. Reuse the structure, then verify that no previous buyer’s names, terms or questions remain.
- 02
Keep the project and delivery link together
Save the project link with the source version and shared link. For a revision, reopen that project and ask for the change; for a new topic, return to this workflow and fill in a fresh brief.
Examples
See the format in action
Explore examples and the source prompts behind them.
Templates
Start with a reusable brief
Adapt the template to your source, audience and next step.
Features
Refine the finished video
Explore the features that help you shape the result.
Solutions
Make it part of your team’s work
Find related video jobs for the people doing this work.
Use cases
Put the video to work
Explore the communication job behind this workflow.
Converters
Start with the source you have
Choose a starting format that fits your material.
Tools
Prepare the supporting pieces
Open a focused tool for the next part of the job.
Integrations
Create and share where you work
Explore another connection that fits your process.
Related workflows
Keep the next task moving
Try a related workflow when the source or next step changes.