For Financial Analyst (Corporate)s ·
What you'll accomplish
This guide gives you a repeatable AI workflow for the three most time-consuming parts of annual budget season: writing submission guidance for business unit managers, reviewing and summarizing budget inputs, and building the budget narrative for leadership review. You'll reduce the chaos of budget season by 20–30% with tools you can use immediately.
What you'll need
Set up a Claude Project that knows your company's budget context. You'll use it for all four budget-season activities below.
You are my budget season assistant for [Company Name]'s annual budget process.
BUDGET CONTEXT:
- Fiscal year: [FY start/end dates]
- Budget currency: USD (in millions with 1 decimal)
- Submitting departments: [list your 10-20 business unit names]
- Budget components: Headcount (salary + benefits), OpEx, CapEx, Revenue (if applicable)
- Budget template: Excel-based, submitted via SharePoint
AUDIENCE:
- Budget submission instructions audience: Department heads and their admins (non-finance)
- Budget narrative audience: CFO and board (senior leadership)
FORMAT PREFERENCES:
- Instructions: Friendly, plain English, numbered steps
- Narratives: Direct, data-first, executive-level language
- No jargon in either format
Click Save.
Stop answering the same 15 questions from department heads every year. Write a clear guide once.
Write a budget submission guide for department heads who are not finance professionals. They need to complete our Excel template with three tabs: Headcount, Operating Expenses, and Capital Expenditures.
For each tab, explain:
- What goes in each column
- What they should NOT include (common mistakes)
- Any formulas or cells they should not touch
Also include:
- The submission deadline: [date]
- Where to upload the completed template: [location]
- Who to contact with questions: [name/email]
Common mistakes from prior years:
- [List 2-3 actual mistakes you see every year]
Tone: Friendly and helpful. Format: Numbered steps with a section for each tab. Keep it to 2 pages.
What you should see: A clear, well-structured submission guide that pre-answers the most common questions.
As submissions come in, you need to quickly identify which ones have problems (missing data, unreasonable assumptions, incomplete submissions).
Review this department budget submission. Flag any of the following issues:
- Missing headcount for open positions (should equal [target headcount] FTEs)
- OpEx that looks significantly higher or lower than prior year without explanation (over 15% change)
- CapEx items without project descriptions
- Any cells left blank that should have data
Provide a brief summary of what the submission looks like and what needs clarification.
[Paste the department's budget summary table]
Time saved: 10–15 minutes per department submission in review time.
After consolidating all submissions into your master budget file, write the narrative that explains the total budget to leadership.
Write a budget narrative for our [Year] annual budget presentation to the CFO.
Key budget figures:
Total Revenue Budget: $[X]M ([+/- X%] vs. prior year)
Total OpEx Budget: $[X]M ([+/- X%] vs. prior year)
Total Headcount: [X] FTEs ([+/- X] vs. prior year)
EBITDA Margin target: [X]%
Top 3 investment priorities reflected in the budget:
1. [Priority 1 — e.g., "Expanding West region sales team — 15 new hires"]
2. [Priority 2]
3. [Priority 3]
Key assumptions:
- Revenue growth assumption: [driver]
- Largest cost driver: [driver]
- Key risks to the budget: [1-2 risks]
Format: 3-4 paragraphs. Executive audience. Under 300 words.
This is the step most teams skip, and they regret it when auditors or new finance hires ask why certain numbers are what they are.
Write a budget assumption documentation page for our [Year] budget. For each assumption below, write 1-2 sentences explaining the rationale in plain language.
Revenue growth: [X]% — assumption: [your reason]
Headcount growth: [X] FTEs — assumption: [your reason]
Compensation increase: [X]% — assumption: [your reason]
Marketing spend: $[X]M — assumption: [your reason]
CapEx: $[X]M — assumption: [your reason]
Format: A table with columns: Assumption | Value | Rationale | Owner
Submission guide:
Write a 2-page budget submission guide for non-finance managers. Template tabs: [list]. Deadline: [date]. Common mistakes: [list]. Tone: friendly.
Submission review:
Review this budget submission and flag any missing data, unreasonable variances from prior year (over 15%), or incomplete fields: [paste data]
Budget narrative:
Write a 300-word CFO budget narrative for [Year]. Key figures: Revenue $[X]M, OpEx $[X]M, HC [X] FTEs. Top priorities: [list]. Key risks: [list].
Assumption documentation:
Write assumption documentation for these budget inputs: [list assumptions and values]. Format: table with Assumption | Value | Rationale | Owner.