The Enterprise AI Hypothesis

The Problem

Enterprise AI has access to data but often lacks business context. Knowledge is scattered across documentation, APIs, semantic models and prompts.

The Hypothesis

Business processes may become the primary artifact for enterprise AI. Humans describe intent, process, business concepts, governance and systems. AI consumes that context to orchestrate work.

Concept Illustration

Enterprise Business Processes (MCP Plugins)

• Lead to Opportunity (MCP Plugin)
• Opportunity to Quote (MCP Plugin)
• Quote to Order (MCP Plugin)
• Order to Cash (MCP Plugin)
• Customer Onboarding (MCP Plugin)
• Customer Renewal (MCP Plugin) ✓
• Case to Resolution (MCP Plugin)
• Record to Report (MCP Plugin)
• Hire to Retire (MCP Plugin)

Selected Process: Customer Renewal

Business Outcome: Renew an existing customer contract while maximizing customer value.

Business Process Flow (Orchestrating MCP Skills)

1. Prepare Client Meeting [Sub-Process / Skill: Client Meeting Brief]
2. Review Customer Health [Sub-Process / Skill: Customer Health Summary]
3. Identify Expansion Opportunities
4. Create Renewal Proposal [Sub-Process / Skill: Renewal Proposal Generator]
5. Executive Approval
6. Close Renewal

Enterprise Knowledge

Every business process contributes to the Enterprise Business Matrix.

Shared business concepts connect processes across the organization.

AI agents consume business context—not just data.

Questions Worth Exploring

• Can business processes become the primary AI artifact?
• Can Enterprise Bus Matrices emerge from governed business processes?
• Should business teams author enterprise context?

References

This article was inspired by Google's Open Knowledge Format (OKF).

Google Cloud: How the Open Knowledge Format Can Improve Data Sharing