Claude for data analysis: from spreadsheet to answer, without writing formulas

What Claude actually does with data

Give Claude a spreadsheet or CSV and you can talk to it like an analyst: which product drove the revenue jump in March, which customers went quiet this quarter, what does the trend look like if you strip out the one-off. It reads the whole file, runs real calculations on it, and can chart what it finds, all from plain-English questions.

The underrated half is explanation. Paste in the inherited spreadsheet with the seventeen-clause nested formula nobody dares touch, and ask what it does. For most teams, understanding the data they already have is worth more than any new analysis, and it's the part Claude does with zero setup.

A realistic workflow

The pattern our trainees settle into looks like this:

• Start with a question, not a dataset. 'Why did April dip?' beats 'analyse this' every time — vague prompts get vague summaries.
• Upload the file and ask Claude to describe the data first: columns, ranges, gaps, oddities. This catches import problems before they become wrong answers.
• Ask your real questions one at a time, and ask it to compute rather than eyeball: totals, medians, cohorts, deltas.
• Have it chart the finding, then ask what would make the chart misleading. It's surprisingly good at critiquing its own picture.
• End by asking for the three follow-up questions the data raises. That's the analyst habit most spreadsheets never get.

None of this needs formulas. It needs clear questions and a little scepticism, which is the same skill split we teach everywhere else: the tool does the mechanics, you do the judgement.

Claude or Excel? Wrong question

Excel (or Sheets) remains the system of record: it's where the data lives, where auditable models belong, and what the rest of the company opens. Claude is the layer on top — the analyst you question, the explainer of what you inherited, the fast first pass that tells you where to look.

The honest limits: very large files need summarising or splitting before Claude can work with them, and anything regulated or auditable should end life as a spreadsheet model a human signed off, not a chat transcript. And check your organisation's data policy before uploading anything sensitive — on business plans, Anthropic doesn't train on your data, but your own governance still decides what leaves your systems.

The habit that keeps it honest

Language models are confident, and confidence is not accuracy. The failure mode in data work isn't usually a wild hallucination; it's a plausible-looking number produced by estimating instead of calculating. The fix is a habit, not a tool: ask Claude to show its working, tell it explicitly to compute rather than approximate, and spot-check one number per session back against the source file. It's the same reflex worth building wherever Claude touches business content, turning a meeting transcript into decisions and actions is another everyday case where a wrong name or number is the real risk, not a wild answer.

Teams that build that verification reflex get compounding value from AI analysis. Teams that don't eventually present a wrong number to a board. This judgement layer — when to trust, how to verify — is the core of what we teach in our hands-on AI training, and it matters more than any prompt template.

When one-off analysis becomes a workflow

The chat window is for exploration. The moment you're re-uploading the same report every Monday, you've outgrown it: with Claude Code and MCP, the analysis can connect to the live data source and run on schedule — the same pattern we cover in building business apps with Claude, and it's within reach even if nobody on your team writes code.

Start manual, prove the questions are worth asking weekly, then automate. Teams that automate first usually automate the wrong report.