Should ServiceNow acquire UiPath to win agent automation?

The UiPath Reality In 2026

• Market cap collapse: From $30B+ peak (May 2021) to $5-7B as of Q1 2026 — an 80%+ drawdown that reflects investor verdict on RPA-as-a-category, not just execution
• Revenue deceleration: ~$1.4B FY25 ARR growing 8-10% YoY, down from 40%+ growth in 2021-22; net retention has fallen from 144% (2021) to ~110% (FY25)
• AI agent pivot status: UiPath Autopilot + Agent Builder launched 2024-25 with mixed reception — analyst notes flag "product-market fit unclear" and overlap with native Microsoft/ServiceNow agent stacks
• Named churn signals: Multiple Fortune 500 deployments downsizing seat counts as Power Automate Premium absorbs use cases; Gartner MQ position weakening vs. Microsoft
• CEO/leadership churn: Daniel Dines returned as CEO in 2024 after Rob Enslin departure — classic founder-rescue pattern that often precedes either turnaround or distress sale

The 4 Reasons NOT To Buy UiPath

• The RPA category is being eaten by Microsoft: Power Automate Premium at $15/user/mo (and increasingly bundled with M365 E5 + Copilot) is destroying standalone RPA pricing. ServiceNow would be acquiring a category in structural decline, not a growth asset.
• It dilutes ServiceNow's AI-first narrative: ServiceNow has spent 24 months positioning AI Agent Studio + Now Assist as the workflow-native AI control plane. Bolting on a screen-scraping RPA vendor is a step backward in narrative — Wall Street would mark it as defensive M&A.
• $5-7B is wildly overpriced for a transitioning company: At ~4-5x revenue for a sub-10% grower with declining net retention, this is a premium SaaS multiple for a company that should trade at infrastructure-software multiples (2-3x). The fair price is closer to $2.5-3.5B.
• Cultural and architectural mismatch: UiPath is a Windows-desktop, agent-on-endpoint vendor. ServiceNow is a multi-tenant cloud workflow platform. Integrating UiPath's runtime into the Now Platform is a 24-36 month engineering slog with high risk of stranded investment.

The 1 Scenario Where It Could Work

• Distress trigger: UiPath market cap drops below $3B in a 2027 down round / activist pressure event (Elliott or Starboard already circling per industry chatter)
• Structured deal mechanics: ServiceNow does a Microsoft-Activision-style structured acquisition — cash + earnout + retention pool, total enterprise value $2.5-3.2B, with regulatory carve-outs for the EU agent runtime
• Acquihire thesis: The 800-person EU automation engineering team (Bucharest, Bellevue) becomes the real asset — folded into ServiceNow's AI Agent Studio org under a single VP
• Customer-base play: UiPath's Fortune 500 install base (Coca-Cola, GE, Cisco) gets migrated onto Now Platform within 18 months — net new ServiceNow workflow seats become the ROI justification
• Product sunset path: UiPath standalone product gets a 36-month maintenance commitment, then end-of-life as customers migrate to native AI Agent Studio

What ServiceNow Should Do Instead

• Build out AI Agent Studio organically: Already 18 months ahead on workflow-native agents; double engineering headcount to 600+ on the agent runtime, ship monthly
• Acquire smaller AI-native ($300-500M Decagon-tier): Decagon, Sierra, Ada, or similar AI-customer-service agents — workflow-native, no RPA legacy debt, integrate in 90 days vs. 24 months
• Partner with named RPA legacy customers: Direct outbound to UiPath's top-50 accounts with a "Now Platform AI Agent Studio + 50% RPA seat-cost" replacement offer
• Talent acquisition from UiPath alumni: Hire 50-100 senior engineers from UiPath via individual offers — same engineering capability, 2% of the cost, no integration drag
• OEM Microsoft Power Automate (counterintuitive): If you can't beat them, embed Power Automate triggers natively in Now Platform — turns Microsoft into a feeder, not a competitor
• Quiet partnership with UiPath itself: Buy the integration, not the company — joint go-to-market, revenue share, optionality on future acquisition without the balance-sheet risk

The Microsoft Question

