Everything Claude Released in September 2026: What Matters for Procurement Teams
Claude’s September updates change where procurement work starts, how it becomes a deliverable, and what teams can govern.
We use Claude Cowork extensively to run Molecule One, and we build procurement workflows for customers. One small irritation kept turning up in both settings. If I started a piece of work in Chat and then needed Cowork to make an actual deliverable, I had to prepare the context and paste it into a new session. Both windows lived in the same app. It felt absurd that a tool capable of automating multi-step work still needed me to do that handover by hand.
That is the September change I care about most. Anthropic is bringing Chat and Cowork into one conversation, so a question can develop into a task with tools and finished files without restarting elsewhere. For procurement teams, that removes a real break in the workflow from research to analysis to an RFP draft or supplier brief.
September also brought Claude Opus 5.5 and Claude Sonnet 5.5. We are working on a full review and comparison of those models and will publish it soon. This article focuses on the product changes a procurement leader can act on now: the Chat and Cowork merger, Claude Docs and Slides, Salesforce, Claude Tag in Slack, smart reports, and the Claude Marketplace.
Claude Chat and Cowork merge: what changes for procurement work?
Anthropic says users no longer have to choose a mode before they begin. In the new Claude experience, the same conversation can answer a quick question, search, read connected material, run code and produce a document, spreadsheet or presentation. Existing chats, tasks, projects and settings carry over. I can start by asking what has changed in a supplier market, then ask for a comparison of shortlisted vendors and a brief for the category team without re-explaining the assignment in Cowork.
The other operational change is where tasks run. Work that uses cloud sources can continue after the laptop closes, and you can check or redirect it from mobile. Tasks that need local files, the built-in browser or computer use still require Claude Desktop to remain open. That distinction matters if you plan to schedule a weekly supplier report or leave a long analysis running overnight.
Rollout matters. The merged experience is arriving gradually, starting with Pro and Max on web, desktop and mobile. Team and Enterprise users still have separate Chat and Cowork while they wait. Anthropic says Enterprise admins will receive at least 30 days' notice before anything changes for their organisation. That is advance notice, not a published promise that admins can choose their own migration date. I would use the window to check permissions, approved connectors, cost expectations and any workflows that currently rely on the old Cowork interface.
Our earlier 60-day Cowork field report documented the old split and the practical uses we found for the desktop agent. Read it as a record of that experience, since product behaviour has moved on.
Claude Docs and Slides: where do they fit beside Word and PowerPoint?
Claude Docs and Claude Slides are editable artefacts created inside a Claude conversation. Ask Claude to turn your sourcing analysis into a decision paper or a category review deck, then edit the result directly, ask for revisions and export it. Docs can export to Word, PDF, Markdown or Google Docs; Slides can export to PowerPoint or PDF.
The distinction from Word, Google Docs, PowerPoint and Google Slides is the starting point. Claude already has the conversation, the files you supplied and any connected sources it is permitted to read. The document or deck begins from that working context. Your established document system remains the place to manage approved versions and formal records. Claude Docs is still in beta and has no version history.
If your organisation connects Microsoft 365 to Claude, Claude can read permitted Word and PowerPoint files from OneDrive and SharePoint as inputs. Creating a Claude Doc or Slide does not automatically update the original Microsoft file. Writing back to OneDrive or SharePoint requires separate admin-enabled write tools and the user's existing permissions. Claude's add-ins for Microsoft apps are another route when you want to work inside Word or PowerPoint itself.
For a procurement pilot, I would start with a reviewable output: give Claude the approved sourcing brief, evaluation criteria and supplier responses, then ask for a draft decision paper with evidence linked to each criterion. The category manager checks every commercial conclusion before the document enters the formal approval process. Docs and Slides are available in beta on paid plans; Enterprise owners must enable them first.
Salesforce in Claude: what changes for organisations already using it?
Anthropic launched Salesforce in Claude in beta with 37 skills for account research, call preparation, pipeline review, meeting follow-up and CRM updates. A seller can pull account history and recent discussions into a meeting brief, turn notes into an email and Slack update, then review proposed changes to the Salesforce record. Salesforce remains the system of record. Claude reads what the signed-in user can access, and by default asks for approval before writing changes.
This is most relevant to procurement teams whose organisation already coordinates supplier relationships or commercial work in Salesforce. It shows how Claude can assemble context from a governed system, perform the surrounding knowledge work and send approved updates back. It does not mean the Salesforce plugin has become a procurement system. Before making a procurement case for it, test one real workflow: which records contain the required facts, what Claude can read, which changes it proposes and who approves the final entry. The plugin is available in beta on paid Claude plans, with an admin connecting Salesforce for the organisation.
Claude Tag in Slack: a procurement workflow with a clear review point
Claude Tag can now use a person's own connected apps when they ask it to work in a Slack channel. It acts with that person's access rather than assuming everyone in the channel can open the same material. The person can review Claude's response before it posts. Anthropic is rolling personal connectors out to Team plans first, with Enterprise to follow.
Here is a workflow I would test, rather than claim we have already run it. A buyer in a sourcing channel has access to supplier proposals in a connected Drive. They ask Claude to compare the proposals against approved criteria and draft an update for the evaluation team. The buyer reviews the response before posting, removes confidential prices that the full channel should not see, and checks the evidence behind any recommendation. The access boundary matters: Claude may be able to read a file through the buyer's connector, while everyone in the channel can see what it posts.
Personal connectors only work when a person initiates the request. Scheduled or unattended channel work needs shared connectors attached by an admin. For procurement, I would begin in review mode and use a channel with a known audience before considering automatic posting.
Smart reports: can Enterprise teams see which Claude workflows are worth repeating?
Smart reports are an Enterprise beta that analyses a sample of Claude sessions for a selected team and recent time period. The report groups work by type, shows spend and common friction, and suggests repeated patterns that could become shared skills. An Enterprise owner must enable it; the feature is off by default.
For a procurement leader, the useful question is whether people are repeatedly building the same supplier brief, RFP draft or meeting follow-up from scratch. If the report shows a recurring task with usable outputs, that is a candidate for a shared skill and a controlled pilot. If sessions stall because a connector is missing or approvals interrupt the work, fix that before training the team to use more prompts.
There is an important governance condition. Reports can include session-level summaries and cost, and admins control whether names can be revealed. Anthropic says smart reports are for understanding adoption and investment, not for evaluating individual performance or making employment decisions. I would tell users what is being analysed before turning the feature on and scope the first report to the procurement team.
Claude Marketplace: which procurement tools deserve attention?
Anthropic's Claude Marketplace brings connectors and plugins, Claude-powered agents and products, and service partners into one discovery point. Anthropic also opened a plugin submission portal for developers. This should make it easier to find extensions, but a large catalogue is not a shortlist for your procurement team.
Start with a defined task. If the problem is supplier bid comparison, write down the inputs, output format, access requirements, review owner and success measure. Then ask whether a connector, a reusable skill, a plugin or your existing process solves it with the least extra complexity. We have published the Procurement OS as an example of packaging repeatable Claude skills across source-to-contract work. The Marketplace may help teams discover options like this, but each option still needs a permissions and output-quality check in your own environment.
What should a procurement team do next?
If you are on Pro or Max, the Chat and Cowork merger is the first change to try. Take a real task that usually starts as a question and ends as a deliverable. Keep the conversation intact, give Claude the approved inputs, and measure whether the resulting draft needs less rework. On Team or Enterprise, prepare the same workflow and wait for your organisation's rollout and controls.
Then choose one adjacent capability according to where work gets stuck: Docs or Slides for draft artefacts, Salesforce for an existing CRM process, Claude Tag for supervised collaboration in Slack, or smart reports for an Enterprise adoption review. The right pilot is the one that produces a useful output your team can inspect and repeat. If you are deciding which procurement workflow to test first, we can help design the pilot, controls and measurement plan.