Claude for Excel: What It Does Well, Where It Stops, and When Your Spreadsheet Needs a Database

Claude for Excel is Anthropic's add-in that puts Claude in a sidebar inside your workbook. It explains formulas with cell-level citations, changes assumptions without breaking the formulas downstream, finds the cause of a #REF!, and builds or fills in models. It needs a paid Claude plan (Pro, Max, Team or Enterprise) and runs in Excel on the web, Windows and Mac. It does not run macros or VBA. And it can't fix the real problem with most small-business spreadsheets: the ones that have quietly become the order system, the price book or the customer list. For those, the better move is to give the data a proper home and connect Claude to it, which the add-in now supports.

---

What Claude for Excel does

From Anthropic's documentation, the add-in can:

• Answer questions about the workbook, with citations you click to jump to the cell. "Walk me through how the revenue number in C42 is calculated."
• Change assumptions safely. It updates the input and keeps formula relationships intact, so dependent cells recompute.
• Debug errors. "Find the source of the #REF! error in the summary tab."
• Build or fill in models, from a description or into an existing template, across multi-tab workbooks.
• Do the native Excel chores: sort, filter, edit pivot tables, conditional formatting, data validation dropdowns.
• Pull outside data through connectors, and apply the Skills you have enabled in Claude.

It also warns before overwriting existing data, and it shares context with Claude for PowerPoint, Word and Outlook, so one conversation can span a workbook, a deck and your inbox.

Where it earns its keep is the workbook you didn't build: the model a former colleague left, the formula nobody dares touch. Ask it to explain the file before you change anything.

Plans, versions and install

• Plans: generally available on Pro, Max, Team and Enterprise. Not on the free plan. It counts against your normal Claude usage limits.
• Excel versions: Excel on the web; Excel on Windows with Microsoft 365, build 16.0.13127.20296 or later; Excel on Mac 16.46 or later.
• Not supported: Excel 2016 and 2019 perpetual or volume licenses, Excel on iPad, Excel on Android.
• Install it yourself: get "Claude for Microsoft 365" from Microsoft AppSource, open Excel, activate the add-in, sign in with your Claude account.
• Deploy it to the company: an admin assigns it to everyone, or to specific users or groups, from the Microsoft 365 Admin Center.

What it can't do

Anthropic is clear about the limits:

• No macros or VBA, and no data tables. If the workbook depends on a macro, Claude can read around it but won't run it.
• Not for audit-critical numbers without checking. Anthropic does not recommend it for final client deliverables without human review, audit-critical calculations without verification, or sensitive or regulated data without proper controls.
• Only trusted files. This is the one people skip. Anthropic warns that spreadsheets from outside sources, such as downloaded templates, vendor files and data imports, can contain hidden instructions that try to make Claude extract data, change records or do something destructive. Claude asks before a risky operation; read those confirmations, especially on a supplier's file.

Where your data goes

Worth knowing before a finance or sales team puts real numbers in it:

• Inputs and outputs are deleted on Anthropic's side within 30 days, with some exceptions Anthropic lists, and cached for a few hours after so recently closed workbooks keep their context.
• Chat history is stored in your browser, not on Anthropic's servers, and doesn't sync between devices.
• Your organization's custom retention settings don't apply to it, and its activity is not in Enterprise audit logs. Enterprise customers with the Compliance API get the sessions there, in public beta.

When the spreadsheet is the problem

Most small businesses we work with have one workbook that isn't analysis. It's the system: the price book, the order tracker, the stock list, the commission sheet. Several people edit it, copies get emailed around, and nobody is sure which version is right.

We rebuilt one of those for a wine distributor: a 20 MB price book with around 90 hand-typed tabs, one per sales agent. When we audited it, we found 7 pricing errors that had already gone out to agents, like prices that went up at higher volume tiers. Each tab was a copy someone had typed, and copies drift.

Claude for Excel could have helped find those errors faster. It couldn't have stopped the next ones, because the cause was the structure, not the formulas. The fix was moving prices into a database, edited in one place, with every agent's tariff generated from it on demand. Nobody types a price twice any more.

Signs your workbook has become a system:

• More than one person edits it, and you've lost work to someone else's copy.
• The same number is typed in more than one place.
• A mistake in it reaches a customer: a wrong price, a missed order, a wrong invoice.
• You export from another system into it every week, then retype the result somewhere else.

If two of those are true, the next step is not a smarter spreadsheet. See what custom software looks like for a small business and how to automate the retyping.

Connect Excel to the real data

The part most guides miss: the add-in can use connectors, including custom connectors your organization has enabled in Claude. So the figures in your workbook don't have to come from a CSV someone exported on Monday.

If your orders live in your own system, an MCP server in front of it lets Claude, in Excel or anywhere else, ask for "this month's orders by customer" and get live numbers. If your books are in QuickBooks, here is what Intuit's connector covers and when you need your own.

The same rules we hold any connector to apply here:

1. It acts as the signed-in person, with their permissions, not with a shared admin key.
2. Read and write are separate permissions. Most Excel work only needs read.
3. Anything that writes back shows a draft first, and a person approves it.
4. The limits live in the server, not in the prompt. A model can be talked into things; a database filter can't.

How to start

1. Install the add-in on one inherited workbook and ask it to explain the model. That's the cheapest win.
2. List the workbooks that are really systems, using the four signs above.
3. Pick the one where a mistake costs the most and move that one first. Keep Excel as a view if people like it, but stop making it the only copy.

Our published prices: a half-day scoping workshop is about $2,300 to $4,700, credited against the work, and a first workflow in production costs $5,000 to $18,000. Details here.

Related: Claude for finance teams, Claude for small business, and Claude connectors explained