Weekly management report in under 30 minutes

Founder, COO, or PM at 10-100 person company; especially SaaS, agencies, consulting firms, professional services · Assemble in ~10 min; first report draft in <30 min once data is exported.

Edit flowon X● golden 91

step 1connector

Export raw data from your tools

⚡ bring your own tool

step 2ready

Analyze raw data for KPIs and trends

data-analysis3 alts

step 3ready

Pull project and sprint status

sprint-brief9 alts

step 4ready

Generate structured performance narrative

performance-report20 alts

step 5partial

Assemble financial snapshot

finance-report3 alts

step 6ready

Compose full report with data storytelling

data-storytelling

step 7ready

Write internal leadership update

team-communications

Did this recipe work for you?

What you get

▸Management report draft (Markdown/HTML) covering KPIs, delivery status, and spend
▸Financial snapshot HTML file for the period
▸Leadership update message (3P format) ready to paste into Slack or email
▸Dated report file saved locally as a running record

tools: Your existing data sources (Jira, QuickBooks, Slack) — no added SaaS cost

tokens: ~$1-3 per report run (5-8 files analyzed, narrative composed)

≈ $4-12/mo at weekly cadence

What stays yours

· Export raw data from each tool before running (5-10 min per source until API pull is automated)
· Review financial figures for accuracy before sharing — numbers from exports should be verified against source-of-truth accounting records
· Approve and personalize the leadership update before distributing to stakeholders

✓ Last verified 2026-06-11claude-sonnet-4-6 (subagent, test-mode fixtures)

✓ step 1 · Export raw data from your tools

✓ step 2 · Analyze raw data for KPIs and trends

✓ step 3 · Pull project and sprint status

✓ step 4 · Generate structured performance narrative

✓ step 5 · Assemble financial snapshot

✓ step 6 · Compose full report with data storytelling

✓ step 7 · Write internal leadership update

view sample outputs from this run

step 2 · Analyze raw data for KPIs and trends

# KPI Summary — Week 23 (June 1–7, 2026)
## Arboreal SaaS Inc.

---

### Revenue

| Metric | W23 Value | vs Target | vs Prior Week |
|--------|-----------|-----------|---------------|
| MRR | $138,600 | +1.2% above target | +$2,500 (+1.8%) |
| Net new ARR booked (W1 Jun) | $50,800 | — | — |
| May EBITDA | $14,800 | +169% above $5,500 budget | — |
| May Gross Margin | 87.2% | Healthy; COGS came in $800 under budget | — |

**Signal**: MRR crossed $138k for the first time, driven by 3 enterprise closes (Meridian Health, Lodestar Logistics, Fenwick & Co. — estimated $54k combined new ARR). Sales &…

step 3 · Pull project and sprint status

# Sprint Status Brief — Sprint 41
## Arboreal SaaS Inc. | Jun 1–14, 2026 | Mid-sprint snapshot (Day 7 of 14)

---

## At a Glance

| | Points |
|---|---|
| Committed | 37 |
| Done | 9 (24%) |
| In Progress | 15 (41%) |
| Not Started | 13 (35%) |
| Remaining days | 7 |

**Pace assessment**: 9 pts done in 7 days = 1.3 pts/day. To hit the 37-pt commitment, the team needs 28 pts in 7 remaining days = 4.0 pts/day. That is a 3x acceleration required. **Sprint is at risk** unless in-progress stories close quickly and unstarted stories are de-scoped.

---

## What Shipped (Done)

| ID | Story | Points…

step 4 · Generate structured performance narrative

# Performance Narrative — Week 23
## Arboreal SaaS Inc. | June 1–7, 2026

---

## Executive Summary

Week 23 was a strong commercial week with a single technical incident that was contained quickly. MRR reached $138,600 — the highest level in company history — driven by three enterprise closes that added $54k in new ARR. The onboarding A/B test shipped to production and immediately showed up in conversion data, with trial-to-paid jumping 2.5 percentage points to 17.3%. On the engineering side, a latency regression hit Friday but was diagnosed and fixed within hours. Delivery risk is elevated a…

The problem

When I need to update leadership or myself on project status, spend, and KPIs every week, I want a narrative report assembled from Slack, Jira, QuickBooks, and spreadsheet data so that I stop spending a day and a half compiling it manually.

Cybernetic layers

Memorybyo

Prior-week report files serve as memory; store them in a dated folder (reports/YYYY-WW/). No harvested memory artifact fits — use a local context file or Google Drive folder as the running record.

Background / schedulingpartial

This recipe is batch-shaped for a single session. A cron trigger (Claude Code scheduled task or system cron) could kick it off weekly, but that requires connecting the data-export step to an automated API pull — not yet a library artifact.

Harnessready

Claude Code is the runtime. Drop each ready skill into ~/.claude/skills/ and invoke in sequence within one session.

Click any step to see what fills it — and the ranked alternatives you can swap in.