GTM KPI Readout
Turn your raw GTM KPIs into an exec readout that explains the why — pairing pipeline, conversion, and win-rate numbers with the market signals behind them.
GTM KPIs with the why attached — market cooling or execution gap?
Win rate down 5pts. HG: category
demand flat, a competitor gaining.
| KPI move | Likely why |
|---|---|
| Pipeline -8% | Category demand flat (HG) |
| Win rate -5pt | Competitor gaining (HG) |
| CAC +12% | Execution - investigate |
Overview
Take a pasted set of GTM KPIs and produce an executive readout that interprets them — pairing the numbers (pipeline, conversion, win rate, CAC) with HG market context (category demand trend, competitive pressure) to explain not just what moved but why — with clear labeling of user-supplied vs. HG-sourced inputs.
Use cases
KPIs that explain themselves
An exec doesn't need another dashboard; they need to know why the number moved. Pairing each KPI with market context separates market headwinds from execution gaps.
Point the response at the real cause
If win rate fell because a competitor is gaining, the fix is competitive enablement, not pipeline volume. The market-grounded why points leadership at the actual lever.
View workflow prompt
# GTM KPI Readout
## Parameters
- `{{gtm_kpis}}` *(required)* — Pasted GTM KPIs for the period (pipeline, conversion rates, win rate, CAC, etc.). Example: `New pipeline $30M (-8% QoQ), win rate 22% (down from 27%), CAC up 12%`
- `{{category}}` *(required)* — Your category, for market context. Example: `observability`
## Purpose
Interpret {{gtm_kpis}} for an exec audience by pairing each KPI move with {{category}} market context from HG — so the readout explains WHY win rate or pipeline moved (market cooling? competitive pressure?), not just that it did. Label user-supplied vs. HG-sourced inputs.
## Process
1. **Lay out the KPIs** — restate {{gtm_kpis}} with the QoQ/YoY moves (user-supplied; labeled).
2. **Market demand context** — `intent_category` + `list_intent_topics` for the {{category}} — is overall demand up or down (explains pipeline moves)?
3. **Competitive pressure** — `company_technographic` + `get_product_reviews` for whether competitors are gaining (explains win-rate moves).
4. **Pair the why** — for each notable KPI move, offer the most likely market-grounded explanation, distinguishing market factors from execution factors.
5. **Readout** — exec narrative: the headline, the why behind each move, and the one thing to act on.
## Output Format
Markdown with:
- `# GTM KPI Readout — {{category}}`
- `## KPI Movement` (your numbers, labeled)
- `## Market Context` (demand + competitive, cited)
- `## The Why` (market vs. execution per KPI)
- `## Act On` (the one priority)
- `## Citations`
## Quality Checklist
- User-supplied KPIs labeled distinct from HG market signals
- Each 'why' distinguishes market factors from execution
- Market context cites HG tools
- The readout commits to one priority, not a list