What should ServiceNow do about ITSM stagnation?

ITSM as a category is mature — global IT Service Management spend grows 6-8% annually, well below ServiceNow's ~20% top-line. But ServiceNow's ITSM line keeps compounding 15-20% by selling AI uplift (Now Assist Pro Plus) on top of existing seats and by stretching the ITSM motion sideways into Enterprise Service Management (HR, CSM, Field Service, Procurement, Legal).

The four moves that keep ITSM growing through FY27 are: (1) reposition Now Assist from "agent helps write the ticket" to "agent resolves without a ticket," (2) bundle ITSM into Workflow Data Fabric so the cross-system context becomes the moat, (3) accelerate ESM expansion where the budget lives in the business unit not IT, and (4) acquire the down-market AI-native challengers (Moveworks-style, Resolve.ai, Rootly) before they compress the bottom of the funnel.

The structural risk is real: if AI agents genuinely kill the ticket as the unit of work by FY28, ServiceNow's per-seat ITSM revenue model needs a successor metric — consumption, resolution-volume, or workflow-execution pricing — and McDermott's pivot to that model is the single biggest bet on the company.

The State Of ITSM In 2026

• Market size: ~$13-14B global ITSM software spend, growing 6-8% CAGR per Gartner — single-digit category, not double.
• ServiceNow share: ~40-45% of the enterprise ITSM seat base; the only Leader in the Gartner ITSM MQ with a meaningfully widening gap on "completeness of vision."
• Bottom-end squeeze: Atlassian Jira Service Management ($17.65/agent/month Standard) and Freshservice ($19/agent/month Starter) are pricing 60-80% below ServiceNow per seat and winning mid-market net-new.
• Top-end squeeze: BMC Helix and Ivanti Neurons compete on AIOps depth; GitLab incident management and PagerDuty AIOps eat the SRE/DevOps adjacency that used to flow into ITSM.
• AI-native challengers: Moveworks (now Microsoft, post-acquisition close), Resolve.ai, Rootly, Aisera — all priced on resolution volume not seats, all attacking the L1/L2 ticket layer where ServiceNow has the most fat to defend.

The AI Agent Threat To ITSM

• Resolution-without-ticket is the existential thesis: if an AI agent in Teams/Slack answers "my VPN is broken" by checking config, restarting the tunnel, and confirming back to the user — no ticket was created, no ServiceNow seat was consumed, no SLA was tracked.
• Microsoft Copilot in Teams is the largest distribution channel for this pattern; once Copilot has read access to Intune, Entra, and Defender it can resolve 30-40% of L1 IT tickets without ever pinging ServiceNow.
• Anthropic + OpenAI agents running on Glean / Writer / custom internal stacks can read SOPs and execute IT runbooks directly against AWS, Okta, and CrowdStrike APIs.
• Named-customer pilots bypassing ticket creation: enterprise IT orgs are publicly piloting "agent-first" intake where the ticket is the fallback not the default.
• The queue dies, the work doesn't: even if ticket volume drops 40%, the underlying work (resolution, audit, change management, compliance evidence) still needs a system of record — that is ServiceNow's defense, but only if the platform captures the agent's resolution as a first-class object.
• Pricing model risk: per-agent-seat pricing assumes humans handle tickets; if agents handle 60% of resolutions, the math forces a pivot to consumption or resolution-based pricing within 18-24 months.

The 4 Moves To Defend + Grow

• Move 1 — Pivot ITSM to ESM aggressively: Every ITSM customer is a warm lead for HR Service Delivery, Customer Service Management, Field Service Management, Procurement, and Legal Service Delivery. ESM expansion typically adds 1.5-2.5x the ACV of the original ITSM deal, and the budget comes from the business unit not IT — different buyer, different P&L line, less price sensitivity.
• Move 2 — Reposition Now Assist as "agent-resolves-without-ticket": Stop demoing Now Assist as a writing aid for human agents. Demo it as the layer that auto-resolves 40% of inbound IT requests in Teams/Slack without ever surfacing a queue. The ticket becomes the audit trail, not the work artifact. This is the only positioning that doesn't get out-flanked by Copilot.
• Move 3 — Bundle ITSM into Workflow Data Fabric: The moat is not the ticket UI — it's the cross-system context (Active Directory, Workday, SAP, Salesforce, Jira, GitHub) that ServiceNow has stitched together over 15 years. Price the data fabric as the platform substrate, with ITSM as one consumer of that fabric. Standalone ITSM dies; ITSM-as-fabric-consumer keeps the renewal sticky.
• Move 4 — Acquire down-market AI-native ITSM: Resolve.ai, Rootly, and the remaining AI-native incident/ITSM startups are 18-month acquisition targets. The Moveworks → Microsoft deal already signaled the consolidation cycle. ServiceNow needs at least 1-2 tuck-ins to compress the challenger response time and protect the SMB-to-mid-market layer where Atlassian and Freshservice are gaining ground.

The ESM Expansion Math

• HR Service Delivery is the single largest ESM line — typical ESM deal lands at 0.6-1.0x the ITSM ACV, and HR-SD alone has been growing 35-40% YoY off a small base.
• Customer Service Management (CSM) is the second-largest ESM line and the most direct Salesforce Service Cloud competitor — wins are tied to existing ITSM/IT-ops accounts where the customer-facing service team already trusts ServiceNow's workflow engine.
• Field Service Management is the smallest but fastest-growing ESM line; named wins in industrial, telecom, and utilities are the public proof points.
• The IT-budget-to-business-budget movement is the quiet structural tailwind: every ESM deal moves dollars from CIO to CHRO/CCO/COO budgets, which insulates ServiceNow from the IT cost-cutting cycle that hit BMC and CA in prior downturns.
• ESM as ITSM share-grab: when ServiceNow lands HR-SD or CSM, it almost always cements the ITSM renewal at premium pricing — ESM is the moat that protects the ITSM cash cow.

