What ServiceNow’s Moveworks Acquisition Means for the Future of AI in Service Management

When I left the ServiceNow ecosystem in 2015 — after building the reseller business that brought ServiceNow to the APAC market — I could see two things clearly. First: ServiceNow was going to become big, complex, and expensive, and eventually it would price out the mid-market entirely. Second: AI was coming out of the AI winter, and any platform that didn't build it in from the start would have to buy it later at a significant premium. The Moveworks acquisition is ServiceNow doing exactly that. They paid $2.85 billion for what should have been built into the platform from the beginning.

‍

This is not a neutral industry development. It is a strategic signal — and if you're an IT leader at a company between 500 and 15,000 employees, you need to understand what it actually means for your team, your budget, and your options going forward.

‍

Here's the direct answer: Moveworks was the independent AI layer that let mid-market IT teams get enterprise-grade conversational AI without paying ServiceNow enterprise prices. That independent layer is now gone. ServiceNow owns it. And K26 — ServiceNow's May 2026 Knowledge conference — showed exactly what they plan to do with it.

‍

What ServiceNow Actually Bought for $2.85 Billion

On the surface, ServiceNow bought a conversational AI platform with a strong natural language understanding engine, enterprise search capability across 100+ systems, and an annual recurring revenue that exceeded $100 million by late 2024, according to the Everest Group's acquisition analysis.

‍

But that's not really what they bought.

‍

What ServiceNow actually acquired was three things: a front-end AI experience they couldn't build internally fast enough, a customer base of enterprises who were using Moveworks as an alternative to ServiceNow's own AI layer, and the elimination of an independent competitive threat.

‍

Before this deal, Moveworks worked across platforms. It plugged into ServiceNow, Jira, Salesforce, Zendesk, BMC, and dozens of other systems. A mid-market IT team running Jira or Freshservice as their primary ITSM could layer Moveworks on top and get a sophisticated conversational AI experience without touching ServiceNow. That was the value proposition — enterprise-quality AI at a price point that didn't require full ServiceNow commitment.

‍

That cross-platform independence is the thing that's now gone. ServiceNow didn't acquire Moveworks to make it better for Jira customers. They acquired it to make ServiceNow's platform more compelling. The distinction matters more than most analysts are acknowledging.

‍

The 20x revenue multiple ServiceNow paid — over $2.85 billion for a company at $100 million ARR — tells you how serious they were about removing this as an independent option in the market.

‍

