Claude Now Runs Inside Excel, Word, and PowerPoint. Here's the Workflow Worth Setting Up First.
Three Office add-ins. One shared context. Most operators have no idea this exists.
Tuesday got a lot of AI coverage because of the GPT-5.5 Instant swap. Buried in the same news cycle, Anthropic confirmed something that matters more for most operators: Claude now covers the full Microsoft Office suite.
Excel. Word. PowerPoint. All three have native Claude add-ins. All three share context with each other in a single conversation. You analyze a spreadsheet in Excel, switch to PowerPoint, and Claude already knows the data. Switch to Word, and it knows both. No copy-pasting. No re-explaining. One continuous session across three applications.
Outlook is next.
Most operators who use Microsoft 365 every day have no idea this exists. This is worth three minutes of your time.
What each add-in actually does
Claude for Excel shipped in beta in October 2025 and became available to all Pro subscribers on January 24, 2026. The key capability: Claude reads your spreadsheet at the workbook level, not cell by cell. It understands multi-tab workbooks, explains calculations with cell-level citations, and writes formulas from plain English. You describe what you want to calculate. It writes the formula. You keep your formula dependencies intact.
That last part matters more than it sounds. Most AI tools that touch spreadsheets either break formulas or work in isolation from the workbook’s structure. Claude reads the model as a whole.
Claude for PowerPoint launched March 11, 2026, with something most slide tools get completely wrong: it reads your entire template: the slide master, the layouts, the fonts, the colors. When you ask it to build slides, the output follows your brand guidelines and uses your actual layout structure. The visuals it produces are native editable PowerPoint objects, not static images.
Claude for Word landed April 13, 2026. The standout: edits appear as tracked changes. If you’re using Word for contracts, proposals, or any document where version control matters, this is how it should work. Claude marks what it changed. You decide what to accept.
The part most operators are sleeping on
The three add-ins share context.
That sounds like a minor technical detail. In practice it changes the workflow entirely.
Here’s what I mean. For three years, the pattern with AI and Office work looked like this: you open Claude in a browser tab, paste in your data, get output, copy the output into your document, repeat. Every step breaks the thread. Every switch between the AI window and your document loses context. You spend half your time re-explaining what you already told the model.
The cross-app context closes that loop. When you’ve been analyzing a financial model in Excel and you switch to PowerPoint and say “build a five-slide summary of this analysis,” Claude already knows the model. It understands which numbers matter and why. When you then open Word and ask for the accompanying written brief, it knows both the data and the slides.
The workflow I keep seeing operators get the most leverage from: data review in Excel, executive summary deck in PowerPoint, client-facing report in Word. Previously, this was a three-session task with a lot of copy-paste in between. Now it’s one session.
The Anthropic team describes the cross-app behavior this way on their support page: “If you’ve been building a financial model in Excel and ask Claude to create a summary deck or draft an investment memo, Claude already understands the model’s structure and key outputs, so you don’t need to re-explain.”
That’s the right framing. The add-ins don’t just put Claude inside your tools. They let Claude hold the full context of your work across multiple tools at once.
There are also Skills
The update that came alongside the March cross-app release introduced reusable Skills: saved prompt workflows that apply automatically when Claude is working in any of the apps.
If you’ve built a prompt that enforces your team’s financial modeling conventions in Excel, and a separate prompt that matches your pitch deck template structure in PowerPoint, you can save those as Skills. When you run a cross-app session, Claude uses the right Skill in the right app as it moves through the workflow.
For teams doing the same type of work repeatedly, this is where the real time savings are. The first time you run an analysis-to-deck workflow, you set it up. The fifth time, it runs with almost no instruction overhead.
What’s honest about the current state
These add-ins are still maturing. There are things worth knowing before you commit.
The Excel add-in handles most standard workbooks well, but very large or complex multi-tab models with unusual structure can still trip it up. If you’re working with thousands of rows or non-standard table structures, test before you depend on it for client deliverables.
The PowerPoint template reading is genuinely good for standard corporate templates. Custom or highly complex slide masters may produce outputs that need adjustment. The output is always editable, so this is a fixable problem, but not a zero-effort one.
The Word add-in’s tracked changes feature is useful, but if you’re used to a specific review workflow with legal or compliance teams, verify how the tracked changes export and display before building a process around it.
And the cross-app context is still in beta. Anthropic labels it as such on the support page. For most business documents it works exactly as advertised. For unusually large files or very long cross-app sessions, it can occasionally lose thread. Worth testing with your actual file types before using it for high-stakes work.
Availability is on Pro ($20/month), Teams ($25/month per seat), and Enterprise plans. Free accounts don’t get the add-ins.
How to set it up in five minutes
Go to Microsoft AppSource and search for “Claude by Anthropic for Excel.” Install it. Do the same for PowerPoint and Word. Activate each from your add-ins menu. Sign in with your Claude credentials. That’s the full setup.
For Teams or Enterprise, an admin deploys the add-ins via the Microsoft 365 Admin Center under Settings, then Integrated Apps, then Add-ins. Individual users can activate after that without any additional steps.
To use cross-app context: just work in sequence. Analyze in Excel, then open PowerPoint with Claude active, and it picks up the session. No settings toggle required.
Three workflows to run first
One: open a spreadsheet you regularly pull numbers from for reporting, and ask Claude to explain the key trends in plain language. This tells you how well it reads your specific file structure before you try anything more complex.
Two: run the full Excel-to-PowerPoint flow on something low-stakes. A weekly report, an internal summary, anything where a rough first draft is still useful. This gives you a real read on how much editing the output needs before you trust it for client work.
Three: if your team does contract reviews or proposal editing in Word, run one document through the Claude for Word add-in with tracked changes. See how the output lands with your review process. The tracked changes behavior is the most useful part of the Word add-in for business teams.
The pattern I keep seeing with operators who are getting the most out of AI right now: they’re not adding new tools. They’re installing AI into the tools they’re already inside every day. The Microsoft 365 suite is where most business operators spend the majority of their working hours. Putting Claude there, with cross-app context, is a different kind of leverage than spinning up a separate AI workflow.
If you want to think through which of your recurring document workflows make the most sense to route through the Office add-ins, that’s the kind of thing we work through in an AI Clarity Call. You can book one at muddventures.com/book.
Andrew
Full archive at muddventures.substack.com.
Building something with AI and want to be in a room with operators doing the same: whop.com/abra-ai.