What The Sales Team Needs To Hear

• For the AI-skeptical IT director: "Your Copilot pilot will resolve 30% of L1 tickets. You still need a system of record for the other 70%, plus audit/compliance evidence for the 30% Copilot resolved. Now Assist + ServiceNow is that system of record — and it captures the Copilot resolutions as first-class objects."
• For the Atlassian JSM displacement play: lead with cross-departmental ESM (HR + IT + Facilities in one workflow), not feature parity on ITSM. JSM cannot match the ESM portfolio at any price point.
• Named reference accounts: lean on Fortune 500 IT-to-ESM expansion stories where the ITSM seat count stayed flat but ACV grew 2-3x via HR-SD + CSM + Field Service attach.
• Pro Plus expansion math: every existing ITSM seat is a Now Assist Pro Plus uplift opportunity at +$20-30/seat/month. A 50K-seat customer is a $12-18M annual uplift before any new seat is sold — pure expansion revenue with near-zero CAC.
• The retention pitch: ITSM gross retention is >97%; the upsell motion is the engine, not new logo acquisition. Sales comp should weight Pro Plus + ESM attach above net-new ITSM seats.

The Honest Bear Case

• AI agents do kill ticket volume: by FY28, L1 ticket volume in agent-mature enterprises drops 40-60%, and the per-seat ITSM pricing model breaks before the consumption-based replacement is fully priced/sold.
• ServiceNow ITSM revenue plateaus by FY28: even with Now Assist uplift, the seat-erosion math catches up, and the ITSM line grows 5-8% instead of 15-20%.
• ESM doesn't scale fast enough to offset: HR-SD and CSM are growing fast off small bases, but absolute dollars take 3-4 years to replace ITSM deceleration — the gap creates a guidance reset.
• McDermott pivot too slow: the move to consumption/resolution pricing requires re-papering thousands of enterprise contracts; sales comp redesign + customer-success retraining is a 24-month project, and the market may not give that runway.
• Microsoft is the existential competitor, not Atlassian: Copilot + Intune + Entra + Defender + Power Platform is a full ITSM stack at near-zero marginal cost for any E5 customer. The 5-10% of enterprises that are Microsoft-everything are gone, and that share is growing.

Lever Scorecard

Flow

FAQ

How big is the ITSM market and how fast is it growing? Global IT Service Management software spend is about $13-14B and growing 6-8% CAGR per Gartner, a single-digit mature category well below ServiceNow's roughly 20% top-line. ServiceNow holds about 40-45% of the enterprise ITSM seat base and is the only Leader in the Gartner ITSM MQ with a widening gap on completeness of vision.

It keeps its own ITSM line compounding 15-20% by selling AI uplift on existing seats and stretching into Enterprise Service Management.

What is the "resolution-without-ticket" threat to ServiceNow? The existential thesis is that if an AI agent in Teams or Slack answers "my VPN is broken" by checking config, restarting the tunnel, and confirming back, no ticket was created, no ServiceNow seat was consumed, and no SLA was tracked.

Microsoft Copilot in Teams is the largest distribution channel for this pattern and could resolve 30-40% of L1 IT tickets once it has read access to Intune, Entra, and Defender. Even if ticket volume drops 40%, the underlying resolution and compliance work still needs a system of record.

Why does ServiceNow push ITSM customers toward ESM? Every ITSM customer is a warm lead for HR Service Delivery, Customer Service Management, Field Service Management, Procurement, and Legal Service Delivery, and ESM expansion typically adds 1.5-2.5x the ACV of the original ITSM deal.

The budget comes from the business unit rather than IT, meaning a different buyer, a different P&L line, and less price sensitivity. This IT-budget-to-business-budget movement insulates ServiceNow from the IT cost-cutting cycle that hit BMC and CA.

Which AI-native challengers is ServiceNow eyeing as acquisitions? Resolve.ai, Rootly, and the remaining AI-native incident and ITSM startups are framed as 18-month acquisition targets, since the Moveworks-to-Microsoft deal already signaled the consolidation cycle. ServiceNow needs at least 1-2 tuck-ins to compress the challenger response time and protect the SMB-to-mid-market layer.

That layer is where Atlassian Jira Service Management at $17.65/agent/month and Freshservice at $19/agent/month are pricing 60-80% below ServiceNow and winning net-new.

What is the long-term pricing-model risk for ITSM? Per-agent-seat pricing assumes humans handle tickets, so if AI agents handle 60% of resolutions, the math forces a pivot to consumption or resolution-based pricing within 18-24 months. If AI agents genuinely kill the ticket as the unit of work by FY28, ServiceNow's per-seat ITSM revenue model needs a successor metric.

McDermott's pivot to that model is described as the single biggest bet on the company.

Bottom Line

ITSM is not stagnating for ServiceNow — it is stagnating for the category. The 15-20% ITSM growth ServiceNow keeps printing is real, but it is increasingly a Now Assist uplift story plus an ESM share-grab story rather than a net-new ITSM seat story. The four-move playbook (auto-resolve repositioning, ESM expansion, Workflow Data Fabric bundling, AI-native tuck-in M&A) carries the line through FY27.

The honest bet beyond that is whether McDermott can re-paper the per-seat pricing model to consumption before AI agents make the ticket itself optional — a 24-month window where the company either becomes the system of record for AI-resolved work, or watches Microsoft Copilot eat the IT helpdesk.

*(see also: q1614, q1615, q1622)*