AI Tools · Marketing Analytics & Reporting
Claude in Excel for Marketers
What the Excel add-in is actually good for on a marketer's spreadsheets, and the verification habits that keep you out of trouble.
Marketing runs on exports. Ads platform, GA4, the CRM, the email tool, the SEO crawler. Every one of them hands you a CSV and walks away.
What happens next is a marketer in Excel at 5pm, doing VLOOKUPs against a naming convention nobody agreed on.
Claude in Excel is a sidebar that lives inside Excel and reads the workbook you have open. It doesn’t connect to your ad accounts and it won’t replace your BI tool. It works on the export. That’s a narrower promise than the marketing around it suggests, and it’s also where most of my bad hours used to go.
This guide covers what it’s good at, what to keep it away from, and the habits in between. It went generally available in May 2026 and costs $20/month on the Pro plan, which is why I think it’s worth your afternoon.
At a Glance
- It’s GA and it’s $20. Claude for Excel went generally available on May 7, 2026, on Pro, Max, Team, and Enterprise. Pro is $20/month ($17 billed annually). The Free plan doesn’t include it.
- You need a Microsoft 365 subscription. Excel on the web, Excel for Windows (build 16.0.13127.20296+), or Excel for Mac (16.46+). Excel 2016 and 2019 perpetual licenses do not work. Neither does iPad or Android.
- It reads your open workbook and cites cells. Every answer points at the cells it used, and you click through to check. That citation is the whole verification story.
- It’s strongest on cleaning and explaining. Standardizing a messy export, splitting columns, tracing where a number came from, finding the broken formula. Weakest on anything where the logic depends on a definition only you know.
- It can now do the Excel things it couldn’t in January. Sort, filter, edit pivot tables, apply conditional formatting, create data validation dropdowns. Still no macros or VBA.
- Client data deserves a second thought. Free, Pro, and Max run on consumer terms and sit outside Anthropic’s SOC 2 / ISO / HIPAA scope. Team and Enterprise run on commercial terms. If you handle client data under contract, that’s the distinction that matters.
The platform export you just downloaded is a file you didn’t write. That’s the one category Anthropic explicitly warns you not to hand it.
Three Ways to Put Claude on a Spreadsheet
Before the use cases, the choice that decides everything else. There are three ways to get Claude and a workbook in the same room, and most people only know the first one.
1. Upload the file to a chat. The obvious move, and the most expensive one. An .xlsx carries a lot of structural noise, and a big multi-tab workbook will burn through context fast, sometimes before it reaches the tab you cared about.
If you go this route, orient it first: a screenshot of the header row, or a couple of lines explaining what the columns mean. Same as you’d do for a new hire who’s never seen the file.
2. Bring Claude into the workbook. This is the add-in, and it’s the mode this guide is about. Claude sits in a sidebar inside Excel, reads the open workbook directly, and cites the cells it used. No upload, no token cost for the file itself, no reformatting.
If you’ve been told spreadsheets are a poor thing to hand an AI, that’s true for uploads. It isn’t what’s happening here. Different mode, different rules.
3. Have it build an artifact. For analysis you rerun constantly, don’t ask for a spreadsheet at all. Ask for a small interactive tool that reads your data and produces the view you need, one you can share with a client or a colleague. Think of it as a pivot table that updates itself. Best for the monthly report you regenerate for the same audience.
The right answer depends on what happens after. If the output has to leave your hands as a spreadsheet, work in the spreadsheet. If the analysis is just for you, upload or artifact may be faster. If it’s the same report every month, build the artifact once and stop rebuilding it.
Before You Install
Check your Excel first. This is the single most common reason someone tells me the add-in doesn’t work. You need a Microsoft 365 subscription, not a perpetual license with a big year on it. Excel 2016 and 2019 perpetual or volume licenses are explicitly unsupported, as are iPad, Android, and older M365 builds.
Install it. Microsoft AppSource, search “Claude for Microsoft 365.” Then in Excel: Home > Add-ins on Windows, or Tools > Add-ins on Mac. Sign in with your Claude account. No second license, no Microsoft surcharge.
If you’re on a company machine, your admin may need to allow it. Microsoft 365 Admin Center > Settings > Org Settings > User owned apps and services > “Let users access the Office Store,” then Settings > Integrated apps.
One gotcha to pass along if IT hits a wall: when an organization uses Microsoft Entra Privileged Identity Management for admin roles, the Integrated apps page doesn’t recognize PIM-activated roles and deployment fails. Known Microsoft issue, tracking ID 11126536.
One toggle worth knowing. “Let Claude work across files” lets one conversation span your open workbook, deck, doc, and inbox. It’s on by default for Pro and Max, off by default for Team and Enterprise, and it’s per-device. If cross-app isn’t working on a work seat, that’s why.
The Spreadsheets Worth Pointing It At
These map onto what the tool does well: cleaning, explaining, multi-tab reasoning, and template population.
Platform exports and data cleaning. The least glamorous item on this list and the one I reach for most. Standardizing date formats, splitting a Full Name column, reconciling campaign naming across two platforms that disagree, flagging duplicate emails before a send.
Campaign performance analysis. Point it at an export and ask in plain language which channels moved, where CPA climbed, which campaigns burned spend while CTR fell. It cites the cells, so you’re checking rather than trusting.
Budget and media plan modeling. Building a plan with quarterly columns and a row per channel, then flexing the growth assumptions to see what breaks. It updates values while keeping formula relationships intact, so downstream cells recompute correctly.
Attribution models. Weighted first/last/middle splits, INDEX-MATCH against campaign IDs, comparing what two models say about the same period.
The monthly reporting rebuild. Conditional formatting that flags anything under target, dropdowns for campaign types, lookup formulas against a reference tab. The mechanical parts of report-building, not the analytical ones.
SEO and content exports. Crawler output, ranking exports, content inventories. Deduping, categorizing by intent or cluster, finding the pages that appear in one export and not the other.
A/B test readouts. Laying out variant performance side by side and being explicit about what the numbers do and don’t support. Ask it to state the caveats, not just the winner.
Inherited models. My favorite, and the one nobody expects. Someone left, and you own their spreadsheet now. “Walk me through how this number is calculated” turns a lost afternoon into a conversation.
The Spreadsheets To Be Careful With
Anthropic publishes a “not recommended for” list. Two lines on it should land for anyone doing client work:
- Final client deliverables without human review.
- Audit-critical calculations without verification.
Translated into marketing terms:
- The number in the client deck. Use it to build the analysis. Check the number yourself before it goes in a slide with your logo on it.
- Anything that drives billing. Media spend reconciliation, commission calculations, retainer true-ups.
- Forecasts leadership will act on. It’s good at building the model. It has no idea which assumptions are politically load-bearing.
- Anything where the logic depends on a definition. What counts as a conversion, which spend is in-channel, how you treat brand versus non-brand. It will apply a reasonable definition confidently, and it may not be yours.
- Client data under a contract that restricts subprocessors. Check the terms before the export goes anywhere.
The rule that covers all of it: Claude can build the analysis. You own the number.
Prompts: Understanding and Cleaning
Copy these. They lead with explanation before edits, which is the order that keeps you out of trouble.
Understanding a file you didn’t build
- “Walk me through how the blended CAC in cell H12 is calculated. List every input cell it depends on.”
- “Summarize what each tab in this workbook does and how they connect.”
- “What assumptions drive this forecast? Cite the cells.”
Cleaning
- “Standardize every date in column C to YYYY-MM-DD and flag anything you couldn’t parse.”
- “Split the Full Name column into First Name and Last Name. Flag rows with more than two name parts.”
- “Our campaign names follow the pattern CHANNEL_GEO_QUARTER_AUDIENCE. Flag every row in column A that doesn’t match, and tell me what’s wrong with each.”
- “Find duplicate email addresses in column D and mark the duplicates, keeping the earliest signup date.”
Prompts: Analysis and Checking
Performance analysis
- “Which channels had the largest CPA increase month over month? Sort by dollar change, not percentage.”
- “Flag every campaign where spend rose more than 20% while conversions fell. Show the cells.”
- “Build a summary table of the top 10 campaigns by ROAS, with spend, conversions, and CPA.”
- “Add conditional formatting that turns any cell below our target CPA green and above it red.”
Budget and modeling
- “Create a media plan template with columns for Q1 through Q4, a row per channel, and formulas for totals and year-over-year change.”
- “Flex the paid social growth rate from 5% to 15% and show me the impact on the annual total.”
- “Build a weighted attribution model: 40% first touch, 40% last touch, 20% split evenly across the middle.”
Checking your own work
- “Do the channel subtotals on the summary tab match the detail tab? Show me any line that doesn’t reconcile.”
- “Find the source of the #REF! error in the reporting tab.”
- “Check that every campaign in the spend tab also appears in the conversions tab, and list the ones that don’t.”
The Client File Problem
Read this one twice. It’s the risk that doesn’t announce itself.
Anthropic ships an explicit warning: only use Claude for Excel with trusted spreadsheets. Files from outside your organization can carry hidden instructions, buried in cells, formulas, or comments, that manipulate the add-in into extracting data, modifying records, or taking destructive actions. Anthropic’s own testing confirmed those scenarios are possible.
Now look at your downloads folder. Platform exports. A client’s budget template. A vendor’s reporting workbook. That template someone posted on LinkedIn. An agency partner’s attribution model. Most of the spreadsheets you touch, you didn’t write.
You don’t have to stop working with outside files. You have to change one habit.
Paste the data into a workbook you control. Don’t point Claude at the file someone sent you.
Open their file yourself, copy the data into your own workbook, and let Claude work there. Thirty seconds, and the whole category of risk goes away.
When Claude does propose something risky, it asks you to confirm first. I read those confirmations instead of clicking through them, and I’d tell you to do the same on anything that came from outside.
What It Can't Do
Set expectations before you build a workflow on top of it.
- No macros or VBA. If your reporting workbook runs on macros, that part stays manual.
- No data tables. The Excel what-if feature specifically.
- No platform connections. It doesn’t talk to Google Ads, GA4, HubSpot, or your BI tool. It works on the export.
- Only open workbooks. It can’t create, open, close, or switch files on its own.
- No scheduled runs. Everything happens with you sitting there. There’s no “email me this report every Monday.”
- Long sessions lose detail. Conversations get auto-compacted to avoid running out of context, and it doesn’t announce what it dropped. The reasoning behind a decision from an hour ago may be gone. Capture decisions outside the chat.
- No published size limits. Anthropic doesn’t publish a workbook size or row ceiling. Performance degrades on large files well before any hard wall. Test your own worst-case export instead of trusting a number.
- Dates are a weak spot. Sorting and reasoning about dates is where these tools are least reliable. Be explicit about format, and check the result.
Your Verification Checklist
Seven rules. Each takes about a minute, and together they’re the difference between a time-saver and an incident.
- Work on a copy. Anthropic’s own best practice: start from a trusted copy before asking it to edit widely.
- Never point it at a file someone sent you. Paste the data into your workbook instead.
- Ask before you tell. Explain and audit first, edit second.
- Click every citation. If you don’t click through, you’ve given up the only verification the tool offers.
- State your definitions up front. What counts as a conversion, which spend is in-channel, how you handle brand. It will guess otherwise, and confidently.
- Check the totals by hand. Every number that goes in a deck, an invoice, or an email to a client.
- Read the overwrite warning. It tells you before it overwrites something. That warning is doing a job.
Where This Fits With Your Stack
Someone will ask whether this replaces something you already pay for. It doesn’t.
The platforms are the system of record. Google Ads, GA4, the CRM, the ESP. That data stays where it is.
Your BI tool is the system of monitoring. Looker, Power BI, whatever dashboard leadership opens on Monday. Still its job.
Excel is the system of thinking. It’s where you go when the dashboard doesn’t answer the question: the ad hoc analysis, the model nobody built a view for, the reconciliation between two tools that disagree.
Claude in Excel is a layer on the thinking, not on the record. It makes the export faster to reason about. It competes with nothing in your stack, and it doesn’t integrate with anything in your stack either. That’s the shape of it.
Start Here This Week
Don’t roll it out to the team. Try it on one file, on something that doesn’t matter yet.
- Pick a finished month. Last month’s campaign export, already reported, nothing riding on it.
- Make a copy. Then open the copy.
- Ask it to explain the workbook before you ask it to change anything. Click the citations and see whether they hold up.
- Try one cleaning task. A messy export, inconsistent naming, duplicate rows. This is where it earns its keep first.
- Then try one analysis task. Something you already know the answer to, so you can grade it.
- Write down where it was wrong. It will be wrong somewhere. That list is what makes you good at using it.
Six steps, one afternoon, one seat. That’s the whole pilot.
Measure the Right Thing
The temptation is to track how much you’re using it. Usage is not value.
Pick one number that means something (hours back in your week) and hold the pilot to that. I’d rather you use it twice a week on the right task than every day on the wrong one.
Make It Yours
The default setup is somebody else’s. Same prompts, same three use cases, same disappointment when it doesn’t fit how you actually work.
Yours gets built by subtraction. You try it on ten things, six are a waste of an afternoon, and the four that stick become the reason you keep the seat. Nobody can hand you that list. It comes out of your own bad afternoons.
So open last month’s export. Make a copy. Ask it one question you already know the answer to. Then keep what earned its place and drop the rest.
That’s how this becomes a tool instead of a subscription you feel guilty about.
Alec
Want the rest of the AI playbooks?
Every Friday I send one real workflow I'm running, broken down to the prompts and the receipts. No jargon, no hype.