A video documentation library that stays correct as your product changes.
100+ videos produced for Jotform. 20+ for Knack.
The problem it solves
What this actually fixes.
Help centers grow article by article, and the hardest tasks are the ones written text handles worst: anything spatial, anything with a dozen steps, anything where one missed setting breaks the result. Video covers those well. But a video library rots faster than an article — one interface change and half of it is wrong. Documentation built as a maintained library treats updating as part of the job rather than an emergency.
Who needs it
Who this is for.
- Documentation and knowledge-base teams whose articles already exist and need a video layer.
- Support organisations measuring deflection and ticket volume per article.
- Products that ship UI changes often enough that a one-off video batch would go stale.
- Enterprise software teams who have to document configuration and permissions accurately.
- Companies consolidating scattered internal recordings into something maintained.
Where they get used
Every video is made for a placement, not a folder.
We ask where a video will be embedded before we script it, because the placement decides the length, the aspect ratio, and whether it has to work with the sound off.
Help center and knowledge-base articles, embedded above or beside the text.
In-product help panels and contextual documentation drawers.
Your product's YouTube channel, where the search traffic already goes.
Support macros and canned replies.
Internal enablement for support agents and new hires.
Customer training portals and certification courses.
Real examples
Work produced in this format.
Published examples in this format are being added. The client work in our portfolio was produced by the same team, to the same standard, and we can send relevant examples on request.
What’s included
Everything in the list below is standard.
Nothing here is an upsell. If a deliverable is quoted separately, it is named as an extra on the estimate before you agree to anything.
Length and delivery
How long, and how soon.
- Typical length
- 90 seconds to 4 minutes per article, quoted in batches of ten.
- Typical delivery time
- 3–4 weeks for the first batch of ten, then a monthly cadence.
The clock starts when the script is approved and a recording environment is available. Those two things are what usually move a schedule, so we agree both before quoting a date.
Every project, the same way
The parts that never change.
Four stages, and you are needed for two: your team scopes the list and approves the scripts, then recording, editing, voiceover and revisions happen without your calendar. Human-recorded English narration is the default, synthetic voice is available where re-cuts are frequent, and every video ships with captions, an SRT and a VTT. Two revision rounds are included and you own the finished files outright.
What affects the price
The variables that move a quote.
Video Documentation is quoted per project, because the same runtime can mean very different amounts of work. These are the factors that change the number.
| Factor | How it moves the price |
|---|---|
| Batch size | libraries are quoted in batches, and the per-video cost falls as the batch grows. |
| Coverage depth | documenting every setting on a screen costs more than documenting the path most users take. |
| Product change rate | a fast-moving interface needs a larger maintenance allowance than a stable one. |
| Maintenance plan | a monthly retainer covering a set number of re-cuts is priced separately from the build. |
| Transcripts and chapters | included as standard, but full verbatim transcripts for accessibility compliance add a review pass. |
| Hosting and delivery | files delivered for your own player cost the same as YouTube-ready uploads; the difference is in the encode set. |
| Languages | subtitle tracks scale cheaply across a library; voiceover languages are quoted per batch. |
Ongoing work runs on monthly plans priced in production credits — see monthly SaaS video production plans. For a single video, send the product and the problem and you get back a video list, a recommended length for each, and a fixed price — not a discovery call. Request a fixed quote.
How many videos should a documentation library start with?
Start with the ten to twenty-five articles that drive the most tickets, not the full help center. That batch tells you what the format is worth in your product before you commit to covering everything, and it covers the topics with the highest support cost first.
How do you keep the library current when the UI changes?
Scripts are written in modular segments and project files are kept segmented to match, so a changed screen means re-recording one segment and re-cutting it in. Version numbers stay on the files, so your team can always tell which build of the product a video reflects.
Should every help article have a video?
No. Video earns its place on tasks that are spatial, multi-step, or easy to get wrong. Reference material — field definitions, limits, API parameters — is faster to read and much cheaper to maintain as text. A library that covers everything is mostly a maintenance liability.
Where do the videos get hosted?
Wherever you already host. We deliver finished files, captions, and transcripts in the encodes your platform needs, whether that is YouTube, Wistia, Vimeo, a help-center player, or your own CDN. We do not host the library ourselves, so nothing is tied to us.
Can the videos be embedded inside the product itself?
Yes. In-product placements need shorter, silent-safe cuts that work in a narrow panel next to the screen they describe. We cut those alongside the full versions, from the same recording, rather than producing them twice.
Do you supply transcripts and chapter markers?
Both, as standard. Transcripts matter more than they look: they are the indexable text that makes a video page rank and lets an assistant quote it, and they give users who cannot watch a way through the same content.
Also produced here
The other formats.
Start with the Video Documentation you need first.
Tell us the product and what your users get stuck on. You get back a video list, a recommended length for each, and what it costs.
Produced by the team behind SaaS Master, reviewing and demonstrating software publicly since 2019.