Turn product release notes into short launch videos

Collect the release notes, product screenshots, screen recordings, target audience, launch CTA, and approved claims in Google Docs. Rewrite the update into plain language: what changed, who benefits, why it matters, and what users should do next. This source brief prevents the video from becoming a list of features with no story.

Turn these product release notes into a launch source brief.

Release notes:
{{release_notes}}

Target audience:
{{target_audience}}

Product context:
{{product_context}}

Approved claims:
{{approved_claims}}

Output:
1. What changed
2. Who benefits
3. User problem this solves
4. Why it matters now
5. Suggested video angle
6. CTA
7. Visuals or screenshots needed
8. Claims to avoid

Use plain language. Avoid internal product jargon.

Decide which formats the update deserves. Not every release needs every asset. Common formats include a 30-second launch video, 60-second feature walkthrough, 15-second social teaser, customer education clip, and sales enablement explainer. Map each format to audience, channel, length, and CTA.

Recommend the best video formats for this product update.

Launch source brief:
{{launch_source_brief}}

Available visuals:
{{available_visuals}}

Channels:
{{channels}}

For each recommended video, output:
1. Format name
2. Audience
3. Channel
4. Ideal length
5. Core message
6. CTA
7. Visuals needed
8. Whether this is must-have or optional

Do not recommend more videos than the update deserves.

Use Claude to write scripts for the selected formats. Each script should open with the user problem, show the improvement, and close with a specific next step. Avoid starting with 'we are excited to announce.' Customers care less that you shipped something and more that their job is easier now.

Write short launch video scripts from this source brief.

Source brief:
{{launch_source_brief}}

Selected video formats:
{{video_format_plan}}

Brand voice:
{{brand_voice}}

For each video, include:
1. Hook
2. Script
3. On-screen text
4. Visual direction
5. CTA
6. Approximate length

Rules:
- Start with the user problem or outcome
- Avoid internal jargon
- Keep scripts concise
- Do not invent functionality
- Make each video useful as a standalone asset

Capture short screen recordings, product screenshots, or simple UI clips for the update. Keep recordings clean and focused. Show only the path that matters for the script. If the UI contains sensitive or messy demo data, blur, crop, or use a prepared demo environment before editing.

Use Descript to assemble the voiceover, screen recordings, and captions. Add simple overlays in Canva for feature callouts, before/after moments, and CTA frames. Keep the editing style consistent so every release starts to feel like part of a recognizable product communication system.

Use Opus Clip or manual cuts in Descript to create short variants for LinkedIn, email, sales follow-up, help docs, and the changelog. Each variant should have its own opening line and CTA based on the channel. A sales follow-up clip should be more direct than a public social teaser.

Create channel-specific captions and CTAs for these launch video variants.

Video summary:
{{video_summary}}

Channels:
{{channels}}

Audience:
{{audience}}

For each channel, output:
1. Caption or intro text
2. CTA
3. Thumbnail text
4. First 3-second hook suggestion
5. Any channel-specific edit notes

Keep the message specific to the viewing context.

Publish the videos on the changelog, launch page, help center, or Webflow resource page. Save final links, scripts, source visuals, and edit notes so the next release can reuse the structure. After launch, track views, clicks, sales usage, customer questions, and whether the video reduced confusion around the feature.