3 Acquisitions, 1 Shift: Why Independent AI Platforms Are the Future of Enterprise Automation

Three acquisitions. One clear pattern. And it's not good for enterprise buyers.

Moveworks → ServiceNow ($2.85 billion). Aisera → Automation Anywhere (November 2025). Forethought → Zendesk (March 2026). In less than twelve months, three of the most promising independent AI agent companies have been absorbed into platform conglomerates—and the implications for enterprise automation are far more significant than any press release will admit.

Here's the truth no acquiring company puts in its announcement: when an AI agent company gets acquired by a platform company, the buyer's ecosystem becomes the product's ceiling. Your AI agents no longer work for you. They work for the platform's roadmap.

This post breaks down what each acquisition actually means for enterprise buyers, why platform-attached AI is a strategic liability, and why independent AI agent platforms—ones that sit between your tools rather than inside one of them—are the only architecture that survives the next wave of vendor consolidation.

The Three Acquisitions: What Actually Happened

Moveworks → ServiceNow ($2.85B, March 2025 announcement)

ServiceNow announced its intent to acquire Moveworks for $2.85 billion in March 2025, calling it a "game changer" for agentic AI. The deal closed in December 2025. On the surface, it looks like a win: ServiceNow gets Moveworks' front-end AI assistant and enterprise search technology, and Moveworks gets ServiceNow's massive distribution channel.

But dig deeper. The DOJ launched an in-depth antitrust investigation in July 2025, issuing a "second request" for documentation—a signal that regulators saw competitive concerns in the enterprise AI sector. The review centered on whether combining ServiceNow's workflow automation dominance with Moveworks' agentic AI capabilities would create an unfair lock-in dynamic.

For existing Moveworks customers who aren't on ServiceNow, the acquisition raises immediate questions:

• Will Moveworks continue to invest in non-ServiceNow integrations? The acquirer's roadmap priorities will naturally shift toward its own platform. Every engineering hour spent on a Salesforce or Jira connector is an hour not spent on ServiceNow integration.
• What happens to pricing? Moveworks mindshare declined from 15.2% to 8.1% post-acquisition announcement, according to industry data. When product investment shifts toward the parent platform, the standalone offering stagnates while pricing often increases.
• What about the DOJ review? Even if the deal cleared, regulatory scrutiny signals that this acquisition is structurally different from a simple talent grab. The market power implications are real.

Aisera → Automation Anywhere (November 2025)

Automation Anywhere acquired Aisera in November 2025, framing it as a move to create "the industry's most comprehensive agentic automation portfolio." Aisera had raised $150 million in funding and built a strong position in IT Service Management (ITSM), HR, and customer service self-service agents.

The problem? Aisera's value proposition was built on being platform-agnostic—working across whatever systems an enterprise already had in place. Post-acquisition, G2 reviews citing "steep learning curve" and "complex and draining" fine-tuning processes suggest the technology is now being molded to fit Automation Anywhere's RPA-first architecture rather than evolving as a standalone agentic platform.

For enterprises, this means:

• Aisera's AI agents will increasingly be bundled within Automation Anywhere's automation suite, reducing the standalone offering's investment and innovation velocity.
• Pricing transparency disappears. Aisera's deals ranged from $100,000 to $500,000 per year pre-acquisition. Post-acquisition, pricing is folded into broader Automation Anywhere contracts, making it nearly impossible to evaluate the AI agent component independently.
• Cross-platform capabilities erode. When your AI agent company is owned by an RPA company, the "automation" lens dominates the "intelligence" lens. Agents become glorified macros rather than autonomous decision-makers.

Forethought → Zendesk (March 2026)

Zendesk announced its acquisition of Forethought on March 11, 2026, projecting it as "the year AI agents will surpass human service." The deal closed within weeks. Forethought's self-improving AI agents and agentic resolution capabilities were the crown jewels—exactly what Zendesk needed to compete in the AI-first customer service race.

But Forethought came with baggage. A 2.3/5 Trustpilot rating. End-user reviews that were nearly 100% one-star. The technology was promising, but the product-market fit was fragile. Zendesk's solution? Absorb Forethought into its own platform rather than maintaining it as a standalone product.

For Forethought customers, the writing is on the wall:

• Forethought as a standalone product has an expiration date. Zendesk stated it will "continue to support existing customers," but the strategic direction is integration into Zendesk's resolution platform. Non-Zendesk customers are on borrowed time.
• $1.50 per resolution becomes a Zendesk pricing line item. The per-resolution model that made Forethought interesting will be absorbed into Zendesk's broader pricing structure, which already includes AI add-ons at $50/agent/month and Quality Assurance add-ons at $25/agent/month.
• The cross-platform promise is gone. Forethought's value was in bringing AI agents to whatever helpdesk you used. Post-Zendesk, it's a Zendesk feature—available inside the walled garden.

The Pattern: AI Walled Gardens Are Being Built in Real-Time

Strip away the press releases and analyst quotes, and the pattern is unmistakable:

