ع
Start Topics Teams Reference What's new Saved
playbook

Brief leadership in plain English

Turn a month of numbers into a narrative leadership will actually read — what changed, why, and the two things to watch, under 200 words — while keeping the formulas and raw figures where you can re-run them.

medium ~30 min
when to reach for this

You've done the work — the export is clean, the accounts reconcile, the spend is audited — and now you have to make leadership care, in a paragraph they'll read between meetings. A table of category totals isn't a briefing; it's homework you're assigning your CEO. This system turns verified numbers into a short narrative: what moved, why it moved, and the two things to keep an eye on — under 200 words, with the raw figures kept underneath so you can defend any line on the spot.

gather this first
  • This month's verified totals — ideally the outputs of Reconcile two files, line by line and Audit the month's spend, so the numbers are already checked.
  • Last month's totals for comparison, and the headline figures leadership tracks (revenue, burn, runway, cash balance).
  • Any context only you know: the one-off tax bill, the new hire, the deal that slipped — the why behind the numbers that a spreadsheet can't see.
the workflow

  1. Find the story before writing the summary

    In Claude Desktop, open the folder with this month's and last month's totals and ask in the chat — no terminal needed. Don't ask for the summary first, though. Ask what changed and what it means — the narrative — so you're editing an insight, not polishing a list of numbers nobody will read.

    you ask
    Here are this month's verified totals and last month's. Before writing anything, tell me the 3 biggest changes in dollars and percent, your best guess at why each happened, and the single most important thing for leadership to notice. Don't write the summary yet — just the story.

    what you get back A story spine: "Burn up 12,000 (+7%), driven by the one-time Cloud Co overage. Revenue flat. Runway shortened by ~2 weeks. The thing to notice: runway, not spend." Now you have a narrative to shape, not a table to transcribe.

    The numbers are the evidence; the story is the product. Getting the story right before any prose is what makes the summary worth reading.

  2. Add the 'why' only you know

    Claude can see what changed; it can't see why. Hand it the context behind the moves so the summary explains causes, not just deltas — that's the difference between a report and a briefing.

    you ask
    Here's the context behind the numbers: the 28,000 was a one-time annual tax bill, the Cloud overage was a migration we knew about, and the slipped deal pushes 15,000 to next month. Fold this in so the summary explains why each change happened, not just that it did.

    what you get back A narrative where every number has a reason: "Spend rose mainly on a one-time tax bill and a planned migration — both non-recurring — so underlying burn is flat." The kind of line that stops a panicked Slack message before it's sent.

  3. Write it tight, under 200 words

    Leadership reads short. Cap the length hard and force a clear structure — what changed, why, what to watch — so it's skimmable in 30 seconds and complete in two minutes.

    you ask
    Now write the leadership summary in plain English, under 200 words: a one-line headline, what changed and why (2-3 sentences), and 'two things to watch' as a short list. No jargon, no hedging, round to the nearest thousand. Then give me a one-sentence version for a Slack update.

    what you get back A tight briefing under 200 words — headline, a short 'what changed and why,' and two watch-items ("runway is now ~3.5 months; the slipped deal lands in June or it doesn't") — plus a one-line Slack version. Skimmable, honest, done.

  4. Keep the math underneath, re-runnable

    A summary you can't back up is a liability. Attach the verified figures and the method so when someone asks 'where's that number from,' the answer is one scroll away — and next month is an update, not a rewrite.

    you ask
    Below the summary, add a short appendix: the key figures as a small table, where each came from (which file, which reconciliation), and the formula for runway. Save the whole thing as leadership-summary-may.md so I can update the numbers and re-run it next month.

    what you get back A leadership-summary-may.md with the narrative on top and a verifiable appendix below — every headline number traceable to a file and a formula — so the summary is defensible and the template is reusable.

make it your own
  • Board deck for the quarter: for the quarterly version, run Assemble the board & investor finance pack — it recasts this same narrative into a board-ready deck outline with the metrics investors track and a traceable appendix. The monthly memo and the quarterly pack share one verified set of numbers.
  • Fold in the variance: pull the 'why' straight from Track budget vs. actuals and explain every variance — the price / volume / timing classification of each gap is exactly the explanation leadership wants, already written.
  • Bilingual briefing: for a leadership team that reads Arabic, produce both — author the Arabic narrative natively for the right register, not translated from the English — over one shared numbers appendix so both versions cite identical figures.
  • Pull the watch-item from the audit: the 'two things to watch' should come straight out of Audit the month's spend — run the audit first and the summary's hardest part is already written.
  • Standardize it (Power Track): once the structure works, save it as a /finance-summary custom command (see the Capabilities tab) so every month's briefing has the same shape and length.
watch out for
  • Plain English makes numbers sound right; it doesn't make them be right. Only summarize figures that came out of a reconciliation or audit you trust — never write a confident narrative over unverified data.
  • Don't let Claude invent a 'why.' If a cause isn't in the context you provided, the summary should say 'reason unclear, investigating' — a plausible-but-wrong explanation is worse than an honest gap.
  • Claude drafts the briefing; a human owns what leadership is told. Read every number against the appendix before you send it — your name is on the summary, not Claude's, and confidential figures stay in your approved workspace.

you'll end up with A under-200-word leadership briefing that explains what changed and why with two clear things to watch — backed by a verifiable appendix, in a reusable template you update each month.

Questions people ask

How long should a leadership summary be?
Under 200 words — a one-line headline, what changed and why in two or three sentences, and two things to watch as a short list, plus a one-sentence version for a Slack update. Leadership reads short, so it should be skimmable in 30 seconds and complete in two minutes.
Why have Claude find the story before writing the summary?
Because the numbers are the evidence, but the story is the product. Asking what changed and why first means you edit an insight — "runway shortened by two weeks, driven by a one-time tax bill" — instead of polishing a table of totals nobody will read.
Claude can see the numbers — why does it need the \"why\" from me?
Because Claude can see what changed but not why. Hand it the context only you know — the one-off tax bill, the planned migration, the slipped deal — so the summary explains causes, not just deltas. If a cause isn't in the context you gave, it should say "reason unclear, investigating" rather than invent one.
How do I make the summary defensible?
Only summarize figures that came out of a reconciliation or audit you trust, and attach a short appendix tracing each headline number to its file and formula. Plain English makes numbers sound right; it doesn't make them be right, so the math stays one scroll away.