How should ServiceNow rethink its workflow thesis for AI buyers?

The Old Workflow Thesis (what got ServiceNow to $11B ARR)

• Single platform of record — one CMDB, one workflow engine, one data model across ITSM, HRSD, CSM, FSM
• ITIL-grounded — ticket → assignment group → resolution → CMDB update is the atomic unit; the entire org chart maps to this
• IT-buyer trust — the CIO is the economic buyer, procurement loves the consolidation story, and the ROI math is "retire 12 point tools"
• Pro / Pro Plus seat-based pricing — predictable per-user uplift, easy to forecast, sales comp aligned
• Named legacy references — Deloitte, NVIDIA-as-customer, Visa, AstraZeneca, US DoD — all bought "workflow consolidation," not "agent platform"

What AI Buyers Actually Want In 2026

• Agent-first, not ticket-first — the work unit is an autonomous agent loop, not a Jira/ServiceNow ticket that a human closes
• Model-flexible, not vendor-locked — buyers want to swap Claude / GPT / Gemini / open-weights without re-architecting; "bring your own model" is table stakes
• Data-portable, not platform-trapped — Iceberg / Delta / open table formats, not proprietary Now-only data graves
• Outcome-priced, not seat-priced — pay per resolved case, per booked meeting, per closed incident — not per logged-in human
• Audit-ready agent governance — every agent action logged, evals on every release, EU AI Act + SOC2 alignment, human-in-the-loop policy controls
• Composable, not monolithic — the AI buyer wants to assemble agents from MCP servers and best-of-breed components, not buy a 7-year platform

The 4 Mental Shifts ServiceNow Needs

• Shift 1 — From "workflow runs on platform" → "agents run workflows on platform." The atomic unit changes. A workflow used to be a deterministic state machine triggered by a ticket. Now it's an agent reasoning loop that *invokes* deterministic workflows as tools. ServiceNow has to reframe Now Assist + AI Agent Studio as the substrate where agents *live*, not as a feature bolted onto Flow Designer.
• Shift 2 — From "ticket → resolution" → "agent → resolution-without-ticket." The aspirational metric stops being MTTR on a ticket and becomes "% of would-be tickets that never opened because an agent resolved upstream." Deflection rate at the edge — not after the fact.
• Shift 3 — From "Pro Plus = AI uplift SKU" → "Pro Plus = agent platform." Today Pro Plus is sold as a 30-60% price uplift for AI features. The new pitch: Pro Plus *is* the agent platform; classic Pro is the legacy compatibility tier. Flip the hierarchy.
• Shift 4 — From "platform of record" → "agent platform of record + record platform." Two-layer pitch: ServiceNow is the *agent* control tower (where agents are governed, observed, and orchestrated) AND the underlying record platform (CMDB, HR record, customer record). The agent layer is the new top — the record layer is the moat underneath, not the marketing lead.

The 1 Narrative Bet That Risks The Moat

• The 18-month repositioning cliff — go too hard on agent-first and the ITIL/ITSM CIO who renews 40% of ServiceNow's ARR feels orphaned; go too soft and Salesforce Agentforce + Microsoft Copilot Studio + Sierra/Decagon eat the agent narrative
• Named risk #1: ITSM stalwarts — Deloitte, Accenture, big-bank ITOps teams bought "single platform of record"; if the new pitch is "agent control tower," those CIOs need a migration story, not a re-pitch
• Named risk #2: Pro Plus pricing inversion — if Pro Plus becomes "the agent platform," classic Pro looks like a legacy SKU and renewals get harder; sales comp has to be re-architected before the narrative ships
• Named risk #3: AI Agent Studio cannibalizing Flow Designer — the agent platform partially obsoletes the no-code workflow tool that Now built its developer ecosystem on; the partner channel revolts if not handled
• The hedge — McDermott's framing has to be additive ("the agent layer sits on top of the platform of record you already own") not replacive ("forget tickets, agents now")

What McDermott's Pitch Should Sound Like

• Investor-day language — "ServiceNow is the control tower for enterprise AI agents — the only platform where agents are governed, observed, and connected to the system of record." Drop "workflow OS" by Q3 FY26; lead with "agent OS, workflow native."
• Sales-pitch language — "You already own the system of record. We turn it into the system of *action* for every AI agent in your enterprise — yours, ours, and your vendors'."
• Product-page hierarchy — Now Assist + AI Agent Studio above ITSM/HRSD/CSM in the nav, not below. Workflow Data Fabric promoted from "data layer" to "AI context substrate."
• Named-customer reference patterns — stop leading with "Deloitte consolidated 12 ITSM tools"; start leading with "NVIDIA runs 200 production agents on the ServiceNow agent platform with full audit trails and model-swap flexibility." Same logos, new headline metric.

What Has To Change Operationally

• Now Assist becomes flagship product, not a feature — its own P&L, its own GM, its own launch cadence; out of the Flow Designer org
• AI Agent Studio becomes the primary GTM motion — sales is comped on agent-platform attach rate, not Pro Plus seat uplift
• Workflow Data Fabric / RaptorDB repositioned as AI context substrate — Iceberg compatibility, vector-native, MCP-server native; the "why ServiceNow under your agents" moat
• Named acquisition target — Decagon (CX agent infra) or Lindy (long-tail agent builder) to bolt agent-first DNA onto the org and signal commitment; alternatively, Cresta for the contact-center agent angle
• Open up the model layer — public BYO-model support for Claude / GPT / Gemini / Llama with first-party benchmarks; kill the implicit "Now LLM is best on Now" narrative
• Agent governance becomes a paid module — Agent Observability + Eval + Policy as a standalone Pro Plus capability; this is the audit-ready governance layer the EU AI Act mandates

