If you finally got your team using Claude Cowork, take a breath.
Anthropic has retired Claude Cowork as a separate product experience and is moving its agentic capabilities into the main Claude interface. Existing users may retain access to relevant projects, connectors and workflows, subject to their plan, account configuration and the rollout process.
The product details in this article reflect Anthropic’s announcements and publicly available information as at 29 September 2026. Features, availability, plan entitlements, integrations and rollout timing may change.
On 16 September 2026, Anthropic announced that Claude Cowork would no longer exist as a standalone product. Its agentic capabilities have been folded into the main Claude interface.
That sounds dramatic.
In practice, Anthropic has removed a confusing choice rather than removed the underlying capability.
The reason given was simple: people were using both standard Claude chat and Cowork, then wasting time deciding where each task belonged.
Now, you describe what you need.
Claude works out whether it is a quick answer, a longer research task, a spreadsheet, a document or a presentation.
For Australian SMEs already dealing with tool fatigue, that is potentially good news.
But a simpler interface does not remove the need for a sensible AI workflow strategy.
What actually changed?
Here is the short version.
- ✅ Claude Cowork has been folded into the main Claude experience.
- ✅ Claude’s modes reduce from three to two: Claude Chat and Claude Code.
- ✅ Claude Docs and Claude Slides launched in beta inside normal Claude conversations.
- ✅ Claude Design, launched in April using Canva’s design engine, is also moving into the main conversation.
- ✅ Claude Code is unchanged and remains a separate product for developers.
- ✅ Anthropic says existing chats, projects, artefacts, connectors and skills carry over, though businesses should confirm availability, permissions and functionality after migration.
- ✅ Documents and presentations remain shareable by link and editable on mobile.
- ✅ The rollout begins with Pro and Max subscribers across web, desktop and mobile, followed by Team and Free plans.
- ✅ Enterprise administrators receive at least 30 days’ notice before the change reaches their accounts.
Claude can now create editable documents, including exports to Google Docs and Microsoft Word.
It can create presentations that open in PowerPoint, export to PDF, or be presented directly from Claude.
Claude Slides is separate from Claude for PowerPoint, Anthropic’s existing Microsoft add-in.
The wider Claude ecosystem is consolidating into fewer surfaces.
That is the trend to watch.
OpenAI launched ChatGPT Work in July 2026, while Google Gemini already creates and edits documents inside Google Docs and Slides. The industry is moving towards fewer disconnected tools and more capable workspaces.
That does not make one vendor automatically right for your business.
It does mean the “one tool for every tiny task” era is starting to look increasingly silly.
Cowork did not fail. It was promoted into the core product.
The important distinction is this:
Cowork has been retired as a separate destination, not stripped of its capabilities.
Anthropic built Cowork for larger, multi-step work. Claude Design was built for visual work. Users told Anthropic they were tired of deciding which surface to use and frustrated that context did not always carry between them.
The solution was to put those capabilities into one Claude conversation.
You might ask Claude to:
- Research a market and prepare a report
- Turn the findings into a spreadsheet with working formulas
- Create a presentation from the same information
- Draft a document and ask clarifying questions
- Collaborate with colleagues on the same file
- Connect to relevant business systems
- Check with you before taking an external action
The files come back editable.
That is more useful than receiving another block of text that someone has to rebuild manually.
Why this matters more to SMEs than big business
A large enterprise may have an IT department, an operations team and a change manager to absorb a platform update.
You probably do not.
You have customers to serve, staff to support, quotes to prepare and invoices to chase.
Every platform change becomes another business decision.
You need to know:
- What changed?
- Which staff members are affected?
- Which data can Claude access?
- What still requires approval?
- Which workflows touch customer information?
- Who is accountable when an output is wrong?
This matters because Claude’s connected workflows can touch sensitive parts of your business.
That may include customer records, quoting, invoicing, financial reporting, lead follow-up and internal documents.
A unified interface can make those activities easier to access.
It can also make it easier to move too quickly.
That is how Random Acts of AI happen: a business connects every available tool, switches on a handful of workflows and hopes the system figures out the strategy.
It rarely does.
What this means for your Claude for Small Business workflows
Our recent post, 43 Ready-Made AI Workflows: What Claude for Small Business Actually Does (and What It Doesn’t), explained how the Claude for Small Business plugin runs inside Claude Cowork.
Now that Cowork has moved into the main Claude interface, the plugin and its workflows are intended to run in the unified experience instead.
The capability is not disappearing. The address is changing.
Anthropic says relevant existing projects, connectors and workflows are intended to carry across to the unified Claude experience. Users should test important workflows after migration and confirm that permissions, integrations and plan entitlements remain suitable.
So if you have built workflows for lead follow-up, proposal preparation, reporting or content planning, there is no reason to panic.
You may need to familiarise yourself with the new interface.
You should still test your workflows after the rollout.
But this is not a forced rebuild.
The underlying capabilities are being consolidated into the main Claude experience, although users should confirm that their workflows, permissions and integrations continue to operate as expected.
The honest part: what consolidation does not do
A cleaner product experience is helpful.
It is not a business strategy.
The change does not:
- ❌ Decide which processes are worth automating
- ❌ Fix a messy or inconsistent workflow
- ❌ Remove the need for human approval
- ❌ Reduce the number of business decisions you need to make
- ❌ Automatically understand your pricing, tone or escalation rules
- ❌ Change your privacy, security or compliance obligations
The Privacy Act point is especially important for Australian businesses.
From 10 December 2026, relevant APP entities will have additional privacy-policy transparency obligations where a computer program uses personal information to make, or substantially and directly assist with, a decision that could reasonably be expected to significantly affect an individual’s rights or interests. Whether the obligation applies depends on the organisation, the information used and the decision-making process.
These requirements apply to relevant APP entities and do not mean that every business using Claude will automatically be subject to the additional disclosure obligation.
A human clicking “approve” does not automatically remove the issue if the system has done the heavy lifting.
A workflow you never mapped is a workflow you cannot properly explain.
The Evolve Way: Map, Ground, Execute
At Evolve With AI, our approach is strategy first, software second.
Anthropic’s product change fits neatly into our three-phase method.
Phase 1: Map
Before changing settings, choose three to five high-value workflows.
For each workflow, identify:
- ✅ Where the process starts and ends
- ✅ How much time it currently takes
- ✅ Which systems contain the required information
- ✅ Who owns each decision
- ✅ Whether it touches personal information
- ✅ Whether it is decision-adjacent
- ✅ What “done properly” looks like
Do not begin by exploring every new Claude feature.
Begin with the bottleneck costing your business time or revenue.
Phase 2: Ground
Claude needs your real business context.
Give it:
- Your quoting rules
- Approved examples of customer communication
- Product and service information
- Your tone of voice
- Pricing thresholds
- Customer segments
- Escalation paths
- Human approval points
Connect only the integrations that matter.
Keep approval mode switched on, particularly for anything involving financial information, customer communication or external publishing.
Also write down who owns each workflow.
An automation without an owner becomes everyone’s responsibility.
Which usually means nobody checks it properly.
Phase 3: Execute
Measure hours saved per person per week first.
Then measure the potential business impact, noting that results are subject to implementation, data quality and adoption:
- Lead response times
- Number of qualified enquiries
- Proposal turnaround
- Reporting errors
- Month-end preparation time
- Potential revenue impact
If a workflow moves neither time nor business performance, improve it or retire it.
Do not keep an automation simply because it looks impressive.
What to do this week
You do not need a major implementation project.
Start with four practical checks:
- ✅ Check your Claude plan and confirm when the unified experience is expected to reach your account.
- ✅ Confirm your important connectors still work, particularly for CRM, accounting, documents and calendars.
- ✅ Review approval mode for anything customer-facing, financial or externally published.
- ✅ Map one workflow properly instead of switching on ten new features.
That is enough for now.
Do not turn a product update into another subscription and settings marathon.
The bottom line
The era of assembling a pile of disconnected AI tools is ending.
That is good news for SMEs.
Fewer interfaces can mean less confusion, better context and more useful outputs.
But a better tool has never once fixed a broken workflow.
Claude Cowork’s capabilities are now part of the main Claude interface. Claude Docs, Slides and Design make the platform more capable. Existing Claude for Small Business workflows may carry across to the unified experience, but businesses should confirm availability, permissions and functionality after migration.
The strategic question remains the same:
Which process should become better, faster or more reliable?
If you would like clarity before adding more AI to your business, start with our free AI Discovery Audit.
It is a low-pressure way to help identify where AI workflow automation may create measurable value, what needs attention first and what should stay human-led.
And if your team needs practical support, our AI strategy and readiness services and hands-on AI productivity training workshops can help turn good intentions into everyday capability.
No hype.
Just a clearer path forward.
Product details in this article reflect Anthropic’s announcement and related information published in September 2026. Platform features, availability and plan entitlements can change.
Disclaimer: This article provides general information only and is not legal, financial, accounting, privacy, cybersecurity or technology procurement advice. Product features, pricing, integrations and availability may change and may differ by plan, location and configuration. AI outputs may be inaccurate or incomplete and must be reviewed by an appropriately authorised person before use. Evolve With AI does not guarantee any particular time saving, revenue outcome, compliance result or business performance improvement.
Anthropic, Claude, Claude Code, Claude Docs, Claude Slides and related product names are trademarks of Anthropic PBC. Evolve With AI is independent of Anthropic unless expressly stated otherwise. Product features, pricing, availability and plan entitlements may change.