• Power Automate Premium pricing kills standalone RPA: $15/user/mo is 60-70% below UiPath equivalent; bundled with M365 E5 it's effectively free for the largest enterprise buyers
• Copilot Actions absorbs the agent layer: Microsoft is shipping native AI agents in Teams, Outlook, and Dynamics — the "automation" use case is being absorbed into the productivity suite
• The free-with-M365 thesis: Once a category is bundled into a $57/user/mo productivity suite, standalone vendors lose pricing power permanently — see what happened to standalone email security vs. Defender
• Named pattern: Same dynamic killed standalone web conferencing (vs. Teams), standalone diagramming (vs. Visio), standalone forms (vs. Forms) — RPA is next
• Implication for ServiceNow: Acquiring UiPath means inheriting a price war you cannot win against an opponent who can give the product away

The Comparable Failed RPA-Adjacent Acquisitions

• BMC + Innotas (2018): PPM tuck-in that took 36 months to integrate, shed 40% of customers, written down as goodwill in 2021
• Pega + various RPA tuck-ins (2019-22): Pega's RPA strategy — partly organic, partly acquisition — never produced material revenue lift; analyst day disclosures dropped RPA as a separate category in 2024
• Appian + Jitterbit partnership (not acquisition, but instructive): Appian wisely chose partnership over acquisition for integration capability — preserved balance sheet, kept narrative clean
• Salesforce + MuleSoft (2018): $6.5B price, integration took 4 years, eventually justified — but only because integration-platform-as-a-service grew into AI; RPA has no such tailwind
• Pattern: Workflow platform + RPA vendor acquisitions consistently underperform deal models by 30-50%; the integration drag and narrative confusion outweigh revenue synergy

Strategy Comparison Table

Strategic Decision Flow

Related on PULSE

• [Should ServiceNow launch its own AI agent marketplace?](/knowledge/q1665)
• [How does ServiceNow ARPU change post-AI agent rollout?](/knowledge/q1633)
• [How should B2B companies redesign their demo environments to handle simultaneous AI agent testing by prospects?](/knowledge/q16563)
• [What specific signals indicate a buying committee is using an AI agent to negotiate contract terms in 2027?](/knowledge/q16400)
• [How do you structure a 2027 sales contract when the main buyer is an AI procurement agent?](/knowledge/q16309)
• [What are the most common friction points when a buying committee uses an AI procurement agent to negotiate contract terms in 2027?](/knowledge/q13532)

Integration Complexity and Cultural Clash

Beyond the financial and product concerns, the operational reality of merging ServiceNow's structured IT service management (ITSM) culture with UiPath's automation-first DNA would be a multi-year distraction. ServiceNow's platform is built on a strict data model, workflow engine, and governance framework; UiPath's core value proposition has historically been its ability to operate outside such boundaries — scraping legacy UIs, orchestrating unattended bots across unmanaged endpoints, and handling "swivel-chair" tasks that ITSM tools explicitly avoid. Integrating UiPath's agentic automation layer into ServiceNow's Now Platform would require either gutting UiPath's flexibility (alienating its existing customer base) or weakening ServiceNow's governance (risking compliance failures in regulated industries like finance and healthcare). Industry sources indicate that post-merger integration for enterprise software acquisitions typically consumes 12-24 months of engineering bandwidth, during which both product roadmaps stall — a dangerous window given the rapid pace of AI agent development from Microsoft, Salesforce, and startups like Decagon.

The Tuck-In Alternative: Targeted AI Agent Acquisitions

