The task
You finalised next year’s budget. The spreadsheet is closed. Now leadership wants a narrative: what changed, why, what increased, what got cut, and what risks you took on. The narrative is short (300-400 words), but it is the only artefact most of the executive team will read. Get it wrong and the budget gets unbundled in committee. Get it right and the spreadsheet ships intact.
When AI helps — and when it does not
AI is excellent at structuring a narrative around variances, naming year-over-year changes, and framing trade-offs in business language. It is poor at knowing internal politics. If a cut affects a specific exec’s team, AI will not soften the language correctly. Read the AI draft against your stakeholder map; the narrative is part finance, part diplomacy.
What to feed the AI
- Budget table: this year vs last, by category, with absolute and percentage change
- Top 3 strategic priorities driving spend
- 1-2 cuts with the reason behind each
- The audience (CFO, CEO, board)
- Tone preference (confident, cautious, candid)
- Anything that is not up for re-negotiation, so AI does not invite it
Copy-ready prompt
Write a budget narrative.
Audience: <CFO / CEO / board>
Tone: <confident / cautious / candid>
Strategic priorities driving spend: <list>
Cuts and reasons: <list>
Not up for re-negotiation: <list>
Budget data (this year vs last):
"""
<paste table>
"""
Return:
1. A 300-400 word narrative with: total $ + YoY change, top 3 areas of increased investment with rationale, top 2 cuts with rationale, 1 risk if the budget is wrong
2. A "what stakeholders will challenge" — 3 predicted objections and the prepared response
3. A "summary line" — one sentence that captures the whole budget for executive consumption
4. A redline on any number you cannot verify from the source — flag [VERIFY]
Tone constraint: assume the reader supports the strategy. Confidence, not justification. Numbers without rationale are forbidden.For board-facing narratives: “Add a 100-word ‘why now’ framing that anchors this budget to the multi-year plan.”
Recommended output structure
Three paragraphs: macro picture (totals + YoY), investments (top 3 with reason), cuts and risk (top 2 cuts + 1 risk). A summary line at the top. The “predicted objections” block goes to your prep notes, not the narrative.
How to check the output is usable
- Every number traces to the source (no invented totals)
- Cuts are not hidden in passive voice. They are named, explained, and owned
- The “risk if the budget is wrong” is a real risk, not boilerplate
- Predicted objections include the specific person likely to raise them
- The summary line is repeatable. Your CFO can quote it in committee
Common mistakes
- Numbers without rationale. Execs reverse-engineer rationale on their own, badly
- Hiding cuts. They get found anyway; ownership beats discovery
- Letting AI invent percentages or YoY figures. Verify each
- Defensive tone. Assume the reader supports the strategy
- Missing the strategic frame. Without it, the budget reads as accounting
Practical depth notes
For AI Budget Narrative: Stakeholder-Ready Story from a Spreadsheet, the difference between a usable AI result and a generic one is the input packet. Give the model the audience, the current draft or raw material, the desired format, the decision you need to make, and two examples of what good and bad output look like. Ask it to preserve facts first, then improve structure or wording second.
After the first response, do a separate review pass. Look for missing constraints, invented details, weak calls to action, and language that sounds plausible but does not match the real situation. The best final output should be easy to use immediately: clear owner, clear next step, and no hidden assumption that someone else has to untangle. A stronger version of this workflow also defines the handoff. Decide who will use the output, what they should do next, and what information would make them reject it. If the deliverable is copy, test whether it has a single clear action. If it is analysis, test whether it separates observation from recommendation. If it is planning, test whether dates, owners, and tradeoffs are explicit enough for someone else to execute.
FAQ
- How long should it be? 300-400 words is the sweet spot. Shorter feels thin; longer goes unread.
- Should I include charts? Reference but do not embed in the narrative. Keep narrative narrative.
- What if leadership pushes back on a cut? Have the prepared response ready from the prep notes.
Related
- Financial trend analysis — multi-year trend writing
- KPI weekly report AI — same structure for weekly updates
- Manager update email AI — when the narrative is an internal update
- Financial report summary AI — same compression pattern for 10-Ks
- Business data analysis AI — adjacent business analysis
- Roadmap planning AI — when budget supports a roadmap
- Career Pivot Narrative Prompts for a Convincing Story
- AI Pricing Strategy Memo: Tier Design, Anchor, Discount Floor
- AI Monthly Investor Update Without Sounding Defensive