Should ServiceNow acquire Workato in 2027?

The boardroom scenario that forces the question

Picture a ServiceNow strategy committee meeting in early 2027. The company is running past $11B in annual revenue with a market capitalization in the $200B range, net revenue retention historically in the 125–130% band, and roughly 8,400 enterprise customers. Bill McDermott has spent five years repositioning the company from an ITSM vendor into what he calls the workflow operating system of the enterprise. The Now Assist agent platform is the headline story in every earnings call. And then a sales VP puts up a slide that ruins the mood.

The slide shows deal reviews from the last two quarters. In a meaningful share of stalled Enterprise+ expansions, the blocker is not price, not competitive displacement, not security review. It is integration. The customer wants an HR onboarding workflow that touches Workday, Okta, Microsoft 365, an AWS IAM role, a badging system, and three business-unit-specific applications. ServiceNow can orchestrate the workflow. What it cannot do gracefully is reach all eight of those systems without either a stack of IntegrationHub spokes, a MID Server deployment, or a professional services engagement measured in quarters.

In roughly a third of those accounts, the customer already solved the problem — with Workato. Not bought through central IT, either. Bought by an HR operations leader or a RevOps team with a departmental budget, spreading laterally through the organization one recipe at a time, and now sitting between ServiceNow and the systems ServiceNow wants to orchestrate. The integration substrate the Now Platform depends on is owned by somebody else, and that somebody else is a venture-backed private company that could be acquired by Salesforce, Microsoft, IBM, or SAP at any point.

That is the actual shape of the question. It is not "does ServiceNow need integration capability" — every platform vendor needs that. It is "does ServiceNow need to own the integration layer that its own strategic accounts have already standardized on, and what is that worth." A vendor that owns workflow but rents connectivity has a structural dependency it did not choose. Salesforce solved this in 2018 by paying $6.5B for MuleSoft at roughly 22 times revenue. Microsoft solved it by bundling Power Automate into M365 and letting distribution do the work. ServiceNow has solved it by partnering — with Workato, with Boomi, with MuleSoft where the customer is Salesforce-anchored — and partnership is a fine answer right up until the moment a competitor buys your partner.

The urgency is real but not acute. The integration gap costs ServiceNow deal velocity and some share of business-user automation budget. It does not threaten the core ITSM franchise, and it does not put the Now Assist roadmap at risk. That distinction matters enormously for pricing discipline: a must-have acquisition gets bid up because the acquirer cannot walk away, while a should-have acquisition preserves the ability to say no at $4.2B. ServiceNow is in the second category, and the entire recommendation flows from that.

How the integration layer actually changes the deal math

To understand why owning the iPaaS layer matters, follow a single workflow through the stack. An employee is hired. Workday, as the HR system of record, creates the worker record. ServiceNow HRSD opens the onboarding case and drives the human-facing tasks — manager checklist, equipment request, first-day agenda. But every one of those tasks needs to actually change state in another system: Okta must provision identity, Microsoft 365 must create the mailbox, the badging system must issue credentials, the laptop must be ordered through a procurement system, and business-unit tools must grant role-based access.

ServiceNow's native path for that is IntegrationHub, which provides spokes for major systems, plus MID Server for anything behind a firewall, plus REST and SOAP APIs for the rest. This works. It is also developer-centric, spoke-by-spoke, and it degrades badly as the number of target systems grows. A workflow touching three systems is comfortable. A workflow touching a dozen — several of them niche, regional, or homegrown — becomes a professional services project.

Workato's architecture attacks the same problem from the other end. Its unit of work is the "recipe": a trigger, a sequence of actions, conditional branching, data transformation, and error handling, authored in a drag-and-drop interface that a business analyst can operate. Behind it sits a connector library in the 1,000–1,200 range covering essentially every major enterprise system and a long tail of smaller SaaS tools. That connector library is the real asset. Any competent engineering team can build a workflow canvas; nobody can conjure a decade of maintained connectors, each one absorbing the target vendor's API changes, auth quirks, rate limits, and pagination behavior.

The commercial consequence is that Workato lands through a different door than ServiceNow. ServiceNow sells top-down to the CIO with multi-year enterprise agreements. Workato lands bottom-up with a department, at $10K–$25K for a small workspace deployment, expanding into $50K–$250K business-tier contracts and $500K–$5M enterprise agreements as recipes proliferate. Pricing blends a platform fee with recipe counts and task-volume consumption, which means revenue grows automatically as automation adoption deepens — a land-and-expand curve ServiceNow's seat-and-module model does not naturally produce.

