Template · Demo flow (branching)
Demo flow template.
A stop-by-stop flow for one demo that serves two roles — a shared opening, a branch at stop two, two short paths, a shared close — with the copy for the branch prompt.
Use when: When two audiences genuinely need different screens — ops and finance, admin and member, buyer and evaluator — and one linear demo would bore one of them.
The one line
What this demo proves
Each audience sees only the four screens that matter to them, and the analytics show which audience visits.
Stop by stop
7 stops
| # | Screen | Action (hotspot) | Tooltip |
|---|---|---|---|
| 01 | Overview dashboard | Click 'Show me' | One product, two jobs. Pick yours on the next screen. |
| 02 | Branch prompt | Choose 'I run operations' or 'I run finance' | Which describes you? You'll see four screens, not twelve. |
| 03 | Ops path · the queue | Click the oldest item | Ops: the queue sorted by age, nothing hidden in a report. |
| 04 | Ops path · the item | Click Resolve | Resolve from the item — the context is already here. |
| 05 | Finance path · the ledger | Click 'Unreconciled' | Finance: what's unreconciled, today, without an export. |
| 06 | Finance path · the entry | Click Match | Match from the entry; the candidates are already listed. |
| 07 | Shared close · weekly summary | Click 'Get this for my team' | Both paths end here: a Monday summary for your team. Set it up free. |
Copy
The lines that do the work
- Branch prompt
- Which describes you? Ops · Finance — you'll see four screens, not twelve.
- Shared CTA
- Get this for your team — free, no card.
Take it with you
The template as text
DEMO FLOW (BRANCHING) — TEMPLATE
Outcome: Each audience sees only the four screens that matter to them, and the analytics show which audience visits.
Use when: When two audiences genuinely need different screens — ops and finance, admin and member, buyer and evaluator — and one linear demo would bore one of them.
01. Screen: Overview dashboard
Action: Click 'Show me'
Tooltip: One product, two jobs. Pick yours on the next screen.
02. Screen: Branch prompt
Action: Choose 'I run operations' or 'I run finance'
Tooltip: Which describes you? You'll see four screens, not twelve.
03. Screen: Ops path · the queue
Action: Click the oldest item
Tooltip: Ops: the queue sorted by age, nothing hidden in a report.
04. Screen: Ops path · the item
Action: Click Resolve
Tooltip: Resolve from the item — the context is already here.
05. Screen: Finance path · the ledger
Action: Click 'Unreconciled'
Tooltip: Finance: what's unreconciled, today, without an export.
06. Screen: Finance path · the entry
Action: Click Match
Tooltip: Match from the entry; the candidates are already listed.
07. Screen: Shared close · weekly summary
Action: Click 'Get this for my team'
Tooltip: Both paths end here: a Monday summary for your team. Set it up free.
Branch prompt: Which describes you? Ops · Finance — you'll see four screens, not twelve.
Shared CTA: Get this for your team — free, no card.
Measure: Branch choice split — which audience actually visits; Completion per branch; Where each branch parks; CTA clicks per branchCreates a lane with one stop per row above — the screen as the title, the action and tooltip as the body — then opens the editor so you can capture the real screens.
The format
What the finished lane feels like
Measure
What to watch after publishing
- Branch choice split — which audience actually visits
- Completion per branch
- Where each branch parks
- CTA clicks per branch
FAQ
Questions
Can branches rejoin?
Yes — point both paths' last stop at the same closing stop, as this flow does at stop 7.
What if three audiences?
Three options at the branch, three short paths, one close. Beyond three, make separate lanes and a hub page.
Related
More templates
Comparing tools?