Walkthrough Videos for Business Software: The Complete Guide (From 60 Real Recordings)

We looked at every recording uploaded to Nook over the last six weeks to see what people are really making. The answer surprised us a little. The glossy launch video gets the attention, but what most people record is a quiet one to three minutes of one feature in a business application: approving a duty trip request, creating an accounting transaction and attaching the documents, marking attendance for a class, exporting a tender report, checking a vehicle's history, configuring products and carriers in an insurance back office.

The person recording is usually the one who built the tool, runs it, or has to teach it. The viewer is a customer, a colleague, or a new hire who needs to do that one thing today. About one recording in six is in Spanish or Portuguese. The typical recording is 1 to 3 minutes long and turns into a walkthrough of 5 to 20 steps.

This guide is for that person. It covers what the videos are for, how to record one that works the first time, how to narrate it, what to do with the written guide, how to share it, and how to keep it alive when the software changes. It is long on purpose; skip to the part you need.

#Who makes these videos, and for whom

From the recordings themselves, the same handful of situations come up again and again:

• A product or ops person at a B2B software company records a feature so support can send a link instead of a paragraph. The viewer is a customer's admin.
• The person who implemented a system for a client (an ERP, a CRM, a booking tool, a custom portal) records how it was set up, so the client can run it without calling.
• An internal tools team inside a larger company records how to file a request, log hours, or run a report in a system most staff touch once a month and forget.
• A trainer or manager records a process for new hires: the screen, the order of clicks, what to check before pressing save.
• A founder records the one feature a prospect asked about after a demo call, instead of booking another call.

What they have in common: the viewer is not browsing. They have a task, they are a little stuck, and they want to be unstuck in under three minutes. That shapes everything below.

#The seven jobs a walkthrough video does

Each job wants a slightly different recording. Pick yours before you press record.

#1. The help-centre answer

"How do I export the orders report?" is a ticket that arrives every week. A 90-second walkthrough, embedded in the help article next to the written steps, answers it for everyone who searches, not just the person who asked.

• Record: start on the page where the report lives, not the login screen. End on the exported file.
• Narrate: say what the export is for and what the options mean. "Pick the date range first; the status filter applies to that range."
• Where it goes: the help article, and the saved reply your support team pastes into tickets. See help centre videos.

#2. Onboarding staff to an internal tool

New hires meet a dozen systems in their first week. The ones they use rarely are the ones they forget. A walkthrough per process ("file a travel request", "log time against a project") beats a one-off training session they will not remember in March.

• Record: a test account with realistic data. Include the step people get wrong (the approval field, the cost centre).
• Narrate: the why. "Pick the cost centre of the project, not your department, or finance will send it back."
• Where it goes: the onboarding checklist, the intranet page for that process, and the written guide as a PDF for people who prefer reading. See employee training videos.

#3. Announcing a change to existing customers

You redesigned the inventory screen. Customers who learned the old one will open a ticket the morning it ships. A two-minute "what changed and where things moved" walkthrough, sent the day before, cuts that down.

• Record: the new screen, doing the three most common jobs on it. Mention where each thing used to be.
• Narrate: reassure. "Everything you had is still here; the stock levels moved to the top so you don't scroll for them."
• Where it goes: the release email, the in-app announcement, the changelog.

#4. The sales follow-up

A prospect asked "how do carriers get configured?" on the call. Instead of a second call, send a walkthrough of exactly that, with their scenario in the narration.

• Record: a demo account set up to look like the prospect's situation. Keep it under two minutes.
• Narrate: their words. "You mentioned you work with three carriers; here is how each gets its own rate table."
• Where it goes: the follow-up email, with the written guide attached for the people who were not on the call. See sales demo videos.

#5. Handing over a system to a client

You configured the tool. Now the client has to run it. A set of short walkthroughs ("add a product", "process a refund", "run month-end") plus the written guides is the handover document people actually use.

• Record: their real configuration, with the data anonymised or a staging copy.
• Narrate: the order things must happen in, and what to check before each step.
• Where it goes: a shared page per client with the videos and guides, linked from the handover email. See client handover videos.

#6. The SOP that gets followed

Written procedures exist; they are rarely read. A walkthrough shows the procedure being done, and the written guide generated from it becomes the SOP, with a screenshot per step.

• Record: the whole procedure once, without skipping the boring checks. The boring checks are the point.
• Narrate: the rule and the reason. "Reconcile before you post, because a posted entry can't be edited."
• Where it goes: the quality system, the audit folder, the team's shared drive. See SOP videos and how to write an SOP from a screen recording.

#7. The same video in another language

A sixth of the recordings we see are in Spanish or Portuguese, and many English ones serve teams who read English but think in something else. One recording can become a walkthrough with a native voice and captions in each language, with the same guide translated.

• Record: once, in whichever language you speak. The narration can be rewritten in another.
• Where it goes: the same help article, with a language switch. See Nook en español and Nook em português.

