How-To & Tutorial Videos

60 to 120 seconds if it covers a single task, which is the format worth defaulting to. A full walkthrough covering an entire product area can run three to five minutes, but only if it is chaptered so a viewer can jump to the step they need. The failure mode is one long video covering everything — it is too general to be linked from a support reply, and support links are where most tutorial views come from.

Several short ones, in nearly every case. Short single-task videos can be linked from a specific help article, a support macro, an onboarding email, or a tooltip, and each one is cheap to re-record when that part of the UI changes. A long walkthrough only gets watched once, by people evaluating the product rather than using it — which is a different asset with a different job. If you need both, produce them together so they share captures and a visual system.

They give your team something specific to link instead of retyping an answer, which is the mechanism by which repeated questions stop consuming human time. We will not promise you a percentage, because the honest answer depends on your ticket mix and whether the videos are actually surfaced at the moment of confusion. What we do control is scoping the series from your real ticket queue rather than your feature list, and delivering clips short enough that a support agent will genuinely paste the link.

Yes, every tutorial ships with burned-in captions plus separate .srt and .vtt files and a plain-text transcript. The sidecar files make the spoken content indexable and accessible, and they are what platform chapter and key-moment features read. The transcript is deliberately supplied in plain text so it can be pasted into the matching help centre article — one production then serves both the video and the written documentation.

Each step is kept as a separate capture inside the delivered project, so replacing one screen is a small re-record rather than a new production. Tell us at the brief stage if a redesign is coming — where a product is mid-change we build the walkthrough around abstracted screens that stay accurate across releases. Because you own the source files, your own team can also swap a screen without coming back to us.

A demo or seeded account is by far the best input, because a tutorial has to show the real interface at its real pace and with plausible data in it. Clean screen recordings at 1080p or higher work when access is not possible, though they limit our ability to re-record a step later. We mask account names, emails, API keys, and any customer data before delivery, and credentials you share are stored in a password manager and revoked at project close.

Fixed-price packages run 3 to 14 days for the entire kit — Solo Launch, which includes a tutorial, is a 5-day turnaround. A custom-scoped tutorial library outside the package ladder runs 7 to 10 days. If you are producing tutorials continuously as features ship, the monthly retainer is usually the better fit: individual requests average about 48 hours each, handled one at a time from a queue you control.