Video production for SaaS

What this is about

The first deliverable of a SaaS shoot is not footage but a demo environment: a tenant filled with fictional yet plausible data, because real customer names, metrics or documents on screen are a GDPR incident, not a design flaw. The interface itself drifts — releases between recording and publication change buttons and layouts, so the plan pins a UI version, freezes feature flags for the demo tenant, and schedules re-capture windows. Casts are distributed: founders, customers and product people sit in different cities, which makes remote recording kits, lighting guidance and consistent framing part of pre-production. And the story must map to what the product visibly does — a promised workflow the screen cannot show reads as fiction.

Sector routine beats general experience: knowing the field's approval paths and constraints produces more realistic plans than more shoot days without that context.

What runs differently here

Where this differs from the general case:

• A dedicated demo tenant with fictional data is built before the shoot — real customer data on screen is a data-protection incident
• UI versions are pinned: feature flags frozen for the demo environment, and a re-capture window scheduled before publication
• Screen recordings follow a spec — resolution, cursor behavior, timing — so captures from different weeks cut together
• Remote contributors record with shipped kits and live direction; their framing and light are planned, not hoped for
• Product claims map to visible workflows — the script is checked against what the current build actually shows

What the plan has to deliver

A production plan is useful to this role when it provides the following:

• A demo-environment brief — data, users, feature flags — delivered before the capture day
• A capture spec and UI-version pin, with a re-capture slot before launch
• A remote recording plan per contributor with kit, framing and direction call

Common pitfalls

What most often goes wrong in practice:

• Recording the demo on a colleague's live account full of customer names
• Publishing a launch film whose UI is two releases old
• Letting remote interviews arrive in five formats, three framings and one unusable audio

With TillyGen

TillyGen splits a SaaS brief into screen scenes, live scenes and remote scenes — each with its capture spec and UI-version note — so the film still matches the product on launch day.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.