Finance agent brief
What changed this week
Explain why a metric moved between two frozen snapshots.
At a glance
Each week
[prior frozen snapshot]; [current snapshot]; [approved metric definition]
A sourced bridge in [finance review channel], updated after the owner replies
What it does
Each week, compare two frozen snapshots and post a sourced bridge to the finance review channel. Ask about unexplained changes and update the same bridge after replies. Reconcile opening to closing, separate historical corrections, and cite changed records. Preserve both snapshots and keep unconfirmed causes visible.
A standalone finance agent brief from Agents for Finance. It works in Claude, ChatGPT, Grok Bot, or the agent tool you already use. Adapt the placeholders to your setup. This is a starting brief, not an installable plugin.
Role and instructions
Replace the [bracketed placeholders] first, then paste this into your agent:
Instructions prompt
CopySetup checklist
Fill these in before the first run. Use the systems you already have — a spreadsheet export is enough to start.
- Cadence: [week]
- Approved metric definition: [the metric this bridge is allowed to use]
- Prior frozen snapshot: [where the opening snapshot is retained]
- Current snapshot: [where the closing snapshot is retained]
- Owner to ask about unexplained movements: [name and channel]
- Finance review channel: [Slack channel, email, or doc where the bridge is posted and updated]
- Out of scope: the agent may not overwrite either snapshot or hide unconfirmed causes
Output format
Post a sourced bridge to the finance review channel, then update that same bridge after the owner replies. Include:
- Headline: what moved, and any amount that came from a historical correction
- A bridge from opening to closing, with each movement classified
- Changed records cited, with historical corrections kept separate
- After a reply: how the cause was classified, that the bridge still ties, and any effective date to carry into the next run
- Sources: both frozen snapshots, the agreed metric definition, and the changed-record history used
Illustrative output
Illustrative shape, from the playbook
$500k more ARR, of which $70k came from a historical edit.
| Movement | Amount |
|---|---|
| Opening ARR | $28.40m |
| New business | +$420k |
| Expansion | +$180k |
| Contraction | −$60k |
| Churn | −$110k |
| Historical correction | +$70k |
| Closing ARR | $28.90m |
After the owner confirms the $70k is a correction to an earlier period, keep it separate from new business and carry its effective date into the next run. The bridge ties and source history is retained.
Pressure-test it
Backdate a record. The bridge should separate effective date from discovery date and still tie.
Run this test on historical or redacted data before you put the job on a schedule.
Works standalone
This brief is enough to run the job with files, exports, or the tools you already have. You do not need a special agent pack or plugin. Once the placeholders are filled in and the pressure-test passes, you can put it on a schedule.
