---
name: scale-exec-dashboard
description: Scores the pilot against the Module 1 charter, tracks stage-to-stage conversion and the two headline metrics, and produces a three-layer dashboard with an expand / adjust / stop recommendation. Use when the user says "did the pilot work", "build the dashboard", "results", "should we scale this", "what do I show the exec team", or when a pilot reaches its midpoint or end.
---

# scale-exec-dashboard

Produce `artifacts/scale-dashboard.md` and update `context/metrics.md`. Judge against the charter, never against the demo.

## Preflight (every run)
1. Confirm `GTM-AI-OS/` is accessible. If not: "I need access to your GTM-AI-OS folder. Select it in Cowork's folder picker, or run `os-install` from the core plugin." Stop until it is.
2. Read `CLAUDE.md`, `INDEX.md`, and the last 20 lines of `signals/log.md`.
3. Check the prerequisites below. For anything missing, ask the cold-start questions and offer: (a) run the earlier skill now, or (b) fast path: answer the questions and this skill writes a minimal version of the missing artifact marked `status: draft (fast path)`.
4. On finish, update the artifact row in `INDEX.md` and append one line to `signals/log.md`: `<date> | <skill> | <produced> | <human changed> | <open question>`.

## Prerequisites
- `artifacts/scale-charter.md` and `artifacts/scale-pilot.md` with success criteria and baselines.
Cold-start: "What did you set out to move, from what to what, and what happened?" Write it as a fast-path charter and pilot summary, mark every number Inferred, continue.

## Step 1: Pull the numbers
For each success criterion: baseline, current, target. From `~~crm` where connected (stage conversion, pipeline by motion, retention and expansion), else from the user. Update `context/metrics.md`.

## Step 2: Diagnose by stage
Stage-to-stage conversion tells you which thing is wrong: early-stage drop = ICP or signal problem (send back to Module 2); late-stage drop = motion or skill problem (Module 3 or enablement); post-sale drop = product or onboarding.

## Step 3: The two numbers
Restate Sourced Qualified Pipeline and Retained-and-Expanded Revenue, baseline and current. Say plainly whether the pilot moved either, directly or through a driving KPI.

## Step 4: Three layers
- Executive: impact and adoption, three numbers, one sentence
- Management: driving KPIs and pilot criteria with red / yellow / green
- Technical: system health, data quality trend, guardrail incidents, reversal-trigger status

## Step 5: The call
Recommend one: Expand (scale to a defined next group, not the whole org), Adjust (what specifically, and re-run the window), Stop (and what was learned). Scaling too fast is the most common post-pilot mistake; say so if the user wants to go org-wide.

## Step 6: Write
Write the dashboard with the CEO slide at the top. Update `INDEX.md`.

## Hand off
Say: "Now set the rhythm that keeps this alive. Run `scale-operating-calendar`."