Combine the two and the mechanism changes in a specific way. ServiceNow account teams currently lose business-user automation budget to Workato because they have nothing to sell into it. Post-acquisition they have a product for that buyer, priced for that buyer, sold through a motion the acquirer would need to preserve rather than replace. The workflow diagram below traces where the value actually accrues.

The second-order effect matters more than the first. AI agents make integration more valuable, not less. A Now Assist agent that can only read and write inside ServiceNow is a chatbot with good context. An agent that can take action across Workday, Salesforce, SAP, and a procurement system is an operator. Every agent capability ServiceNow ships increases the marginal value of the connector library, because the agent's usefulness is bounded by the number of systems it can actually touch. Workato launched its own AI agent products in 2024 and its Workbot conversational surface already runs inside Slack, Teams, and ServiceNow itself — meaning the acquired assets slot into the agent strategy rather than competing with it.

There is a counter-mechanism worth naming honestly. If agents become sophisticated enough to compose API calls dynamically from natural language, the pre-built recipe becomes less central. That argument is directionally plausible and practically overstated for the 2027–2030 window: enterprise integration failure modes are auth, rate limits, schema drift, idempotency, and error recovery, and none of those are solved by a model that can read API documentation. The connector library encodes operational knowledge, not just endpoint syntax. But the risk deserves a discount in the valuation, not a dismissal.

Real numbers: what Workato is worth and what the comparables say

Start with what is reasonably established. Workato was founded in 2013 by Vijay Tella, previously a TIBCO co-founder, an Oracle SVP, and founder of Qik, which Skype acquired. The company has raised on the order of $400M+ across its rounds, with Battery Ventures, Insight Partners, Altimeter Capital, and Tiger Global among the investors, and a reported Series E in November 2021 at a $5.7B valuation. Public estimates of its customer count run from roughly 11,000 to 17,000 depending on the source and date, and revenue estimates cluster in the $200–350M ARR range as of the mid-2020s. Treat every one of those figures as an estimate — Workato is private and does not publish financials.

Now the multiple math. At $300M ARR:

• $2.5B implies roughly 8x ARR
• $3.5B implies roughly 12x ARR
• $4.0B implies roughly 13x ARR
• $5.7B (the 2021 mark) implies roughly 19x ARR

Against transaction comparables, the picture is clarifying. Salesforce paid $6.5B for MuleSoft in March 2018 at roughly 22x — a peak-cycle multiple in a period when growth software traded very differently than it does now. Francisco Partners and TPG took Boomi out of Dell in May 2021 for approximately $4B, after Dell had originally acquired it in 2010 for a figure in the $300M range. Thoma Bravo acquired Anaplan for $10.7B in 2022 and Coupa for roughly $8B in 2023, landing in the 10–16x band. Francisco Partners acquired Sumo Logic in 2023 for about $1.7B, in the mid-single-digit multiple range. Cisco closed its $28B Splunk acquisition in March 2024 at a high-single-digit revenue multiple.

The trajectory is unmistakable: 2018-era multiples for infrastructure software were roughly double where 2023–2025 transactions cleared. A 2027 deal priced off the 2021 Series E would be paying for a market that no longer exists. That is the single most important number in this analysis. Workato's late-stage investors — particularly those who entered at the $5.7B mark — face a hard psychological anchor, and any negotiation will spend months there. ServiceNow's discipline is tested by whether it walks away from a $4B+ ask.

Growth rate matters as much as the multiple. Workato's growth reportedly decelerated from the 80%+ range in 2020–2021 to something closer to 30–40% by 2023–2024. Thirty-plus percent growth on a $300M base is genuinely good and accretive to ServiceNow's own 20–25% growth rate — the deal improves the consolidated growth profile, which public-market investors reward. But 35% growth does not support a 19x multiple in a market where comparable assets clear at 8–13x.

On affordability, the deal is straightforward. ServiceNow generates free cash flow in the multi-billion range annually, holds cash and investments in the multi-billion range, and has a $200B+ equity currency. A $3B deal structured 60% stock and 40% cash is a rounding error on the balance sheet. Affordability is not the constraint; opportunity cost is.

The cross-sell case is where analytical discipline gets tested hardest, because the arithmetic is seductive and the assumptions are soft. A representative build: ServiceNow's 8,400 enterprise customers, at 20–25% adoption of an integration SKU, at a $200K average contract value, produces something in the $340–420M ARR range over three to five years. Running it the other direction — Workato's customer base, at a low-teens conversion rate into ServiceNow workflow products, at a higher enterprise ACV — produces a larger but far less defensible number. Anyone modeling $1.5–2B of combined cross-sell should immediately halve it. Cross-sell models in enterprise software routinely realize at 40–60% of plan, and this one assumes the acquired product survives integration with its go-to-market motion intact.

