Monthly Business Review Brief

The Prompt

You are a business operations writer. Turn metrics and operating notes into a monthly review that tells leadership what changed, what matters, and what needs a decision.

KPI SNAPSHOT:
{{kpi_snapshot}}

MAJOR WINS:
{{major_wins}}

MAJOR ISSUES:
{{major_issues}}

NEXT MONTH FOCUS:
{{next_month_focus}}

Return exactly:
1) Signal check
   - biggest positive movement
   - biggest negative movement
   - what may be noise or still uncertain
2) Executive summary
   - 5 to 7 lines
3) KPI narrative
   - what changed
   - likely causes
   - why it matters
   - confidence level
4) Wins worth repeating
   - what worked
   - what made it work
5) Issues and root-cause hypotheses
   - issue
   - likely causes
   - evidence strength
6) Next 30-day priorities
   - priority
   - why now
   - suggested owner profile
7) Leadership decisions or escalations
   - decision needed
   - consequence of delay

Rules:
- Avoid vanity framing and empty optimism.
- Separate observed data from interpretation and from speculation.
- Keep the tone suitable for leadership but concrete enough for cross-functional operators.
- If the data is contradictory, say so instead of forcing a tidy story.

When to Use

Use this at month-end or before leadership reviews when a team has metrics and status notes but needs a sharper operational narrative. It works well for business, product, customer, and operations teams that want more than a dashboard screenshot.

Variables

Variable	Description	Example
kpi_snapshot	Metrics, trend direction, and any known caveats	”Revenue +6%, churn +1.2pp, NPS -3”
major_wins	Positive outcomes with supporting detail	”Support response time down 22%“
major_issues	Problems, misses, or unresolved concerns	”Conversion dropped in self-serve funnel”
next_month_focus	Priority areas, planned bets, or constraints for the next cycle	”Retention initiatives plus pricing experiment”

Tips & Variations

• Ask for a board-style version only after the operating draft is solid; otherwise the summary tends to get too polished too early.
• Add explicit data-quality notes when some KPIs are estimated, lagged, or sampled.
• Request a one-slide summary if the brief must be turned into a deck, but keep the richer operating version first.
• Include the previous month’s stated priorities when you want the model to evaluate whether the team actually followed through.

Example Output

Executive summary: Growth improved, but retention risk increased and the current gains may be less durable than the topline suggests.

Leadership decision: approve customer-onboarding pilot budget or accept slower recovery on churn.