In Lesson 3, you established that knowledge workers -- not developers -- are the central figures in the enterprise agentic transition. Now the question becomes practical: which platform do you actually use to deploy a domain agent?
The enterprise agentic landscape in 2026 is shaped by two dominant platforms. They share the same underlying paradigm -- large language models executing structured tasks against enterprise data -- but they differ fundamentally in who they target, how they deploy, and what they assume about your organisation. Understanding both, their architectures, their strengths, and their limitations, is a prerequisite for every deployment decision this book will ask you to make.
This lesson introduces both platforms and gives you a decision framework to choose between them. By the end, you will not be guessing. You will be qualifying.
Cowork is a desktop productivity tool built for knowledge workers. Out of the box, Claude is a generalist. Plugins turn it into a specialist for your role, team, and company.
A plugin bundles the domain expertise, tool connections, and workflows a specific role needs. Anthropic and the community have built plugins for sales, legal, finance, marketing, data, customer support, and more. You install one in seconds. The entire plugin is file-based -- markdown and JSON, no code, no infrastructure, no build steps.
What's Inside
What It Does
Skills (SKILL.md)
Domain expertise Claude draws on automatically -- persona, principles, and constraints
Commands
Explicit actions you trigger (e.g., /finance:reconciliation, /sales:call-prep)
Connectors
Wire Claude to the external tools your role depends on -- CRM, email, project tools, data warehouses -- via MCP
The SKILL.md is the part only you can write. It is a natural-language instruction document that tells the agent who it is, what it knows, what it must never do, and how it should respond. It is not code. It is not configuration in the traditional sense. It is your institutional knowledge, made executable.
Plugins arrive as ready-made packages. Your contribution is customising the skills -- encoding how your organisation actually works. Chapter 26 covers plugin anatomy in detail.
Cowork ships with production-ready MCP connectors for the systems knowledge workers already use: Google Workspace (Drive, Gmail, Calendar), Salesforce, HubSpot, DocuSign, Slack, Notion, Jira, WordPress, Apollo, Clay, Outreach, and Similarweb. Industry-specific connectors serve financial data (FactSet, MSCI), legal workflows (LegalZoom), and other verticals. When you write a SKILL.md that says "pull the latest pipeline data from Salesforce," the connector handles authentication, API calls, and data formatting. You never see it.
The connector ecosystem is Anthropic's primary infrastructure investment. The open-source MCP standard means third-party developers can build connectors for any system, and the growing marketplace through which connectors are published and distributed is creating the same kind of developer community dynamics that have driven the expansion of other platform ecosystems.
Cowork follows a product-led growth model. Adoption is bottom-up: one team tries it, sees results, tells the next team. Procurement happens at the team level -- a department budget line, not a board-level capital expenditure. This means you can start deploying agents within weeks, not months.
The organisations that have adopted Cowork most deeply typically started with a single team, a single vertical, and a single agent -- and expanded from there. The profile is the technically sophisticated team inside a larger organisation: the FP&A team that deployed a financial research agent before the CFO had approved a formal AI strategy. The in-house legal team that stood up a contract triage tool six months before IT had finished its vendor assessment. The architecture practice that deployed a BIM coordination assistant because the project manager could not wait for a platform decision. These teams share a characteristic: they have domain expertise that they understand is deployable in agent form, and they are not willing to wait for institutional processes to catch up.
Frontier takes a fundamentally different approach. Where Cowork gives individual teams a powerful plugin, Frontier provides the entire organisation with a semantic layer -- a unified intelligence infrastructure that sits across all systems.
Think of a semantic layer as a translation service that understands the meaning of data across every system in the organisation. When the finance team says "revenue," the sales team says "bookings," and the operations team says "throughput," a semantic layer knows these are related concepts and can reason across them.
In practice, this means an agent can move from a customer complaint logged in the CRM to a refund authorisation in the ERP to a follow-up communication drafted in the email system -- without a human touching the handoffs between departments. The agent carries context across each boundary: it knows why the refund was triggered, what the customer's history looks like, and what the finance team's approval threshold is. That cross-departmental continuity is what a single-team agent cannot replicate, and it is the capability that justifies Frontier's enterprise-wide deployment model.
Frontier manages agent identity, permissions, and cross-department context centrally. An agent deployed through Frontier does not belong to one team. It belongs to the organisation and can access data and workflows across departments -- subject to governance rules defined at the enterprise level.
Frontier is sold top-down through Forward Deployed Engineers and consulting firm partnerships (McKinsey, BCG, Accenture, Capgemini). Early adopters include HP, Intuit, Oracle, State Farm, Thermo Fisher, and Uber.
Procurement is enterprise-wide: capital expenditure, legal review, security assessment, executive sponsorship. The deployment timeline is measured in quarters, not weeks. But the payoff is proportional: Frontier deployments touch every department, not just one team.
Dimension
Anthropic Cowork
OpenAI Frontier
Target buyer
Team lead, department head
C-suite, CIO/CTO
Architecture
Plugins (skills, commands, connectors)
Unified semantic layer
Agent scope
Single team or function
Cross-department, enterprise-wide
Adoption path
Bottom-up (product-led growth)
Top-down (enterprise sales)
Procurement
Team budget
Capital expenditure + legal/security review
Time to first agent
Weeks
Quarters
Knowledge assumption
Concentrated in a specific team
Distributed across the organisation
Governance model
Team-level permissions
Centralised enterprise governance
When choosing a platform, ask three questions:
Is the problem contained within one team or function, or does it span the enterprise?
Can you fund this from a team budget, or does it require capital expenditure?
Is the domain knowledge concentrated in one team or distributed across the organisation?
For most Part 3 readers, Cowork is the starting point. You have domain expertise concentrated in your team. You have a team-level budget. You want results in weeks, not quarters. All hands-on exercises in this book use Cowork.
This does not mean Frontier is irrelevant to you. Understanding Frontier helps you recognise when your organisation is ready for enterprise-wide deployment -- and positions you to lead that conversation when the time comes. The platform decision is revisited in Chapter 26 for readers who are advising organisations on longer-term architecture choices.
Use these prompts in Anthropic Cowork or your preferred AI assistant to explore these concepts further.
What you're learning: You are practising the decision framework against your own organisational context. The AI helps you think through each question honestly rather than guessing.
What you're learning: You are testing whether you can apply the framework to unfamiliar scenarios. Getting the right answer for both organisations confirms you understand the framework, not just the vocabulary.
What you're learning: You are connecting the abstract framework to real adoption patterns in your industry. This grounds your platform decision in evidence, not theory.
The enterprise agentic landscape in 2026 is shaped by two dominant platforms: Anthropic Cowork (a desktop productivity tool with plugin-based extensibility, centred on the SKILL.md file) and OpenAI Frontier (a unified semantic layer for enterprise-wide transformation). They share the same underlying paradigm but differ in target buyer, deployment model, and organisational assumptions. A three-question decision framework -- organisational scope, procurement reality, and nature of knowledge -- determines which platform fits a given context.
📋Quick Reference
Access condensed key takeaways and quick reference notes for efficient review.
Free forever. No credit card required.
Ask