.jpg)
What This Guide Covers
Most CFOs who try Claude treat it like a calculator. They paste in a spreadsheet, ask a question, and get a one-off answer with no memory, no context, and no repeatability. That approach leaves 90% of the value on the table.
This guide shows you how to build a persistent, context-aware planning system inside Claude Projects. One where Claude acts as your FP&A copilot: conservative with numbers, explicit about assumptions, and incapable of inventing financial data that is not in your uploaded files.
The workflow is repeatable. Each month, you return to the same Project, upload fresh actuals, and Claude runs the same process faster than the month before because it remembers your model structure, your assumption conventions, and your reporting preferences.
Top 8 Use Cases for CFOs
Claude is not limited to one-off analysis. Here are the highest-value workflows finance leaders are running today.
Monthly Reforecast Cycle
Load actuals, validate against plan, update assumptions, and produce a refreshed forecast with a full audit trail. The entire close-to-forecast workflow in a single session.
Scenario & Sensitivity Analysis
Build three-scenario brackets (base, upside, downside) that change multiple drivers simultaneously, plus one-at-a-time sensitivity tables that isolate each variable's impact on revenue, EBITDA, and cash.
Headcount Planning
Model new hires, departures, backfills, compensation structures (base plus bonus plus variable), payroll taxes, and benefits load across departments and start dates.
Board-Ready Dashboards
Generate interactive HTML dashboards with KPI scorecards, scenario charts, bridge waterfalls, and written narratives that explain the "so what" behind every number.
Variance Analysis & Narrative
Compare actuals to plan at every line item, surface the biggest surprises, and draft CFO-ready commentary explaining what happened and what it means for the rest of the year.
Cash Flow & Runway Modeling
Project monthly cash positions, model burn rate under different growth and hiring scenarios, and identify when funding needs arise before they become urgent.
SaaS Metrics Tracking
Calculate and monitor ARR, net revenue retention, gross churn, expansion rates, CAC payback, and LTV/CAC from your model's customer and revenue data.
Planning Model QA & Audit
Have Claude inspect your model for structural integrity, circular references, hardcoded assumptions, broken links between sheets, and balancing errors before the numbers go to the board.
Building Your Personal AI CFO
Follow these six steps to create a persistent FP&A workspace in Claude that gets smarter every month.
Create a Dedicated Project
Go to claude.ai and click Projects. Create a new one with a clear name and description. The description should state the project's purpose in plain language so Claude understands its role from the start.
The Project is your persistent workspace. Files, instructions, conversation history, and outputs all survive between sessions. Next month, you return to the same Project and pick up where you left off.
Write Detailed Project Instructions
This is the single most important step most people skip. Project instructions act as Claude's operating charter for every conversation in this Project. They govern behavior, set guardrails, and define what Claude can and cannot do with your financial data.
Your instructions should define four things:
A. Core Role
Tell Claude to act as a disciplined FP&A manager. Conservative with numbers. Explicit about assumptions. Auditable in every step. Never invents financial facts not present in uploaded files.
B. Source-of-Truth Hierarchy
This prevents Claude from overriding your actual data with its own reasoning. Define authority in this order:
| Priority | Source |
|---|---|
| 1 (Highest) | Uploaded ERP exports and planning model |
| 2 | Explicit user instructions in current chat |
| 3 | Prior project files and outputs |
| 4 (Lowest) | Claude's own reasoning |
C. Financial Data Rules
Never overwrite actuals with formulas. Never create plug numbers to force statements to balance. Always label assumptions and show their impact. Keep an audit trail of every material change.
D. Output Preferences
Specify your preferred units (thousands vs. millions), fiscal year definition, chart style, and whether you want Excel outputs, HTML dashboards, or both.
You set this up once. It governs every conversation in the Project from that point forward. If you refine your instructions over time, Claude immediately adopts the changes in new conversations.
Upload Your Planning Model & Actuals
Upload your Excel planning model and the latest ERP export (CSV or Excel) into the Project's files area. Claude will read the structure, identify sheet names, understand column headers, and map relationships between tabs.
Your planning model should ideally contain these components:
| Sheet | Contents |
|---|---|
| Assumptions | Growth rates, churn, expansion, pricing, headcount variables |
| P&L | Monthly income statement with actuals and forecast columns |
| Balance Sheet | Monthly balance sheet or at minimum a cash position tracker |
| Headcount | Roster with department, role, start date, compensation, and status |
Claude performs best when your model has clear labels in row 1 or column A. Avoid merged cells, hidden rows with critical formulas, and color-coded-only conventions. If something is an assumption vs. an actual vs. a formula, label it explicitly.
Run the Reforecast Prompt
This is where the real work happens. Use a structured prompt that tells Claude exactly what to do, in what order, and what guardrails to follow. Here is a production-grade reforecast prompt you can adapt:
Build Scenarios & Sensitivity Analysis
Once the base reforecast is complete, ask Claude to layer scenarios on top. The key principle: scenarios should be clearly separated from the base case and should never overwrite it.
Generate Board-Ready Dashboards
This is where the compounding advantage of doing everything in one Project becomes obvious. Because Claude performed the entire reforecast, it has full context for every chart, every narrative, and every scenario. It does not need to be briefed. It was present for every decision.
Ask for an interactive HTML dashboard with KPI scorecards, scenario comparison charts, and written narratives. Claude can also produce downloadable Excel files with the same analysis.
The difference between a cold-start dashboard and one built after a full reforecast is enormous. Context makes the analysis better, and the Project keeps that context alive across sessions.
7 Things Most People Miss
The gap between CFOs who get modest value from Claude and those who build a genuine planning copilot comes down to these overlooked practices.
Projects Are Not Optional
Starting a fresh conversation every time means Claude has zero memory of your model, your conventions, or your last forecast. Projects retain files, instructions, and conversation history. Without a Project, you are rebuilding context from scratch each session.
Instructions Are Your Operating Charter
Most people write a one-line project description and move on. Detailed instructions that define Claude's role, the source-of-truth hierarchy, and financial data rules transform output quality. Think of it as writing a job description for your best analyst.
Claude Checks Assumptions Before Acting
Claude will present an assumption delta table before it modifies your model if you ask for it. This means you can review every change, reject the ones that look wrong, and approve the rest. Most people skip this step and lose the audit trail.
The Reforecast and the Dashboard Should Live in the Same Session
When Claude builds a dashboard after just helping you think through the forecast update, the narratives are dramatically better. It knows which assumptions changed, why, and what the variance story looks like. A dashboard built from a cold spreadsheet has none of that context.
Memory Compounds Over Time
Claude writes to long-term memory within a Project. Each monthly cycle teaches it your planning conventions, your model quirks, and your reporting preferences. Month three is noticeably faster and more accurate than month one.
You Can Ask Claude to QA Its Own Work
After any model update, tell Claude to verify that the balance sheet balances, that the P&L ties to the assumptions sheet, and that no actuals were overwritten. Claude will run the checks and flag any discrepancies before you download the file.
Guardrails Prevent Hallucinated Numbers
Without explicit instructions telling Claude never to invent financial data, it may fill gaps with plausible-sounding numbers. The source-of-truth hierarchy and the "no plug numbers" rule are safety mechanisms, not suggestions.
10 Keys to Successful Financial Modeling with Claude
Use a Project, Not a Conversation
Every financial model lives inside a Claude Project. Files persist. Instructions persist. Memory persists. A standalone conversation is a throwaway. A Project is a system.
Define the Source-of-Truth Hierarchy
Uploaded data beats user instructions. User instructions beat prior outputs. Prior outputs beat Claude's reasoning. This single rule prevents 80% of financial modeling errors.
Separate Actuals from Forecast Explicitly
Always tell Claude which months are actuals and which are forecast. A model without a clear cutoff is a model where Claude may accidentally overwrite real data with projected figures.
Show Assumption Deltas Before Committing
Before Claude updates the model, ask it to present a delta table: what was the prior assumption, what is the new one, and why. Approve the deltas first, then let Claude build.
Use Structured, Sequential Prompts
Break your request into numbered steps. Claude follows ordered instructions far more reliably than a single paragraph asking for everything at once. Sequence matters.
Keep Scenarios Separate from the Base Case
Never let a scenario overwrite the base reforecast. Scenarios are parallel tracks. Label each one explicitly, state which assumptions changed, and maintain one clean base case at all times.
Demand an Audit Trail
Ask Claude to log every material change: what it changed, where in the model, from what value to what value, and why. A model without an audit trail is a model you cannot defend in a board meeting.
State Limitations Honestly
If your model cannot represent a requested change precisely, Claude should say so and choose the closest transparent alternative. "I approximated this as X because the model does not support Y" is always better than a silent fudge.
Build Dashboards After the Reforecast, Not Before
The order matters. A dashboard built after a full reforecast has complete context: what changed, why, and what the numbers mean. A dashboard built from a cold file is just a chart with no story.
Run the Same Process Next Month
The real power is compounding. Return to the same Project, upload fresh actuals, and run the same workflow. Each month takes less time and produces sharper analysis because Claude remembers your system.
Copy-Paste Prompts for Every Stage
Use these prompts as starting points. Adapt the specifics to your company's model and conventions.
Actuals Validation
Headcount Change
Scenario Builder
Board Dashboard
Traditional FP&A vs. Claude Workflow
| Task | Traditional | With Claude Project |
|---|---|---|
| Load actuals & validate | 2-4 hours manual mapping | 5 minutes with audit trail |
| Update forecast assumptions | 1-2 hours, scattered notes | 10 minutes with delta table |
| Build 3 scenarios | Half a day, often skipped | 5 minutes per scenario |
| Sensitivity analysis | Rare, ad hoc if done | Built into every cycle |
| Board dashboard | 1-2 days in slides | 10 minutes, auto-narrated |
| Variance commentary | Written manually | Drafted by Claude, reviewed by you |
| Model QA | Eye-check, maybe a peer review | Automated cross-check on every run |
| Month-over-month continuity | Tribal knowledge | Persistent Project memory |
Advanced Techniques
Tip: Use "Extended Thinking" for Complex Models
When working with large workbooks (50+ rows, 24+ columns), select Opus 4.6 Extended in the model picker. Extended thinking gives Claude more internal processing time, reducing errors on multi-sheet calculations and cross-tab dependencies.
Tip: Upload Supporting Context Files
Upload your board memo, investor update, or prior quarter commentary as Project files. When Claude drafts narratives for the dashboard, it will match the tone, terminology, and level of detail your board expects because it has seen your prior communication style.
Tip: Ask for the "Planning System Working Memory" Document
After each reforecast cycle, ask Claude to create a "Planning System Working Memory" text file that captures key assumptions, model conventions, known limitations, and decisions made this cycle. Upload it as a Project file. Next month, Claude reads it first and picks up exactly where you left off.
Tip: Use Bridge Charts to Explain Variances
Ask Claude to build waterfall/bridge charts that walk from prior plan to revised plan. These are far more effective in board presentations than tables because they visually decompose the "walk" from one number to another.
Tip: Run QA as a Separate Step
After Claude generates the updated workbook, run a dedicated QA prompt: "Verify the balance sheet balances for every month. Confirm the P&L ties to the assumptions sheet. Check that no actuals were overwritten. List any issues." Treat QA as a gate, not an afterthought.
Tip: Version Your Outputs
Name each output file with the cycle date: "CoolDashboards_Reforecast_Apr2026_v1.xlsx". When you iterate, increment the version. This makes it trivial to compare this month's output to last month's and keeps the audit trail clean.
Example Dashboard Components
Here are the types of visualizations Claude can produce as part of your board-ready dashboard. Each of these can be generated as interactive HTML, embedded in Excel, or exported to PowerPoint.
New customer acquisition is the dominant single driver. A +/-20% swing in logo volume produces a roughly $1.9M EBITDA impact in FY2026.
Your First 15 Minutes
You do not need a perfect model to start. You need a model, a set of instructions, and a willingness to treat Claude as a thinking partner rather than a calculator.
The minimum viable setup
Create a Project. Write 200 words of instructions defining Claude's role, the source-of-truth hierarchy, and two or three financial data rules. Upload your planning model as an Excel file. Ask Claude to inspect the workbook structure and summarize what it sees. That single conversation will tell you whether Claude understands your model, and you can iterate from there.
Pick one workflow. Define the steps. Give Claude context. Check the output. Then run it again next month and watch it get faster.