AI-native ITSM platforms have captured significant market share in three years. We look at which legacy vendors are mounting a credible response, and which are losing ground fast.
Key Takeaways
The ITSM market has not experienced a structural disruption of this magnitude since the shift to cloud-based service management platforms in the early 2010s. Over the past two years, AI-native ITSM platforms have grown adoption by 88%, a rate that reflects genuine switching activity rather than greenfield deployments alone. Churn from legacy platforms is up 23% year-over-year, and the switching cohort is disproportionately concentrated in the mid-enterprise segment, organisations with 2,000 to 15,000 employees that have the scale to feel the operational cost of AI capability gaps but lack the enterprise inertia that keeps the largest deployments locked in complex multi-year contractual relationships. The market dynamics have shifted decisively, and the competitive response from legacy vendors is now a primary strategic variable for every IT leader facing a platform renewal decision in the next 18 months.
The core driver is operational performance, not feature preference. When AI-native platforms are resolving P1 incidents 44% faster than legacy counterparts, the performance differential has moved beyond the threshold where it can be rationalised as a tooling preference. Forty-four percent faster P1 resolution translates directly into reduced business impact, lower SLA penalty exposure, and measurable improvements in customer and employee experience metrics that appear in board-level reporting. The mechanism is well-understood: AI-native platforms were architected from the outset to ingest telemetry at scale, perform automated correlation across infrastructure domains, surface contextually relevant knowledge base content to engineers without requiring manual search, and generate AI-drafted resolution guides that compress the time from incident identification to remediation. Legacy platforms were designed for a world of human-driven triage, and retrofitting AI capability onto that architectural foundation is a fundamentally different challenge than building AI-native from scratch.
The 88% adoption growth figure for AI-native platforms requires some contextualisation to understand its competitive significance. This is not growth from a negligible baseline. Platforms including Freshservice, Atlassian Jira Service Management, and the newer pure-play AIOps-to-ITSM entrants had already established meaningful customer bases entering 2024. The growth reflects a combination of net-new customer acquisitions in the mid-enterprise segment, displacement of legacy platforms at renewal, and expansion within existing accounts as organisations consolidate tooling previously spread across multiple ITSM and AIOps platforms. Competitive win rate data from the AI-native cohort shows displacement of ServiceNow at the mid-enterprise tier as the single largest source of new logo growth, followed by BMC Helix and Ivanti.
The P1 resolution speed differential is the number most frequently cited in competitive sales cycles, and it withstands scrutiny. The 44% improvement is a composite across deployment configurations and incident types, but individual outcome studies at specific organisations show outcomes in the 38% to 61% range depending on infrastructure complexity and the maturity of the organisation's knowledge base investment. The technical drivers break down across three capabilities. Automated correlation reduces the time from alert ingestion to probable cause identification by eliminating the manual war room correlation process. Contextual knowledge surfacing puts relevant resolution history and documentation in front of the engineer within seconds of incident creation rather than requiring manual knowledge base navigation. AI-drafted resolution guides, the newest capability in the stack, compress the time from probable cause identification to remediation action by generating structured, step-by-step guidance based on the incident context and historical resolution patterns.
The mid-enterprise switching dynamic deserves particular attention because it represents the most strategically significant cohort for legacy vendors to retain. Mid-enterprise customers have lower switching costs than large enterprise customers, where ITSM platforms are deeply integrated with broader IT service management ecosystems and where migration complexity scales with the number of integrated systems and the volume of historical data. At the mid-enterprise tier, a motivated organisation can complete an ITSM platform migration in six to nine months with a dedicated project team. The $1.8M average total effort estimate for ITSM migration includes internal labour, consulting fees, data migration, integration rebuild, and training costs. At that cost, a platform generating $400,000 to $600,000 per year in operational value improvement from faster incident resolution and reduced analyst burden crosses the break-even threshold within three to four years, a justifiable investment by most enterprise capital allocation standards.
ServiceNow's response has been the most substantive among legacy vendors, and it reflects the advantages that come with having the financial resources and engineering capacity to make material platform investments quickly. Now Assist, ServiceNow's generative AI layer, is now integrated across the incident, problem, change, and service request management workflows on the platform. The Now Assist capabilities for incident management include automated incident summarisation, AI-generated resolution notes, and contextual knowledge recommendations, all addressing the core capability gaps that AI-native competitors have been exploiting in competitive sales cycles. ServiceNow's additional advantage is platform breadth: Now Assist integrates with the broader ServiceNow ecosystem including IT operations management, security operations, and HR service delivery, providing a consolidation opportunity that pure-play ITSM platforms cannot currently match. The honest assessment is that ServiceNow's AI investments are substantive, not marketing, and they are materially narrowing the gap with AI-native competitors at the platform level.
BMC Helix's AI investments are directionally credible but are executing on a slower timeline than ServiceNow. Helix's AIOps integration has improved significantly over the past 18 months, and the platform's predictive service management capabilities, covering proactive incident identification and change risk assessment, represent genuine capability additions. BMC's challenge is that its historical strength in large enterprise environments, particularly in mainframe and hybrid infrastructure management, means its AI development priorities reflect that customer base rather than the mid-enterprise segment where switching pressure is most intense. For IT leaders in large enterprise environments with complex hybrid infrastructure, BMC Helix remains a credible platform with a defensible AI roadmap. For mid-enterprise buyers evaluating pure AI capability on a feature-for-feature basis, the gap relative to AI-native alternatives remains meaningful.
Ivanti and Cherwell face the most significant competitive pressure among major legacy vendors, and the difference in their positions is instructive. Ivanti has been investing in AI capabilities but has been simultaneously managing the integration complexity that came with its acquisition-driven growth strategy, which has created a roadmap execution challenge. Cherwell, now operating under the Ivanti umbrella following acquisition, has an installed base that is particularly vulnerable because its pre-acquisition development trajectory did not prioritise AI integration. For customers on these platforms facing renewal decisions, the AI capability gap relative to both AI-native alternatives and ServiceNow is substantial enough to warrant serious competitive evaluation rather than routine renewal.
The challenger cohort deserves a more nuanced assessment than it typically receives in analyst commentary focused on the established vendor landscape. Freshservice has matured into a credible mid-enterprise platform with a strong AI roadmap that includes automated incident classification, AI-assisted service desk response, and predictive ticket routing. Atlassian Jira Service Management has made significant investments in AI-assisted incident correlation and benefits from deep integration with the Atlassian development toolchain, making it particularly competitive in organisations that have standardised on Atlassian for software development workflows. The pure-play AIOps-to-ITSM entrants, including platforms that originated in observability and are now extending into service management, represent a longer-term threat with capabilities that could accelerate the market displacement of traditional ITSM platforms if they successfully address the process and workflow management depth that currently differentiates established platforms.
"Customers are not leaving legacy ITSM platforms because they want to. They are leaving because the gap in AI capability has become too operationally costly to ignore. When your competitors are resolving P1s 44% faster because their platform surfaces contextual knowledge instantly and yours does not, that is a business performance problem, not just a tooling preference."
Dr. Marcus Webb, VP ITSM Research, Gartner
For IT leaders facing ITSM platform renewal decisions, a structured evaluation framework should include five questions that cut through vendor marketing to assess actual AI capability maturity. First: can the vendor demonstrate the P1 resolution speed improvement in a customer environment comparable to yours, with documented before-and-after metrics? Second: is the AI capability native to the platform architecture or a bolt-on integration that requires separate licensing and maintenance? Third: what is the vendor's published roadmap for AI capability development over the next 24 months, and does it address the specific capability gaps you have identified? Fourth: what does the vendor's customer retention data look like in your segment over the past two years? Fifth: what is the total cost of staying on your current platform, including the opportunity cost of slower incident resolution, versus the total cost of migration to a higher-capability alternative?
The migration cost question deserves particular attention because it is frequently estimated inaccurately in both directions. Organisations that have completed ITSM migrations report that the most significant underestimated cost is the integration rebuild effort, particularly in environments with many custom integrations to monitoring, change management, and CMDB systems. The most significant overestimated cost is typically the training and adoption effort, where modern platforms with well-designed AI-assisted interfaces tend to achieve comparable or better user adoption velocity compared with the legacy systems they replace. The business case for switching is stronger when the current platform is more than four years old, when AI capability gaps are generating measurable operational impact, and when the legacy vendor's current-generation AI roadmap does not credibly close the gap within 18 months. For a growing number of mid-enterprise IT organisations, all three conditions are currently true.
AI ops teams achieve 52% MTTR reduction. But 79% of IT leaders say governance frameworks are not keeping pace with AI deployment in operations.
Hype aside, only 18% of self-described hyperautomation programmes meet Gartner's criteria for true hyperautomation. Here is what the rest are missing.