Each acquisition follows the same playbook:

1. Acquire a promising independent AI agent company with cross-platform capabilities
2. Integrate the technology into the acquirer's platform ecosystem
3. Deprioritize non-platform integrations and standalone functionality
4. Bundle pricing into opaque enterprise contracts
5. Lock in customers who now depend on a single vendor for both their platform and their AI capabilities

The result? Enterprise buyers who chose these AI agent companies because they were independent now find themselves trapped in a platform they didn't sign up for. Their AI agents don't cross boundaries anymore—they patrol the walls.

Why Platform-Attached AI Fails Enterprise Operations

The fundamental problem with platform-attached AI agents isn't technology—it's incentives. When your AI agent company is owned by your CRM company, or your helpdesk company, or your ITSM company, the agent's design decisions are driven by what sells more platform licenses, not what solves more operational problems.

The Cross-Platform Reality

Modern enterprise operations don't live in one system. A single freight claims workflow might touch Salesforce (customer record), Jira (engineering escalation), Zendesk (support ticket), a carrier portal (proof of delivery), and a TMS (shipment data). An AI agent that only operates inside one of those systems can only handle a fraction of the workflow.

Here's what that looks like in practice:

• Salesforce Agentforce can route a case and update a record, but it can't pull proof of delivery from a carrier portal or create a Jira escalation ticket without MuleSoft (an additional $250,000+/year integration layer).
• Zendesk AI (now with Forethought) can resolve support tickets autonomously, but it can't update the Salesforce opportunity or trigger a Jira workflow. Its world ends at the Zendesk boundary.
• ServiceNow + Moveworks can automate IT service management end-to-end—within ServiceNow. But operations teams using Salesforce + Jira + Zendesk together? That's not the product's focus anymore.

The average enterprise operations team uses 4.6 systems for a single workflow. A platform-attached AI agent can reach 1 of them natively. That's not automation—that's a tourist visa.

The Vendor Lock-In Multiplier

Here's the insidious math of platform consolidation. Before these acquisitions, an enterprise buyer could:

• Use ServiceNow for ITSM
• Use Moveworks for AI-assisted employee support
• Use Salesforce for CRM
• Use Zendesk for customer support

Each tool competed on its own merits. If Moveworks underperformed, you could replace it without touching ServiceNow. If Forethought didn't deliver, you could swap it out without disrupting Zendesk.

Post-acquisition, replacing your AI agent means replacing—or at minimum renegotiating—your entire platform contract. The switching cost isn't just the AI tool. It's the platform integration, the data migration, the team retraining, and the contract penalty. VentureBeat reported in January 2026 that acquisitions and consolidation in enterprise AI "can lead to vendor lock-in"—a polite way of saying you're trapped.

The Incentive Misalignment

When ServiceNow owns Moveworks, the incentive is to make Moveworks work best with ServiceNow. When Zendesk owns Forethought, the incentive is to make Forethought a reason to buy Zendesk. When Automation Anywhere owns Aisera, the incentive is to sell more Automation Anywhere licenses, not more Aisera standalone value.

This isn't speculation—it's economics. The acquiring company paid billions for these AI companies. The ROI on that investment comes from selling more of the acquirer's platform, not from maintaining a healthy standalone AI agent market.

Constellation Research noted in their 2026 enterprise trends analysis that "the buy side is still wary of lock-in." They're right to be. The lock-in isn't coming—it's already here.

The Counter-Strategy: Independent AI Agent Platforms

If platform-attached AI agents are the problem, the solution isn't another platform-attached AI agent. It's an independent AI agent platform—one that sits between your existing tools rather than inside one of them.

What "Independent" Actually Means

An independent AI agent platform has three non-negotiable characteristics:

1. Platform-agnostic by design. The platform's architecture treats every connected system—Salesforce, Jira, Zendesk, ServiceNow, SAP—as a first-class citizen. No system gets preferential treatment based on corporate ownership.

2. SOP-driven, not platform-driven. The AI agent's behavior is governed by your standard operating procedures, not by the platform's product roadmap. Your claims handling process doesn't change because a vendor got acquired.

3. Portable. Your SOPs, agent configurations, and workflow automations can move with you. If you switch from Zendesk to Freshdesk, your AI agents adapt—not get sunset.

SOP Portability as the Moat

The deepest moat in enterprise AI isn't the model. It's not even the platform. It's your SOPs—the institutional knowledge encoded in your standard operating procedures that defines how your business actually runs.

When your AI agents are platform-attached, your SOPs get absorbed into the platform's architecture. You can't take them with you. When your AI agents are independent, your SOPs are portable. You own the intelligence layer. The platform is just infrastructure.

This is what we mean by SOP portability: the ability to define what your AI agents do independently of where they do it. Your freight claims process—verifying proof of delivery, checking shortage quantities, escalating to the carrier, updating the customer record—shouldn't be a Zendesk workflow or a Salesforce flow. It should be an SOP that your AI agents execute across whatever systems are involved.