[IMAGE: Diagram showing Moveworks' pre-acquisition multi-platform integrations vs. post-acquisition ServiceNow-first focus. Simple, clean infographic style.]

‍

K26 Shows the Real Strategy: The Walled Garden

In May 2026, ServiceNow held its annual Knowledge conference and announced a cluster of products that, taken together, reveal exactly what the Moveworks acquisition was building toward.

‍

Action Fabric opens ServiceNow's "system of action" to external AI agents via a generally available MCP Server. On the surface, this looks like openness — AI agents built on Claude, Microsoft Copilot, or a company's own stack can now trigger governed ServiceNow workflows. But read it more carefully. The governance layer, the audit trail, the permission scoping, the identity verification — all of it runs through ServiceNow's AI Control Tower. ServiceNow is not becoming a commodity workflow layer. They're becoming the governance control plane that every AI agent must pass through. That's a more powerful position, and a more locked-in one.

‍

AI Control Tower is ServiceNow's centralized governance product. It discovers, monitors, governs, and measures AI activity across enterprise systems. For organizations running complex multi-vendor environments, the pitch is compelling: one place to see everything. But one place to see everything means one vendor to depend on for everything.

‍

Otto is the integration point where Moveworks lands. ServiceNow's May 2026 announcement pulled Moveworks' technology — the EmployeeWorks product — together with Now Assist and ServiceNow's AI Experience layer into Otto, a unified AI experience for the enterprise. The conversational AI, enterprise search, voice agents, and data explorer that Moveworks customers paid for independently are now components of a ServiceNow product that requires a ServiceNow contract.

‍

My take, straight: this is platform consolidation disguised as platform openness. ServiceNow is building a walled garden and they're doing it by wrapping enterprise governance around the entrance. The MCP Server is genuinely available to external agents. But all roads run through ServiceNow's control layer, ServiceNow's pricing model, and ServiceNow's contract terms. That's not an open ecosystem. That's a toll bridge.

‍

For mid-market IT leaders, the K26 announcement has a concrete implication: the AI capabilities that were accessible through Moveworks as a standalone purchase are becoming features within a ServiceNow platform that starts at enterprise price points.

‍

What This Means If You're a Moveworks Customer

If you're currently running Moveworks, here's what the transition path looks like in plain terms.

‍

Your existing contracts are being honored. Moveworks' integrations with Jira, Slack, Teams, and Okta continue to function. ServiceNow has not announced a forced cutover. But the direction of travel is clear. As Atomicwork's analysis of the acquisition noted, "new feature investment on the standalone Moveworks platform is likely to slow as talent consolidates around the combined product." The engineering resources are moving to build Otto, not to improve the standalone Moveworks experience.

‍

For mid-market teams running Moveworks on top of non-ServiceNow platforms, the specific risk is this: you are now a second-class customer in your own contract. You're paying for a product whose roadmap is being built for ServiceNow customers. The integrations you rely on — Jira, Freshservice, Zendesk — will receive progressively less investment as Moveworks talent moves to work on Otto and the ServiceNow platform.

‍

If you're on ServiceNow and using Moveworks, your short-term situation is actually positive. Consolidation means a single vendor, fewer integration points, and the promise of a more coherent AI experience. But you will pay for it. Atomicwork's analysis specifically flags what they call the "ServiceNow tax" — the pattern where acquired products "become expensive add-ons to ServiceNow ITSM/ESM licenses, bundled at higher overall costs and reducing customer flexibility."

‍

For non-ServiceNow Moveworks customers, the practical question is: when does your next renewal come up? That is your evaluation window. After that renewal, you are implicitly betting that ServiceNow will continue investing in the standalone product that competes with their core platform. That's a bet I wouldn't make.

‍

For more detail on what a migration from ServiceNow looks like, see our comprehensive migration guide.

‍

The Mid-Market Squeeze Nobody's Talking About

This is the part that most of the industry commentary on the Moveworks acquisition has missed entirely.

‍

Enterprise IT teams — the ones running ServiceNow at 20,000, 50,000 employees — can absorb what comes next. ServiceNow bundling Moveworks into their platform pricing is a price increase for those teams, but their IT budgets and their organizational complexity justify the investment. ServiceNow is built for that scale.

‍

Mid-market IT teams have a fundamentally different situation. The 500-to-15,000-employee company doesn't have a team of ServiceNow-certified developers. They don't have an eight-figure IT infrastructure budget. What they've been doing — often very successfully — is running lightweight ITSM platforms and layering independent AI tools like Moveworks on top to punch above their weight class on the AI experience. The Moveworks acquisition eliminates the workaround.

‍

Before the acquisition: mid-market team on Freshservice + Moveworks = enterprise-quality AI at mid-market cost. After the acquisition: that combination either degrades as Moveworks investment moves to ServiceNow, or the team faces the choice between going without AI capability or paying ServiceNow prices for it.

‍

The real cost data makes this concrete. Our analysis of actual customer deployments found that companies switching from ServiceNow to Servicely consistently see total ITSM cost drop from around $562,000 per year to around $120,000. You can see the full breakdown in The Real Cost of Your ITSM Platform. That $442,000 gap exists because of ServiceNow's professional services dependency — and here's where Jack Ashton, our Sales Director covering EMEA, surfaces a number that explains why that gap is so large.

‍

The professional services ecosystem around platforms like ServiceNow is approximately five times the size of the software licensing revenue in the space. For every dollar a company pays in ServiceNow licenses, they spend roughly five dollars on implementation consultants, certified developers, system integrators, and ongoing customization work. Deloitte, KPMG, Accenture, and hundreds of boutique ServiceNow practices exist to service this gap between what the platform does out of the box and what enterprise customers actually need it to do.

‍

Servicely's AI-native architecture means 90-95% of that configuration work happens through natural language — a business user describes what they need, the platform builds it. No certified developer required. That's not a feature claim. It's an architectural consequence of building AI into the platform from the start, rather than acquiring it a decade after the platform was designed.

‍

Mid-market IT leaders shouldn't be benchmarking themselves against the Fortune 500. The question isn't whether ServiceNow is good — it is, for the right scale. The question is whether it was built for you.

‍

Why "Bolting On" AI Is the Wrong Architecture — And ServiceNow Just Proved It

I've been saying since I founded Servicely that any platform that wasn't built AI-native from the ground up would eventually have to buy its way in. ServiceNow just proved that thesis with a $2.85 billion data point.

‍

The Now Platform was designed in the early 2000s as a workflow and ticketing engine. It is an extraordinarily capable system for what it was built to do — automate IT service workflows at enterprise scale. But its architecture was designed before transformer models existed, before large language models existed, before the current generation of AI reasoning capabilities existed. When AI became a core enterprise requirement, ServiceNow's options were: bolt it on as a layer (Now Assist), buy it (Moveworks), or rebuild from scratch. They chose the first two options because the third wasn't viable for a public company with a trillion-dollar-plus valuation to protect.

‍

The result is what you see at K26: Otto, which pulls together three separate AI products (Now Assist, EmployeeWorks from Moveworks, and the AI Experience layer) into a single experience. Under the covers, those are still separate systems being integrated. The integration will work — ServiceNow has the engineering talent to make it coherent — but it will cost money and it will take time, and the customers paying for it during the integration phase are the beta testers.

‍

Compare this to what an AI-native architecture actually looks like. When Servicely was built, the question wasn't "how do we add AI to our ticketing system?" The question was "how do we build a service management platform where AI runs across every workflow from the beginning?" The difference isn't cosmetic. It's architectural. AI-native means the reasoning engine is not a separate product sitting on top of the platform — it's the mechanism by which the platform operates.

‍

I've written more about this architectural distinction in the context of agentic AI — see From Chatbots to Agentic AI. And if you want to understand the model selection decisions underneath AI-native ITSM — which LLMs handle which types of service desk queries — the LLM guide gets into the details.

‍

When I look at K26, I don't see a threat. I see validation. ServiceNow is telling the market that AI-native service management is the future. They just can't deliver it from their existing architecture. So they're paying billions to approximate it.

‍

What Smart IT Leaders Should Do Right Now

The Moveworks acquisition creates a decision window. Here's how to use it.

‍

If you're currently on ServiceNow:

‍

Audit your Moveworks integration before your next renewal. Understand which capabilities you're relying on and whether those features are moving to the ServiceNow-native Otto product or staying in a standalone Moveworks SKU. Get a quote for the full bundled ServiceNow + Otto licensing. Then model your three-year total cost of ownership — licenses, implementation, professional services, and the ongoing customization overhead.

‍

The 5x professional services multiplier is real. When you're doing your TCO analysis, the license fee is the smallest number on the spreadsheet.

‍

If you're evaluating ITSM platforms right now:

‍

Ask every vendor one question: "Is your AI native or acquired?" The answer tells you everything about their roadmap, their architecture, and how much you'll pay to get full AI capability five years from now. If the answer involves acquisitions, partnerships, or third-party integrations, the underlying architecture wasn't built for this.

‍

If you're mid-market (500-15,000 employees):

‍

Stop using enterprise benchmarks to evaluate your ITSM options. The Fortune 500 use case for ServiceNow is legitimate — global IT operations at massive scale require what ServiceNow delivers. But you don't need what they need, and more importantly, you don't have what they have: the headcount to staff a ServiceNow team, the budget to fund a 12-18 month implementation, or the ongoing consultants to keep it current.

‍

You need a platform that was sized for you. AI-native, right-sized for mid-enterprise, and deployable in 12 weeks rather than 12 months.

‍

For everyone:

‍

Don't wait for your renewal to discover the price increase. The post-acquisition pricing consolidation at ServiceNow is not a future risk — it's a present reality. The time to evaluate alternatives is before you're in a renewal negotiation, not during it.

‍

‍

Want to see what AI-native ITSM looks like without the ServiceNow price tag?

‍

Book a 30-minute personalized demo with Servicely → (No sales script. You tell us your environment. We show you how it handles it.)

‍