Your first demo

The short version

1. Open the home page or the composer.
2. Paste the URL of the page the demo should start on.
3. Write one line about what to show — a flow, not a feature list.
4. Press the button.

That is the whole path. No account is created, no email is asked for, and nothing is charged. A demo takes 10–20 minutes end to end, most of which is capture and compositing rather than thinking — the same range the job page quotes you while you wait.

What happens while you wait

You are moved to the job page, which streams the build log as it happens. The phases are

and each one writes lines you can read: which element discovery chose, what it typed, which check it waited on, how long the capture ran. Reading the build log explains what the lines mean and which ones matter.

You can close the tab. The job keeps running and the page will show the finished video when you come back to it — the library at My videos is where you find it again.

Writing the intent line

The sentence is the only steering you get, and it is worth thirty seconds of thought. The best ones name a flow with an end state:

• "Create a new project and show it appearing in the list"
• "Search for an invoice, open it, and download the PDF"
• "Turn on two-factor authentication from the security settings"

The worst ones name a feature, because a feature is not a sequence of clicks:

• "Show the dashboard"
• "Our analytics"

If you are not sure, write the rough version and press the Refine button beside the box. It rewrites your line into one tight instruction of at most 40 words, hands it back into the field, and you can edit it further or ignore it. It is capped at 10 refines an hour and costs nothing. The URL and the intent line goes into what discovery actually does with it.

The URL matters more than people expect

Point it at the screen the flow starts on, not at your marketing home page. Discovery explores forward from wherever it lands; if it lands on a landing page it will spend its first beats getting into the product, and those beats are in the video.

If the flow is behind a sign-in, the URL alone will not reach it. Save a browser session first — see Recording behind a login — and pick it in the composer.

The knobs on the composer, and the two that are not there

Four choices sit under the box, and all four are free:

There is deliberately nothing else. The look of the video, the camera, the narration, the trims and the audio are all decided after the first render, in the editor, where you can see what you are changing. That is a rule rather than an omission: a create form that asked twenty questions before it had shown you anything would be a worse first minute.

When the first one is not right

Almost nobody's first demo is the one they ship, and the product is built around that.

• Wrong words? Open the editor and retype the narration. That is an edit, not a re-shoot; it costs one render and no exploration.
• Wrong flow? Change the intent line and make another. "Make another like this" on the job page pre-fills the URL and the prompt.
• The app changed since? Press Refresh. It explores the live app again from the same URL and the same sentence.

Every one of those produces a NEW video beside the old one. Nothing you have already shared changes under you — see Version history.