Table of Contents
A practical AI workflow for a Product Hunt launch
Method: We tested the source handoff, video-type picker, editing controls, and export options on July 16, 2026. We also checked the Product Hunt requirements against the official documents linked below. The worked example is illustrative, not a performance study.
TL;DR
- Open the Product Hunt Launch Teaser Maker, choose Prompt, File, or URL, supply that first source, and then select Create launch video.
- Define one audience, one outcome, one real product workflow, a 45-to-60-second target, and an ethical CTA.
- Review the script and storyboard in chat before rendering. After the first cut, use scene regeneration or the timeline to correct the video.
- Export a 16:9 MP4, upload it to YouTube at least 12 hours before launch, and paste the full non-private YouTube URL into Product Hunt.
A useful Product Hunt product teaser video has one job: to prove what the product does quickly enough that a visitor wants to try it. It should feel like a teaser, yet show enough real product behavior to earn trust.
In this guide, we will create the teaser using ngram. The workflow accepts a product page, screenshots, a PDF, launch notes, or a rough screen recording, then turns that material into a script, storyboard, editable draft, captions, product callouts, voiceover, and launch-ready exports.
What to prepare for your product teaser video
Collect the source material before generating the video. A strong brief reduces invented filler and keeps the first draft tied to the live product.
| What to prepare | What it should contain | Why it matters |
|---|---|---|
| Product URL or launch copy | Current positioning and approved claims | Gives the script a factual base |
| Product proof | One workflow plus screenshots, a PDF, or a clean recording | Gives the storyboard something real to show |
| Audience and outcome | One viewer and one result to remember | Controls language and keeps the cut focused |
| Brand kit | Logo, colors, fonts, tone, and approved phrasing | Keeps the video consistent with the launch page |
| Product Hunt CTA | A visit, trial, comment, or feedback request | Avoids an improper request for votes |
Write the audience and outcome as one sentence:
After watching, [viewer] should understand that [product] turns [input or old process] into [specific result].
For example: “After watching, a solo SaaS founder should understand that Acme turns a rough product recording into a captioned launch clip.” Choose the shortest workflow that makes this promise believable: import the source, complete one key action, and reveal the result.
Step 1: Open the Product Hunt Launch Teaser Maker
Open ngram’s Product Hunt Launch Teaser Maker. Choose a source mode, supply the source, and then select Create launch video. If you are signed out, complete the sign-in step; your source stays attached to the project through the handoff.
The starting page offers three source choices:
- Prompt: paste a written brief and launch notes.
- File: upload one JPEG, PNG, WebP, or PDF reference.
- URL: paste a public product, landing, launch, documentation, or announcement page.
The landing panel accepts one mode at a time. Prompt users can paste the full brief before creating the project. URL and File users submit that first source, then add the detailed brief and any remaining assets after Studio opens.
Step 2: Add your source material
Choose the first source that contains the most accurate version of the product story. Once Studio opens, add the context that the landing panel couldn’t convey. A URL-led project may still need current screenshots; a file-led project still needs positioning and audience; a prompt-led project needs visual proof.
If the live page contains your approved positioning and current screenshots, turn the product page into a video draft and direct it toward a Product Hunt teaser. This gives you a practical URL to the video starting point.
For a screenshot of a video project, supply the screens in their intended order and identify the final result. This works well when the product is private, or its public page is out of date.
The Product Hunt tool’s initial file tab is for an image or PDF reference. For a recording-led teaser, add the recording after entering the project or use the screen recording to video workflow. It can transcribe the upload, find useful moments, trim dead air, smooth the cursor, emphasize clicks, add step labels, and apply smart zooms.
Use this instruction with a raw recording:
Use the uploaded screen recording for the product-proof scenes.
Keep only the workflow from [START POINT] to [RESULT].
Trim dead air and wrong clicks, smooth the cursor, emphasize important clicks,
and add short step labels.
Replace the rough narration with the approved script.
Do not use any frame containing personal, customer, or test data.
Do a privacy pass before uploading. Remove real customer names, personal email addresses, private analytics, access tokens, notifications, and unfinished interface states. The source can come from any screen recording software; the quality of the demo account and the clarity of the workflow matter more than the recorder.
Step 3: Write a focused AI video brief
The prompt tells the tool what the product teaser video must prove. Give the video script generator clear boundaries: the audience, source limit, outcome, proof workflow, length, tone, CTA, and anything it must avoid.
If you started on the Prompt tab, paste the full template before selecting Create launch video, then add visual sources in Studio. If you started with a URL or File, open Studio with that source first, paste the detailed brief there, and attach the remaining approved material.
Copy and adapt this prompt:
Create a 50-second, 16:9 Product Hunt launch teaser for [PRODUCT],
aimed at [AUDIENCE].
Use [PRODUCT URL] and the attached [SCREENSHOTS / PDF / LAUNCH NOTES]
as the only factual sources.
The video should prove this outcome:
[INPUT OR OLD PROCESS] becomes [SPECIFIC RESULT].
Use this real product workflow as the proof moment:
[STEP 1], [STEP 2], [STEP 3].
Structure:
0-4 seconds: show the problem or finished result
4-9 seconds: explain what [PRODUCT] does
9-30 seconds: show the real product workflow
30-40 seconds: reveal the result
40-46 seconds: state one defensible differentiator
46-50 seconds: close with the CTA
Tone: concise, specific, and maker-led.
Use the [BRAND KIT NAME] brand kit.
Add readable captions and a clear voiceover.
Do not invent features, metrics, customer results, or interface screens.
Flag anything that the supplied sources do not support.
End with:
“Try [PRODUCT] on Product Hunt and tell us what you think.”
Do not ask viewers to upvote.
Show me the script and storyboard before rendering.
The phrase “only factual sources” matters. A model can organize supplied information, but your team still needs to approve every product claim and every screen used in the video.
Product Hunt generally features products that are live and usable. Avoid presenting a waitlist or concept render as a finished workflow that visitors can try. (Product Hunt featuring guidelines)
Step 4: Choose the video treatment and brand kit
Before the generation begins, the ngram’s start wizard asks how the video should be made. Choose the format that best fits your source material, and decide whether you want a presenter.
| Video type | Use it when | Product Hunt treatment |
|---|---|---|
| AI Motion Graphics | You are starting from a URL, screenshots, a PDF, or mixed visual sources | Combine product frames, motion graphics, captions, and callouts |
| Avatar video | A presenter-led explanation will make the launch feel more personal | Keep the presenter concise and move to product proof quickly |
| Screencast + Avatar | An avatar should guide uploaded footage throughout the video | Use the recording for proof and the presenter for context |
AI Motion Graphics is a reliable default for a product-first teaser because it can combine real product material with branded text, transitions, and supporting visuals.
Select a saved brand kit in the wizard before generation. It can apply your logo, colors, fonts, motion style, screenshot treatment, tone, and approved or blocked phrases. If you do not have one, state the minimum visual rules in the prompt:
Use [HEX COLORS], [FONT OR FONT STYLE], and the attached logo.
Keep the visual treatment close to [PRODUCT URL].
Use clean product frames and restrained motion.
Do not introduce colors or claims that are absent from the source.
Choose the voice in the voice picker if the teaser uses generated narration. Add a pronunciation guide for a company name or technical term before rendering, especially when a single mispronunciation could undermine trust.
Step 5: Review the script and storyboard
Next, the tool writes the script and maps it to scenes. Its AI storyboard generator turns your sources and brief into timed scenes, narration, on-screen text, and visual direction. Treat this as the main approval point.
Check four things:
- Does the first scene show the problem, result, or product in action?
- Does the middle demonstrate one complete, accurate workflow?
- Does every visual come from approved material or a clearly supporting graphic?
- Does the CTA ask for a trial or feedback rather than a vote?
Use this table as a marketing video storyboard template during review:
| Time | Scene direction | Voiceover | On-screen text |
|---|---|---|---|
| 0-4 seconds | Show the painful starting state or finished result | Name the problem | One short problem or result |
| 4-9 seconds | Introduce the product beside its input | Explain the promise | Product name and promise |
| 9-30 seconds | Show one real workflow | Explain why each action matters | Short step labels |
| 30-40 seconds | Reveal the output | State the result | Before and after |
| 40-46 seconds | Show one defensible difference | State the differentiator | One supporting phrase |
| 46-50 seconds | Finish on the launch CTA | Ask viewers to try it and respond | Try it. Share feedback. |
Ask for changes before rendering:
- “Begin with the finished result and remove the logo-only opening.”
- “Keep one complete workflow and remove the secondary feature.”
- “Replace scene 3 with the attached dashboard screenshot. Do not invent UI.”
- “Move the differentiator after the result so the product proof lands first.”
Read the narration aloud. Remove lines that merely describe actions already obvious on screen; use the voiceover to explain why the result matters.
Step 6: Generate and revise the launch video
Once the storyboard is approved, generate the first cut. The draft can include AI visuals, voiceover, burned-in captions, music, motion graphics, product callouts, scene transitions, backgrounds, and branded opening or closing elements.
Watch the full cut once, then fix the largest communication problem first. Use agentic chat for broad changes, the script editor for wording, scene regeneration for a weak scene, visual chat or canvas controls for individual elements, and the timeline for clips, captions, audio, and effects.
| Problem in the first cut | Revision request to paste into chat |
|---|---|
| The opening is slow | “Remove the logo-only opening and show the finished result in the first frame.” |
| The cut is too long | “Shorten the video to 50 seconds while preserving the complete proof workflow.” |
| The interface is inaccurate | “Replace scene 3 with the attached dashboard screenshot. Do not invent UI.” |
| Captions carry too much text | “Rewrite the captions so each scene communicates one short idea.” |
| The CTA breaks Product Hunt rules | “Change the final CTA to: ‘Try [PRODUCT] on Product Hunt and share your feedback.’” |
| One scene feels generic | “Regenerate scene 4 as a before-and-after comparison using the supplied assets.” |
Regenerate one weak scene instead of restarting the full project. After the story is stable, check caption line breaks, product names, UI labels, sound levels, transitions, and the final frame.
Step 7: Review and export the launch video
Run two review passes inside the editor before exporting.
Review pass one: clarity without sound
Mute the voiceover and music in the finished preview. Confirm that the first frame, captions, product recording, callouts, and CTA still explain the product.
The caption generator burns captions into videos by default. Review every line for spelling, breaks, product names, acronyms, numbers, and technical terms.
Review pass two: accuracy with sound
Restore the intended audio and listen for pacing, pronunciation, abrupt edits, and music that competes with narration. Compare every product claim with the live product page or approved launch copy.
Export the approved master as a 16:9 MP4 for YouTube. Then request 9:16 and 1:1 variants from the same project:
Export the approved video as a 16:9 MP4.
Then create 9:16 and 1:1 versions from the same project.
Reframe the product UI for each aspect ratio and recheck every caption.
Preserve the approved message and CTA.
Use the widescreen version for the Product Hunt video. Use the vertical or square variants for launch posts on other channels.
Step 8: Upload to YouTube and add the video to Product Hunt
The exported product teaser is the creative asset. Product Hunt’s current posting workflow uses a YouTube URL, so you still need to publish the approved 16:9 master to YouTube and add that link to the launch.
Use this sequence:
- Upload the final 16:9 MP4 to YouTube.
- Set the video to be public.
- Confirm that embedding is permitted.
- Add a clear title, description, thumbnail, and captions.
- Upload at least 12 hours before the Product Hunt launch.
- Copy the full YouTube URL, not a shortened link.
- Paste the URL into the Product Hunt draft.
- Test playback after YouTube processing is complete.
Product Hunt warns that a newly uploaded YouTube video may take about 12 hours to integrate correctly. Shortened URLs will not load, and a private video cannot be shown. (How to post a product, YouTube troubleshooting)
If the scheduled launch remains private, change its visibility before asking someone outside the maker account to test the preview link. Scheduled launches are private by default. (Product Hunt scheduling help, sharing a scheduled launch)
Keep the CTA ethical. Product Hunt prohibits mass vote requests, voting incentives, coordinated voting groups, and paid manipulation. Ask viewers to visit, try the product, comment, or leave honest feedback. (Product Hunt sharing guidance, Community Guidelines)
Worked product teaser video example: From a SaaS page to a 50-second teaser
Suppose SignalDesk, a fictional SaaS product, turns customer interview notes into a prioritized opportunity list. Its maker starts a project with a product page, three screenshots, and a 90-second workflow recording, plus this brief:
- Audience: early-stage product managers
- Outcome: turn scattered interview notes into a ranked list of opportunities
- Proof workflow: import notes, group recurring themes, and rank the opportunities
- Source boundary: the product URL, three screenshots, and the recording
- CTA: “Try SignalDesk on Product Hunt and tell us what you think”
The first storyboard might map those inputs like this:
| Time | SignalDesk scene |
|---|---|
| 0-4 seconds | Show a folder of scattered interview notes beside the finished ranked list |
| 4-9 seconds | Introduce SignalDesk and the outcome |
| 9-18 seconds | Use the recording to import the notes |
| 18-28 seconds | Show themes being grouped |
| 28-38 seconds | Reveal the ranked opportunity list |
| 38-45 seconds | State one approved differentiator |
| 45-50 seconds | Show the product name and feedback CTA |
During review, the maker spots a long logo opening and a generic dashboard. Two revisions fix them:
Start with the before-and-after result. Remove the standalone logo scene.
Replace scene 4 with dashboard-final.png.
Keep the supplied interface exactly as shown and add one callout to the top-ranked opportunity.
After approval, the maker exports the 16:9 YouTube master and creates 9:16 and 1:1 variants. The story stays the same while the frame, captions, and product crop change for each channel.
Product teaser video checklist
Source and brief
- The product URL or launch copy reflects the current product
- The brief names one audience, outcome, and real workflow
- Assets contain no private data, and the prompt forbids invented claims or UI
Script and storyboard
- The first scene shows a problem, result, or product action
- The video shows one complete workflow, and every claim matches a source
- The storyboard ends with a trial or feedback CTA, not an upvote request
Edit and export
- Product names, captions, callouts, pronunciation, and sound are correct
- The 16:9 master works on both laptop and phone
- Any 9:16 and 1:1 variants were reframed and rechecked
YouTube and Product Hunt
- The YouTube upload was completed at least 12 hours before launch
- The video is not private, and embedding is permitted
- The full YouTube URL works in the Product Hunt draft
- Gallery images, the product thumbnail, and the processed preview are ready
Frequently asked questions
Can an AI video generator create a product teaser video from a URL?
Yes. Paste a public product, landing, launch, documentation, or announcement URL into the Product Hunt Launch Teaser Maker. The tool reads the page as source context, writes the script, builds the storyboard, and prepares the first video draft for review.
Can I use a screen recording in this workflow?
Yes. Add one inside the project or start with the Screen Recording to Video workflow. The editor can transcribe it, trim dead air, smooth the cursor, emphasize clicks, add labels, and apply smart zooms.
Which aspect ratio should I export for Product Hunt?
Export a 16:9 MP4 as the YouTube master for Product Hunt. Create 9:16 and 1:1 variants for social posts, then recheck each product crop and caption layout.
Does this workflow upload the video directly to Product Hunt?
No. This workflow creates and exports the assets. Upload the master to YouTube, then add its full non-private URL to your Product Hunt draft.
How long should a Product Hunt teaser video be?
Product Hunt publishes no official runtime requirement. Start with 45 to 60 seconds per workflow, then adjust as needed to fit the proof.
Create the video around one proof moment
The fastest way to lose a Product Hunt visitor is to explain every feature before showing why the product matters. Keep the brief to one audience, one outcome, and one complete product workflow.
Review the script and storyboard, correct the first cut with specific instructions, and export the approved widescreen master for YouTube. That sequence turns existing launch material into a product teaser video without surrendering control of the claims or the final Product Hunt handoff.
About the contributor
ngram is an AI video platform for business communication. Teams use it to turn product pages, documents, screenshots, and screen recordings into scripts, storyboards, product videos, captions, and channel-ready variants.
