Moveworks Pricing: Moveworks ServiceNow Cost Per User and License Tiers

Moveworks costs whatever your negotiated contract says, but there is one published number to anchor against. The Moveworks listing on AWS Marketplace prices the product at $150.00 per user per year for the 1,000 to 2,500 user band on a 12 month contract. That is $12.50 per user per month. It is the only list price Moveworks publishes anywhere, and we read it off the listing itself on September 3, 2026 rather than repeating it from another article.

Run that rate across its own band and you get the bracket Moveworks is willing to put in public: 1,000 users at $150 is $150,000 a year, and 2,500 users at $150 is $375,000 a year. The listing says explicitly that pricing scales with your user count inside the band, and that a headcount above 2,500 needs a different arrangement.

Set that against what buyers report paying. Vendr, which aggregates anonymized transaction data from its customers, publishes a median Moveworks contract of $130,000 a year across 31 purchases, with a low of $89,500 and a high of $271,333, last updated February 2026. Two things fall out of putting those numbers side by side, and neither one is on any other page about Moveworks pricing.

This is the finding worth taking into a negotiation. The AWS list rate at the top of its own band, 2,500 users at $150, comes to $375,000 a year. The highest Moveworks contract in Vendr's recorded set is $271,333. The published list price at the top of the band is roughly 38% higher than the most anyone in that transaction set is recorded as having paid.

It holds at the bottom of the band too. The list rate at 1,000 users is $150,000 a year, which is about 15% above the $130,000 median contract. Divide the median contract by the list rate and you get roughly 867 users, meaning the median buyer is paying less in total than the smallest deal the public band describes.

So treat $150 per user per year as the number Moveworks is comfortable showing a stranger, not as the number a prepared buyer pays. Vendr's own guidance on this catalog is that multi year commitments move pricing 15% to 30% lower, a competitive evaluation moves it 10% to 25%, and the two together land in the 25% to 40% range. Applied to the $150 list rate, a 25% to 40% reduction puts you between $90.00 and $112.50 per user per year. That is a defensible target to walk in with, and it is derived from the vendor's own published rate rather than invented.

One caution on the per employee figures that circulate. Vendr reports $20 to $40 per employee per year for organizations of 1,000 to 5,000 staff, dropping to $15 to $30 above 10,000. Those are not in conflict with the $150 AWS rate, they are measuring a different denominator: the AWS number is per licensed user in a small band, and the per employee number is a blended rate across a much larger enterprise after volume discounting. The practical read is that the effective per head price falls by roughly five times as you scale from the published 1,000 user band to a 4,000 plus employee rollout. If a vendor quotes you close to list at enterprise headcount, that is the discrepancy to raise.

Moveworks charges an annual committed license priced on total employee headcount, plus a separately quoted implementation. It is not consumption pricing, it is not per ticket, and it is not per resolution. You are buying access for a population, and the population is everyone who might ever open the assistant.

That unit matters more than the rate. A per ticket or per resolution vendor bills you for work performed, so a quiet month costs less. Moveworks bills the same amount whether the assistant handles 40,000 requests or 400. The upside is a predictable line item that finance can forecast exactly. The downside is that adoption risk sits entirely with you: if the assistant only gets used by the IT organization, you still paid to license sales, finance and the warehouse.

The practical test before signing is to divide the annual fee by the number of support interactions you honestly expect the assistant to deflect in year one, not the number your vendor's business case assumes. At the $130,000 median contract, deflecting 40,000 requests a year works out to about $3.25 per deflected request. Deflecting 8,000 works out to $16.25. Both are plausible year one outcomes depending on how much knowledge you have cleaned up first, and the gap between them is the entire business case.

ServiceNow announced its agreement to acquire Moveworks on March 10, 2025 at $2.85 billion, and completed the acquisition on December 15, 2025. The close is confirmed on Moveworks' own press release, which is the source to cite rather than the March announcement that most articles still link to.

For buyers, the commercially important part is that Moveworks continues to be sold as a standalone product and not only as a ServiceNow ITSM add on. You do not need a ServiceNow platform license to buy it. That is unusual: Microsoft 365 Copilot requires a qualifying base license, and Salesforce Agentforce assumes you are already a Salesforce customer, so the two largest agent vendors both gate the purchase behind an existing seat. Moveworks does not, at least today.

What has not been published is any change to how it is priced. The close announcement covers product integration, specifically bringing the Moveworks AI Assistant, enterprise search and Reasoning Engine into ServiceNow's workflow automation, and defers commercial positioning to later announcements. The AWS Marketplace listing still shows Moveworks as the vendor and still carries the same $150 per user per year band as of September 3, 2026.

