---
name: hotspot-dropoff-analyzer
description: Finds exactly where viewers abandon a Supademo demo using step-level hotspot performance, diagnoses why, and recommends fixes. Use when a demo gets traffic but completion is low.
---

# Hotspot Drop-off Analyzer

Traffic isn't the problem — step 6 is. This skill finds the leak and tells you how to plug it.

## Prerequisites

- Supademo MCP connected
- A demo with meaningful traffic (drop-off analysis on 12 views is astrology)

## Workflow

1. **Pull step-level data.** `get_demo_hotspot_performance` for per-hotspot engagement; `get_demo_sessions` for where sessions actually end.
2. **Build the funnel.** Viewers remaining at each step, step 1 → end. Identify the steepest single-step drop and any slow bleed.
3. **Diagnose the drop step.** Pull `get_demo` and inspect the offending step against the usual suspects:
   - **Too much text** — annotation over ~40 words
   - **Unclear next action** — hotspot placed on ambiguous UI, or multiple competing hotspots
   - **Context switch** — the demo jumps screens without explanation
   - **Premature ask** — a form or CTA before the viewer has seen value
   - **Boring stretch** — three consecutive setup/config steps
4. **Check the device split.** `get_device_analytics` — if mobile viewers drop 3× faster, the fix is a mobile-friendly variant, not copy edits.
5. **Recommend, tied to actions:**
   | Step | Drop | Diagnosis | Fix | Tool |
   Fixes map to `update_steps`, `update_hotspots`, `reorder_steps`, `delete_steps`, or `update_chapters`.
6. **Set up the before/after.** Note current completion so the fix can be measured next period.

## Guardrails

- Correlate, don't assume: a drop at the final CTA step is often success (they clicked through), not abandonment. Check CTA clicks before calling it a leak.
- Apply fixes only on approval; re-measure before declaring victory.