IT helpdesk automation costs anywhere from $500 a month for a narrow chatbot add-on to seven figures a year for an enterprise agent platform. Most mid-market deployments land between $80,000 and $400,000 in year one, depending on whether you buy a platform, build in-house, or run a hybrid model. The sticker price matters less than cost per ticket resolved, which is the number that actually determines when the project pays for itself.
Every vendor conversation I sit in on starts the same way: a pricing page that says "contact sales," followed by a quote that has almost nothing to do with what the company down the street paid.
That gap makes budgeting for automation harder than it needs to be.
This post lays out real contract ranges, real build costs, and a formula for figuring out which path pays back fastest for your ticket volume. The numbers come from procurement data and published benchmarks, not sales decks.
Moveworks does not publish list pricing. It sells on a quote-based model tied to total company headcount, not active users or ticket volume. According to procurement marketplace Vendr, companies with 1,000 to 5,000 employees typically see annual contract values between $200,000 and $600,000, which works out to roughly $20 to $40 per employee per year. Vendr also reports a median annual contract value near $130,000 across all deal sizes it has tracked, with larger enterprises frequently landing in six or seven figures once professional services are added.
ServiceNow moved to a new tier structure in April 2026: Foundation, Advanced, and Prime, replacing its old five-tier lineup. Only Prime includes the fully autonomous AI Agents for ITSM and the L1 Service Desk AI Specialist. Estimated per-user costs run $70 to $100 a month for Foundation and $160 to $200 or more for Prime, before any AI consumption charges. Those consumption charges bill separately once a bundled usage pool runs out, and enterprise agent actions on comparable platforms typically run $2 to $5 per action.
Neither vendor publishes a rate card, so treat every figure above as a market range, not a quote you can hold anyone to. Get quotes from at least two vendors against the same ticket volume and headcount before you build a budget around a single number.
Building means paying engineers instead of a license fee, and the range is wide because scope varies so much. A single-intent automation, one ticket type, one integration, typically runs $5,000 to $30,000 to build. A production agentic system that spans ServiceNow and Microsoft 365 with real judgment calls costs $80,000 to $300,000 or more, and integration work drives most of that number, not the language model itself. Model API costs typically make up only 8 to 15% of total build spend on projects like this.
The build number people forget is what comes after launch. Budget $3,200 to $13,000 a month in ongoing costs for hosting, monitoring, prompt tuning, and security patching on a production agent serving real users. Annual maintenance runs 15 to 30% of the initial build cost every year after that, which means a $150,000 build can carry a $25,000 to $45,000 annual maintenance bill indefinitely.
We covered the decision framework behind this tradeoff in more depth in our <a href="/blog/it-support-automation-build-vs-buy">build versus buy guide for IT automation</a>. The short version: building rewards teams with platform engineers already on staff and a narrow, well-understood ticket type. It punishes teams who underestimate maintenance.
Cost per ticket is what turns a platform price tag into a payback date. Industry benchmarks put the average fully loaded cost per ticket at $15.56, with a range from $2.93 to $49.69 depending on tier and industry. HDI puts Tier 1 support around $20 a ticket. Offshore providers run $6 to $13 for L1 and $22 to $28 for L2. B2B support with more technical complexity runs $30 to $60 a ticket.
A 2,000-employee company generating 50,000 tickets a year at a $22 median cost is spending $1.1 million annually on ticket handling before automation touches it. Deflecting even 30% of that volume saves roughly $330,000 a year. That is the number a Moveworks or ServiceNow Prime contract has to beat, not the sticker price on the invoice.
No vendor puts that number on a pricing page.
| Approach | Year 1 Cost | Ongoing Annual | Typical Time to Deploy | Best Fit |
|---|---|---|---|---|
| Buy (Moveworks, ServiceNow Prime) | $130,000 to $600,000+ | Renews at similar cost, headcount-based | 2 to 4 months | Teams that want a vendor-owned outcome and can accept flat per-employee pricing |
| Build in-house | $80,000 to $300,000+ | $25,000 to $90,000+ (15-30% maintenance plus hosting) | 4 to 9 months | Teams with existing platform engineers and a narrow, well-defined ticket type |
| Hybrid (managed build on your stack) | $30,000 to $100,000 | $15,000 to $60,000 (support and tuning) | 6 to 10 weeks | Teams that want to own the automation logic without carrying full-time engineering headcount |
The formula is simple even when the inputs are not: (ticket volume x deflection rate x cost per ticket) minus annual platform or maintenance cost equals annual savings. Divide the year-one cost by annual savings and you get payback in years.
Take a 1,500-employee company with 35,000 tickets a year at $20 each. A platform quoted at $250,000 a year that deflects 35% saves $245,000 annually, a payback of just over a year. The same volume automated through a $60,000 hybrid build deflecting 25% saves $175,000 a year against a $25,000 ongoing cost, paying back in about four months. Neither number is universal. Run your own ticket volume through the formula before you compare vendor quotes at all.
Ask every vendor for their deflection rate on comparable ticket volume in writing, not a slide with an industry average. Deflection is the variable that makes or breaks the payback math, and it is the one number sales teams are most likely to round up.
Hybrid is not automatically cheaper per ticket deflected. It is cheaper to start, because you are paying for a scoped build against your existing ServiceNow and Microsoft 365 tenant instead of a headcount-based license or a from-scratch engineering team. That lower entry cost is why it fits most mid-market IT teams: you get ownership of the automation logic, so it does not disappear if you change vendors, without carrying the full maintenance burden of an in-house build.
It is also the fastest of the three to a working pilot. Six to ten weeks is realistic when the integrations already exist in ServiceNow and Entra ID. A full Moveworks or ServiceNow Prime rollout with professional services commonly takes two to four months just to configure, before tuning starts. If you are not sure which ticket types are even worth automating yet, our <a href="/readiness">AI readiness assessment</a> is a faster starting point than pricing out a platform.
Expect $60,000 to $200,000 in year one depending on path. A headcount-based platform like Moveworks scales down proportionally but still carries a floor around $75,000 to $100,000 annually at that size. A scoped hybrid build against an existing ServiceNow instance typically runs $30,000 to $70,000 to launch.
It depends on ticket volume and how much of your workforce actually contacts IT. Because Moveworks prices on total headcount rather than active users, a company where only a third of employees generate tickets pays the same rate as one where everyone does, which makes the per-ticket economics worse for smaller, less ticket-heavy organizations.
Building is usually cheaper in year one for a narrow, well-defined ticket type if you already have engineers who know ServiceNow Flow Designer and the Graph API. It gets more expensive than buying once you count 15 to 30% annual maintenance across multiple ticket types, which is where in-house projects tend to stall.
Most well-scoped projects break even between four months and just over a year, depending on deflection rate and cost per ticket. A hybrid build against existing systems tends to pay back faster because the upfront cost is lower, even at a lower deflection rate than an enterprise platform.
No. Fully autonomous AI Agents for ITSM and the L1 Service Desk AI Specialist require the Prime tier, ServiceNow’s highest license level introduced in April 2026. Foundation and Advanced include assist features but not autonomous ticket resolution, and AI consumption above the bundled pool bills separately.
Support Team runs on the ServiceNow and Microsoft 365 stack you already have, with a fixed scope and a payback timeline you can hand to your CFO before you sign anything.
See How It WorksFree 2-minute assessment. Get an industry-specific score and action plan — no call required.