When Anthropic announced general availability for Claude in Excel, PowerPoint, and Word — plus Outlook in public beta — on May 5, the headline feature was “cross-app context.” One Claude conversation, four Office apps, no re-explaining when you switch from spreadsheet to slide deck to memo.
That’s a real change. It’s also abstract. “Context that follows you” doesn’t tell you whether to install it tomorrow.
Here’s the single workflow that does. The one consultants on X this week are calling the “killer flow” — and once you’ve done it once, the cross-app feature stops being a marketing bullet and starts being the reason you keep the Claude pane open in Excel.
The workflow: from raw data to delivered deck without re-explaining
You have a 200-row Excel file with quarterly sales by region. Your manager wants a 5-slide deck for Friday’s executive review, plus a one-page memo for the board. Last quarter, that took three hours of moving between Excel, PowerPoint, and Word, copy-pasting numbers, re-formatting charts twice, and discovering at slide 4 that the regional grouping in your pivot is different from the regional grouping in your memo.
This quarter, in the cross-app world, it takes about 25 minutes. Here’s the exact sequence.
Step 1 (Excel): Analyze the data and shape the story
Open the workbook. Open the Claude pane (Ctrl + Option + C on Mac, Alt + Shift + C on Windows). Type:
“Look at this Q2 sales data. Find the three insights an exec would care about — the win, the surprise, and the risk. Then build a clean pivot that supports each one and add the charts as separate sheets.”
Claude reads the workbook, runs the analysis, builds the pivot, and lays out three labeled chart sheets — “WIN — APAC up 22%”, “SURPRISE — Mid-Market churn”, “RISK — Q3 pipeline gap.” This part already worked before the May 5 launch. The next step is where the change is.
Step 2 (PowerPoint): Open a blank deck and ask for the executive cut
Open a blank PowerPoint. Open the Claude pane. Type — and read this prompt carefully, because the cross-app trick is in what you don’t have to say:
“Build a 5-slide exec review deck using the analysis you just did in Excel. Title slide, then one slide per insight, then a closing ‘what we’d do next’ slide. Use the chart sheets I made — don’t redraw the charts.”
That phrase “the analysis you just did in Excel” is the cross-app moment. Pre-May 5, you’d have had to re-paste the Excel context, re-describe the three insights, and re-import the chart images. Now Claude already has it. It builds the deck, pulls in the three chart images from the Excel chart sheets you labeled, writes the headlines and the speaker notes, and stops.
Per the Anthropic cross-app docs, this works because the same Claude conversation — not the same Office file, the same Claude conversation — carries across apps as long as both apps have the Claude add-in active and the user is signed in with the same Claude account. The conversation history is the connective tissue, not Microsoft Graph.
Step 3 (Word): Open a memo and ask for the board version
Open a blank Word doc. Same Claude pane. Type:
“Now write a one-page board memo summarizing the deck. Use plain prose, no bullets, no headers. Lead with the win, surface the risk in paragraph two, ask for the resource we need to close the Q3 pipeline gap in paragraph three.”
Claude writes the memo. It already knows the three insights, the “what we’d do next” slide, and the tone you’ve been using in the deck. The memo reads like a single author wrote it — because functionally, one Claude session did.
Step 4 (Outlook beta): Compose the send
If your org has the Outlook beta enabled (it’s free on all paid Claude plans as of the May 5 launch), open Outlook and type:
“Draft the email that sends the deck and memo to the exec team for Friday’s review. Tone: confident but acknowledging the Q3 gap. Three sentences max. Attach the deck and memo.”
The email lands in your drafts, the deck and memo attached. You glance at it, edit one sentence, hit send.
Twenty-five minutes door-to-door, on a workflow that used to be a Tuesday afternoon.
Why this works (the technical bit)
The cross-app context isn’t magic. Three concrete things make it real:
One conversation across four apps. When you open the Claude pane in Excel and then open it again in PowerPoint with the same Claude account signed in, you’re not starting a new conversation. You’re continuing the same one. The conversation memory is in the Claude account, not the Office file. This is the single most important mental model shift — stop thinking “Claude in Excel,” start thinking “my Claude conversation that happens to be looking at Excel right now.”
Read access to the workbook, deck, and document. When you ask Claude a question in PowerPoint about the Excel analysis from earlier, Claude doesn’t re-read the Excel file from disk. It uses what’s already in the conversation. But when it builds the deck, it does need to write into PowerPoint — and the same is true in reverse if you ask it later to “update slide 3 with the new APAC number from the Excel file.” Per the Anthropic blog announcement, Claude can “make changes to them directly” — edit cells while preserving formulas, generate slides connected to live Excel data, update charts when assumptions change.
Manual cross-app activation. For Team and Enterprise customers, an organization owner has to toggle Anthropic Console → Organization settings → Office agents → Let Claude work across apps on before this works. For Pro and Max users, it’s on by default. If you’re on Team/Enterprise and the cross-app step in the workflow above doesn’t seem to know about Excel, that toggle is the first thing to check.
What the production customers are doing
Three early-customer stories Anthropic published with the launch are worth reading because they hint at where this gets actually load-bearing:
- Citadel uses Claude in Excel on the investment-modeling side, where the firm’s “investment professionals live in data and analytical models” (Atte Lahtiranta, Head of Core Engineering). The cross-app pattern matters here because the same model needs to land in a memo, a board deck, and an internal IC packet — and one missed number across those four artifacts is a costly mistake.
- ServiceNow is using it as a context-preservation tool: “Claude does the work in Excel itself, instead of asking us to move content between tools” (Rajeev Sethi, GVP Enterprise Technologies). For an enterprise org with 20,000+ employees and an army of analysts, removing the copy-paste-between-apps step removes a meaningful percentage of total knowledge work.
- BCI is using it on the communications side: building a personal style guide for executives so their EAs can draft emails in the exec’s voice (Ben Letalik, Sr. Director, Digital Transformation & Innovation). Cross-app makes this work because the style guide lives in Word, the source corpus is in Outlook, and the drafted output is back in Outlook.
On X this week, three patterns dominate the consultant chatter:
- Financial deal review — upload Excel client data, prompt for sales/EBITDA/leverage analysis, surface anomalies, write the memo. @fmeyrath posted a live walk-through May 11 with screenshots, with the caveat: “pretty good for a quick review, but needs human oversight.”
- McKinsey-style strategy deck from rough notes — @heynavtoor on May 11 documented turning Excel data plus a rough outline into a polished deck in a single session.
- Formula debugging across tabs — @Gianna3328 on May 8 documented fixing a coworker’s overnight
#REF!error in 3 seconds by tracing logic across tabs that they wouldn’t have spotted manually.
What this means for you
If you’re a consultant or analyst who builds decks and memos from data, this is the highest-leverage workflow change you’ll get this quarter. The 3-hour pattern becomes the 25-minute pattern. Plan to use it twice this week on real work before you try to evaluate it.
If you’re a financial professional doing DCF, LBO, or sensitivity analysis, the cross-app handoff is most valuable where the work product is a deck or memo built on top of an Excel model. The Citadel customer story is the canonical pattern — model in Excel, talking points in Word, presentation in PowerPoint, one consistent set of numbers across all three.
If you’re an executive assistant or chief of staff, the BCI style-guide pattern is your version: build a Word style guide from the executive’s prior writing, then have Claude draft emails in Outlook in that voice. The cross-app context here is the connective tissue that makes “Claude knows how I sound” actually true.
If you’re in education, government, or any document-heavy workflow, the Japanese educators on X this week (notably @teacher_manager on May 12) are using it for school admin documents — proposal in Word, supporting data in Excel, summary memo for the board in PowerPoint, parent communication in Outlook. Same four-app loop, completely different domain.
If you’re a Microsoft 365 Copilot user comparing this to Copilot’s cross-app behavior, the honest read from independent posters this week is that Claude wins on reasoning quality and formula preservation, and Copilot wins on tenant integration (SharePoint, Teams, Power Platform). On personal Macs and small-team Microsoft 365 tenants, several users (notably @OrenCShur on May 8 and @iam_elias1 on May 9) say Claude feels “ahead.” In full enterprise ecosystems with deep Microsoft Graph integration, the contest is closer.
If you’re a CTO evaluating which to standardize on, the right answer is probably both for a quarter. Claude wins on the focused analytical workflows (Excel modeling, deck building, memo drafting). Copilot wins on the broad tenant-grounded chat (asking Copilot about a SharePoint document it can find that Claude can’t). The cross-app context launch doesn’t change that picture, but it does shrink the gap.
What it can’t do
A few honest limits.
- It doesn’t replace VBA, Power Query, or external database connections. Multiple consultants on X this week called this out as the boundary. If your “workflow” depends on a macro that pulls from SAP, Claude doesn’t touch it. The add-in works on what’s in the workbook.
- It doesn’t share context with Microsoft Copilot. “Cross-app” means cross-app for Claude. Copilot and Claude don’t talk to each other; they’re parallel side panes that don’t share session state.
- It needs the cross-app toggle enabled for Team/Enterprise plans. Pro and Max are on by default. If you’re on Team/Enterprise and you get confused responses, check Anthropic Console → Org settings → Office agents.
- Outlook is still beta as of May 12. Per the Anthropic launch post, Outlook integration is available on all paid plans but flagged as public beta. Expect rough edges through Q3 2026.
- It’s not free. The Excel, PowerPoint, and Word add-ins require Claude Pro ($20/mo), Max, Team ($30/user/mo), or Enterprise. Free Claude accounts can use claude.ai in a browser but cannot use the side pane in Excel.
- It doesn’t see other apps that aren’t open. If you ask Claude in Excel “what does the deck say?” and PowerPoint isn’t running with that file open, Claude will tell you it can’t see the deck. Cross-app context follows the conversation, not the file system.
The bottom line
The cross-app launch is one of those features that sounds like marketing copy until you actually run the four-step workflow above. After that, the question stops being “do I need this?” and starts being “how much of my week was the copy-paste-between-apps loop, and what would I do with that time back?”
For most knowledge workers who build decks and memos from data, the answer is: a lot, and several useful things. Install it this week, run the deck-and-memo workflow on a real assignment, and check back in seven days. The time savings show up that fast.
If you want to go deeper on building the prompt patterns that get the most out of Claude in Microsoft 365 — including the chart-preservation trick, the speaker-notes prompt that actually produces speaker notes, and the memo voice-matching template — our Claude Cowork Essentials course covers the seven cross-app patterns we’ve found ourselves reusing weekly.
Sources
- Anthropic: Collaborate with Claude across Excel, PowerPoint, Word, and Outlook (May 5, 2026)
- Anthropic help center: Work across Microsoft 365 apps
- Anthropic help center: Use Claude for PowerPoint
- Anthropic help center: Use Claude for Excel
- Claude for Microsoft 365 hub
- The New Stack: Claude can now follow users across Outlook, Word, Excel, and PowerPoint
- MindStudio: How to Use Claude in Microsoft Excel and Word — cross-file context explained
