The demo you give every week, recorded once

If you give the same walkthrough more than about twice a month, record it once and send the recording. The live version is worse than you think it is, for a reason that has nothing to do with your ability: the fifteenth time you say something, you skip the part you have stopped noticing, and that part is usually the part the listener needed.

This is for founders, sales and support people, and anyone whose calendar quietly filled up with the same forty minutes repeated at different strangers.

What the live demo really costs

Book an hour and you spend ten minutes waiting for people to join, five apologising for a screen share, and then a version of the walkthrough shaped by whatever happened in the first two minutes. Some prospects get the good one. Somebody gets the one where the test account was in a strange state. Nobody gets the same one.

Then it evaporates. Nothing is left to forward to the person who decides, which is the person who was not on the call.

A recording inverts all of that. Every viewer gets the best version you have ever given, it forwards itself around a company without you, and it turns the live call into a conversation about their situation rather than a performance you have given fifteen times.

Script the spine, improvise the rest

A fully scripted demo sounds like an advert and a fully unscripted one runs long and buries the point. Write the parts that must be exact and leave the rest loose.

Exact: the opening twenty seconds, every number, every claim about what the product does, and the sentence at the end that says what happens next. Loose: the connective narration while you move between screens, where the small imperfections keep it human.

Open by naming the problem rather than the product. "This is for teams who are tracking releases in a spreadsheet and losing track of who changed what" tells the right viewer to keep watching and lets the wrong one leave, which is a favour to both of you.

Show the real thing

Record the actual product, not a set of slides about it. A prospect is trying to work out what using it would feel like on a Tuesday, and a screenshot in a deck answers a different question.

Prepare the account first. Realistic data with plausible names, no lorem ipsum, nothing half-configured, and no notification from your own team arriving mid-take. Close everything else, because a stray tab is the detail people remember.

Then draw on it while you talk. Circling the field that matters, or putting an arrow on the button you are about to press, does in one second what a sentence of narration does badly. It also solves the pointing problem, where you say "up here in the corner" and four people look at four corners.

Where the script goes

The awkward part of a recorded walkthrough is that you are reading, clicking and talking at once. If the script lives in a document behind the window you are sharing, every glance at it is a click away from what you are doing, and the recording catches the pause.

Keep the words at the top of the screen, near the lens, over the top of what you are demonstrating, and moving at the pace you are speaking rather than on a timer. Then a walkthrough is one job again. There is more on the mechanics of that in reading a script while looking at the camera.

Keep it short and keep it current

• Aim for five to eight minutes. A forty-minute recording is a meeting nobody agreed to attend.
• Split by question rather than by feature. "How do I get my data in" travels further than "Integrations".
• Say the date or the version out loud if the interface changes often, so an old recording admits it is old.
• Re-record the piece that went stale, which is cheap when the pieces are short and miserable when the demo is one long file.

The awkward benefit

Recording the demo will show you that part of it does not make sense. You will hear yourself explain a screen apologetically, or need forty seconds to justify where a button lives. On a live call that gets smoothed over by tone. On a recording it just sits there.

That is worth more than the recording. The feedback was always in the demo and the live version kept hiding it.

LensFloat records this shape directly. Share the window, keep the script at the lens where it stays out of the recording, draw over the part that matters while you talk, and finish with a file you can send. If the honest problem is that you keep abandoning takes halfway, the sixth take is the one to read first.