The risk to price into a multi year deal is straightforward: acquisitions of this size usually end with the acquired product folded into the parent's licensing metric, and ServiceNow's metric is very different from Moveworks' metric. If that happens, a per employee contract becomes a per seat or per assist contract at renewal. Ask for renewal terms in writing that survive a repackaging, and ask specifically what happens if the product is renamed.

Now that both products sit under ServiceNow, this is the comparison buyers actually run, and the two are priced on opposite units. Moveworks charges per employee per year. ServiceNow Now Assist charges an AI native seat premium per fulfiller seat per month, on top of your existing platform license, with consumption pools on top of that.

Seat premium estimates for Now Assist commonly land between roughly $70 a user at the Foundation tier and $160 to $200 and up at Prime, per month. Work an example at 200 ITSM agents on an Advanced tier estimate near $120 a seat per month: that is about $24,000 a month, or $288,000 a year in seats alone, before any consumption.

Now price the same organization on Moveworks. At the middle of the reported per employee range, $30 a year, $288,000 licenses about 9,600 employees. So a 200 seat Now Assist deployment costs roughly what it would cost to put Moveworks in front of an entire 9,600 person company.

That is not an argument that one is better. They serve different populations: Now Assist makes the people who work tickets faster, and Moveworks tries to stop the ticket from being filed. It is an argument that the unit of pricing, not the rate, is what decides which one is expensive for you. If you have a small fulfiller team and a large employee base, Now Assist is cheap and Moveworks is expensive. Invert the ratio and the answer inverts with it. Both figures above are estimates rather than published rates, and the assumption behind each is stated so you can substitute your own.

Moveworks lists Professional Services on AWS Marketplace as a separate product, and we checked it: it carries no published price at all, only custom pricing through a private offer. The scope described on the listing is a configuration proposal based on an assessment of your environment, configuration and launch of the platform against your key systems, and end user onboarding.

Third party estimates put that engagement between $50,000 and $200,000 and up. Against the $130,000 median license, that is roughly 38% to 154% of your first year license fee, which is the reason first year budgets for this category are so often wrong. Teams model the license, sign, and then discover that year one costs somewhere between one and a half and two and a half times the number they took to finance.

The work that drives the number is rarely the integration itself. Connecting Okta, ServiceNow, Workday and a knowledge base is well trodden. What takes time is that the assistant is only as good as the content behind it, so someone has to find, deduplicate and rewrite the knowledge articles it will answer from. Budget internal time for that explicitly, because it is real cost that appears on no invoice, and it is the single best predictor of whether the deflection rate in your business case shows up.

Five levers, in the order they are worth pulling.

Anchor on the published rate. Open with the AWS Marketplace figure. Most sellers do not expect a buyer to know a public list price exists, and starting from $150 per user per year with a documented 25% to 40% discount target is a very different conversation from asking what it costs.

Buy through AWS Marketplace if you have a committed spend agreement. This is the structural lever rather than a discount. Private offers on Marketplace draw down against an AWS commitment you have already promised to spend, so the effective cost to the business is lower even when the sticker price is identical.

Negotiate the headcount definition, not just the rate. Because the license is per employee, the definition of employee is worth as much as the price. Exclude contractors, seasonal staff, frontline workers without a corporate identity, and anyone in a subsidiary that will not be in scope for two years. Get a written true up mechanism with a floor, so growth does not reprice the whole base.

Put implementation in the same negotiation. Services are quoted separately and are therefore usually discounted separately, which means they are usually discounted less. Bundle them, and tie a portion of the fee to a milestone you can verify, such as a measured deflection rate at 90 days.

Ask what happens at renewal if the product is repackaged. After a $2.85 billion acquisition this is a live question, not a theoretical one. Get language that holds your pricing metric for the term even if the product is renamed or merged into a ServiceNow SKU.

Moveworks is built for a specific profile: a large employee base, a heavy volume of repetitive internal requests across IT and HR, mature systems of record to act against, and a budget that treats a six figure annual platform fee as normal. If that describes you, the per employee model is defensible and the deflection case is real.

If it does not, the economics get hard to justify quickly. Below roughly 1,000 employees you are outside the smallest band the vendor publishes, you carry the same implementation burden as a company ten times your size, and you are paying a platform fee to solve a ticket volume that a much smaller tool handles. Buyers in that position are usually better served by picking up narrow, ready made agents for the specific jobs that actually generate the volume, deploying them against the systems they already run, and paying per agent instead of per head. That is what our AI agent store is for, and it is why the entry point there is $29 a month rather than $130,000 a year.

The middle case, a few thousand employees with real request volume, is where the negotiation levers above matter most. You are large enough that Moveworks wants the logo and small enough that the list price would be indefensible. That is the position where knowing the published $150 rate and the $130,000 median is worth the most.