Record mode

Three ways to record a demo

You drive, you show it once, or the agent drives. The right choice depends on how well the workflow is known — and only one of them is reliable on an unfamiliar UI.

I drive

You perform the demo yourself in the built-in Demo Browser, at your own pace, without narrating. The studio records every click and polishes the take afterwards. This is the reliable path and the one to reach for by default: what gets filmed is exactly the workflow you meant to show, because a person who knows the product did it.

One-click Polish then applies silence cuts, filler-word removal and an optional voice swap. An Auto-Director pass adds camera zooms, click callouts, captions and chapter cards. The result opens as a real, editable Editor project rather than a flat export.

Show it once

You click through the workflow a single time and the agent learns it, cleans it up, and performs it smoothly on camera. Useful when the demo is fiddly to perform cleanly — a form with a lot of typing, a flow where you keep fumbling the same step — but the path itself is well defined.

The agent drives

Given a goal and a URL, the agent works out the workflow itself, practises off-camera, writes the script from what actually happened, voices it, performs it on camera and composes the result.

Be clear-eyed about this one: an agent working an unfamiliar interface is markedly less reliable than a person doing it once. It is the right choice when nobody is available to perform, or when you are producing demos of many products at volume. It is the wrong choice when the demo has to be perfect and you could simply have recorded it.

Studying the site first

Whichever mode you pick, point Record at the product's URL and let it study the site first. It crawls same-site pages several links deep and distils the pitch, the pricing, the integrations and the product's own vocabulary into a knowledge pack.

This is what stops a demo sounding generic. A studied demo uses the real plan names and the real claims, because it read them — rather than narrating around the interface in the abstract.