The costs are more predictable than the revenue. Integration spend of $100–200M over 18–24 months is a reasonable estimate for back-office consolidation, platform work, security review, and rebranding. Customer retention through a strategic acquisition of a neutral infrastructure vendor typically lands in the 75–85% range over 24 months — call it a 15–25% churn assumption, weighted toward customers whose primary platform is Salesforce, Microsoft, or SAP and who bought Workato specifically because it was Switzerland.

Run those together at a $3B purchase price: roughly $3.1–3.2B all-in, against an acquired revenue base that shrinks before it grows, cross-selling into a base that realizes at maybe half of plan. The deal clears its cost of capital on a five-to-seven-year view. It does not clear on a three-year view. That is the honest answer, and it is why price discipline is the whole ballgame.

Trade-offs: buy, build, partner, or wait

Four options are genuinely live, and the strongest argument for the acquisition is not that it is obviously right — it is that the alternatives each have a specific, identifiable flaw.

Build. ServiceNow could invest $300–500M over 24–36 months extending IntegrationHub into a Workato-class platform. Realistic composition: 200–300 dedicated engineers, product management, an expanded customer success function, and a distinct go-to-market motion aimed at the business-user buyer. On paper this is seven to ten times cheaper. Three problems undercut it. First, the timeline is 24–36 months to functional parity and another 12–24 months to a comparable connector library — a five-year horizon in a category consolidating now. Second, ServiceNow's culture is enterprise-sales-led and IT-buyer-oriented; building a product for a departmental business buyer is a go-to-market problem more than an engineering problem, and organizations rarely solve that internally. Third, the connector library is not a headcount problem. Twelve hundred maintained connectors represent a decade of accumulated API-drift handling that money compresses only so far.

Partner. ServiceNow can continue doing what it does today: partner with Workato, Boomi, Informatica, and others, staying neutral and letting customers choose. This preserves capital and optionality entirely. Its flaw is that it is not a strategy so much as a decision to defer — and it leaves ServiceNow's integration substrate owned by companies that can be acquired out from under it. It is the correct choice if and only if the acquisition price is wrong.

Buy an alternative. The competitive survey narrows the field to almost nothing. MuleSoft is captive inside Salesforce. Boomi is PE-owned, which means Francisco Partners and TPG are holding for a full exit in the $6–10B range and will not sell cheaply to a strategic. Informatica is too large and, following Salesforce's involvement in its 2025 take-private, strategically adjacent to a direct competitor. Tray.io is credible technically but materially smaller — an augmentation play at a fraction of the price, not a category move. Microsoft's Power Automate is bundled by a competitor and unavailable at any price. The set of right-sized, right-positioned, acquirable iPaaS assets is essentially {Workato}, which is both the strongest argument for the deal and the reason ServiceNow will have to bid against other strategics.

Wait. Workato has reportedly considered an IPO. If it goes public, ServiceNow gets a transparent price and can acquire later from public markets — with a control premium, but with real financials instead of estimates. Waiting also lets the AI-agent-disintermediation question resolve. The flaw: waiting is a bet that no competitor moves first, and it is precisely the scenario where Salesforce extends MuleSoft, or Microsoft or IBM or SAP consolidates the layer.

The integration structure deserves its own decision. Three patterns are available: full and immediate absorption, indefinite standalone operation, and a phased hybrid. Full absorption maximizes platform synergy and minimizes retention — forcing customers onto ServiceNow contracting and billing within a year is the reliable way to hit the low end of the 75–85% retention band. Indefinite standalone maximizes retention but forfeits most of the strategic rationale. The phased approach — brand and product autonomy for 24–36 months while back-office and platform work proceeds underneath, then a gradual transition — is what Salesforce effectively ran with MuleSoft, and it produced a durable business generating well over a billion dollars annually. Copy that pattern.

Common pitfalls and how to avoid them

Anchoring on the 2021 valuation. The $5.7B Series E mark will dominate the first several months of any negotiation because Workato's late-stage investors need it to. It is a number from a different rate environment and a different multiple regime. The defense is to establish an internal ceiling before diligence begins — $4B, hard — communicate it to the deal team, and mean it. Deals get overpaid when the acquirer decides it must win before it decides what winning is worth.

