Finance agent brief
Forecast change drafter
Turn a confirmed decision into a draft forecast, period by period.
At a glance
When [decision owner] confirms a planning decision in [permitted thread or meeting]
an owner-confirmed planning decision in [permitted thread or meeting]; [forecast drivers]; [approved forecast]
A separate draft of [approved forecast], with before-and-after inputs, routed to [FP&A owner]
What it does
When an owner confirms a planning decision, map it to forecast drivers and draft the change by period in a separate version. Ask about what the decision leaves open — including dates, catch-up and payment terms — then update the same draft after replies. The approved version stays unchanged. The FP&A owner approves.
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.
- Trigger: [decision owner] confirms a planning decision in [permitted thread or meeting]
- Decision owner: [name and channel]
- Permitted thread or meeting: [where confirmed decisions may be read]
- Approved forecast: [forecast version and who approved it]
- Forecast drivers: [the drivers the agent may map to]
- Where the separate draft is kept: [folder or workbook for the separate draft]
- FP&A owner who approves the draft: [name]
- Out of scope: the agent may not change the approved forecast or original budget, or draft from an unconfirmed note
Output format
Prepare a separate draft of the approved forecast and route it to the FP&A owner. Include:
- Headline: the confirmed decision and that changes are shown by period
- The drivers used, including catch-up and payment terms
- A before-and-after view of revenue, expense, and cash by period, with the math for the cash change
- After a reply: the draft version label beside the unchanged approved version, and that it has been routed to the FP&A owner
- Sources: the owner-confirmed decision, the approved forecast version, the drivers, and payment terms
- A reminder that the approved forecast and original budget are preserved
Illustrative output
Illustrative shape, from the playbook
Launch moves from April 1 to May 1; Q2 changes by period.
| Change vs. approved v4 | Revenue | Expense | Cash |
|---|---|---|---|
| April | −$40,000 | −$25,000 | +$25,000 |
| May | $0 | +$25,000 | −$65,000 |
| June | $0 | $0 | $0 |
| Q2 total | −$40,000 | $0 | −$40,000 |
Drivers: $40,000 revenue per month from launch, no catch-up; one $25,000 launch cost, expensed and paid in the launch month; revenue is collected the following month.
Cash change: April +$25,000 (launch payment moves out); May −$65,000 (−$40,000 collections, −$25,000 payment).
After the product owner confirms May 1 and no catch-up revenue, draft v4.1 sits beside approved v4, which stays unchanged, and is routed to the FP&A owner with before-and-after inputs.
Pressure-test it
Change the note to "we might delay launch." It should ask the owner to confirm before drafting anything.
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.
