Onboarding tours that don't break in three weeks
CaptureBeam re-runs the same script against your new UI and emits a new MP4. The cursor finds the right buttons through a layered NL → cached selector → visual anchor recovery chain. Schedule a nightly re-render and stop maintaining tours.
Product, growth, customer success
You spent two days recording an onboarding tour with cursor highlights and crisp narration. It launched. It got engagement. Three weeks later you shipped a redesigned dashboard and the tour stopped pointing at the right buttons. You decided you'd update it 'next sprint.' That was eight weeks ago.
The problem
You record a polished onboarding tour. Three weeks later your dashboard ships a new layout and the tour stops making sense. The fix is to record again — and again, and again.
What CaptureBeam does for you
- Author one YAML per tour and check it into your repo
- Schedule a re-render on every main-branch push
- Get a 'needs review' notification when a step misses (visual-anchor recovery diff)
- Embed the latest MP4 with a single signed-URL — never republish stale assets
- Personalize per-customer with token substitution (workspace name, plan tier)
# demos/onboarding-welcome.yaml
title: Welcome to {{workspace.name}}
preset: iris
aspect: "16:9"
steps:
- goto: https://app.example.com/welcome
- click: { role: "button", name: "Start tour" }
caption: "Welcome — let's get you set up"
- click: { role: "tab", name: "Workspace" }
caption: "Configure your workspace first"
- type: { label: "Workspace name", text: "{{workspace.name}}" }
- click: { role: "button", name: "Save" }
- assertVisible: { text: "Workspace saved" }Onboarding tours updated themselves every push to main, instead of every two months by hand.
Ship onboarding demos that don't go stale.
$19.99/mo or $199/yr. Render through the dashboard or via the API — same access either way.