Welcome to this Cloud Wars Agent and Copilot Minute. In these discussions, I’ll be analyzing opportunities, impact, and outcomes possible with AI; today I discuss Claude’s and Copilot’s different approaches to becoming employees’ central workplace for AI.
Highlights
00:18 — Claude, including Claude Opus 5.5 in Copilot Chat, Word, Excel, and Copilot Studio, can serve as a unified workspace where users connect systems, draft documents, build spreadsheets, and solve problems. Claude often feels like a workplace because individuals can configure it themselves. Copilot is designed more as a governed set of tools, though Microsoft is moving toward a unified work destination by bringing Office into the Copilot app.
01:47 — Claude supports bottom-up customization through user-connected systems, often via Model Context Protocol (MCP), and user-written skills. In Copilot, makers or administrators configure and approve agents or connectors; users cannot independently add an MCP server. Think of this as a tradeoff, not a flaw: bottom-up setup encourages ownership and experimentation, while top-down setup offers consistency, governance, and access for people who do not configure tools themselves.
03:06— At Paragon Films, a finance employee built and shared live finance models, while a logistics employee moving temporarily into procurement configured connectors and skills to automate routine work. Neither waited for IT to build an agent. Bottom-up adoption helps discover what works and top-down governance helps scale it. Which tools people use matter less than where they start their workday.
More CIO and AI Agent Insights:
- Why AI Requires Access To Business Knowledge and Processes
- Debunking ‘Software Is Dead’ Nonsense
- Cowork Experiment Delivers Powerful AI Cost Lessons
- 4 Requirements to Drive Results That Go Beyond ‘AI Theater’
Kenny Mullican
CIO
Paragon Films
Related Posts
