You May Already Own Moveworks. What's Stopping You From Turning It On?

Here's a conversation we've had more than once this year. A customer tells us they're evaluating AI assistants for employee service. They've seen a few demos and are building a business case. Then we look at their ServiceNow order form from a recent renewal, and the capability they're shopping for is already on it.

It's an easy thing to miss. Renewals are negotiated by procurement and platform owners, line items get swapped, and new SKU names don't always make it into the IT roadmap. But if your organization renewed ServiceNow in 2026, it's worth a second look. You may already be paying for Moveworks.

How Moveworks ended up in your contract

ServiceNow completed its acquisition of Moveworks in December 2025. In February 2026, it launched ServiceNow EmployeeWorks, which combines Moveworks' conversational AI and enterprise search with ServiceNow's portal and workflows.

The packaging changed at the same time. Employee Center Pro Plus went end of sale, the standalone Employee Center Pro SKU is reaching end of renewal, and customers on those products are being moved to EmployeeWorks. EmployeeWorks includes Employee Center Pro alongside the Moveworks AI Assistant, Enterprise Search, and Agent Studio.

In plain terms: if your renewal moved you off Employee Center Pro or Pro Plus, there's a good chance Moveworks came with it. And EmployeeWorks is one of the first places ServiceNow Otto, the company's unified AI experience, shows up.

Check what you own

Before anyone builds a business case or books another demo, answer three questions:

• What's on the order form? Look for ServiceNow EmployeeWorks, and note any related add-ons such as additional content connectors or a Moveworks sandbox.
• How many users are covered? EmployeeWorks is licensed by enabled user. Know whether you bought for IT, HR, or the whole workforce.
• What services came with it? An implementation service is required with EmployeeWorks, because the Moveworks assistant can't be self-implemented. Find out what was purchased and who's scheduled to deliver it.

If the answers surprise you, you're not alone. Unused entitlements are one of the most common things we find in AI readiness work: licenses sitting dormant while new tools get procured beside them.

So what's stopping you?

When a capability is paid for but not live, the reason is rarely the technology. It's usually one of these:

• Nobody owns it. The renewal was a procurement event, not a program. No product owner was named, so no plan was made.
• The knowledge isn't ready. Teams worry, often rightly, that turning on an assistant will surface outdated or duplicate articles. That's a reason to prepare, not a reason to wait indefinitely.
• Permissions haven't been validated. Security wants to know what an AI could expose before it goes near employees.
• It's unclear where to start. IT? HR? Teams or the portal? Without a first use case, everything stays on the someday list.
• There's no baseline. Without current ticket volume and resolution times, nobody can prove the value, so nobody wants to put their name on it.

Every one of these can be solved. None of them gets solved by waiting.

Turning it on the right way

"Turn it on" doesn't mean flip a switch and hope. It means a short, deliberate path:

• Agree where you stand. Review your data, knowledge, catalog, and integrations, and be honest about what's ready.
• Fix what the first use case needs. Clean up the knowledge and catalog items behind your top request categories, validate permissions, and capture a baseline.
• Go live small and measurable. Start with the AI Assistant and Enterprise Search answering common IT and HR questions from ServiceNow knowledge. It's the first customer-facing proof point, and it goes live without waiting for anything else.
• Expand from proof. Connect Teams, SharePoint, and your HRIS next, then move to Agent Studio so the assistant finishes work instead of just answering.

The cost of waiting

An unused entitlement isn't free. You're paying for it every month, and at the next renewal someone will ask what you got for it. Meanwhile, your employees are still opening tickets for questions an assistant could answer, and your service desk is still spending its time on password resets and "where's my ticket?"

The good news is that the hardest step, buying it, is already done.

Where CoreX comes in

We start with the question most organizations skip: what do you already own? Our CoreX AI Horizon approach begins by establishing what you already own, what your platform can support, and which investment comes first. From there, we score readiness, fix what the first use case needs, and get Moveworks live and measured. Then we help it keep improving long after launch.

You may already own it. Let's turn it on.