Product video producer

Give a video producer a product launch, changelog entry, or feature page and it storyboards the piece, composes it as a timed web animation, and renders a short video on your machine — you approve the storyboard before production and the final cut before anything publishes.

Saves you ~6.9 h / week

Start with this playbook

How it works

Trigger
On the “Weekly video run” schedule.
Job
Storyboard the subject for approval.
Outcome
A production-ready script or video package with evidence and approval checkpoints.

What it installs

Agents 2

  • Video Producer

    Storyboards a product subject, composes it as a timed web animation, and renders the final cut for approval.

  • Product video producer Quality Reviewer

    Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.

Teams 1

  • Product video producer quality team

    The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.

Workflows 2

  • Storyboard, compose, render, approve

    Storyboard the subject for approval, compose the approved storyboard as a timed web animation, lint and preview it, render the deterministic final cut for approval, and log the piece.

  • Product video performance readback

    Load due platform results, separate packaging, retention, and business outcomes, approve a decision, and preserve the learning.

Documents 1

  • Video log

    The living record of every video produced — subject, format, storyboard verdict, render details, final-cut verdict, and what to reuse next time.

Goals 1

  • Every subject becomes a publishable final cut

    Keep launches, changelog entries, and feature pages turning into short videos the team can actually publish. Success looks like: Each assigned subject ends as an approved final cut: a storyboard approved before production, a composition that lints clean and renders deterministically, a final cut approved as-is or with one revision round, and a video log entry that makes the next piece faster.

Skills 3

  • hyperframes-video-production

    Produce short videos as HTML compositions with declarative timing — plan, confirm the subject, compose with data-* timing, wire seekable animations, lint, preview with live reload, and render a deterministic MP4 with npx hyperframes. Adapted from heygen-com/hyperframes/hyperframes.

  • video-format-selection

    Route each request to the right video shape — product-launch promo, website tour, faceless explainer, changelog video, motion graphic, or slideshow — and set the length and pacing that shape demands. Adapted from heygen-com/hyperframes/hyperframes.

  • storyboard-direction

    Turn a subject and a chosen format into an approvable storyboard — a scene-by-scene shot list with message hierarchy, one idea per scene, brand direction, and a call-to-action end-card.

Schedules 2

  • Weekly video run

    Turns the next queued subject into a rendered video on the schedule you choose; start the workflow directly for one-off pieces. ## Professional quality control Objective: complete the recurring Product video producer operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Check the artifact against the brief, design system, responsive states, accessibility, contrast, focus, reduced motion, token consistency, and realistic content. Flag fashionable defaults that the brief did not justify. User-facing copy must be direct and specific, without generic AI phrasing, filler, or vague promises. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.

  • Weekly product video performance readback

    Reviews published product videos whose complete fixed windows are due. ## Professional quality control Objective: complete the recurring Product video producer operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Check the artifact against the brief, design system, responsive states, accessibility, contrast, focus, reduced motion, token consistency, and realistic content. Flag fashionable defaults that the brief did not justify. User-facing copy must be direct and specific, without generic AI phrasing, filler, or vague promises. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.

Folders 1

  • Product videos

Requirements

  • A worker machine with Node.js, headless Chrome, and FFmpeg — The rendering toolkit runs `npx hyperframes` on the machine you connect: Node.js drives the toolkit, headless Chrome draws the frames, and FFmpeg encodes the MP4. Lint, preview, and render all happen there, and identical inputs produce identical video.
  • Brand assets the videos should carry — Logos, colors, fonts, and product screenshots or recordings, plus where they live. Until real assets are supplied, the producer composes with neutral placeholders and flags every scene that still needs one before the final cut.

Setup guide

How to Produce Product Videos

A practical guide to turning launches, changelog entries, and feature pages into storyboarded, rendered product videos with approvals.

Read the setup guide

Don't see your workflow? Describe it.

A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.

* What keeps taking time you don't have? *

Takes a minute · no account needed