Monthly Report
Monthly Report for Stakeholders
A monthly narrative: plan vs actual, variance, and next month's bets - in language non-specialists get.
The Prompt
monthly-report-for-stakeholders.md
Write a monthly stakeholder report. Function: {{function}} Month: {{month}} Plan vs actual: {{numbers}} Narrative notes: {{notes}} Next month bets: {{bets}} Sections: 1. In one paragraph: did we do what we said? 2. Variance table 3. Three stories (one win, one miss, one learning) 4. Next month: 3 bets with leading indicators 5. Asks Plain English. No unexplained acronyms. No hockey-stick charts in prose.
Negative prompt
Included when you copy the prompt
Do not use unexplained acronyms or jargon stacks. Do not invent plan/actual numbers beyond {{numbers}}. Do not write hockey-stick projections or hype charts in prose. Do not skip variance, the three stories (win / miss / learning), bets with leading indicators, or asks. Do not bury whether you hit the plan in a long soft narrative - answer in the opening paragraph. Do not present hopes as committed outcomes.
Fill in your details below - this prompt updates as you type, then copy it.
Fill in your details
0 of 5 filled. Preview updates as you type - then copy the finished prompt (negative prompt included when present).
monthly-report-for-stakeholders.md
Prompt preview
Write a monthly stakeholder report. Function: {{function}} Month: {{month}} Plan vs actual: {{numbers}} Narrative notes: {{notes}} Next month bets: {{bets}} Sections: 1. In one paragraph: did we do what we said? 2. Variance table 3. Three stories (one win, one miss, one learning) 4. Next month: 3 bets with leading indicators 5. Asks Plain English. No unexplained acronyms. No hockey-stick charts in prose.
Examples
Example input
Function: Customer Success (mid-market) Month: July 2026 Plan vs actual: - Net revenue retention plan 108% / actual 104% - Logo churn plan ≤1.5% / actual 2.2% - QBR completion plan 40 accounts / actual 37 - Expansion pipeline created plan $180k / actual $210k - CSAT plan 4.6 / actual 4.5 (n=88) Narrative notes: - Lost 2 logos: one acquired, one switched after we delayed Salesforce sync 6 weeks - Expansion beat plan from 3 seat-upsell plays and one annual prepay - New health-score v2 flagged risk earlier but playbooks not staffed for "yellow" accounts - Hired 1 CSM; still 1 open backfill Next month bets: Staff yellow-account playbook; ship Salesforce sync milestone; run save offers on dual-vendor accounts
What you should get
1. Did we do what we said? Partially. We beat expansion pipeline ($210k vs $180k) and nearly hit business reviews (37 of 40), but net revenue retention landed at 104% vs 108% and logo churn ran hot at 2.2% vs 1.5%, driven by an acquisition loss and a save failure tied to the delayed Salesforce sync. Customer satisfaction was 4.5 vs 4.6 on 88 responses. 2. Variance table | Metric | Plan | Actual | Variance | | Net revenue retention | 108% | 104% | -4 pts | | Logo churn | ≤1.5% | 2.2% | Miss | | Business reviews completed | 40 | 37 | -3 | | Expansion pipeline created | $180k | $210k | +$30k | | Customer satisfaction | 4.6 | 4.5 (n=88) | -0.1 | 3. Stories Win: Expansion pipeline outperformed on three seat upsells plus one annual prepay. Miss: Two logo losses - especially the Salesforce sync delay - pushed churn above plan. Learning: Health-score v2 surfaces "yellow" risk earlier, but without a staffed playbook those alerts do not change outcomes. 4. Next month bets (with leading indicators) 1. Staff yellow-account playbook - indicator: % of yellow accounts with an owned next step within 5 days 2. Ship Salesforce sync milestone - indicator: sync error rate and open sync-related tickets week over week 3. Save offers for dual-vendor accounts - indicator: save conversations started and retained ARR from that cohort 5. Asks - Approve remaining CSM backfill start date so yellow playbooks have coverage - Confirm Salesforce sync milestone date with Engineering for customer communications - Green-light save-offer discount band (cap %) for dual-vendor accounts
When to use this prompt
Use it when
- You need help with managers.
- You need help with founders.
- You need help with agencies.
Skip it when
- You only need a one-line ask with no constraints, format, or context.
- You cannot supply the fill-in details the template asks for.
- A different category or tool-specific workflow fits the job better.
How to get a good result
Done when
1. Did we do what we said? Partially. We beat expansion pipeline ($210k vs $180k) and nearly hit business reviews (37 of 40), but net revenue retention landed at 104% vs 108% and logo churn ran hot at 2.2% vs 1.5%, driven by an acquisition loss and a save failure tied to the delayed Salesforce sync. Customer satisfaction was 4.5 vs 4.6 on 88 responses. 2. Variance table | Metric | Plan | Actual | Variance | | Net revenue retention | 108% | 104% | -4 pts | | Logo churn | ≤1.5% | 2.2% | Miss | | Business reviews completed | 40 | 37 | -3 | | Expansion pipeline created | $180k | $210k | +$30k | | Customer satisfaction | 4.6 | 4.5 (n=88) | -0.1 | 3. Stories Win: Expansion pipeline outperformed on three seat upsells plus one annual prepay. Miss: Two logo losses - especially the Salesforce sync delay - pushed churn above plan. Learning: Health-score v2 surfaces "yellow" risk earlier, but without a staffed playbook those alerts do not change outcomes. 4. Next month bets (with leading indicators) 1. Staff yellow-account playbook - indicator: % of yellow accounts with an owned next step within 5 days 2. Ship Salesforce sync milestone - indicator: sync error rate and open sync-related tickets week over week 3. Save offers for dual-vendor accounts - indicator: save conversations started and retained ARR from that cohort 5. Asks - Approve remaining CSM backfill start date so yellow playbooks have coverage - Confirm Salesforce sync milestone date with Engineering for customer communications - Green-light save-offer discount band (cap %) for dual-vendor accounts
Common mistakes
- Leaving function, month, numbers vague - the model then invents placeholders.
- Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules.
- Stopping when the first draft appears instead of checking it against the success criteria below.
FAQ
- What do I fill in before I copy this prompt?
- Replace these placeholders with your details: function, month, numbers, notes, bets. Required fields are marked on the page. The prompt text updates as you type.
- Which AI tools is this prompt written for?
- It works best with ChatGPT, Claude, Gemini. Copy the filled prompt and paste it into the tool you already use.
- What should a good result look like?
- 1. Did we do what we said? Partially. We beat expansion pipeline ($210k vs $180k) and nearly hit business reviews (37 of 40), but net revenue retention landed at 104% vs 108% and logo churn ran hot at 2.2% vs 1.5%, driven by an acquisition loss and a save failure tied to the delayed Salesforce sync. Customer satisfaction was 4.5 vs 4.6 on 88 responses. 2. Variance table | Metric | Plan | Actual | Variance | | Net revenue retention | 108% | 104% | -4 pts | | Logo churn | ≤1.5% | 2.2% | Miss |…
- What are common mistakes with this prompt?
- Leaving function, month, numbers vague - the model then invents placeholders. Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules. Stopping when the first draft appears instead of checking it against the success criteria below.
Best for
- Managers
- Founders
- Agencies
Related Prompts
More prompts like this — same topic and style.
