01 / The short answer
The practical answer.
Use Claude to turn a fact sheet into hook options, a structured storyboard, and a reusable production brief. If you also request an artifact, keep the planned video and its export requirements explicit.
A useful prompt separates facts from creative choices. Supply the product’s real features and evidence first, then ask for a hook or storyboard. The assistant should flag missing material rather than invent customers, metrics, integrations, or testimonials. Treat its output as a draft you verify before building the video.
- Product name, audience, current problem, supported features, evidence, brand tone, and the desired CTA.
02 / The walkthrough
The Claude walkthrough.
Make one clear first version, review it, then refine the details.
Give Claude a source-of-truth brief.
Supply the product facts, audience, real CTA, and assets. Ask it to list assumptions and unresolved questions. Approve the factual summary before moving to the creative direction.
Explore a few story directions.
Request a benefit-first, workflow-first, and problem-first opening. Choose one rather than combining them. Tell Claude the tone to preserve and the claims it must not introduce.
Request a structured scene document.
Use the storyboard prompt below to separate copy, visuals, and timing. Ask for a document you can revise scene by scene. A coherent scene brief should remain useful even without an interactive artifact.
Specify what a prototype must do.
If you want an HTML animation, ask for a finite timeline, local assets, and reproducible frames. Treat it as a separate production request. The prompt should not describe an HTML export as if it were a completed MP4.
Review the brief and the resulting film.
Ask Claude to identify mismatches between scenes and the source facts. Then inspect the actual video for readable text and timing. Preserve the approved brief with the exported version so future edits have a clear starting point.
03 / A useful prompt
Start with a usable brief.
Use this in Claude with your product facts. Replace the bracketed details before asking for a draft.
Product: [name] Audience: [specific user] Current problem: [what is difficult today] Verified product facts: [supported features and evidence] Available visuals: [logo, screenshots, clips] Brand: [colors, font, tone] CTA and destination: [real action and URL] Write five hooks for a 30-second product launch video. Each hook must identify a specific customer problem and use no more than eight words. Explain which supplied product fact supports each hook and reject hooks that require unverified claims. Do not invent features, metrics, testimonials, prices, or availability. Flag missing facts and assets. Separate on-screen copy, narration, and production notes.
This prompt produces a brief or checklist. The walkthrough explains the separate production and delivery work.
04 / Storyboard prompt
Storyboard prompt.
Product fact sheet: [paste verified facts] Approved hook and storyboard: [paste current draft] Available assets: [list actual files] Use the approved hook and the supplied facts to make four scenes totaling 30 seconds. Return a table with start time, end time, headline, optional narration, actual product visual, motion idea, and required asset. Keep each headline concise enough to read during its still interval.
Approve the output before using it in the film. These prompts do not establish that a feature or claim is true.
05 / Creative direction prompt
Creative direction prompt.
Product fact sheet: [paste verified facts] Approved hook and storyboard: [paste current draft] Available assets: [list actual files] Propose three distinct visual directions for the approved storyboard. For each, specify a color treatment, typography hierarchy, screenshot framing, movement style, and music mood. Preserve the real logo and exact interface labels. Describe the tradeoff and asset requirements; do not assume a stock visual proves a product feature.
Approve the output before using it in the film. These prompts do not establish that a feature or claim is true.
06 / Review prompt
Review prompt.
Product fact sheet: [paste verified facts] Approved hook and storyboard: [paste current draft] Available assets: [list actual files] Review the attached storyboard against the supplied fact sheet. List unsupported claims, ambiguous wording, missing visuals, excessive reading load, and CTA problems. Suggest exact changes without adding new features. Recalculate the scene timings and identify anything that needs a human decision before production.
Approve the output before using it in the film. These prompts do not establish that a feature or claim is true.
07 / Worked examples
Three ways to apply it.
These are illustrative production briefs. They are not customer case studies or claims that the featured tool produced the LaunchVideoAI film above.
A scheduler: ask for the mechanism, not generic hype
Supply “Draft once, choose supported channels, schedule from a calendar” as the verified mechanism. Ask for hooks aimed at a solo marketer, such as “Your next week, already in view.” Reject wording like “Ten times more engagement” unless you have evidence. A good follow-up is “Show the calendar result in scene three and remove the second slogan.” In Claude, request these exact states and hold times. If using a coded prototype, inspect the key frames and treat video rendering as a separate delivery step.
An API: turn technical details into a visible story
Provide a supported input, an output example, and the documentation language your team has approved. Ask for a storyboard that makes the transformation visible without inventing latency or cost claims. For an audio API, the sequence might be text, voice selection, and a preview. Keep endpoint names out of an introductory video unless the audience needs them. In Claude, request these exact states and hold times. If using a coded prototype, inspect the key frames and treat video rendering as a separate delivery step.
A team app: write for a specific new user
Describe a new teammate who needs to find an onboarding answer. Ask for a 30-second story that shows the question, the searchable guide, and the answer. Then ask the assistant to identify assumptions about permissions or search that need confirmation. This produces a brief a designer can follow while leaving product facts under your control. In Claude, request these exact states and hold times. If using a coded prototype, inspect the key frames and treat video rendering as a separate delivery step.
08 / Checks and limits
Before you publish.
An artifact can help you iterate on source and layout. An HTML export still needs rendering or recording for MP4 delivery. Check local assets, fonts, and timing before capture.
- Include a fact sheet and identify what is unknown.
- Ask for scene durations that add up to the intended length.
- Distinguish on-screen copy from narration and production notes.
- Review factual claims and trim the script by reading it aloud.
09 / A website-first option
Choose the production path.
Use Claude when its workflow fits your project. For an original product film based on a public website, LaunchVideoAI offers another starting point.
01 / THE WORKFLOW
Work with Claude
- Use the Claude walkthrough for this specific task
- Supply accurate product facts and publishable assets
- Review the scene plan and produce or export the film
- Keep the editable source and verify the delivery file
02 / THE WORKFLOW
Start with LaunchVideoAI
- Enter a public website URL
- Choose the theme, length, and anything to highlight
- Generate original animation and music for the product
- Review versions, request an edit, and download the MP4
YOUR WEBSITE IS ALREADY THE BRIEF
Let’s put it in motion.
Original animation and music, made for your brand.
10 / Common questions
Questions before you start.
Will these prompts produce a finished branded MP4?
The prompts below produce copy and production briefs. Other media features or connected tools may be available in your account, but a script or storyboard is not itself an exported video. Choose an editor or a website-to-video workflow for the finished file.
Is an HTML artifact already a video file?
An artifact can help you iterate on source and layout. An HTML export still needs rendering or recording for MP4 delivery. Check local assets, fonts, and timing before capture.
Was the audixa example made with Claude?
No. The featured audixa film was made with LaunchVideoAI. It is product-video inspiration, not a result from this Claude walkthrough. The worked examples are proposed briefs, not demonstrations of measured customer results.
Can I start from my public product website?
Yes. LaunchVideoAI starts from a public website URL. Choose your theme, video length, and focus, then review the generated film and request changes if needed. Check the current Essential and Explore packages before purchasing.
You can use LaunchVideoAI to make an awesome launch video in a few minutes.
Sources & further reading