A more capital-efficient path for ServiceNow involves acquiring smaller, specialized AI agent startups at $200-500M valuations rather than pursuing a mega-deal. Decagon (AI for customer service automation) and similar firms offer proven agentic capabilities that can be natively embedded into ServiceNow's existing workflows without the integration baggage of a $5B+ acquisition. These tuck-ins typically come with 50-150 engineers, established enterprise customers, and technology that complements rather than conflicts with ServiceNow's architecture. The acquisition premium for such targets remains reasonable (3-5x ARR vs. UiPath's ~8-10x current revenue multiple), and integration timelines shrink to 6-9 months. ServiceNow's strong balance sheet ($6-8B cash and equivalents as of late 2025) gives it ample dry powder for 3-5 such deals over 18 months — a portfolio approach that builds agent automation capabilities organically while avoiding the "melting ice cube" risk of a legacy RPA platform.

Strategic Fit Gaps

ServiceNow’s platform is built on a unified data model (CMDB) and workflow engine, while UiPath’s architecture is agent-agnostic and desktop-centric. A merger would require deep re-platforming of UiPath’s robot runtime to ServiceNow’s cloud-native stack—estimated at 12-18 months and $200-400M in engineering costs—with no guarantee of seamless integration. The resulting product would compete internally with ServiceNow’s own AI Agent Studio, creating channel conflict and customer confusion.

Alternative Tuck-In Candidates

ServiceNow could achieve similar agent automation capabilities for 5-10% of UiPath’s acquisition cost. Companies like Decagon (AI customer service agents, ~$300M valuation), Skan.ai (process discovery, ~$150M), or Kryon (attended automation, ~$100M) offer targeted technology without the legacy RPA baggage. Each provides a discrete capability—agent orchestration, process mining, or desktop automation—that plugs directly into ServiceNow’s existing workflow engine, avoiding integration drag and preserving the $300-500M tuck-in budget for 3-5 smaller, higher-ROI acquisitions.

Sources

• Gartner — market analysis and forecasts for enterprise automation and RPA.
• Forrester Research — reports on robotic process automation and AI-driven agent platforms.
• ServiceNow Investor Relations — official financial filings, strategy presentations, and acquisition history.
• UiPath Investor Relations — official financial disclosures, product roadmaps, and market positioning.
• Harvard Business Review — articles on enterprise automation strategy, M&A rationale, and organizational impact.
• IDC — industry research on automation software market share, trends, and competitive dynamics.

FAQ

Is UiPath's market cap really that low? Yes, UiPath's market cap has dropped from over $30 billion at its 2021 peak to roughly $5–7 billion by early 2026. That decline reflects slowing revenue growth (around 8–10%) and increasing competition from Microsoft and other AI-native platforms.

Could ServiceNow ever benefit from acquiring UiPath? Only if UiPath's valuation falls below $3 billion in a distress scenario, and even then the value would be in the engineering team and enterprise customer base, not the current product. At any higher price, the integration costs and product overlap would outweigh the benefits.

How does Microsoft Power Automate threaten UiPath? Microsoft bundles Power Automate Premium at $15 per user per month, and basic automation is often included free with Microsoft 365 subscriptions. This makes it nearly impossible for UiPath to compete on price or scale, especially as Copilot Actions further erode the need for traditional RPA.

What should ServiceNow do instead of buying UiPath? ServiceNow's best strategy is to build organically with its AI Agent Studio and pursue small tuck-in acquisitions (like Decagon) for $300–500 million. This avoids the 18-month integration drag and high cost of a large acquisition.

Is UiPath's RPA technology still relevant? Desktop and screen-scraping RPA is being rapidly replaced by AI-native agent automation. UiPath is trying to pivot, but its heritage and product architecture make it a "melting ice cube" in a market shifting toward embedded, cloud-based AI agents.

What would a "distress deal" for UiPath look like? If UiPath's market cap drops below $3 billion by 2027, ServiceNow could structure a deal similar to Microsoft's Activision acquisition—buying primarily for the talent (around 800 EU engineers) and the Fortune 500 install base, while phasing out the core RPA product over time.

Bottom Line

No — ServiceNow should not acquire UiPath at $5-7B. The RPA category is structurally declining under Microsoft Power Automate pressure, the integration would dilute ServiceNow's AI-first narrative, and the price is 1.5-2x what a transitioning company should command. The dominant strategy is organic AI Agent Studio investment + $300-500M AI-native tuck-ins + talent raid on UiPath alumni. The only scenario where acquisition makes sense is a 2027 distress event at <$3B with a structured Activision-style deal where the engineering team and customer base — not the product — are the prize.

*(see also: q1620, q1628, q1655)*