Jotform

100+ videos, each one built to close a single question.

100+ videos produced for Jotform, an online form builder and form automation platform. Published on Jotform's own YouTube channel. Most of the library answers one narrow question each. Some of it answers questions about a competitor's product. This is how both get made.

By Jorge AguilarUpdated July 19, 2026

The problem

What made it hard to explain on video.

A form builder is a blank canvas. Two users open the same screen wanting different things — one is collecting event registrations, the other is taking payments and routing the result somewhere else. There is no single path through the product to record, which is exactly why a general product tour fails here. The work splits three ways instead. Most of it is narrow and high-intent: someone has a spam problem and needs the CAPTCHA setting, and the video has to answer that and stop. Some of it leaves the product entirely, walking an integration across into a third-party service where the authorisation step is where users abandon setup. And some of it is not about Jotform's product at all — it is recorded inside a competitor's tool, published by Jotform to meet an audience already using something else. Three different jobs, one library, and at a hundred videos a fourth problem appears that never shows up at ten: drift. Scripted and cut on instinct, video ninety stops looking like video two.

The approach

The production decisions behind it.

Craft notes, not a methodology diagram. Each of these is a choice that changed how the finished videos play.

01
Scope one task per video, named the way a user would ask for it. Not "the form builder" but "how to add CAPTCHA to your form". A hundred narrow videos beat ten broad ones, because support can link to exactly one of them.
02
Let the short ones be short. A video answering a single setting change opens on the problem, shows the setting, and ends. The discipline is in what gets left out — padding a ninety-second answer to three minutes is how a help video stops closing tickets.
03
Write the script against a live account before recording anything. Every click gets walked and written down first. Accuracy is cheap at the script stage and expensive once voiceover is cut.
04
Record from one canonical demo account, seeded with realistic data. Same window size, same zoom, same theme, every time. It makes the library look like one thing, and it makes a segment from video 8 safe to reuse in video 60.
05
Record integration flows end to end, including the part outside the product. Connecting a form to a notification service means crossing into another company's interface and through an authorisation screen. Cutting away at the handoff leaves the viewer exactly where they were going to get stuck.
06
Redact by default. Those third-party screens carry account data, keys, and addresses, so masking is a standing rule rather than a per-video judgement call.
07
Make the competitor-comparison videos genuinely useful first. Where a video is recorded inside another product to reach people searching for help with it, the tutorial is honest and complete on its own terms. Attention gets earned by answering the question properly, and a video that half-answers to force a switch is transparent to the viewer.
08
Solve density in the edit, not in the recording. Capture the whole screen, then let the cut decide what the viewer sees: push in on the panel in play, hold, pull back only when the context changes. The pointer leads and the zoom follows it.
09
Hold to one idea on screen at a time. A highlight box, a label, or a masked region — never all three fighting for the same second.
10
Write narration that says what is happening, not what is visible. The screen already shows the button being clicked. The voiceover exists to say why that field is set that way.
11
Cut for repair. Videos are built in segments with clean audio boundaries, so when a screen moves we replace the affected twenty seconds instead of re-recording the whole thing. At this volume that is the difference between a library and a backlog.

What was delivered

The finished library.

Over a hundred finished videos, delivered publish-ready and published on Jotform's own YouTube channel: 1080p masters, burned-in and sidecar captions, and consistent titling across the set. The library reads as one production rather than a hundred separate jobs — same pacing, same visual grammar, same voice — while still covering three different jobs, from a single-setting support answer to a full integration walkthrough to acquisition content shot inside a competing product. It is structured so individual segments can be re-cut when an interface moves, which is what it was built for: answers that stay usable long after the day they were recorded.

Services used

From this project