Key takeaways
- A solutions engineer records 10 to 20 core flows once during setup.
- Each step keeps its selector, a screenshot and narration notes.
- Replay is deterministic, with fallback selectors when the page shifts slightly.
- Import a Playwright or Chrome DevTools recording, or let Claude Code draft flows; or click through it with the TalkDemo Recorder for Chrome.
Why recorded demo flows beat improvising
An AI that clicks around a product it has never seen is slow and sometimes wrong. A path someone recorded is fast and predictable. TalkDemo uses both, in that order: flows for the parts of the demo that matter most, and live clicks only for questions no flow covers.
Flows also keep the story yours. The narration notes on each step carry the point your best AE makes on that screen.
Recording a flow
- 1Name the flow after the buyer's goal, for example "send a payment reminder".
- 2Record the path once: import a Playwright or Chrome DevTools recording, let Claude Code draft it, or click through it with the TalkDemo Recorder for Chrome. Each step saves the element and the page address.
- 3Add a sentence of narration per step and the questions buyers usually ask there.
- 4Replay it in the test console and fix any step that lands in the wrong place.
Keeping flows healthy after releases
Product teams ship, and recorded steps can break. Every replay in a real demo is counted: when a flow fails at the same step three replays in a row, it is marked broken and your admins get an alert. Automatic re-scans when you deploy, self-healing steps and flows proposed from a crawl of your product are on the roadmap.