#Recording: get it right the first time

Most problems in walkthrough videos are recording problems, and no amount of editing fixes them. A short checklist:

One feature per video. If you have to say "and now let's look at a different thing," stop and make a second video. People search for one job; give them one job.

Start on the right screen. Not the login page, not the dashboard, unless the video is about getting to the feature. Open the feature, take a breath, press record.

Use a test account with realistic data. Empty tables teach nothing; real customer data is a privacy problem. A demo account with twenty plausible records is the sweet spot. If you must use a real account, Nook flags emails, phone numbers and card numbers on screen for blurring, and you can mark any other region yourself; check every flag before sharing.

Record at 1080p, or the full width of the window. Business software is dense. A 720p recording of a table with twelve columns is unreadable once it is in a help article.

Keep the mouse honest. Move deliberately to the control, pause, click. Nook zooms on each click; fast, wandering mouse movement makes the zoom chase you.

Talk, or don't. If you narrate while recording, the script comes from what you said, tidied up. If you stay silent, Nook writes the script from what is on screen; you then edit the lines. Both work. Half-mumbled narration is the one thing that doesn't: speak in full sentences or not at all.

Length: 60 to 180 seconds. Under a minute usually means a step was skipped. Over three minutes usually means two features. Dead time (loading spinners, you reading the screen) is cut automatically, so don't rush.

Device tips. Mac: ⌘ Shift 5, record a selected portion. Windows: the Snipping Tool's video mode. Web apps on a phone: the built-in screen recorder, portrait is fine. Loom or Zoom recordings: download the MP4 and upload it; no need to re-record.

#Narration: the three-part line

The difference between a walkthrough people finish and one they abandon is almost always the narration. The weak kind describes the click: "Click the Export button." The viewer can see that. The strong kind gives the viewer something they could not see.

A line that works has up to three parts:

1. Why this step exists. "To send the invoice, it needs a payment method on the customer."
2. Where the control is, in words. "Open the customer, then the Billing tab."
3. What to check before moving on. "Make sure the status reads Verified, or the invoice will bounce."

Not every line needs all three; most need the why. Here is the same step, both ways:

Weak: Click on the Carriers tab. Then click Add Carrier. Fill in the form and click Save.

Strong: Each carrier you work with gets its own rate table, so add them here before you quote. The name is what your agents will see in the dropdown, so use the one they know. Save, and it's available on the next quote.

Rules of thumb:

• One sentence per click, two at most. Long lines mean the footage freezes while the voice catches up.
• Name things as they appear on screen. If the button says "Post", don't say "submit".
• Say the consequence of getting it wrong, once. "If you pick the wrong period, the report will be empty" saves a ticket.
• No throat-clearing. "In this video we are going to take a look at how you can…" costs eight seconds and tells nobody anything. Start with the first why.
• End with the result. "The report downloads as a spreadsheet and the export is logged under Activity." The viewer knows they are done.

Nook writes the first draft of each line from your speech or the screen; the editor lets you rewrite any line, rewrite all of them in a different tone, or remove a step. The voice is re-read for the lines you change, nothing else.

#The written guide is not optional

Roughly half of the people who open a help article will not play a video. They are in a meeting, on a slow connection, or they just prefer reading. The walkthrough's written guide, a heading, a sentence and a screenshot per step, serves them.

A few things that make the guide useful rather than a transcript:

• Headings are actions. "Add the carrier's rate table", not "Step 4".
• The screenshot shows the click. Nook captures the frame at each click and marks the control; crop to the part of the screen that matters when the page is huge.
• Export in the format your tools want. PDF for a handover or an audit folder, Word for a team that edits SOPs, Markdown for a help centre or a wiki that takes it.
• Keep the guide next to the video. Same page, video on top, steps below. People who start the video and get lost drop down to the step they need.

#Captions, because most business video plays muted

Open-plan offices, shared screens, a phone on the train. A walkthrough without captions is a silent film to a good share of its viewers. Captions also make the video searchable and are the simplest accessibility step you can take. Keep them on, keep them to one line where possible, and check names and product terms in the editor, since those are where automatic captions go wrong.

#Privacy, before you share

Business software is full of other people's data. Before a walkthrough goes to anyone outside the team:

• Use a test account or staging environment where you can.
• Review every blur Nook suggests and add your own where needed (customer names in a table, an address on a form, the API key in a settings page).
• Watch the whole video once at full size. Blurs are per region; a scroll can reveal a new row.
• Set the share link to private, password-protected or expiring if the content is sensitive, and prefer a link you can revoke over an MP4 you can't.

#Where to put the video so it gets watched

The best walkthrough in the world does nothing in a folder. Put it where the question is asked:

• The help article for that feature, video first, steps below.
• The saved reply your support team uses for that question, as a link.
• Inside the product, a "How does this work?" link next to the feature that opens the walkthrough.
• The onboarding checklist, one link per process.
• The release email and changelog for changes.
• Slack, Teams or WhatsApp for teams who live there. In Latin America, a WhatsApp link to a Spanish or Portuguese walkthrough is how most of these get watched.
• A QR code in the printed SOP for shop-floor and warehouse processes.

