Anthropic just shipped a feature that is easy to miss if you only watch the demo for thirty seconds. Claude can now keep the same conversation context across Excel and PowerPoint at the same time. Open both files, ask Claude to help, and it can work from the spreadsheet and the presentation together instead of treating each file like a separate job.
That sounds technical. It is actually very practical.
For most small and medium businesses, the annoying part of office work is not making one chart or one slide. It is the handoff between them. Someone updates numbers in a spreadsheet, then someone else copies those numbers into a deck, rewrites the takeaways, fixes a mismatch, and hopes nothing changed again before the meeting.
Claude's new cross-app context points straight at that bottleneck.
What Anthropic actually launched
In Anthropic's demo on X, Claude works with multiple Microsoft Office files at once and carries the full conversation across them. That means the assistant does not lose the thread when you move from the workbook to the presentation. If you asked for a revenue summary in Excel, Claude can use that same context when helping draft the PowerPoint slides that explain it.
Alex Albert from Anthropic framed it well: knowledge work is starting to look a lot like agentic coding looked last year. That feels right. First came isolated prompts. Then came workflows. Now the software is starting to understand the full working set instead of one window at a time.
That is the important part.
Why this matters to regular businesses
Small businesses live in spreadsheets and slide decks.
Sales teams track pipeline in Excel, then turn it into a weekly forecast deck. Operations teams manage budgets and staffing plans in spreadsheets, then present those updates to owners or managers. Agencies build client reports in Excel, then package the story in PowerPoint. Finance teams close the month in one file and explain it in another.
Most of that work is repetitive. Not simple, but repetitive.
A cross-app assistant can shorten three common steps:
- pulling the right numbers from the source file
- translating those numbers into plain-English takeaways
- keeping the presentation aligned when the spreadsheet changes
That does not remove judgment. It removes busywork.
The real win is fewer broken handoffs
The best way to think about this feature is not "AI in Office." Microsoft has had AI stories for a while. The better framing is "fewer broken handoffs between related files."
That matters because handoffs are where mistakes creep in.
A manager asks for a board deck. The analyst updates the spreadsheet. The slide still shows last week's number. A client report gets copied over by hand and one label stays wrong. Someone asks a question in the meeting and now a team member is clicking between tabs trying to remember which file had the final version.
If Claude can understand both the numbers and the presentation context in one thread, that reduces the chances of those small errors turning into expensive embarrassment.
For an SMB owner, this is not about novelty. It is about saving an hour here, two hours there, and avoiding the kind of sloppy mismatch that makes a team look less sharp than it really is.
Where this will show up first
The first clear use cases are boring in the best possible way:
- monthly business reviews
- sales forecast decks
- client performance reports
- budget presentations
- hiring and headcount planning
- franchise or location reporting
Those are exactly the places where teams already bounce between tables, charts, summaries, and presentation language.
If Claude can move fluidly between the workbook and the deck, one person can produce a stronger first draft faster. A small team may not need a separate analyst, writer, and presentation cleaner for every update. One operator with good judgment and a solid source file gets a lot more leverage.
What business owners should not assume
This does not mean the deck is suddenly correct because an AI touched it.
If your spreadsheet has messy inputs, unclear definitions, or bad assumptions, Claude can carry those problems across apps just as efficiently as it carries the good context. Garbage still travels fast.
It also does not mean every employee will know how to prompt well enough to get useful output. Teams will still need basic standards: which spreadsheet is the source of truth, what must be reviewed by a human, and what claims need a second look before they go to a client or leadership.
So no, this is not magic. It is leverage. There is a difference.
Barista Labs take
This is one of the more believable AI productivity updates we have seen lately because it targets the messiest part of normal office work. Not writing a sentence. Not making a chart. Connecting the numbers to the story without making people do the same manual shuffle all day.
For small businesses, that is where the value lives.
The teams that benefit first will be the ones already doing frequent reporting, planning, and presentation work. If your company spends a lot of time turning spreadsheets into decisions, this feature is worth watching closely.
The big shift is not that Claude can help in Excel or PowerPoint. It is that the walls between those tasks are starting to matter less. Once the assistant can follow the work across files, the average business gets something more useful than a clever demo.
It gets continuity.