Most KPI commentary repeats the chart in prose. A good prompt extracts what changed, why, and what to do — not “revenue grew 5%”.
Who this is for
Operators preparing weekly / monthly numbers, founders writing investor updates, BizOps adding context to dashboards.
When not to use these prompts
Don’t use these without verified numbers. Don’t use them when there’s no actual change worth commentary.
Prompt anatomy / structure formula
Every prompt should carry six elements:
- Role: who AI plays — analyst, chief of staff, manager.
- Context: team / org / project / data scope.
- Goal: one deliverable — table, doc, talking points, plan.
- Constraints: word count, must-include fields, audience seniority.
- Tone: confident, neutral, factual — depends on audience.
- Examples: 1-2 samples of prior work to anchor format.
Best for
- Weekly metrics commentary
- Monthly business review commentary
- Investor update narrative
- Anomaly callouts
- Trend vs noise framing
12 copy-ready prompt templates
1. What-changed-why-what-to-do
KPI: `{kpi}` moved from `{prior}` to `{current}` ({delta}). Write 3-sentence commentary: (1) What changed (factual), (2) Why (most likely cause), (3) What action / no-action implied. Skip restating the number.Variables to swap: kpi, prior, current, delta
2. Trend vs noise
Is this `{kpi}` move a trend or noise? Output: (1) Compare to last 8 periods' variance, (2) Statistical signal vs jitter, (3) Verdict: "Trend", "Noise", or "Wait one more period". One paragraph.Variables to swap: kpi
3. Anomaly callout
This week, `{kpi}` is +/- {N}σ from rolling mean. Write a 2-sentence callout: (1) Magnitude + direction, (2) Plausible explanations to investigate. No "we need to dig in" filler.Variables to swap: kpi, N
4. Cohort-explained delta
Total `{metric}` moved {delta}. Decompose by cohort (new vs existing, segment, region). Identify which cohort drove the move. Output: "X% of the +Y came from cohort Z because…".Variables to swap: metric, delta
5. Goal-pacing commentary
KPI target for Q is `{target}`. Currently `{current}` at `{percent}` of period elapsed. Commentary: ahead / on / behind pace + adjustment ask. No "we're crushing it".Variables to swap: target, current, percent
6. Multi-KPI dashboard summary
Here are 6 KPIs: {kpis}. Write a 5-bullet exec summary: most important movement, one risk, one tailwind, one anomaly, one ask. ≤ 200 words.Variables to swap: kpis
7. Investor-update KPI section
Write the KPI section of a monthly investor update: (1) Headline metric movement, (2) Three supporting numbers, (3) What changed in our funnel, (4) What we're doing differently. ≤ 150 words.8. Cohort retention commentary
Retention curves: {data}. Commentary: (a) Where the cliff is, (b) Whether week-N retention shifted, (c) One explanation, (d) One action. Don't restate the data.Variables to swap: data
9. Conversion funnel narration
Funnel: {funnelData}. Identify: (1) Biggest drop-off stage, (2) Whether it changed this period, (3) Likely root cause, (4) Lowest-effort experiment to validate. Skip "needs further analysis".Variables to swap: funnelData
10. KPI fatigue audit
Our weekly KPI doc has 18 metrics. Audit: (1) Which haven't moved meaningfully in 90 days? (2) Which are derivatives of others? (3) Which would we never act on? Trim to 6.11. Narrative for a flat KPI
`{kpi}` is flat. Write 2-sentence commentary that doesn't fake significance: (1) flat + context (good or bad), (2) what would change it next month. No padding.Variables to swap: kpi
12. Forecast vs actual commentary
Forecast: `{forecast}`. Actual: `{actual}`. Miss / hit / beat by `{diff}`. Commentary: (1) what drove the variance, (2) whether the forecast model needs adjusting, (3) implication for next period.Variables to swap: forecast, actual, diff
Common mistakes
- No specific context — output is generic.
- Skipping fact-check — AI invents numbers when given soft inputs.
- Vague audience — output overshoots or undershoots seniority.
- No word limit — receivers won’t read past line 5.
- Same template for every situation — readers tune out.
- No “decision needed” framing — readers don’t know what to do.
- Forgetting to attach the source data — claims without receipts.
How to push results further
- Always specify audience level (IC / Manager / VP / CEO).
- Cap length: 1-page max for tactical, 3-bullet for executive.
- Lead with the ask / decision needed. Context after.
- Attach source data link — saves a follow-up email.
- Read aloud before sending; cut every sentence > 25 words.
- Use AI to draft and audit, not to ship without review.
- Save best examples; reuse format, refresh content.
Practical depth notes
Use these prompts as starting points, not final answers. For KPI Commentary Prompts: 12 Templates for Numbers That Tell a Story, the useful extra work is to replace every generic placeholder with a real constraint: audience, channel, length, brand voice, examples to imitate, and examples to avoid. Run at least two versions with different constraints, then compare the outputs side by side instead of accepting the first polished response.
A good result should pass three checks: it is specific enough that another person could reuse it, it avoids vague praise or filler, and it gives you an editable artifact rather than a broad suggestion. If the output feels generic, add one concrete reference, one forbidden pattern, and one measurable success criterion before rerunning the prompt. One final check: compare the finished result against the original goal in a single sentence. If that sentence is hard to write, the output is probably polished but unfocused. Tighten the goal, remove decorative language, and rerun only the weak section instead of regenerating the entire piece.
FAQ
- How long should this doc be?: Match audience patience. Tactical: 1 page. Executive: 3 bullets + link.
- Can AI replace the analyst?: For first drafts and templates yes; for judgment calls no.
- How often refresh?: Cadence-driven (weekly / monthly / quarterly) but adjust when audience signals fatigue.
- Should I include risks?: Always. Pretending no risk exist erodes trust on the next update.
- How to keep it fact-checked?: Attach data sources and have a peer skim numbers before sending.
- Can AI generate the data itself?: No — AI invents plausible numbers. Connect to real data sources.
Related
- Weekly report prompts
- Monthly business review prompts
- Executive summary prompts
- Excel analysis prompts
- Write the Narrative Around Your KPI Movement With AI
- Write a Weekly KPI Summary With AI: Numbers In, Executive-Ready Summary Out
- Productivity & Office Prompts hub
Tags: #Prompt #Productivity #KPI #Commentary