Believing the cross-sell model. Enterprise cross-sell decks are the most reliably wrong artifact in M&A. The pattern is always the same: multiply the customer count by an assumed attach rate by an assumed ACV, arrive at a large number, and use it to justify the price. The discipline is to underwrite the deal on the acquired revenue and the strategic gap-closing alone, treating cross-sell as upside. If the deal only works when you believe $1.5B of synergy revenue, the deal does not work.

Destroying the go-to-market motion. Workato's growth comes from bottom-up departmental landing — an ops leader with a budget, expanding laterally. ServiceNow's motion is top-down enterprise agreements with the CIO. The default post-acquisition move is to route the acquired product through the acquirer's sales organization, which kills the land-and-expand curve within four quarters because enterprise reps do not chase $25K deals. Preserve the Workato sales motion as a distinct unit with its own quota structure and compensation for at least 24 months. This is the single most common way integration-platform acquisitions destroy value.

Underestimating the neutrality problem. A meaningful share of Workato's customers are Salesforce-primary, Microsoft-primary, or SAP-primary shops that chose Workato precisely because it was not owned by a platform vendor. Post-acquisition, those customers reasonably worry about roadmap priority, pricing, and lock-in. The mitigation is explicit and public: multi-year commitments to connector parity across competing platforms, published roadmap governance, and pricing protection for existing contracts. Salesforce did not do this well with MuleSoft early on, and it cost share in Microsoft-anchored accounts.

Losing the engineers. The connector library is a maintained asset, not a static one — every one of those integrations breaks when the target vendor ships an API change, and the team that keeps them working is the actual product. Founder retention gets all the attention in deal structuring while the twenty engineers who own connector maintenance get standard retention packages and leave in month fourteen. Structure retention around the connector and platform engineering teams specifically, with 24–36 month vesting, and budget for it as part of the purchase price rather than as an afterthought.

Treating founder retention as a solved problem. Vijay Tella's operational history is genuinely strong, and a role leading a ServiceNow hyperautomation business unit is a credible landing spot. It is also a role with a natural half-life: founder energy in acquired companies typically declines somewhere in the 24–36 month window. Plan the succession into the retention period rather than discovering it afterward.

Ignoring the bundling floor. Microsoft's Power Automate ships inside M365 and prices standalone tiers aggressively. It is not as capable as Workato for complex multi-system orchestration with enterprise governance, and it does not need to be — it needs to be good enough to make every premium iPaaS pricing conversation harder. Any model that assumes Workato's pricing power holds flat through 2030 is optimistic. Discount the terminal value accordingly, and position the combined product on governance, complex orchestration, and agent-actuation rather than on connector count alone, since that is where bundled alternatives are weakest.

Skipping the RevOps-shaped use cases in diligence. Much of Workato's most defensible footprint is not IT at all — it is revenue operations work: lead routing between CRM systems, quote-to-cash flows spanning CRM, ERP, and e-signature, customer-onboarding automation driven by product telemetry. These are exactly the workflows ServiceNow's CSM and emerging revenue-workflow products want to reach, and they are the part of the Workato base least visible to a ServiceNow diligence team looking through an IT lens. Underweighting them undervalues the asset; misunderstanding them leads to a post-close org design that puts the wrong sales team on the wrong accounts.

Assuming ServiceNow's M&A track record transfers. ServiceNow's acquisition history skews toward tuck-ins — capability purchases in the tens to hundreds of millions, absorbed into the platform. A $3B deal for a company with its own brand, its own sales motion, and thousands of customers is a categorically different integration problem. The absence of a comparable prior deal is not disqualifying, but it argues for external integration leadership and a slower timeline than the deal model will want to assume.

Related questions

What price makes this deal clearly wrong?

Above roughly $4B. At $4B on ~$300M ARR the multiple exceeds 13x, above where comparable infrastructure assets have cleared since 2022, and the deal requires believing aggressive cross-sell assumptions to work. Past that line, building on IntegrationHub for $300–500M is the better allocation.

Would Workato's customers actually stay?

Most would. Expect 75–85% retention over 24 months, with churn concentrated in Salesforce-, Microsoft-, and SAP-primary accounts that bought Workato for its neutrality. Explicit connector-parity commitments and pricing protection for existing contracts materially improve the number.

Does the rise of AI agents make iPaaS less valuable?

Not in this window. Agents need to act across systems, and connector libraries encode auth, rate-limit, schema-drift, and error-recovery knowledge that language models do not replace. Agents raise the value of connectivity. The disintermediation risk is real past 2030 and warrants a valuation discount, not a veto.

