A product video is most useful when it shows what the software actually does. In this conversation, Andrew Warner watches Hyperagent's Alex McDonnell demonstrate Sizzle, an agent that explores a product, rebuilds selected interface states as animated scenes and edits them into a marketing video. Alex also gives it rough phone footage; the agent trims the retakes and places product visuals against his narration. The result is compelling, but it is a vendor demonstration, not an independent test across many products.
Sizzle is worth investigating if your team ships product changes faster than it can make clear demo videos. Start with one public or test feature, a limited demo account and a short script. Ask for a draft, compare every reconstructed screen with the real product, then approve the cut and its claims. The current Sizzle page advertises a startup waitlist; do not assume the video workflow is generally available or included in Hyperagent's free allowance.
Watch Andrew Warner's Sizzle Demonstration
Presented by Hyperagent. Alex works on the product being demonstrated, and Andrew describes using Hyperagent with his team. The supplied transcript supports what appears in the interview; product access and billing below were checked against Hyperagent's own pages on 10 November 2026.
How Sizzle Turns Product Use Into a Video
The official Sizzle page describes four stages: explore the feature in its own browser, extract the front-end structure and styling, recreate the interface as an animatable scene, and render the scene to video. The interview adds the editing layer: Sizzle selects moments, builds motion graphics, aligns visuals with a speaker and accepts revision notes in the same conversation.
| Stage | What the demo shows | What to verify |
|---|---|---|
| Explore | The agent opens a web or desktop product and learns which action tells its story. | Use a dedicated account. Keep private customer data, admin functions and unreleased work out of reach. |
| Reconstruct | It redraws interface states so text and actions are legible in a short video. | Check that every visible feature, result and transition matches a real capability. |
| Edit | It cuts rough footage, adds product B-roll, captions and motion, and chooses a concise narrative. | Listen for edits that change meaning; check captions, branding, music and source-asset rights. |
| Revise | Alex gives conversational feedback instead of rebuilding a timeline by hand. | Compare the revised export with the requested changes and keep the approved version identifiable. |
Hyperagent's browser documentation confirms that agents can operate signed-in sites and hand the session to a person for login or other judgment calls. Its code-and-files documentation describes a private workspace that can process media and produce files. These are platform capabilities, not proof that every Sizzle attempt will match the polished examples.
Two Formats in the Episode
Product-led demo: Alex shows short concepts made for several YC companies, including a 3D-product tool called Confetti. Sizzle uses a real product as its starting point and makes an edited, stylized sequence around a feature or payoff. The official Sizzle gallery labels these as demos or demo concepts. They are useful examples of visual treatment, not evidence that the companies commissioned or approved the videos.
Speaker-led launch video: Alex records about five minutes of imperfect talking-head footage on his phone and shows a finished video of about one minute. Sizzle removes pauses and retakes, adds captions and chooses product shots for what he says. We see the source and the output in the interview, but there is no independent timing or quality benchmark for how consistently another team could repeat it.
A Recreated UI Is Not a Raw Screen Recording
Alex argues that ordinary desktop UI can be too dense for a tiny social-feed video. Recreating a scene lets Sizzle enlarge the important action, simplify surrounding controls and animate a clear before-and-after. That is a sound design reason to use a stylized product visual. It also creates an editorial obligation: a viewer may read the scene as literal product behavior.
Label conceptual sequences when needed. Do not show an unsupported result, a hidden integration or an unrealistically instant workflow as if a customer can reproduce it today. For onboarding, compliance, training or bug reproduction, a real screen recording may be better than an animated reconstruction. For a launch teaser, a faithful stylized scene can communicate the value more quickly.
A Controlled First Test
- Check access first. Visit the Sizzle page. As checked, it invites startups to a waitlist and describes a limited promotional-credit offer. The interview's Marketplace walkthrough may not reflect what every account can install today.
- Choose one safe feature. Write a one-sentence claim, the user action that proves it and the final screen the viewer should remember.
- Prepare a demo environment. Create a non-admin product account with synthetic data and only the screens Sizzle needs. Do not give an agent shared production credentials or customer records.
- Supply source material. Give it the product URL or build, approved brand assets, aspect ratio, target length and optional speaker footage. State which features are real and which visuals must be labeled as concepts.
- Review a first cut. Check sequence accuracy, legibility at phone size, captions, audio, rights and the call to action. Ask for concrete revisions and verify the final export before publishing.
Free to Start Is Not the Same as Free Video Generation
At 06:45 in the interview, Alex says Hyperagent's free plan should let a viewer start a first Sizzle video. Hyperagent's current free-allowance documentation says generated images, video and audio are not included in that allowance and use paid credit. Its Sizzle page currently offers $1,000 in credits to 25 startups through a waitlist. That offer is limited, not a general free-video promise. Verify eligibility, current account access and the estimated credit use before starting a render.
The interview also shows Sizzle receiving footage and revision notes through iMessage, and mentions Slack. Hyperagent's current Slack guide documents agent deployment and notes that the AI assistant integration requires a paid Slack workspace. The iMessage setup is visible in Alex's account in the video; check whether your own account exposes it rather than assuming universal availability. Neither channel removes the need to control who can invoke the agent or see the footage.
What Must Be True Before You Publish
| Question | Pass condition | Why it matters |
|---|---|---|
| Is the product behavior real? | Every feature and result in the reconstructed UI can be reproduced in the current product, or is plainly marked as a concept. | A polished animation can overpromise more easily than a raw capture. |
| Is the environment clean? | No real customer records, credentials, private messages or confidential roadmap details appear in source or output. | The agent explores a signed-in product and handles raw files. |
| Is the media cleared? | Speaker, product screenshots, logos, music and any third-party footage have the intended usage rights. | Automated editing does not grant new permissions to use assets. |
| Does the video work on a phone? | The key action is legible without pausing; captions match speech; the result and CTA survive a small preview. | Sizzle's visual advantage depends on clarity at the size viewers actually see. |
JQ AI Systems take: the most promising use is repeatable launch production, not a one-click replacement for a product marketer. Test one feature video against your usual manual process. Record setup time, credit spend, revision count, factual corrections and the time to an approved export. If the agent makes a beautiful but inaccurate UI, it has moved work into review rather than removed it.
Sources and Related Video
Andrew Warner and Alex McDonnell's Sizzle interview · official Sizzle page and gallery · free-plan limits · browser tool · workspace and files · Slack integration. The earlier Andrew and Alex Hyperagent walkthrough shows a different sales-agent use case, not a second test of Sizzle. Access and billing checked 10 November 2026.
Video Chapters
| Time | Segment |
|---|---|
| 00:00 | Introduction to Sizzle |
| 00:36 | Sizzle examples for YC companies |
| 01:03 | Using the real product |
| 01:21 | Recreating the interface |
| 02:24 | Speaker-led videos |
| 03:00 | Matching product B-roll |
| 03:27 | The marketing bottleneck |
| 04:12 | Editing through conversation |
| 04:30 | Five minutes of raw footage to one minute |
| 05:15 | Updating videos as the UI changes |
| 05:33 | Finding the Sizzle template |
| 06:09 | Computer and desktop access |
| 06:18 | Andrew on Hyperagent |
| 06:45 | The free-plan claim |
| 07:03 | Editing through iMessage |
| 07:39 | iMessage setup in the demo |
| 08:06 | Human and agent group chats |
| 08:33 | Letting Sizzle explore the product |
| 09:18 | Why stylized UI can read better |
| 10:21 | The future of product demos |
| 11:06 | Earlier Hyperagent walkthrough |