Software tutorial videos that show the exact steps, in your real product.
100+ videos produced for Jotform. 20+ for Knack.
The problem it solves
What this actually fixes.
Support tickets cluster around a handful of screens. Written documentation covers those screens, and users still open a ticket, because reading a numbered list is not the same as watching where the cursor goes. A tutorial video removes the ambiguity. The viewer sees the exact control, in the exact state, in the exact order — and the ticket never gets filed.
Who needs it
Who this is for.
- Support teams watching the same few screens generate most of their ticket volume.
- Documentation and technical writing teams who need video beside articles they already maintain.
- Customer success managers who repeat the same walkthrough on every call.
- Product teams shipping a feature complex enough that the release note is not enough.
- No-code and developer-tool companies whose users learn by copying what they see.
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 articles, embedded beside the written steps.
In-app tooltips, empty states, and contextual help panels.
Your product's YouTube channel, where search traffic finds it directly.
Support replies, where an agent links a video instead of retyping the steps.
Partner and reseller enablement portals.
Community forums and knowledge bases your users search first.
Real examples
Work produced in this format.
Knack · Create an Inventory Management System with a Text Prompt
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
- 2–5 minutes per task; 6–10 minutes for workflows that span several screens.
- Typical delivery time
- About 2–3 weeks per video from an approved script; a 10-video series in 3–4 weeks when episodes run in parallel.
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.
Software Tutorial Videos 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 |
|---|---|
| Number of videos | a series shares its script template, brand assets, and setup, so cost per video falls sharply after the first three. |
| Runtime per video | longer tasks mean a longer script, a longer recording session, and more edit passes. |
| Interface complexity | dense admin screens need more zooms, more callouts, and slower pacing than a simple linear flow. |
| Environment setup | recording is faster when a seeded sandbox exists. Building demo data ourselves adds time. |
| Motion graphics | animated diagrams to explain a concept before the clicks cost more than a straight screen recording. |
| Languages | each additional voiceover language is priced per project; subtitle-only tracks cost less. |
| Update commitments | an ongoing plan that re-cuts videos when your UI changes is priced monthly rather than per video. |
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 long should a software tutorial video be?
Between two and five minutes for a single task. The limit is set by the task, not the clock: one video should teach one job, from the screen the user starts on to the result they were after. Workflows that genuinely span several screens run six to ten minutes, and anything longer is usually two videos.
What kind of account access do you need to record?
A sandbox, demo tenant, or staging environment with realistic seeded data is ideal. A read-only or limited-permission account works for most tutorials. If access cannot be granted at all, we can direct a recording session with someone on your team driving and capture from that instead.
How do you keep customer data off the screen?
We record against demo data rather than production wherever possible. When a real environment is unavoidable, anything identifying is blurred or replaced in the edit, and every frame is reviewed before delivery. Credentials, account numbers, and email addresses are treated as redaction targets by default.
Do you write the script, or do we?
We write it. We work from your existing documentation, a walkthrough of the product, and whatever your support team knows about where users get stuck. You review and approve the script before recording, which is the cheapest point to fix anything wrong.
What happens when a step changes after the video is live?
Videos are edited in segments, so a changed screen means re-recording and re-cutting that segment rather than rebuilding the video. The voiceover for that section is re-recorded to match. Ongoing plans include a set number of these updates each month.
Can you cover a whole feature area as a series?
Yes, and it is the cheaper way to buy. We map the feature area into a video list first, agree the order and the length of each, then produce them against a shared template so the series looks consistent and later additions still match.
Also produced here
The other formats.
Start with the Software Tutorial Videos 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.