01 / The short answer
The practical answer.
Give Gemini a product fact sheet and relevant files, then ask for a timed launch-video brief. Use the prompts below for planning and review, and keep that text workflow separate from any media-generation feature available in your account.
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 Gemini walkthrough.
Make one clear first version, review it, then refine the details.
Attach relevant source material.
Provide the current product copy and selected screenshots or supported files using the available upload controls. Keep the material focused. Ask Gemini which facts it can establish from what you supplied.
Choose a customer and a hook.
State the intended audience and their current problem. Request several short openings with the supporting fact beside each. Select one angle that accurately represents the product.
Build a timed storyboard.
Ask for four scenes, their durations, copy, product visuals, and motion notes. Make Gemini identify any missing assets. Do not accept a beautiful-sounding scene that depends on an invented feature.
Refine the brief for production.
Specify the editor or workflow that will make the video and the assets you can actually use. Ask for a small set of production notes. Keep the script and the factual product description separate.
Verify before making the film.
Use the review prompt to surface claims, assumptions, and reading-time problems. Check them against the source documents. Produce the video in your chosen workflow and review the finished file rather than only the generated text.
03 / A useful prompt
Start with a usable brief.
Use this in Gemini 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 Gemini, supply the relevant fact sheet and ask for scene timings and missing-asset questions. Confirm the facts before handing the brief to an editor.
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 Gemini, supply the relevant fact sheet and ask for scene timings and missing-asset questions. Confirm the facts before handing the brief to an editor.
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 Gemini, supply the relevant fact sheet and ask for scene timings and missing-asset questions. Confirm the facts before handing the brief to an editor.
08 / Checks and limits
Before you publish.
Use relevant files as context and verify that the resulting brief reflects them accurately. The prompts here ask for text planning, not guaranteed video generation or a particular account feature.
- 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 Gemini 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 Gemini
- Use the Gemini 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.
Do the prompts guarantee a finished video?
Use relevant files as context and verify that the resulting brief reflects them accurately. The prompts here ask for text planning, not guaranteed video generation or a particular account feature.
Was the audixa example made with Gemini?
No. The featured audixa film was made with LaunchVideoAI. It is product-video inspiration, not a result from this Gemini 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