Skip to main content

Demo presets and the Pre-flight presenter screen

Updated Sep 10, 2026

Overview

Demo presets let you save a named bundle of variable values (customer name, industry, currency, logo, sample data) and switch a demo to that bundle in one click. Instead of re-typing the same seven variables before every discovery call, a presenter opens the demo, picks the preset for the account they're meeting, and the demo opens already skinned to that vertical.

Presets pair with a Pre-flight presenter screen — an interstitial that appears before the demo opens so the presenter can confirm the preset (and any per-run overrides) without the buyer watching them fumble in the URL bar.

Use presets when you want to:

  • Ship one master demo that renders as a dozen vertical-specific stories.
  • Standardize sample data across the sales team so every demo looks "on brand" for the target account.
  • Move variable configuration from a share-link URL to a picker the presenter can operate live.

Create and manage presets

Presets are managed at the company level. Any admin can create them.

  1. Go to Company Settings → Global variables.
  2. Click the Presets tab.
  3. Click New preset and give it a name (e.g., "FinServ — mid-market").
  4. Fill in the value for each template variable in the list. Leave a field blank to let the demo's default value stand.
  5. Click Save. The preset is available immediately to every demo in the workspace.

Presets appear as rows in the Presets tab. Each row has:

  • Edit — reopen the value form.
  • Duplicate — start a new preset from a copy of this one (fastest way to build a "FinServ — enterprise" from a "FinServ — mid-market").
  • Delete — remove the preset. Deleting a preset does not touch demos that were run under it; it only removes it from the picker going forward.

Turn on the Pre-flight screen for a demo

  1. Open the demo and click Create & share in the top-right.
  2. In the share modal, toggle Pre-flight on.
  3. (Optional) In the Allowed domains field, add the email domains that may reach the Pre-flight screen. Named external domains — for example, partneraccount.com — are supported alongside your own domain.
  4. Copy and share the link.

When Pre-flight is on, opening the demo link no longer takes the viewer straight into the demo — it lands on the presenter config screen first.


The Pre-flight presenter screen

The Pre-flight screen shows:

  • A live preview of the demo, re-rendered with each choice below.
  • A Preset picker listing every company preset. Selecting one applies its values to the live preview.
  • The template variables the preset filled in, with the values shown inline so the presenter can override any one without touching the preset itself.
  • A Start demo button that opens the demo with the chosen preset (and any per-run overrides) applied.

The picker is intentionally in front of the presenter, not the buyer — the Pre-flight link is meant to be opened by whoever is about to run the demo (a presenter, an SE, or an SDR sending a pre-recorded walkthrough).


Preset narration

If your demo uses AI-generated narration or per-step text-to-speech, the preset carries its own narration variants. When a presenter picks a preset from the Pre-flight screen, the narration on every step swaps to the preset's variant — and the same narration is carried through to every viewer of that session, not just the presenter's own tab. So a buyer watching a screen-share hears the same customized narration the presenter set up.


Allowed domains

The Allowed domains input beside the Pre-flight toggle limits who can reach the presenter config screen. Add one domain per row:

  • Your own workspace domain is included automatically.
  • Add partner or reseller domains (e.g., partneraccount.com) so their SEs can also open the Pre-flight link.
  • Viewers whose email domain isn't listed skip the Pre-flight screen and open the demo with its default values.

The allowlist gates the screen only. The demo itself remains subject to whatever share-link settings you've configured (allow/block lists, email gate, verification).


Best practices

  • Name presets by the story, not the variable set. "FinServ — enterprise" beats "CustomerName=Acme, Currency=USD, LogoID=1234".
  • Keep the preset list short. Presenters scan; they don't search. 6–10 well-named presets outperform 40 near-duplicates.
  • Duplicate to iterate. When a new vertical shows up, duplicate the closest preset and change three fields rather than starting from scratch.
  • Pair Pre-flight with live demos, not embed links. Buyers don't need to see the picker; presenters do.

FAQ

Do presets change the demo itself?
No. A preset only replaces variable values at run time. The underlying demo, its screens, and its guides are untouched — closing the demo leaves the master unchanged.

Can a buyer skip the Pre-flight screen?
No. Pre-flight is opened by a presenter. If you want a buyer-facing link, share the demo without Pre-flight or use a share link with a specific preset already applied.

What happens if I delete a preset that was used on past demos?
Past demo sessions keep the variable values they were run with. New sessions can no longer choose that preset from the picker.

Can I preset any variable, or only the built-in ones?
Any template variable exposed by the demo, including custom ones. This makes presets a first-class way to reskin a template without re-authoring it.

Was this helpful?