The Center of Gravity: Who Wins the Future Enterprise
This is the final article in Arion Research's "Future Enterprise" series. Over seven previous articles, we have examined how AI agents are restructuring the enterprise software stack: the architectural layers, the protocols, the identity and governance gaps, the pricing disruption, and the cross-organizational frontier. This concluding article synthesizes those threads into a competitive landscape analysis and a strategic playbook for the transition ahead.
In the first article of this series, I posed a question: as the traditional enterprise application bundle collapses under the pressure of AI agents, where does the center of gravity of enterprise technology land? Does control accrue to whoever owns the data, whoever owns the intelligence, or whoever owns the business logic?
Seven articles later, we have built the framework to answer that question. We have mapped the three-layer architecture (Enterprise Platform, Agentic Platform, Collaboration), the cross-cutting vertical services (Identity, Governance, Context and Memory, Metering), the connective tissue (Agent Service Bus), and the cross-organizational dimension that stress-tests all of it. Now it is time to map some of the major vendors against this framework and evaluate who is best positioned to win, over what time horizon, and under what conditions.
The answer, as with most things in enterprise technology, is not simple. The center of gravity shifts over time, and the vendors positioned to win in the near term are not necessarily the ones positioned to win in the long term. Understanding this dynamic is the key to making sound enterprise technology decisions over the next several years.
The Competitive Landscape Mapped to the Framework
The major players in the Future Enterprise landscape fall into four categories, each with distinctive strengths and structural weaknesses when mapped against the architecture we have built in this series.
The Vertical Integrators: Oracle, Salesforce, ServiceNow, zoho, SAP
Large technology providers including Oracle, Salesforce, ServiceNow, Zoho and SAP, control the Enterprise Platform layer today. They own the systems of record, the business logic, and the transactional data that enterprises depend on. Their AI agent strategies share a common pattern: embed agents deeply into the application, operating at the transaction layer with direct access to the data model and business rules.
Oracle has been the most aggressive, embedding over 600 agents across Fusion Cloud applications in finance, HCM, supply chain, and customer experience, and including them at no additional cost within existing subscriptions. This is a deliberate strategy to accelerate adoption and make Oracle's agent layer the default for Fusion customers. Oracle's additional advantage is its infrastructure stack: Database 26ai and OCI provide the compute and data layer beneath the agents, creating a full-stack integration from infrastructure through application through agent that no other vendor can match in depth.
Salesforce has taken a different approach with Agentforce, positioning it as a platform for building and deploying agents across the customer lifecycle. Salesforce's strength is its CRM data: no vendor has a richer, more broadly adopted model of customer relationships, sales processes, and service interactions. Agentforce agents operate within this data model with native understanding that external agents cannot replicate. Salesforce has also been the most aggressive on pricing experimentation, testing per-conversation, consumption, and seat-based models as it navigates the pricing paradox I discussed in Article 6.
SAP controls the operational backbone of many of the world's largest enterprises. Its ERP data, covering finance, supply chain, manufacturing, and procurement, is often the most business-critical data an enterprise holds. SAP's agent strategy embeds AI across these operational workflows, with a particular focus on the complex, regulation-heavy processes where deep data model access provides the most value.
The structural advantage of the vertical integrators is depth. As I argued in Article 3, native agents operating at the transaction layer understand the data model, the business rules, the validation logic, and the exception handling in ways that external agents accessing the same systems through APIs cannot match. This depth advantage is real and durable.
The structural weakness is scope. Each vertical integrator's agents work brilliantly within their own ecosystem and are blind to everything outside it. Oracle's procurement agent cannot orchestrate with Salesforce's CRM agent. SAP's finance agent cannot coordinate with a third-party logistics system. The vertical integrators control deep, narrow slices of the enterprise, and the connective tissue between those slices (the Agent Service Bus, the cross-platform orchestration layer) is not their strength. All of them are adopting open protocols (MCP and A2A), which narrows this gap by enabling their native agents to participate in cross-vendor workflows. But protocol connectivity solves message routing, not semantic translation between different data models, not cross-vendor governance arbitration, and not the commercial tension between openness and platform lock-in. The trajectory is positive. The gap is closing, but it has not closed.
The Horizontal Platforms: OpenAI and Anthropic
OpenAI and Anthropic are building from the opposite direction. They do not control the Enterprise Platform layer. They do not own the systems of record or the business logic. What they control is the intelligence layer: the frontier-class reasoning capability that powers the most sophisticated agent behaviors.
OpenAI's Frontier platform, launched in February 2026, is the most ambitious play to build a horizontal agentic layer across the enterprise. Frontier positions itself as the orchestration platform where agents can work across systems, across vendors, and (eventually) across organizations. The value proposition is breadth: a single platform that can coordinate agents spanning CRM, ERP, HCM, and custom systems rather than being confined to one vendor's applications.
Anthropic has taken a more infrastructure-oriented approach. The Model Context Protocol (MCP), now hosted by the Linux Foundation, has become the de facto standard for agent-to-tool connections with over 10,000 active servers. The Claude Partner Network, backed by a $100 million investment, builds the implementation ecosystem through partnerships with Accenture, Deloitte, Cognizant, and other major system integrators. Anthropic's strategy is less about building a competing application platform and more about becoming the intelligence and connectivity layer that other platforms build on.
The structural advantage of the horizontal platforms is intelligence breadth. They offer the most capable reasoning models available, and their agents can orchestrate across vendor boundaries. For the cross-functional processes I described throughout this series (order-to-cash, procure-to-pay, hire-to-retire), horizontal platforms are the natural orchestration layer.
The structural weakness is the depth gap I explored in Article 3. Horizontal agents interacting with enterprise systems through APIs see only what the APIs expose. They lack the transaction-layer access, the business rule awareness, and the validation logic that native agents operate within. This gap is narrowing as protocols like MCP and A2A improve, but it has not closed.
The Infrastructure and Ecosystem Players: Microsoft and Google
Microsoft and Google occupy a distinctive position. They are not primarily application vendors (though both have significant application portfolios). They are infrastructure and ecosystem players whose AI strategies span compute, models, platforms, and tools.
Microsoft's strategy is the most layered. Azure provides the cloud infrastructure. OpenAI models (and increasingly Microsoft's own MAI models) provide the intelligence. Microsoft 365 Copilot and the new E7 Frontier Suite embed agents into the productivity tools that hundreds of millions of workers use daily. Entra Agent ID provides the identity layer. Agent 365 provides governance and management. Microsoft is the only vendor attempting to play at every layer of the Future Enterprise architecture simultaneously, from infrastructure through identity through applications.
Google brings its own strengths: Gemini's multimodal capabilities (text, images, video, audio) provide advantages in scenarios requiring unstructured data processing. The A2A protocol, which Google originated and contributed to the Linux Foundation, is becoming a standard for agent-to-agent communication. Google Cloud Platform provides the infrastructure, and Vertex AI Agent Builder provides the development platform.
The structural advantage of the infrastructure players is reach. Microsoft touches more enterprise workers through Microsoft 365 than any other vendor. Google touches more consumers and has deep strengths in data processing and search. Both can embed agent capabilities at a scale that specialized vendors cannot match.
The structural weakness is that neither Microsoft nor Google controls the deep business logic of the enterprise. Their agents interact with Oracle, Salesforce, ServiceNow, Zoho and SAP systems as external parties, subject to the same depth-versus-breadth trade-offs that affect all horizontal agents.
The Time-Horizon Analysis: Three Overlapping Phases
The center of gravity question is not static. It shifts over time as the technology matures, standards solidify, and enterprises build new capabilities. I see three overlapping phases, each favoring different vendors and different strategies. These phases are not sequential in the clean sense. Early adopters compress the timeline, and the boundaries between phases blur as the pace of agentic AI development accelerates. But the directional logic holds.
Phase 1: Data Wins (Now through 18 Months)
In the near term, the center of gravity sits with whoever controls the enterprise data. Agents are only as good as the data they can access, and the vendors who own the systems of record hold the most valuable data. This is the vertical integrators' moment.
Oracle's full-stack advantage (database through applications through agents) is strongest in this phase. An Oracle Fusion customer deploying Oracle's embedded agents gets immediate value because the agents operate directly on the data model they already run their business on. No integration required. No API translation. No data pipeline to build. The same logic applies to Salesforce within CRM and SAP within ERP/supply chain.
Horizontal platforms face their biggest challenge in Phase 1. Their agents need data to be useful, and getting access to enterprise data at the depth required for high-value workflows is slow, expensive, and often politically difficult. MCP and API connections provide access, but not the same depth of access that native agents enjoy.
For enterprises, the Phase 1 implication is clear: start with your existing vendors' native agents for the highest-value workflows within their domains. The quick wins are there, and the integration cost is lowest.
Phase 2: Intelligence Wins (12 Months through 3 Years)
As data connectivity matures (through MCP, A2A, and improving API ecosystems), the advantage shifts from who has the data to who has the best reasoning about the data. In this phase, the horizontal platforms and infrastructure players gain ground.
The reasoning gap between frontier models and vendor-embedded models is significant today and shows no sign of closing. OpenAI and Anthropic are investing billions in model capability. Vertical integrators are licensing or partnering for model access, not building frontier models themselves. As agents take on more complex, multi-step, cross-system workflows, the quality of reasoning becomes the differentiator.
This is also the phase where the Agent Service Bus (Article 2) and the third path of native agents with open interoperability (Article 3) become critical. The enterprises and vendors that have built the orchestration layer, the capability discovery, the intent resolution, and the protocol connectivity will be able to combine native depth with horizontal intelligence. Those who have not will face expensive retrofits.
Microsoft is particularly well positioned for Phase 2. Its combination of Azure infrastructure, OpenAI models, Copilot distribution, and Entra Agent ID gives it a play at every layer. The risk for Microsoft is complexity: maintaining coherence across this many products and strategies is an execution challenge that has tripped Microsoft up before.
For enterprises, the Phase 2 implication is: invest now in the interoperability layer. Demand A2A and MCP support from your vendors. Build the Agent Service Bus infrastructure. The enterprises that have this connective tissue in place when intelligence becomes the differentiator will be able to adopt the best reasoning models regardless of which vendor provides them.
“The Accelerating Timeline
When I first proposed this three-phase model, the phases were relatively distinct: data dominance for 1-2 years, intelligence dominance for 3-5 years, business logic dominance for 5+ years. Recent developments suggest the timeline is compressing.
The pace of agentic AI evolution is faster than any previous enterprise technology cycle. Protocol adoption (MCP, A2A) is happening in months, not years. Model capabilities are improving quarterly. Enterprise adoption patterns show early movers already entering Phase 2 dynamics while most organizations are still in Phase 1.
The practical implication is that the phases overlap more than originally anticipated. Early adopters are already compressing the data-to-intelligence transition, and the intelligence-to-business-logic transition may begin before most enterprises have fully navigated Phase 1.
This does not change the directional logic (data, then intelligence, then business logic), but it does change the urgency. Enterprises that plan for a leisurely, sequential transition through these phases may find the market has moved faster than their roadmap anticipated.”
Phase 3: Business Logic Wins (2-4 Years and Beyond)
In the long term, the center of gravity shifts to whoever controls the business logic: the rules, processes, constraints, and domain knowledge that define how an enterprise actually operates. This is the most consequential phase, and it is the one where the competitive landscape is most uncertain.
Here is the logic: data access will commoditize as protocols and integration platforms mature. Every agent will eventually be able to access every system's data through standardized connections. Model intelligence will also commoditize (or at least converge) as frontier capabilities diffuse through open-source models, smaller specialized models, and multi-model architectures. What will not commoditize is the business logic specific to each enterprise: the approval chains, the compliance rules, the pricing algorithms, the exception handling, the institutional knowledge about how the business actually works.
The vendors who control the deepest, most business-critical logic have a durable advantage. Today, that business logic lives inside Oracle, Salesforce, ServiceNow, Zoho and SAP applications. But here is the disruption: as agents become more capable, enterprises may choose to extract their business logic from vendor applications and run it on open platforms with better reasoning models, lower costs, or more flexible governance. The application, as I argued in Article 1, is a bundle of data model, business logic, UI, and workflow. Agents only need the data and the logic. If the logic can be separated from the application and expressed as agent-callable APIs, the traditional application vendor's lock-in weakens.
This is the existential question for the vertical integrators. Their long-term competitive position depends on whether business logic remains inseparable from their application platforms (which favors them) or becomes portable and platform-independent (which threatens them). Oracle's full-stack strategy, binding database, application, and agent into a unified architecture, is in part a bet that keeping business logic tightly coupled to the platform creates durable competitive advantage. The horizontal platforms are betting the opposite: that business logic will eventually be expressible in forms that any capable agent can execute.
For enterprises, the Phase 3 implication is the most important: document, structure, and own your business logic. Regardless of which vendor scenario plays out, the enterprises that have their business rules, processes, and domain knowledge well-documented and accessible (as high-quality, agent-callable APIs and machine-readable policy) will have optionality. They can run that logic on whatever platform provides the best combination of intelligence, cost, governance, and interoperability. The enterprises that leave their business logic buried inside vendor applications will be dependent on those vendors' agent strategies, for better or worse.
The Strategic Playbook
Across all three phases, certain strategic principles apply regardless of which vendors you use or which phase you are currently navigating. This is the playbook that synthesizes the entire Future Enterprise series into actionable guidance.
1. Treat identity and governance as foundational investments, not compliance exercises. Articles 4 and 5 made the case that agentic identity and governance are architectural layers, not security features. Every agent you deploy without proper identity, governance, and accountability is a liability you have not sized. Build these layers first, not after the agents are already in production.
2. Build the orchestration layer now. The Agent Service Bus (Article 2), with its five functions of capability discovery, intent resolution, contract negotiation, conflict arbitration, and message routing, is the infrastructure that makes a multi-vendor agent portfolio work. Without it, your native agents and external agents operate in parallel but never collaborate. The enterprises that have this infrastructure when Phase 2 arrives will have a structural advantage.
3. Demand interoperability from every vendor. Every agent you deploy should support open protocols: A2A for agent-to-agent communication, MCP for agent-to-tool connections, and emerging standards for agent identity and governance. If a vendor says their agents only work within their platform, you are building the next generation of integration silos. The third path (native agents with open interoperability) is the right architectural target.
4. Adopt a portfolio approach to agents. As I argued in Article 3, the native-versus-external question is not either/or. Use native agents for deep, high-volume, compliance-heavy workflows within a single vendor's domain. Use horizontal agents for cross-functional orchestration across vendor boundaries. Match the agent model to the process requirements, not the vendor pitch.
5. Plan pricing for the consumption era. Per-seat pricing is structurally breaking down (Article 6). Build metering infrastructure, develop internal cost allocation capabilities, and negotiate hybrid contracts that balance predictability with consumption alignment. Resist value-based pricing pitches until the attribution and measurement problems are solved.
6. Prepare for cross-organizational collaboration. The enterprise boundary is where the entire architecture gets stress-tested (Article 7). Build identity frameworks that can verify external agents. Develop governance policies for cross-boundary interactions. Establish Know Your Agent processes for evaluating the agents you interact with. Start with your most strategic external relationship and pilot cross-org collaboration there.
7. Own your business logic. This is the single most important long-term strategic action. Document your business rules, processes, and domain knowledge in forms that are machine-readable and platform-independent. Express them as agent-callable APIs. Build the institutional capability to maintain and evolve this logic independently of any vendor. In Phase 3, the enterprises that own their business logic will have options. The enterprises that have ceded it to vendor platforms will not.
Closing the Series
Over eight articles, we have mapped a structural transformation in enterprise technology. The traditional application model, built for human users interacting with bundled software through graphical interfaces, is giving way to an agent-native model where AI agents interact directly with data and business logic, orchestrate across systems, and collaborate with each other and with humans in increasingly sophisticated ways.
This transformation is not hypothetical. It is happening now, unevenly, with significant gaps in identity, governance, interoperability, and pricing that the industry has not yet resolved. The vendors are moving fast. The standards are emerging. The regulatory frameworks are taking shape. But the architectural foundations that enterprises build today will determine whether they can participate in this transformation or will be constrained by decisions made before the full picture was clear.
The center of gravity will shift. Data wins now. Intelligence wins next. Business logic wins in the long run. The enterprises that understand this progression and invest accordingly, building depth where depth matters, breadth where breadth matters, and the connective tissue that links them, will have the most capable, most governable, and most adaptable technology infrastructure in the market.
The future enterprise will not be defined by any single vendor's platform. It will be defined by the architecture that connects them all.
This concludes the Future Enterprise series. A comprehensive research report synthesizing the findings across all eight articles will be published by Arion Research later in 2026.
