Claude 3.5 Sonnet for Financial Analysis: Case Study
Real-world test of Claude 3.5 Sonnet analyzing quarterly financials and identifying trends. What works, doesn't work, and practical workflows for finance teams.
In this article

The Test Setup
- Q2 2024 Income Statement (P&L)
- Q2 2024 Balance Sheet
- Q2 2024 Cash Flow Statement
- Q1 2024 statements for comparison
- Same quarter prior year (Q2 2023) for YoY analysis
- Management commentary from board deck
Analysis Request
We uploaded all documents and prompted:
"Analyze these quarterly financials. Focus on:
Write for a CFO audience. Include specific numbers to support findings."
What Claude Found
Claude correctly identified:
- 28% YoY revenue growth (Q2 2024 vs Q2 2023)
- 6% QoQ growth (Q2 2024 vs Q1 2024) - noted this was slower than Q1's 9% QoQ growth
- New business grew 35% YoY but expansion revenue only 18% YoY
- Flagged that slowing expansion revenue could indicate customer health issues
Claude observed:
- Gross margin declined from 82% to 79% YoY
- Traced this to higher infrastructure costs (+45% YoY) growing faster than revenue
- Operating margin at -15%, improving from -22% prior year
- Correctly calculated burn multiple: $1.35 for every $1 of revenue growth
Claude identified:
- Operating cash flow: -$2.1M (vs -$3.5M in Q2 2023)
- Cash on hand: $18.5M
- Current burn rate suggests 15-month runway
- Collections cycle improved: DSO down from 48 to 41 days
Claude analyzed:
- Accounts receivable growing slower than revenue (good - collections improving)
- Deferred revenue up 32% YoY (strong - indicates future revenue booked)
- Accounts payable as % of operating expenses increasing (potential vendor payment pressure)
Claude flagged:
What Claude Recommended
Claude noted the company is in "scale-up phase" where efficiency matters more than pure growth. Recommended shifting focus from growth-at-all-costs to improving unit economics.
Where Claude Excelled
Claude correctly traced relationships across income statement, balance sheet, and cash flow statement. Example: Connected deferred revenue (balance sheet) to recognized revenue (income statement) to understand booking vs revenue timing.
Spotted the QoQ growth slowdown (9% → 6%) without being explicitly asked to look for it.
Applied appropriate SaaS metrics (burn multiple, DSO, expansion revenue) without needing them defined.
Flagged gross margin compression as the most urgent issue - correct priority given the company's stage.
Where Claude Needed Help
Claude couldn't determine whether the metrics were good or bad relative to industry benchmarks without additional data.
Claude analyzed historical data well but needed prompting to project forward.
Couldn't incorporate market conditions, competitive dynamics, or strategic initiatives not mentioned in the financials.
Practical Workflow for Finance Teams
Export financials to PDF or paste into text format. Include:
Claude Models Overview: Compare Claude model capabilities and pricing Learn more
- Current period statements (all three: P&L, balance sheet, cash flow)
- Prior period for QoQ comparison
- Prior year same period for YoY comparison
- Any relevant management commentary
Prompt template:
"Analyze these financials for [Company] [Period]. Focus on:
Write for [audience: board/management/investors]. Include specific metrics to support findings."
After initial analysis, ask follow-up questions:
- "Explain the gross margin decline in more detail"
- "What's driving the infrastructure cost increase?"
- "Project cash runway under different burn scenarios"
Ask Claude to format findings:
- "Create an executive summary (under 250 words)"
- "List top 5 findings as bullet points for board deck"
- "Draft talking points for CFO to discuss with CEO"
Manual financial analysis for quarterly board prep: 4-6 hours
With Claude: 30-45 minutes (review data, prompt Claude, refine analysis, customize outputs)
You still review Claude's analysis for accuracy, but the initial synthesis and structure work is automated.
Accuracy Validation
We had a professional financial analyst review Claude's output:
Claude Pricing: Current pricing for Claude API and subscriptions Learn more
What Not to Use Claude For
Quick Takeaway
Claude 3.5 Sonnet performs financial analysis at the level of a competent junior analyst. It correctly identifies trends, calculates relevant metrics, spots risks, and provides reasonable recommendations.
For finance teams, this means:
- 80-90% time savings on routine quarterly analysis
- Faster identification of issues requiring deeper investigation
- More consistent analysis structure across periods
- Junior analysts can focus on strategic work instead of data synthesis
Claude doesn't replace financial expertise but handles the structured analytical work efficiently, letting finance professionals focus on interpretation, strategy, and decisions.
Get the Claude playbook in your inbox.
One weekly email for Claude and Claude Code users. Real workflows, no hype. Subscribe and we send you The Claude Power-User Cheatsheet.
— ¶ —

Luke Thompson
Luke Thompson is the founder of The Operations Guide, LLC and editor of The Claude Insider. Based in Jonesborough, Tennessee, he has spent years building AI-augmented business systems and automation workflows for operators and teams. He began working with large language models in production well before the current wave of consumer AI tools, integrating them into client workflows, content pipelines, and operational infrastructure. At The Claude Insider, he writes about Claude with the specificity of someone who uses it daily as a professional tool — not as a reviewer or commentator, but as a builder. His coverage focuses on what actually works: prompt patterns, API integration strategies, agentic workflows, and the real-world tradeoffs that practitioners face. He is not affiliated with Anthropic, PBC.
Articles are researched and drafted with AI assistance, reviewed and edited by Luke Thompson.
Know where AI can pay off in your company.
Take the free two-minute AI Readiness Assessment. See your score, the two gaps holding you back, and the next move worth making.


