How We Build the Agentic Enterprise

1. Operating Layer

   Executive-authored knowledge, decisions, workflows. The strategic context that turns Claude from a chatbot into an agent.

   ↑↓

2. Agent Layer

   Anthropic Claude

   Reasoning, document understanding, tool use, generation. The brain.

   ↑↓

3. Integration Fabric

   MuleSoft + Agent Fabric

   Governance, observability, rate limits, audit trails. The platform that turns AI from a science project into operational software.

   ↑↓

4. Systems of Record

   Salesforce, ERP, HRIS, billing, custom

   Where the data model has been hardened over years. Where audit trails compound.

The three-platform thesis

Every honest enterprise AI architecture in 2026 turns out to be three platforms with three different jobs. Not one platform doing everything; not a constellation of point tools; three peers, each with a clear scope.

• Anthropic provides the brain. Claude is the state-of-the-art reasoning model — document understanding, tool use, code generation. The model is a building block, not a product. It does not enforce auth, retain audit trails, version prompts, or rate-limit itself.
• MuleSoft provides the platform. Governance, observability, batching, error handling, lifecycle management. The integration layer that turns AI from a science project into operational software the business can rely on. MuleSoft Agent Fabric is the productized version of this pattern.
• Salesforce — or whatever runs your business — provides the system of record. Where the data model has been hardened over years. Where exceptions get reviewed. Where audit trails compound. Salesforce is the most common pattern and the one we deliver most often, but the architecture works against any system MuleSoft can integrate with — ERP, HRIS, billing, custom — when Salesforce isn't the right anchor.

Skip any leg of that triangle and you can usually still get a demo to run. Skip any leg and you cannot run a business on what you built.

The operating layer is where competitive advantage compounds

Above the three platforms sits the operating layer — the executive-authored knowledge, decisions, and workflows that tell agents what to do with the platforms' capabilities. Pipeline reconciliation rules, hiring evaluation criteria, deal coaching context, content cadence, customer signal interpretation — the things that lived in the executive's head and now run as structured, queryable, agent-actionable strategy.

The operating layer is what separates AI-native businesses from AI-applied businesses. AI-applied means a chatbot bolted onto an existing process. AI-native means the strategic context that drives the business now flows through agents that can act on it.

We author this layer for ourselves — our quoting, hiring, customer-saves, and content-cadence systems all run on the operating layer above Claude and MuleSoft. We deliver this pattern for clients via Run on Claude engagements.

Common objections, addressed

“Can't Claude just do all of this on its own?”

Claude is excellent at reasoning, synthesis, and code generation. It does not enforce authentication, retain audit trails for enterprise data flows, manage rate limits across systems, or version prompts and tool calls over time. These are platform problems, not model problems. Skipping the platform layer because the model is smart is the most expensive mistake in enterprise integration in 2026.

“Can't we vibe-code this with Claude Code / Cursor / Codex?”

You can vibe-code a prototype. You cannot vibe-code production-grade governance, observability, retry logic, transaction management, audit trails, and lifecycle versioning. Three out of four integration deals on our pipeline this quarter are competing against “we'll just build it ourselves.” One prospect is eight months into an engagement that was supposed to take six weeks. The DIY path looks cheap until you measure it in calendar quarters and burned operating capital.

“Do I really need MuleSoft? Can't I just connect Claude directly to Salesforce?”

Directly connecting Claude to Salesforce works for a demo. It does not work at production scale across compliance, audit, observability, and cross-system orchestration. Salesforce-hosted MCP servers govern access to Salesforce — they don't govern access to your other systems. MuleSoft is the cross-system fabric that coordinates agents across Salesforce and everything else. Salesforce's own MuleSoft Agent Fabric is the productized version of this pattern — and it's effectively required for multi-system agentic workflows.

“Why not just Salesforce + Anthropic?”

If your business runs entirely inside Salesforce, you can probably defer MuleSoft — Salesforce Headless 360 makes Salesforce-only agentic workflows accessible. But most businesses have meaningful systems outside Salesforce: ERP, HRIS, billing, custom platforms, partner systems. Cross-system orchestration is what MuleSoft solves. The moment your AI roadmap crosses the Salesforce boundary, the integration fabric becomes essential.

“What about Microsoft Copilot, Google Vertex AI, AWS Bedrock?”

The three-platform thesis is brand-agnostic at the agent layer. Anthropic Claude is our preferred reasoning layer because of its tool-use quality and operator-credibility track record — but the architecture pattern works with any state-of-the-art reasoning model. The integration and system-of-record layers stay the same regardless of which model is in the agent slot.

How Green Irony delivers this architecture

Green Irony delivers the three-platform architecture across two engagement types:

• SMB MuleSoft — fixed-price MuleSoft integrations, three weeks, $15K–$40K. The integration foundation for businesses that aren't yet ready for the full Run-on-Claude motion.
• Run on Claude — paired strategy and architecture for executives running their enterprise on Claude. Strategic intake, architecture, delivery, and managed services. Engagements scope per outcome, not per product menu.

We use this same architecture to run our own business. Read more from Aaron on the three-platform thesis and what AI-native delivery actually looks like in practice.

Frequently asked questions