A Product Hunt launch video should let someone inspect what the product does without requiring them to read the rest of the launch first. The product name and a recognizable result provide useful context when someone opens the video directly or watches only part of it. Playback settings and launch requirements need checking in the actual draft; they should not rest on assumptions about autoplay or gallery order.
Petal, a fictional invoicing product, supplies the example. A freelancer sends a draft invoice and checks its payment status. The film follows invoice INV-042 for $480, using demonstration data and a test payment.
Choose a result that the product can show honestly
An invoice changing to Paid can introduce Petal's status tracking, but the transition needs a cause. Sending an invoice does not itself make a customer pay. A cut that moves directly from Send to Paid could imply a guarantee the product cannot provide.
The source package therefore includes the draft invoice, the sent state, and the recorded test payment that produces the paid state. The producer identifies which payment environment the run uses and labels the demonstration accordingly. A time jump needs a visible indication if the sequence could otherwise suggest immediate payment.
The opening can show the paid invoice with its payment record, then explain how the user reaches that state. Reordering the footage must retain enough context to make the chronology understandable.
Either treatment needs a reason to fit this launch. A viewer who already recognizes invoicing may need little setup; an unfamiliar product category may need a brief explanation before its controls mean anything.
Build the invoice demonstration
The storyboard retains the invoice identifier across every surface.
- Show the invoice and its amount.
INV-042, the customer name, and $480 remain readable. Unrelated account details stay outside the crop. - Send the invoice using the actual control. The interface changes to the verified sent state. The video does not invent a delivery confirmation if the product only records a send request.
- Identify the test payment. A caption or recorded payment view explains the event between Sent and Paid. If the film compresses waiting, it says so.
- Show the payment record on the invoice. The paid amount and invoice identifier connect the result to the original draft.
- End with the available next action. The final frame names the product and directs an interested viewer to the actual trial, demo, or waitlist offered at launch.
An early estimate can allocate time across these scenes, but the reading load and recorded narration determine the finished duration. A dense payment record may need more time than the send action.
- 1Invoice. The draft identifies INV-042 and its $480 amount.
- 2Send. The actual control changes the invoice to its recorded sent state.
- 3Payment. A labeled test payment explains why the status changes.
- 4Result. The paid invoice and payment record retain the same identifier.
Check the video without sound
A muted review tests whether the invoice and its changing status remain identifiable. Captions preserve narration for viewers who do not enable audio. Essential qualifications, including the test-payment label, need to remain available in that viewing mode.
The reviewer checks the video at the launch player's displayed size. Cropped text, unreadable amounts, and captions covering the active control require layout changes. Enlarging the whole interface may hide the product name or invoice identifier, so the producer needs to review the resulting context as well as the text size.
Scrubbing through the cut can expose a scene that lacks identifying labels. It does not mean every paused frame must explain the whole product or that reading holds should disappear. A clear result frame is useful even when it stays still.
Verify the launch draft and final export
Before publication, the team checks the current submission requirements and previews the actual draft. That review verifies the supported media format, poster, playback behavior, and surrounding text. Platform requirements can change, so this production method does not prescribe a fixed upload specification.
The final export needs a playback check after encoding. The reviewer verifies the invoice data and timing disclosures again, along with the final destination link. A video that passes those checks presents a specific product task clearly; launch ranking, traffic, and trial conversion remain separate outcomes that the cut alone cannot guarantee.
The launch planning guide covers product readiness and review scheduling for the wider release.