Embedding works anywhere that takes an iframe; the share page has chapters, so a viewer can jump to the step they need, and a button at the end if you want them to go somewhere next.

#Keeping walkthroughs current when the software changes

This is where most video documentation dies. The UI changes, the video shows the old button, and someone decides videos are more trouble than they are worth. Three habits keep that from happening:

1. One feature per video (again). A small change invalidates one short video, not a 20-minute tour.
2. Edit the line, not the recording. When a label changes, edit that narration line and re-voice it in a minute. When a step moves, remove the step or re-record just the feature; the other videos are untouched.
3. Name and date them. "Export orders report, v2 (Nov 2026)". When support sends a link, they know which version they are sending.

Keep the recordings. A re-record is a 90-second job when the original recording's setup (account, data, window size) is written down with it.

#Measuring whether it works

You don't need an analytics project. Three numbers tell you most of it:

• Watch-through. If most viewers stop at the same step, the narration there is confusing or the step is wrong. Fix that one step.
• Tickets on that topic, before and after the article got its video. This is the number your manager wants.
• Plays from inside the product versus from the help centre. If nobody finds it from the product, the link isn't where the question is asked.

Nook's share page counts views and shows where viewers drop off, per video.

#The ten mistakes we see most

1. Starting at the login page when the video is about a report.
2. Narrating the click ("click save") instead of the reason.
3. Two or three features in one video, so nobody finds the part they need.
4. Recording at 720p; the table is unreadable.
5. Real customer data on screen, shared externally.
6. No captions, so the muted majority gets nothing.
7. A five-second intro card before anything happens. The viewer is stuck; get to it.
8. No written guide, so the readers bounce.
9. Burying the video on a page nobody visits instead of the help article for that feature.
10. Never updating it, then blaming video.

#Three script templates

Fill in the brackets. Each line is one step.

Help-centre how-to (60 to 120 s)

[Feature] lets you [outcome]. Here's how. Open [screen], then [tab or section]. [Why this field matters]. Enter [value]; [what to check]. [Why the next step]. Choose [option]. If [condition], pick [other option] instead. Press [button]. [What happens next, where to find the result]. That's it: [result], and you can [follow-on] from here.

Onboarding a process (90 to 180 s)

When you need to [task], it goes through [system]. This takes about [time]. Start from [screen]. You'll need [information] ready: [where to get it]. [Step with the rule]. [Common mistake and consequence]. [Step]. [Who sees this next and what they do with it]. Before you submit, check [the two things that get sent back]. Submit. You'll get [confirmation]; [what to do if it doesn't arrive].

Change announcement (60 to 90 s)

[Screen] has a new layout. Everything you had is still here; here's where it moved. [Most common job] now lives at [place]. [One-line how]. [Second job]: [where, how]. [What's new and why it helps]. [Where to find the old way for the next month, or that it's gone].

#How this works in Nook

Upload the recording (MP4, MOV or WebM; from QuickTime, Zoom, Loom, OBS, a phone). Pick the walkthrough. Nook finds the steps from your clicks, writes a line per step from your speech or from the screen, reads it in a natural voice in your language, zooms on each click, flags private data for blurring, adds captions and chapters, and writes the step guide with a screenshot per step. You check the script, fix any line, and share the link or embed it. The guide exports to PDF, Word or Markdown. When the UI changes, edit the line and re-voice it.

The first video is free, up to three minutes. Plans start at $9 a month for four videos of up to ten minutes each, with no per-seat pricing, so the whole support team can send the links. A worked example of the single-feature case, start to finish, is in how to make a feature walkthrough video, and the training-specific version in how to make a software training video.

#Questions

#The recording has no sound. Can it still become a narrated walkthrough?

Yes. Nook writes the script from what is on screen and the text it can read, and you edit the lines. Tell it what the feature is and who it's for in the box on the upload page, and the first draft is much closer.

#My feature takes eight minutes to show. One video or several?

Several. Split at the points where a viewer could stop and come back: "set up", "daily use", "month end". Link them from one page in order.

#Can one recording become Spanish and Portuguese versions?

Yes: the narration is translated and read by a native voice, captions and the guide follow, from the same recording. Check the product terms in the translated script; those are what automatic translation gets wrong.

#What about a mobile app?

Record the phone's screen with its built-in recorder and upload the file. Portrait recordings are kept at full size.

#How do I update a walkthrough when a button is renamed?

Open the script, edit that line, and update the video. The voice is re-read for that line only. If the step itself moved, remove it or re-record the feature.

#Where should the video live: YouTube or our help centre?

Your help centre, embedded, where the question is asked. YouTube is fine as a second copy if you want it found by search, but a help article with the video and the steps together is what gets a stuck customer unstuck.