Part 1 of the series "The Enterprise AI Vendor Landscape"
How AI Agents Became the New Battleground for Enterprise Software Dominance
The Repositioning
Every decade or so, the enterprise software industry goes through a repositioning so thorough that the competitive landscape that emerges bears little resemblance to the one that preceded it. The shift from on-premises to cloud in the 2000s and 2010s was one. The mobile-first era was another, though it proved more consequential for consumer than enterprise software. The current repositioning, the pivot to agentic AI as the primary interface between users and enterprise systems, is shaping up to be the most consequential since the cloud transition, and possibly since the original ERP consolidation of the 1990s.
The evidence is in the numbers. BCG's AI Radar 2026, surveying 2,360 executives across 16 markets, found that companies plan to devote 1.7% of revenue to AI in 2026, up from 0.8% in 2025. More than 30% of those AI budgets are now directed specifically at agentic AI, with aggressive adopters allocating more than half. Gartner projects end-user spending on AI models and platforms of roughly $64 billion in 2026, up 63% year over year. The enterprise agentic AI market alone is estimated between $5.3 billion (Grand View Research) and $7.5 billion (Research and Markets) in 2026, with growth rates ranging from 27 to 46% annually, depending on whose definition you use.
The money is flowing. The question is where it lands, because the vendors competing for that spend are not just selling AI features. They are attempting to become the platform layer through which enterprises interact with all of their software, and the platform choices enterprises make in the next 18 to 24 months will shape their technology architecture for the next decade.
The Competitive Map
The agentic enterprise platform war has seven primary combatants, each approaching the market from a different position of strength and with a different theory of how agents will reshape enterprise software.
Microsoft is the installed-base play. With more than 450 million Microsoft 365 commercial seats and Azure passing $100 billion in annual revenue in fiscal year 2026, Microsoft's strategy is to make agents the natural extension of the productivity suite that enterprises already own. Microsoft 365 Copilot reached 30 million paid seats by the fourth quarter of fiscal 2026, growing from 20 million just one quarter earlier. The company's AI revenue run rate hit $37 billion in Q3 FY2026, driven primarily by Azure. Microsoft's Agent 365, introduced with an E7 tier at $99 per user per month, positions the company as the enterprise AI control plane: governance, security, and agent management across deployments. The thesis is straightforward. If agents are the new interface, and Microsoft already owns the productivity interface, then agents should flow through Microsoft. The limitation is equally straightforward. Microsoft's control plane works best with Microsoft's agents. Cross-vendor orchestration is a stated capability but not a demonstrated strength, and the 30 million Copilot seats, while growing fast, still cover only about 6.7 % of the commercial installed base. The gap between distribution advantage and actual adoption is real.
Salesforce is the CRM-outward play. Agentforce has been the company's fastest-growing product in its history, reaching approximately $800 million in annual recurring revenue by the end of fiscal 2026 (January 2026) and growing 169 % year over year. By Q1 FY2027 (May 2026), ARR had crossed $1.2 billion, growing 205 %. By Q2 FY2027, it crossed $1.5 billion. Combined with Data 360, the total AI ARR reached nearly $3.4 billion, though that figure includes roughly $1.1 billion from the Informatica acquisition, making organic growth harder to isolate. Salesforce's strategic bet is that agents should be anchored in customer data. The Koa reasoning model, Multi-Agent Orchestration (generally available as of 2026), and consumption-based pricing are all designed to position Agentforce as the coordination layer for customer-facing operations. The company is building outward from CRM toward broader enterprise workflows, which is the opposite direction from Microsoft's productivity-inward approach. The risk for Salesforce is scope. CRM is a strong foundation for customer-facing agents, but enterprise agent coordination spans finance, supply chain, HR, IT, and operations. Salesforce has to convince enterprises that a CRM-rooted platform can govern agents across all of those domains. That is a harder sell than governing agents within the customer engagement boundary.
Google is the infrastructure-up play. At Cloud Next 2026, Google rebranded its enterprise AI offerings under the Gemini Enterprise banner: a unified control plane for building, deploying, securing, and orchestrating AI agents at enterprise scale. The platform includes Agent Designer for schedule-based and trigger-based agents, long-running agent capabilities for complex business processes, and native integration with Google Workspace. CEO Sundar Pichai reaffirmed capital spending of $175 billion to $185 billion for 2026, signaling investment at a scale only two or three other companies can match. Google's advantage is technical: proprietary silicon (TPUs), model capabilities (Gemini), and data infrastructure give it a vertically integrated stack no other enterprise vendor can replicate. The disadvantage is commercial. Google has historically struggled to build the enterprise sales relationships and ecosystem partnerships that Microsoft, Salesforce, and SAP cultivated over decades. The AI platform war tests whether technical superiority can overcome go-to-market disadvantage, and historical precedent is not encouraging.
AWS is the model-agnostic infrastructure play. Amazon Bedrock AgentCore reached general availability in June 2026 with published per-vCPU pricing and framework-agnostic design. AWS's Q2 2026 results showed the cloud business growing 36.7% year over year to a $169 billion annualized run rate, with the AI business passing a $25 billion run rate and growing at triple-digit rates. Hundreds of thousands of customers now use Bedrock, and Amazon says customers spent more on the platform in Q2 than in all prior quarters combined. AWS's theory is that enterprises will want to choose their own models, their own agent frameworks, and their own orchestration approaches, and that the platform that enables the most choice wins. This is the same strategy that won the cloud infrastructure war: be the utility, not the application. The OpenAI models arriving on Bedrock after the Azure exclusivity ended in April 2026 reinforced the positioning. If every major model is available on AWS, the argument goes, why commit to a single-vendor agent stack? The counterargument is that infrastructure neutrality is not the same as enterprise coordination. AWS provides the compute and the model access, but the governance, orchestration, and business logic layers that enterprises need to coordinate agents across functions are problems that infrastructure alone does not solve.
SAP is the business process play. At Sapphire 2026, SAP unveiled the Autonomous Suite, deploying more than 50 domain-specific Joule AI assistants across finance, supply chain, procurement, HR, and customer engagement. For RISE with SAP customers, Joule Assistants will be activated within the first year. SAP's Joule Studio offers agent-to-agent integration with Microsoft 365 Copilot through a bilateral partnership, and the company has established partnerships with Anthropic, Microsoft, NVIDIA, AWS, Google, and Palantir. SAP's advantage is business process depth. No other vendor has the same breadth of structured enterprise data and process knowledge across finance, supply chain, and procurement. The Joule agents are embedded in the business processes, not layered on top of them. Early adopters include Nestle (Accounts Receivable Assistant across 140 countries) and PwC (Billing Assistant). SAP reports that Joule Work is live with 110,000 internal employees, delivering 20% productivity gains, though that figure is internal and unverified externally. The limitation is adoption speed. SAP itself acknowledges that Joule Studio adoption has been minimal. The barrier is not technology but prerequisites: SAP's autonomous agents depend on clean core, BTP-based extensibility, and consumption-based AI Units. On-premises customers can access Joule assistants only by committing 50% of maintenance spend to cloud first. For the large portion of SAP's installed base still on legacy systems, the agent future requires a migration that many have been slow to complete. Only about a third of SAP customers have moved to S/4HANA.
ServiceNow is the workflow-automation play. The company's AI business crossed $1 billion in annual contract value in Q2 2026, with management projecting AI ACV to exceed $1.5 billion by year-end. Agentic deployments increased ninefold in nine months, and ServiceNow claims its autonomous ITSM specialists can resolve 80 to 85% of service requests without human intervention. Q2 subscription revenue reached $3.88 billion, up 24.5% year over year. Total remaining performance obligations hit $29 billion. ServiceNow's strategic position is distinctive. It does not compete directly in productivity (Microsoft), CRM (Salesforce), or ERP (SAP/Oracle). It competes in workflow automation, which is the connective tissue between all of those systems. The AI Control Tower, announced at Knowledge 2026, positions ServiceNow as the governed layer for enterprise AI, and the acquisitions of MoveWorks (conversational AI for IT) and Veza (identity and access governance) strengthen the platform's ability to manage agent permissions and cross-system workflows. The dual partnerships with both OpenAI and Anthropic, signed in January 2026, were explicitly framed as a customer optionality feature, avoiding model lock-in while building the orchestration layer above it.
Oracle is the embedded-and-included play. Oracle's Fusion Agentic Applications bring more than 1,000 AI agents across Fusion Cloud in HCM, finance, supply chain, and customer experience, all at no additional cost to existing customers. The September 2026 launch of Fusion Claw brought the total to 75 purpose-built agentic applications for governed, autonomous business process execution. For fiscal Q2 2026, cloud revenues surged 34% to $8 billion, with total revenues of $16.1 billion. Oracle's theory is that agents should be invisible. They should be embedded in the applications customers already use, running on the database that already holds the data, governed by the policies already in place, and charged for as part of the existing subscription. This is the opposite of the platform-play approach: instead of asking enterprises to adopt a new agent platform, Oracle absorbs agents into the existing application stack. The risk is that invisible agents are also unremarkable agents. If every enterprise vendor embeds basic agent capabilities at no additional cost, embedded agents become table stakes rather than a competitive differentiator. Oracle's bet is that depth of business process integration will distinguish its agents from commodity offerings.
The Three Fault Lines
Beneath the vendor-by-vendor competition, three structural fault lines will determine how the platform war plays out.
The first fault line is platform scope versus best-of-breed. The cloud era produced a clear winner in the platform-versus-best-of-breed debate: platforms won. Salesforce consolidated CRM, Microsoft consolidated productivity, and the hyperscalers consolidated infrastructure. The agentic AI era may produce a different outcome, because agents create value at the boundaries between platforms, not within them. An agent that coordinates a customer interaction across CRM, ERP, and IT service management creates more value than an agent that operates within any one of those systems alone. If cross-platform coordination becomes the primary source of agent value, the advantage shifts from platform breadth to interoperability, and the vendors that enable coordination across ecosystems may win over the vendors that try to own the entire stack.
The second fault line is pricing model. The vendors have not converged on how to charge for agents. Microsoft charges per seat ($99/user/month for E7). Salesforce uses consumption-based pricing. SAP charges through AI Units. Oracle includes agents at no additional cost. ServiceNow prices through existing subscription tiers with AI ACV tracked separately. AWS charges per vCPU for infrastructure. The pricing model matters because it shapes adoption. Per-seat pricing creates predictable costs but limits experimentation. Consumption pricing aligns cost with usage but makes budgeting harder. Included-at-no-cost drives adoption but raises questions about long-term sustainability. The pricing models will converge over time, but in the near term, the model a vendor chooses signals what it thinks the market will reward: breadth of deployment, depth of usage, or platform stickiness.
The third fault line is lock-in versus portability. Every platform vendor benefits when agents stay within its ecosystem. Agent-level lock-in forms through three mechanisms: API dependency (architecture bends around a single vendor's design choices), agent framework capture (switching costs compound when workflows sit on proprietary orchestration), and data gravity (institutional knowledge accumulates in the platform, making departure progressively more expensive). The A2A and MCP protocols provide some portability at the communication layer, but the harder lock-in is at the business logic layer, where the agent's reasoning, memory, and workflow state are tightly coupled to the platform.
Zylo's 2026 SaaS Management Index found that 79% of IT leaders were hit with a price increase at their most recent renewal. The agentic AI era will amplify this dynamic. The more institutional knowledge an organization deposits into an agent platform, the more leverage the vendor holds at renewal. Enterprises that do not design for portability from the beginning will discover the cost of switching too late.
The Historical Parallel
The closest historical parallel is the cloud platform war of 2006 to 2016. AWS launched S3 in 2006 and held a commanding lead for years. Azure launched in 2010 and leveraged Microsoft's enterprise relationships to close the gap. Google Cloud launched in 2012 with arguably superior technology but consistently lagged in enterprise market share. By the time the cloud market matured, three hyperscalers controlled the infrastructure layer, and the competitive positions established during the first five years proved durable.
The agentic AI platform war is following a similar pattern, with a critical difference. The cloud war was primarily an infrastructure fight: who provides the best compute, storage, and networking. The agentic AI war is an application-layer fight: who provides the best interface between humans, agents, and enterprise systems. This means the competitors are not just the hyperscalers. They are the application vendors (Salesforce, SAP, Oracle, ServiceNow) who own the business processes that agents need to automate, and the productivity vendors (Microsoft, Google) who own the user interfaces through which humans interact with agents.
The ERP consolidation of the 1990s is an instructive parallel for the application-layer dimension. In the early 1990s, enterprises ran best-of-breed systems for finance, HR, manufacturing, and supply chain. By the late 1990s, SAP, Oracle, and PeopleSoft had consolidated those functions onto integrated platforms. The argument for consolidation was the same one platform vendors make today: integrated systems reduce complexity, improve data consistency, and lower total cost of ownership. The argument against consolidation was also the same: integrated platforms sacrifice best-in-class functionality for ease of management, and once you commit, you are locked in.
The ERP consolidation took roughly a decade and produced two durable winners (Oracle and SAP) from a field of more than a dozen serious competitors. Siebel, PeopleSoft, JD Edwards, and Baan were either acquired or marginalized. The agentic AI platform war will produce its own set of winners and casualties, and the timeline may be shorter, because cloud distribution enables faster adoption cycles than the on-premises installation cycles of the 1990s.
What Enterprise Leaders Should Ask
The platform choices enterprises make in the next two years will be difficult to reverse. Before committing to a primary agent platform, enterprise leaders should ask five questions.
First, where is the coordination value? If the highest-value agent use cases in your organization span multiple systems (customer interactions that touch CRM, ERP, and IT simultaneously), a single-vendor platform may not capture that value. Map the use cases first, then evaluate which platform or combination of platforms can support cross-system coordination.
Second, what is the lock-in trajectory? Every platform creates some lock-in. The question is not whether lock-in exists but how fast it compounds. Evaluate how much institutional knowledge (agent memory, workflow state, fine-tuning data, custom logic) accumulates in the platform over time, and whether that knowledge can be exported or replicated. Design for portability even if you do not exercise it immediately.
Third, what is the pricing endgame? Vendors are currently competing for adoption, and pricing reflects that. But adoption-phase pricing is not steady-state pricing. Evaluate where the vendor's pricing model is heading, not where it is today. A platform that includes agents at no additional cost today may introduce consumption charges once adoption is established. A per-seat model may shift to consumption as usage patterns become clearer.
Fourth, who owns the orchestration layer? As the Agent Coordination Gap series argues, the coordination layer between agents from different platforms is the most consequential piece of infrastructure in a multi-agent enterprise. If your vendor claims to provide it, ask whether the orchestration works equally well for agents from competing platforms or only for agents within the vendor's ecosystem. If the answer is the latter, the orchestration layer is a lock-in mechanism, not a coordination tool.
Fifth, does the vendor's theory of agents match your operating model? Microsoft assumes agents extend productivity tools. Salesforce assumes agents extend customer relationships. SAP assumes agents extend business processes. Oracle assumes agents are embedded and invisible. ServiceNow assumes agents extend workflow automation. AWS assumes agents are model-agnostic and infrastructure-hosted. Google assumes agents are built on proprietary AI infrastructure. Each theory implies a different organizational model, different governance requirements, and different skill sets. The right platform is the one whose theory aligns with how your organization creates value, not the one with the best benchmark or the largest market share.
The Next 18 Months
The agentic enterprise platform war is in its early innings. The competitive positions are not yet fixed, the pricing models are not yet settled, and the standards (A2A, MCP) that will enable cross-platform coordination are still maturing. But the window for making platform choices without incurring significant switching costs is narrowing. Every quarter that enterprises deploy agents on a specific platform adds to the institutional knowledge, workflow state, and organizational habits that make switching more expensive.
The organizations that navigate this well will be the ones that treat the platform decision as a strategic choice, not a technology procurement exercise. They will evaluate vendors not just on current capability but on strategic alignment, portability, and long-term pricing trajectory. They will design for multi-platform coordination from the beginning, even if they start with a single vendor. And they will remember the lesson of every previous platform war: the vendor that wins the adoption race in the first three years usually holds the position for the next ten.
This series will examine each vendor's strategy in depth over the next eight articles, beginning with the two largest combatants: Microsoft and Salesforce.
Strategy Playbook
1. Platform Landscape Assessment. Before making or deepening any platform commitment, map the full agent landscape across your organization. Document which vendors are already deployed, which agent capabilities each provides, and where the highest-value use cases sit relative to platform boundaries. The goal is a clear picture of where single-platform agents deliver sufficient value and where cross-platform coordination is required. This assessment should include shadow AI and unsanctioned agent deployments, which Airia's 2026 data suggests account for 65 to 75% of enterprise AI tools.
2. Lock-In Stress Test. For each platform under consideration, model the switching cost trajectory over three years. What institutional knowledge accumulates in the platform? What is the export path for agent memory, workflow state, and custom logic? What happens to pricing at renewal? Zylo's finding that 79% of IT leaders faced price increases at their last renewal is a baseline assumption, not an outlier. Build the exit scenario before you build the deployment plan.
3. Multi-Vendor Coordination Architecture. Design the coordination layer between platforms as a first-class architectural concern, not an afterthought. This means evaluating A2A and MCP support across your vendor stack, establishing shared governance frameworks that span platform boundaries, and defining cross-platform decision authority for agents that interact with multiple systems. The Agent Service Bus framework described in the Agent Coordination Gap series provides a reference architecture for this work.
4. Pricing Model Scenario Planning. Build financial models for at least three pricing scenarios per vendor: current pricing, a 25% increase at renewal, and a shift to consumption-based billing. The vendor that looks cheapest under current pricing may be the most expensive under steady-state pricing. Factor in the full cost of agent operations, including model inference, data processing, governance overhead, and the organizational cost of managing the platform, not just the license fee.
Arion Research advises enterprise leaders on AI strategy and the shift to a digital workforce.
