How to use Claude to make a product launch video
A founder used Claude Code with a product codebase, iterative feedback and separate reviewer and designer subagents to produce a launch video over two to three days.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Use [product codebase] to create a launch video explaining [product purpose] for [audience]. Have reviewer subagents critique the work and designer subagents revise it. Incorporate my feedback between iterations and show me the resulting video for review.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- jackogrady
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reports producing a working launch video over two to three days, using subscription token usage and without recording the live product.
- Human involvement
- The author directed many iteration cycles and supplied feedback; the post does not describe a formal final review procedure.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Supplied the product codebase to Claude Code as the basis for a launch video.
- Spawned subagent review panels to provide feedback to designer subagents.
- Repeated feedback and revision cycles over two to three days.
The author needed a launch video for a side product and wanted to avoid paying an agency. After seeing video examples associated with Opus 5.5, they tried making the video through Claude Code using the product's codebase and iterative feedback. They report that the approach worked, although it required many iteration cycles over two to three days.
A specific part of the process was dividing feedback and design work between subagents. The author spawned review panels with different intelligence levels, then used their feedback to inform another pool of designer agents. This gave the video repeated rounds of criticism and revision rather than relying on a single generated attempt.
The author says access to the site's source code removed the need to record the live product. They also describe the process as massively cheaper than the agency route, with usage covered by their subscription plan, but provide no monetary comparison. They shared the resulting video and invited feedback on both it and the site.
Who it's for: Side-project builders who have a product codebase and can spend time directing repeated creative revisions.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · jackogrady
Frequently asked questions
Did the author record the product manually?
The author says no live product recording was needed because the agent had the source code behind the site.
How much iteration did the video require?
The author reports many iteration cycles over two to three days, including review-panel feedback passed to designer subagents.
More details
Remaining steps
- Shared the resulting launch video and invited feedback on the video and site.
About this account
Designer subagents produced revisions informed by separate review panels, while the author supplied iterative feedback throughout the process.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=50106617. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: jackogrady on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Opus 5.5
Launch videos · Subagents · Product marketing
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.