How to make a product launch video with Claude Opus 5.5 (and why we still storyboard first)

If you want to make a product video with Claude Opus 5.5, the useful question is not "can it make the video?" It is "which part of the work is it good at?" Claude Opus 5.5, Anthropic's model, does not render video. What it does well is the thinking that comes before any frame exists: reading your landing page and README, finding what is actually worth saying, and turning that into a brief, a shot list and on-screen copy you can hand to an editor, a motion designer, or a service like LaunchReel AI.

This guide walks through that workflow with example prompts, then explains why we put a storyboard review in front of every render.

An update to this guide: inside our own pipeline, Claude Opus 5.5 now goes one step further and also writes the motion-design scenes our engine renders. The Claude Opus 5.5 product video page explains how that works and what it still can't do.

Step 1: Give it the real source material

The model can only work with what you give it. Paste the text of your landing page and your README into the conversation, or attach them as files. If your setup lets Claude fetch web pages, you can give it the URLs instead, but pasting is more predictable because you control exactly what it reads.

• Your homepage copy, including headings and feature sections
• Your README, especially the description, quick start and feature list
• Your pricing page, if the offer matters to the launch
• A one-line note on who you are launching to and where the video will be posted

Step 2: Extract positioning before writing anything

Resist asking for a script straight away. First ask for an analysis, so you can check its understanding against yours.

Here is my landing page and README. Without writing any marketing copy yet, tell me: 1) what the product is in one sentence, 2) who it is for, 3) the problem it solves in the user's own words, 4) the three to six features that best support that, ranked, and 5) any claims on the page that are vague or unsupported. Quote the source line for each point.

Asking for source quotes matters. It keeps the output tied to what your page actually says and makes it easy to spot where the model filled a gap with a guess. Correct anything that is wrong now; every later step inherits it.

Step 3: Turn it into a one-page brief

Once the positioning is right, ask for a brief in a fixed format. A consistent format makes it easy to review and easy to hand off.

Write a video brief with these fields: Product, Audience, Core problem, Selling points (3 to 6, one line each), Tone (three adjectives), Length (30 s), Formats (16:9 and 9:16), Assets needed (list the specific screenshots that would prove each selling point), Call to action. Do not invent metrics, customers or testimonials.

The "assets needed" field is the most practical part. It tells you which screenshots to capture before any production starts, and it shows you which selling points you cannot actually show yet.

Step 4: Write the shot list and on-screen copy

Now ask for a shot list using a structure that is known to work. Our product launch video template uses hook, problem, reveal, three feature beats, proof and end card. You can paste that structure in directly.

Using the brief, write a 30-second shot list as a table with columns: Time, Visual, On-screen text. Follow this structure: hook (0-3 s), problem (3-6 s), reveal (6-9 s), three feature beats (about 5 s each), proof (3 s), end card (3 s). On-screen text must be under 8 words per shot and readable at phone size. Every visual must use one of the listed screenshots or a simple motion-graphic element, not stock footage.

Then run a second pass focused only on the words:

Review the on-screen text. For each line, give two shorter alternatives. Flag any line that states a benefit we can't show in that shot's visual.

What to check yourself

1. Does the hook sound like something your user would think, not your tagline?
2. Is every feature beat tied to a real screen you can provide?
3. Is every number and claim on screen already public and true?
4. Would the video make sense with the sound off?

Step 5: Why we storyboard before rendering

At this point you have a brief and a shot list. The next step is where time and money are usually lost. Rendering is the expensive part of video: it takes machine time or an editor's hours, and changes after rendering are slow. A text shot list hides problems that only show up when you see frames: a screenshot that is unreadable once scaled, two shots that look identical, a caption that is too long for the 9:16 crop.

A storyboard, even a rough one, makes those problems visible for almost no cost. It turns each row of the shot list into a frame with the actual screenshot, the actual text and the actual colors. Reviewing it takes five minutes. Fixing the same issue after a full render can take a day.

• Catch readability early. Text that fits in a table may not fit in a vertical frame.
• Agree before spending. Your cofounder or client signs off on frames, not on a description of frames.
• Keep edits local. If each shot is its own unit, changing one line should only redo that shot.

Where LaunchReel AI fits

You can take the brief and shot list from this guide to any editor or motion designer. If you would rather not run the process yourself, LaunchReel AI does the same steps as a service. You give us a URL, and optionally a GitHub repo and a one-line note. We read the site, write the brief back to you to confirm, draw the storyboard for you to review, then render motion design from your real screenshots, colors, fonts and logo. You can revise each shot on its own, and only that shot re-renders.

Your first brief, storyboard and watermarked 720p preview are free, with no card needed. After that you pay with credits from one-time packs: 1 credit to regenerate a shot, 10 for a clean 1080p export, 5 for a 9:16 version. A typical launch video with a few shot edits comes to about 19 credits, inside the $9 Starter pack. See the pricing page, or the pages for SaaS explainer videos and GitHub to video.

Summary

1. Give Claude Opus 5.5 your real landing page and README text.
2. Ask for positioning with source quotes before any copy.
3. Lock a one-page brief, including the screenshots you need.
4. Write a shot list in a proven structure, then tighten the words.
5. Review a storyboard before anything renders.

The model is good at the thinking. The storyboard is where you check that the thinking survives contact with real pixels.