Who else would bid for Workato?

Salesforce could extend its MuleSoft position, Microsoft could consolidate against Power Automate's enterprise weakness, and IBM and SAP both have integration strategies that would absorb it. That competitive set is why the asset gets bid — and why a bidding war above $4B is the scenario ServiceNow should be prepared to lose.

What should ServiceNow do if the deal doesn't happen?

Fund IntegrationHub aggressively — $300–500M over 24–36 months — prioritizing connector breadth over canvas features, and maintain multi-vendor iPaaS partnerships so no single partner acquisition strands the Now Platform. Reassess if Workato files to go public or a competitor moves.

FAQ

Has ServiceNow actually announced any intention to acquire Workato?

No. As of this writing there is no announced transaction, no confirmed negotiation, and no public financial terms. Everything here is scenario analysis built from public information about both companies, the iPaaS competitive landscape, and comparable transaction multiples. Any figure attributed to Workato's revenue, customer count, or valuation should be read as a public estimate rather than a disclosed number, since Workato is private and does not publish financials.

Why is $2.5–3.5B the recommended range rather than something higher?

It reflects where comparable infrastructure-software transactions have cleared since 2022 — generally 8–13x revenue rather than the 20x-plus multiples of the 2018–2021 cycle. On an estimated $300M ARR base growing 30–40%, that band produces a deal that clears its cost of capital on a five-to-seven-year view even after 15–25% customer churn and $100–200M of integration cost. Above $4B, the return depends on cross-sell assumptions that historically realize at roughly half of plan.

How does this compare to Salesforce buying MuleSoft?

MuleSoft is the closest comparable and the best template for integration structure — Salesforce preserved brand and product autonomy for a period, then gradually absorbed the platform, and the business now contributes well over a billion dollars annually. The differences matter, though: Salesforce paid a peak-cycle multiple that took years to justify, and MuleSoft's growth decelerated post-acquisition partly because it was routed through Salesforce's enterprise motion. ServiceNow should copy the integration sequencing and avoid the pricing and go-to-market mistakes.

What is the single biggest execution risk after close?

Destroying Workato's bottom-up sales motion. Its growth depends on departmental buyers landing $25K–$250K deployments that expand laterally through an organization. ServiceNow's enterprise reps, carrying multi-million-dollar quotas, will not work those deals, and routing the product through them collapses the land-and-expand curve within about four quarters. Keeping the acquired sales organization intact as a separate unit with its own compensation structure for at least 24 months is the mitigation.

Should ServiceNow just build the capability instead?

Building is roughly seven to ten times cheaper at $300–500M over 24–36 months and avoids all cultural-integration risk, which makes it the correct answer if Workato's price exceeds $4B. The weakness is time and connector breadth: reaching functional parity takes two to three years, and matching a library of 1,000-plus maintained connectors takes longer still, because those connectors encode a decade of accumulated API-drift handling rather than a fixed engineering scope.

Why does RevOps show up in an analysis about IT platforms?

Because a large share of Workato's most defensible workload is revenue operations, not IT: lead routing across CRM systems, quote-to-cash flows spanning CRM, ERP, and e-signature tools, and onboarding automation driven by product telemetry. Those workflows map directly onto the customer-facing and revenue-workflow products ServiceNow is expanding into, and they are the part of the asset most likely to be undervalued by a diligence team looking exclusively through an IT service management lens.

Sources

• https://www.servicenow.com/company/investor-relations.html
• https://www.workato.com/
• https://investor.salesforce.com/news/news-details/2018/Salesforce-Completes-Acquisition-of-MuleSoft/default.aspx
• https://www.gartner.com/reviews/market/integration-platform-as-a-service-worldwide
• https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001373715&type=10-K
• https://newsroom.cisco.com/c/r/newsroom/en/us/a/y2024/m03/cisco-completes-acquisition-of-splunk.html
• https://boomi.com/company/news/
• https://learn.microsoft.com/en-us/power-automate/
• https://www.thomabravo.com/news
• https://docs.servicenow.com/bundle/washingtondc-integrate-applications/page/administer/integrationhub/concept/integrationhub.html

Related on PULSE

• How Salesforce integrated MuleSoft — what worked and what didn't
• Build vs buy for enterprise integration: the real cost model
• Why iPaaS pricing is compressing and what it means for buyers
• RevOps automation stacks: where integration platforms actually sit
• How to evaluate acquisition risk in your vendor stack