The Cross-Platform Advantage

Independent AI agent platforms don't just avoid the lock-in problem—they turn it into a competitive advantage. When your agents can operate across Salesforce, Jira, Zendesk, and any other system in your stack, you get capabilities that platform-attached agents literally cannot deliver:

• End-to-end workflow automation. Not "automate the Salesforce part" or "automate the Zendesk part"—automate the entire workflow from trigger to resolution.
• Intelligent routing across platforms. An AI agent that can read a Salesforce case, determine it needs engineering attention, create a Jira ticket with full context, and update the customer in Zendesk—all without human intervention.
• Cross-platform analytics. Knowing that 34% of your Jira escalations originate from Zendesk tickets about carrier delays isn't possible when your analytics are siloed by platform.
• Consistent SOP execution. Your returns handling process should work the same way whether the customer contacts you through Zendesk, email, or a carrier portal. Independent agents make that possible.

The Decision Framework: How to Evaluate AI Agent Platforms in 2026

If you're evaluating AI agent platforms right now, the acquisition wave adds a critical question to your due diligence: Who owns this company, and what happens to my workflows if that changes?

Here's a five-question framework:

1. Is the platform independent or platform-attached?

If the AI agent company is owned by a platform company, assume that platform gets priority. Ask for a roadmap commitment in writing. If they won't give you one, that's your answer.

2. Can my SOPs move with me?

If your AI agent's behavior is defined by platform-specific workflows (Salesforce flows, Zendesk triggers, ServiceNow workflows), you're locked in. If it's defined by portable SOPs that work across any connected system, you're in control.

3. Does the platform treat all integrations as first-class citizens?

Check the integration depth. A platform that has a "native" integration with one system and "API-based" integration with everything else is telling you where its priorities are. Look for equal integration depth across all your critical systems.

4. What happens to my investment if the vendor gets acquired?

This is the question nobody asked Moveworks, Aisera, or Forethought customers before the acquisitions happened. Ask for contractual guarantees around standalone product investment, cross-platform support, and pricing stability post-acquisition. If the vendor won't commit, factor that risk into your TCO calculation.

5. Does the pricing model incentivize cross-platform use or platform lock-in?

Per-resolution pricing that only counts resolutions within one platform incentivizes the vendor to keep you in that platform. Per-case or per-workflow pricing that spans multiple systems incentivizes the vendor to help you automate end-to-end.

The Strategic Reality

The enterprise AI market is consolidating. That's not a prediction—it's a fact, proven by three acquisitions in under a year totaling well over $3 billion. The question isn't whether consolidation will continue. It's whether you'll be ready when it reaches your vendor.

The enterprises that win the AI automation race won't be the ones that bet on the right platform. They'll be the ones that bet on architecture—choosing independent, cross-platform, SOP-driven AI agents that work with what they already have, rather than forcing them into a walled garden they'll pay to escape later.

Three acquisitions have already happened. The next one could be yours. Choose independence while you still can.

---

Ready to see what cross-platform, SOP-driven AI automation looks like in practice? Book a demo to see how CorePiper handles end-to-end workflows across Salesforce, Jira, Zendesk, and your carrier portals—no walled gardens required.

Frequently Asked Questions

What does "independent AI agent platform" mean?

An independent AI agent platform is one that isn't owned by or structurally tied to any single enterprise software platform (CRM, ITSM, helpdesk). It sits between your existing tools and orchestrates workflows across all of them, treating every connected system as a first-class citizen. Independence means your AI agents work for your operations, not for a platform's ecosystem strategy.

Why are AI agent companies getting acquired?

AI agent companies represent the "intelligence layer" on top of enterprise platforms—and platform companies want to own that layer. By acquiring independent AI companies, platform vendors can turn a competitive threat (AI agents that work across platforms) into a competitive moat (AI agents that only work inside their platform). The financial incentive is clear: AI agents drive platform adoption and increase switching costs.

Is the Moveworks acquisition by ServiceNow a problem for non-ServiceNow customers?

Yes. ServiceNow acquired Moveworks to strengthen its own agentic AI capabilities, not to maintain a thriving cross-platform AI assistant. Non-ServiceNow customers should expect diminishing investment in non-ServiceNow integrations, potential pricing changes, and reduced strategic attention. The DOJ's antitrust investigation itself signals competitive concerns.

What is SOP portability and why does it matter?

SOP portability means your standard operating procedures—the rules and workflows that govern how your AI agents behave—aren't locked into a specific platform's format or architecture. If you switch helpdesk tools or CRM platforms, your SOPs move with you. Without SOP portability, changing platforms means rebuilding your entire automation layer from scratch.

How do I evaluate whether an AI agent platform will stay independent?

Look at four signals: (1) ownership structure—is the company independent or subsidiary? (2) Integration parity—do all connected systems get equal investment? (3) Pricing model—does it incentivize cross-platform use or platform lock-in? (4) Contractual commitments—will the vendor guarantee standalone product investment and cross-platform support in writing?