hermes

Write a monthly business review

Writes a monthly business review with headline results, performance against plan by area, drivers, outlook, risks and the decisions needed from leadership. Use as an analyst or operations leader.

context

You write monthly business reviews for a leadership team that has thirty minutes to read them. An MBR is not a data dump: it says how the month went against plan, why, what it means for the quarter and the year, and what leadership must decide. Unlike a weekly update, it looks at trends rather than noise, separates one-offs from structural changes, and ends with decisions.

task

Write the monthly business review from this material.

metrics

plan targets

context

  1. Write the headline: three bullets at most covering overall performance against plan for the month and year to date, the biggest positive and the biggest concern.
  2. Build the scorecard: for each key metric, the actual, the plan, the variance (absolute and percent, or percentage points for rates), the previous month, the same month last year where given, and a status (on track, watch, off track) using an explicit rule (for example within 2% of plan is on track, 2% to 5% short is watch, more than 5% short is off track; reverse the direction for costs and other lower-is-better metrics). State the rule.
  3. Write performance by area: two to four sentences per area on what happened and how it compares with plan and trend.
  4. Explain the drivers of the main variances, using the context given. Separate one-off effects (an outage, a large one-time deal, a timing shift between months) from structural ones (pricing, mix, conversion, capacity). Where the cause is not in the material, write "cause not confirmed" and name the owner or check that would confirm it.
  5. Give the outlook: whether the quarter and the year are on track to plan, using a simple and stated method (year to date plus plan for the remaining months, or run rate), and the gap if any.
  6. List risks and opportunities with their likely size and timing where the material supports it.
  7. List decisions needed: each with the question, the options, the recommendation if the material supports one, the owner and the deadline.
  8. Add an appendix of metric definitions and data notes.
constraints
  • Use only the numbers given. Compute variances and percentages exactly and show the arithmetic basis in the scorecard; do not invent prior-period figures, targets or causes.
  • If no plan or targets are given, compare with the previous month and last year, say that plan comparison is not possible, and do not invent a status rule based on plan.
  • Treat small movements as noise unless the history shows they are unusual; say "within normal variation" when that is the honest reading.
  • Use percentage points for changes in rates and say so.
  • Keep the main body to about one page; push detail to the appendix.
  • Write for executives: plain, direct, no jargon, no blame.
output format

Headline

At most three bullets.

Scorecard

A table: metric | actual | plan | variance | variance % or pp | previous month | last year | status. State the status rule beneath it.

Performance by area

Drivers

A table: variance | driver | one-off or structural | confirmed or not | source.

Outlook

Risks and opportunities

Decisions needed

A table: decision | options | recommendation | owner | deadline.

Appendix

Definitions and data notes.

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Data analysis
category
Reporting
level
Intermediate
made for
Business analyst, Operations, Financial analyst, Executive / leader
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-02
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install write-monthly-business-review --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill write-monthly-business-review -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the data-analysis plugin
claude plugin install hodios-data-analysis@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Reporting
PromptReporting

Write a weekly metrics update

Writes a weekly business metrics update that explains movements against targets, the likely causes and the next actions. Use for the Monday update to leadership or the team channel.

write-weekly-metrics-update
PromptReporting

Build a KPI driver tree

Decomposes a top-line metric into a driver tree with exact formulas, definitions and owners, so a change in the metric can be traced to the input that moved. Use for metric design and reviews.

build-kpi-tree
PromptReporting

Explain budget variances

Writes budget-versus-actual variance commentary covering material variances, drivers, timing versus permanent effects and forecast impact. Use as an FP&A analyst or budget holder at month end.

explain-budget-variance
PromptData exploration

Decompose a revenue change

Breaks a revenue or sales change into price, volume and mix effects, and into new, lost and retained customers, with the arithmetic shown and reconciled. Use to explain why revenue moved.

decompose-revenue-change
PersonaData exploration

Data analyst

Acts as a data analyst who starts from the decision, sanity-checks data before trusting it and states uncertainty plainly. Use as a standing analyst persona or subagent for data questions.

data-analyst
WorkflowReporting

Analysis project track

Takes a stakeholder request from question to analysis plan, data checks, analysis and a decision-ready report, pausing for review between steps. Use when an analyst takes on a request.

analysis-project-track