---
name: exec-analytics-summary
description: Converts raw Supademo analytics into a leadership-ready narrative — reach, engagement, pipeline influence, and one recommendation. Use for QBRs, board updates, or justifying the demo program's budget.
---

# Exec Analytics Summary

Executives don't want completion rates; they want to know if the demo program is working. This skill translates.

## Prerequisites

- Supademo MCP connected
- The reporting period (quarter, month) and the audience (CMO, board, sales leadership)

## Workflow

1. **Aggregate the period.** `get_demo_analytics` and `get_showcase_analytics` across the library; `get_top_performing_demos` / `get_top_performing_showcases` for standouts.
2. **Compare to the prior period.** Every headline number needs a direction and a delta.
3. **Structure the narrative — five beats, one page:**
   - **Reach** — how many people experienced the product through demos this period
   - **Engagement** — did they actually watch (completion), and where do they lean in (`get_demo_hotspot_performance` on the top demo)
   - **Conversion** — CTA click-throughs; demos that hand off to trials/sales calls
   - **Standouts** — the one demo or showcase that outperformed, and the honest laggard
   - **Recommendation** — one concrete next move (double down, refresh, kill)
4. **Write for the audience.** No tool jargon ("hotspot," "step") — translate to "the pricing section," "the setup walkthrough." Percentages over raw counts unless raw counts impress.

## Output

A one-page summary in markdown, ready to paste into a doc or deck, with an appendix table of per-demo numbers for the detail-oriented.

## Guardrails

- Attribute cautiously: demo views correlate with pipeline, they don't prove causation. Phrase accordingly.
- Flag data gaps honestly (e.g., demos with no UTM discipline can't be traced to campaigns).