How to demo an automation so it sells (recording checklist)

A demo sells an automation when a business owner sees, in under a minute, a realistic input arrive, the result appear where they would look for it, an unusual case go to a person, and the workflow they could open themselves. Record it rather than performing it live, narrate one sentence per shot, and use real-shaped data with personal details replaced. That recording, attached to the project on your profile, does more for the next buyer than any deck, and it is the evidence that moves a project up the proof ladder.

Why do most demos fall flat?

They show the builder's screen: nodes, prompts, logs. The buyer sees complexity and worries about who understands it. A selling demo shows the business's screens: the WhatsApp thread, the CRM, the calendar. The automation is invisible; its effects are obvious.

The shot list

Shot 1: the input (0–10 seconds)

Fill the website form, or send the WhatsApp message, exactly as a customer would, with realistic content. "Hi, I'd like to book a consultation next week, mornings are best." Say what you're doing in one sentence.

Shot 2: the result (10–30 seconds)

Cut to where the owner would look: the WhatsApp reply arriving on the business number, then the CRM record appearing with the source and the customer's preference captured. Point at the timestamp. This is the shot the buyer remembers.

Shot 3: the exception (30–45 seconds)

Send the unusual input: "My tooth is killing me, can anyone see me today?" Show it bypassing the automation and landing on the front desk's phone with a flag. Say: "Anything about pain or emergencies goes straight to a person; the automation never guesses."

Shot 4: the owner's view (45–60 seconds)

Open the workflow in Make or n8n for ten seconds. Hover over the message template. Say: "This is the text your office manager can change herself." Close it. End on the CRM record.

Narration rules

• One sentence per shot, in the business's words, no tool names except in shot 4.
• Say what the buyer is looking at before it happens: "Watch the reply arrive."
• No "as you can see", no "basically", no apologies for the test data.
• End with the number if you have one: "In the pilot this took reply time from hours to under a minute."

Preparation checklist

Where the demo goes

Attach it to the project on your AgeBridge profile as evidence. Send it as the second message after a discovery call, before the brief. Play it at the start of a proposal call. Cut a 20-second version for LinkedIn and short-form content with the number as the caption.

Mistakes that cost the sale

• Showing the builder's screen first.
• Fake data that reads fake ("John Doe, test test").
• Skipping the exception shot; buyers imagine the worst case if you don't show it handled.
• Running over two minutes.
• Explaining the model instead of the outcome.

Best fit and not a good fit

Best fit: any automation with a visible input and output, which is nearly all of them. Not a good fit: internal data pipelines with nothing to see; for those, demo the before-and-after of the sheet or dashboard they feed.

What to do this week

Record the 60-second demo for your best project using the shot list. Attach it to the project. Send it to the last person who asked what you do.