Old Thesis × New Thesis × Mental Shift × Cost × Risk × Timeline

Old Thesis → Pivot → New Thesis

Related on PULSE

• [How should Datadog rethink its observability thesis for AI buyers?](/knowledge/q1709)
• [How should Salesloft rethink its sequencing thesis for AI buyers?](/knowledge/q1828)
• [How should Outreach rethink its sequencing thesis for AI buyers?](/knowledge/q1769)
• [Is Vendor Consolidation in 2027 Forcing B2B Sales Teams to Rethink Territory Planning?](/knowledge/q16239)
• [Chief vs AI peer matching in 2027 — why Lunchclub-style platforms eat the cohort thesis](/knowledge/q11002)
• [Why did Snowflake security incidents in 2024 matter for the 2027 thesis?](/knowledge/q1581)

The Agent-Native Pricing Problem

ServiceNow’s current consumption model—per-user subscription for Pro/Pro Plus, with additional per-workflow or per-automation charges—breaks down when an AI agent can perform the work of 50 human operators. The company needs a per-resolution or per-outcome pricing that aligns cost with value delivered, not headcount displaced. Expect to see experiments with “agent tokens” (like Snowflake credits) or outcome-based tiers (e.g., $X per automated incident closure, $Y per self-resolved HR case). The risk: overcomplicating procurement for traditional IT buyers who just want a predictable seat license. The opportunity: capturing the AI buyer’s willingness to pay for measurable business outcomes rather than platform access.

The Data Fabric Moat Nobody Talks About

ServiceNow’s Workflow Data Fabric (powered by RaptorDB and its graph-based CMDB) is the only major platform that can map relationships between people, processes, systems, and data in real time—without requiring a separate data lake or ETL pipeline. For an AI agent to act autonomously, it needs this relational context: knowing that a server outage affects a specific HR application, which impacts a specific employee group, which triggers a specific communication workflow. Competitors like Salesforce and Microsoft require stitching together multiple data stores (Data Cloud, Dataverse, etc.) to approximate this. ServiceNow’s advantage is that the data model is native and pre-joined—the agent doesn’t need to query three different APIs to understand the blast radius of a change. This is the quiet weapon in the AI buyer pitch, but it’s currently buried under “workflow automation” messaging.

Sources

• ServiceNow official website — product documentation and platform capabilities for AI workflow automation
• Gartner — market analysis and research on AI-driven enterprise workflow trends
• Forrester Research — reports on AI adoption in business process automation and workflow platforms
• Harvard Business Review — articles on AI strategy and organizational change in enterprise software
• McKinsey & Company — insights on AI’s impact on operational efficiency and workflow redesign
• MIT Sloan Management Review — research on AI integration and digital transformation in business processes

FAQ

What does "enterprise AI agent control tower" mean for ServiceNow? It means ServiceNow shifts from being a platform that automates human-driven workflows to one that orchestrates autonomous AI agents across the enterprise. Instead of agents just assisting with tickets, they become the primary executors of tasks, with the platform serving as the command center for agent behavior, data access, and governance.

Will ServiceNow abandon its ITIL/ITSM roots for this AI shift? No, but it must balance the messaging. The legacy ITSM buyer built ServiceNow’s install base, and going too aggressively agent-first risks alienating them. The strategy is to frame AI as an evolution of workflow automation—not a replacement—so IT ops teams see agents as a natural extension of their existing processes.

How does ServiceNow’s Workflow Data Fabric give it an edge over competitors? The Workflow Data Fabric, powered by RaptorDB, provides a unified, real-time data layer that connects workflows across departments. This is a defensible substrate because it reduces data fragmentation, which is critical for AI agents to act accurately—something pure-play agent startups like Decagon or Sierra lack.

What is the risk of ServiceNow becoming too agent-first? The main risk is that legacy CIOs who invested in the Now Platform for ITIL/ITSM feel their purchase was a stepping stone to something else. If the narrative shifts too abruptly, it could erode trust in the platform’s long-term stability for traditional use cases.

How does ServiceNow’s Pro Plus SKU fit into the AI thesis? Pro Plus should evolve from being an AI uplift add-on to becoming the core agent platform itself. Instead of charging extra for AI features on top of existing workflows, the SKU should position agents as the default execution layer, with workflow automation as a supporting capability.

Why is the 18-month window critical for ServiceNow? Because competitors like Salesforce (Agentforce), Microsoft (Copilot Studio), and agent-native startups are all racing to own the enterprise AI control tower narrative. If ServiceNow doesn’t solidify its position as the agent orchestration platform within that timeframe, the market perception will ossify, making it harder to claim that role later.

Bottom Line

ServiceNow's workflow thesis got it to $11B ARR; it will not get it to $20B. The pivot is real, the substrate (Workflow Data Fabric + RaptorDB + the system-of-record gravity) is genuinely defensible, and McDermott has the narrative chops to land it — but the 18-month window is unforgiving and the Pro Plus pricing inversion has to be sequenced before the agent-first marketing flips. Bet: ServiceNow makes the pivot but only after a named acquisition (Decagon / Lindy / Cresta tier) forces the org to internalize agent-first DNA. *(see also: q1613, q1614, q1620)*