Turn product release notes into short launch videos

Start in Google Docs with the final release notes, product screenshots, demo environment, target release date, known limitations, and approved customer-facing terminology. Work in google docs and capture the concrete operating details: source asset, audience, hook, angle, channel, draft copy, visual asset, approval status, and publish URL. Keep the work narrow: complete step 1, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the asset matches the channel, the CTA is clear, and the final version is easy to reuse; the expected handoff is An approved release source packet with public facts, assets, owners, and exclusions.

Use Claude to classify the release as a major launch, meaningful feature update, maintenance improvement, or internal-only change. Work in claude and google docs and capture the concrete operating details: source asset, audience, hook, angle, channel, draft copy, visual asset, approval status, and publish URL. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the asset matches the channel, the CTA is clear, and the final version is easy to reuse; the expected handoff is A launch-level decision and audience brief that matches production effort to customer value.

Use Claude to separate the release into problem, change, user benefit, proof, limitation, and next action. Work in claude and google docs and capture the concrete operating details: source asset, audience, hook, angle, channel, draft copy, visual asset, approval status, and publish URL. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the asset matches the channel, the CTA is clear, and the final version is easy to reuse; the expected handoff is An approved message hierarchy that converts release facts into accurate user value.

Use Claude to write one master script that follows the actual demo sequence, then create shorter versions for social, email, and the product page. Work in claude and google docs and capture the concrete operating details: source asset, audience, hook, angle, channel, draft copy, visual asset, approval status, and publish URL. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the prompt includes the actual inputs, the requested output format, and clear rules against invented facts; the expected handoff is A master demo script and approved short-form variants for each launch channel.

Record the approved demo in a clean test environment, using Descript to edit narration and screen footage. Work in descript and capture the concrete operating details: source asset, audience, hook, angle, channel, draft copy, visual asset, approval status, and publish URL. Keep the work narrow: complete step 5, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the asset matches the channel, the CTA is clear, and the final version is easy to reuse; the expected handoff is A clean master walkthrough with accurate product behavior and no sensitive information.

Use Canva to create the opening card, end card, feature labels, comparison frames, and thumbnail from one small launch template. Work in canva and descript and capture the concrete operating details: source asset, audience, hook, angle, channel, draft copy, visual asset, approval status, and publish URL. Keep the work narrow: complete step 6, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the asset matches the channel, the CTA is clear, and the final version is easy to reuse; the expected handoff is A branded master video with captions, thumbnail, labels, and channel-safe layouts.

Use Opus Clip to identify possible short segments, then manually compare them with the approved script. Work in opus clip and claude and capture the concrete operating details: source asset, audience, hook, angle, channel, draft copy, visual asset, approval status, and publish URL. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the asset matches the channel, the CTA is clear, and the final version is easy to reuse; the expected handoff is A reviewed set of launch clips and channel copy derived from the approved master video.

Publish the approved master video and supporting copy in Webflow, then upload channel derivatives through the normal launch process. Work in webflow and google docs and capture the concrete operating details: source asset, audience, hook, angle, channel, draft copy, visual asset, approval status, and publish URL. Keep the work narrow: complete step 8, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the asset matches the channel, the CTA is clear, and the final version is easy to reuse; the expected handoff is A live, tested launch-video package with source files, approvals, and channel links.