A SaaS explainer should show a customer completing a recognizable piece of work. The intended placement helps determine how much the viewer already knows: an onboarding lesson can assume an account exists, while a homepage introduction must establish what the product does before demonstrating its controls.
The fictional CRM Fieldnote organizes deals by stage and creates a follow-up task when a deal enters Proposal. Its worked example follows the Northline deal from Qualified to Proposal, then shows the task assigned to its owner. This workflow connects the board to the task list without touring every feature.
Define the viewer's question
A homepage visitor might ask whether Fieldnote helps a team keep track of follow-up work. A new account owner might need to configure the automation. Those questions require different evidence. The introduction shows the resulting task; the setup lesson also needs the rule editor, permissions, and a test run.
A sales follow-up video may need to explain a narrower requirement, such as whether the task follows the deal owner when ownership changes. The producer should obtain that question from the intended recipient or the sales brief rather than assuming that every evaluator needs the same overview.
The explainer brief records the audience and destination. It also names the action the viewer should be able to take after watching, such as trying the workflow in a demo workspace.
Prepare the product example
Fieldnote's fictional fixture defines a rule that creates a task called “Send proposal” for the deal's current owner when the deal first enters Proposal. The test record needs a visible owner and a known initial stage. The task list initially contains no task for Northline, so the new task is distinguishable from existing work.
For a real product, the producer collects the configuration and a captured run. The product owner verifies whether the trigger runs on every stage entry, whether it creates duplicates, and what happens when a deal lacks an owner. The introductory film can exclude those edge cases, but it cannot describe a broader guarantee than the verified rule supports.
The source package includes the relevant UI version, screenshots, brand assets, and demo data. Public footage excludes private contact details and account information.
Show the same deal across the board and task list
The storyboard gives the viewer enough context to recognize Northline before the action occurs.
- Show Northline in Qualified. Its owner, Maya, appears on the deal card. A brief view of the empty filtered task list establishes the starting state.
- Move the deal to Proposal. The recording or faithful reconstruction uses the actual interaction. The stage label remains readable while the deal moves.
- Show the rule's recorded result. If the product exposes automation history, the video can display the completed run. Otherwise, it proceeds to the task list without inventing a log.
- Open the resulting task. “Send proposal” names Northline and Maya. Those repeated values connect the task to the deal the viewer just saw.
- Show the next human action. Maya opens the task or marks it complete if that action belongs to the explanation. The film need not imply that the software writes or sends the proposal automatically.
The finished sequence establishes a specific capability: entering the configured stage creates the configured follow-up task. It avoids broader claims such as “the pipeline updates itself,” which could imply automation the product does not provide.
Make dense screens readable without changing the workflow
A full CRM page can contain many fields unrelated to this example. Cropping and emphasis can make the deal card readable while preserving the parent view and navigation needed to identify it. A faithful reconstruction can also work, provided the producer retains the real labels and interaction constraints.
Moving a genuine task component onto a screen where the product never displays it would still misrepresent the interface. A diagram that combines views needs an explicit illustrative treatment so the viewer understands that it explains a relationship rather than reproducing a screen.
The producer checks the relevant fields at the embedded player's intended size. A reading hold on the new task lets the viewer confirm the deal and owner. Continuous movement would make that comparison harder.
Adapt the footage to its destination
An onboarding version adds the configuration steps and expected starting state. A homepage version can summarize those prerequisites and focus on the completed workflow. Reusing recordings saves recapture only when the product state and claims remain accurate; changing the scene order may still require new narration and timing.
The final review checks the configured trigger against the recorded run and confirms that the displayed task belongs to Northline. Captions and surrounding text provide qualifications that a viewer needs with the sound off. The product demo comparison helps decide whether the next deliverable should explain the concept or teach the full procedure.