30-Second Explanation
Moveworks was an enterprise AI assistant and search company that ServiceNow agreed to acquire for $2.85 billion in March 2025 and completed on December 15, 2025. [S33]
The acquisition gave ServiceNow something its workflow platform historically lacked: a mature, widely deployed conversational front door for employees.
What Moveworks Built
Moveworks developed:
- an employee-facing AI assistant;
- enterprise search;
- natural-language request understanding;
- integrations across enterprise applications;
- a Reasoning Engine for selecting actions and information.
At the acquisition close, ServiceNow said Moveworks had 5.5 million employee users, approximately 250 mutual customers, and nearly 90% of Moveworks customers had deployed it to all employees. [S33]
Why ServiceNow Needed It
ServiceNow already had deep workflow execution.
But enterprise users often experienced ServiceNow through portals, forms and product-specific interfaces.
Moveworks offered a more natural model:
The strategic combination is therefore:
EmployeeWorks and Otto
After closing, Moveworks technology became central to ServiceNow's EmployeeWorks and Otto strategy. [S18][S19]
This does not mean Moveworks ceased to matter as an acquired product lineage.
The acquisition and later product identities are distinct:
Strategic Importance
The acquisition also protects ServiceNow from a major interface risk.
If users increasingly interact with enterprise software through AI assistants rather than application menus, the assistant layer can become the new distribution gatekeeper.
Owning Moveworks gives ServiceNow a strong native interface while Action Fabric lets ServiceNow participate when the front door belongs to another vendor.
Integration Risk
The challenge is maintaining a simple user experience while integrating:
- Now Assist heritage;
- Moveworks search/reasoning;
- ServiceNow AI agents;
- EmployeeWorks;
- Otto;
- external assistants.
If customers cannot understand which layer does what, product complexity can offset the strategic value.
Deal Timeline
- March 2025:
ServiceNow announced an agreement to acquire Moveworks for an announced value of $2.85 billion. [S33]
- December 15, 2025:
The transaction completed, establishing ownership rather than merely an intended integration. [S33]
- February 2026:
EmployeeWorks connected the acquired conversational capabilities with the broader platform direction. [S34]
- May 2026:
Otto was introduced as a unified AI experience, a later product development rather than a new name for the original legal company. [S42]
What Capability Actually Transferred
The acquired capability concerns the start of the employee journey: interpreting a request, searching enterprise information and helping identify the relevant action. The receiving platform supplies work records, permissions and execution paths. The value of the combination depends on those components reaching one another in a real customer environment.
A useful analogy is the distinction between understanding where a request should go and having authority to complete it. The first can reduce navigation effort; the second requires a supported process and access to the appropriate system. A successful acquisition integration must preserve both jobs rather than assume a strong conversational interface replaces the operating backend.
Integration Tests After Completion
Context must survive the handoff
The user should not have to repeat information merely because a request moves from search to fulfillment. The system needs to retain the relevant identity, question and authorized context while avoiding unnecessary transfer of confidential information.
Completion must be observable
An assistant saying that it has acted is weaker evidence than the authoritative service record showing the permitted result. A failed action should return a clear exception rather than disappear behind a fluent summary.
Existing customers need continuity
An acquired product's users still need dependable search and assistance. Aligning a portfolio cannot be judged only by whether its branding looks consistent; the acquired capability has to remain useful while the integration changes its operating relationships.
Why the Acquisition Is Not a Finished Platform Outcome
The announced transaction value measures the commercial agreement, not a later return on investment. User counts at completion describe the installed base at that date, not guaranteed adoption of every new ServiceNow offering. These distinctions matter because acquisition stories often compress ownership, technical integration and customer value into one event.
The more durable mechanism is a repeated journey in which employees can reach and complete useful work with less coordination effort. Its economics depend on adopted use, operating cost and retention, not simply the number of conversations started. [S33][S34]
Common Questions
Are Moveworks, EmployeeWorks and Otto interchangeable names?
Did the acquisition eliminate external systems?
No. A request can still depend on another application's information or execution rights. The combined system has to respect those boundaries.
Why This Business Role Matters
Moveworks was not mainly a technology tuck-in.
It was a distribution and user-experience acquisition.
ServiceNow bought the AI front door that could translate employee intent into the workflows its platform already knew how to execute.