ServiceNow
Sorbet currently classifies ServiceNow as the leader in its ITSM & workflow bucket. The detailed selection note is not yet available.
Strengthening
Based on 4 material signals in the last 30 days: 4 positive, 0 negative.
Evidence summary, not a buy / sell rating
Latest approved decision: hold · 2026-08-29
The role and pillars explain what job this holding has inside the System-of-Record basket—not whether it suits an individual investor.
ServiceNow is in the portfolio because it owns the densest concentration of enterprise state machines outside of finance: incidents, change requests, service-level agreements, approval chains, and configuration-management records that together constitute the operational memory of the modern enterprise. Those records are not peripheral logs — they are the authoritative source of truth for what broke, who approved the fix, when the change window opened, and whether the audit trail is clean, satisfying P1 (durable records centred on typed objects), P2 (named, enforced state transitions from New → In Progress → Resolved), P3 (explicit ownership fields with role-based permissions at every stage), and P5 (a stable, versioned API and MCP-compatible surface that lets agents read full transition history back through time). As the leader in the ITSM bucket, ServiceNow anchors the 40% leader allocation precisely because its installed base at Global 2000 accounts represents a switching cost that challengers would need years and a complete workflow-engine rebuild to overcome. The agent-readiness narrative here is not aspirational: ServiceNow's Now Assist and AI agent SKUs are monetising records the platform has held for a decade, not records it must go acquire.
The bucket's primary paper position: the company Sorbet currently treats as the clearest expression of this workflow category.
The thesis properties this holding is selected to test. These labels are portfolio classifications, not standalone proof.
Durable records
Explicit state machine
Typed ownership
Queryable history
The thesis for ServiceNow breaks structurally — not merely underperforms — under three observable conditions. First, if a foundation-model provider ships a credible incident-and-change-request layer with typed ownership fields, named state transitions, and a queryable audit API, and enterprise customers begin re-platforming ITSM workflows onto it, that would directly falsify P1 through P3 for NOW; the concrete signal to watch is a major analyst firm removing ServiceNow from the ITSM Magic Quadrant leader position in favour of a model-lab-affiliated entrant. Second, if ServiceNow's disclosed agent-SKU ARR mix stalls or reverses — meaning the Pro Plus and Now Assist attach rates plateau in two consecutive earnings reports while total subscription revenue growth decelerates below the company's own guidance band — that is the failure-to-monetise invalidator firing specifically on NOW, since the entire bull case rests on the company converting its installed workflow state into incremental consumption revenue. Third, Microsoft represents the most credible hyperscaler-bundling threat: if Copilot for ITSM is included in an E5 or equivalent enterprise agreement at no meaningful incremental cost and enterprise customers publicly cite it as a NOW replacement rather than a complement, P3 and P5 erode because ownership and queryable history shift into the Microsoft graph. Open-source clone risk (Plane, OpenProject analogues for ITSM) is a slower-moving signal for ServiceNow given its upper-enterprise seat base, but sustained gross-margin compression below 78% on subscription revenue would indicate pricing-power erosion worth escalating to a trim signal. Underperformance in the share price absent one of these structural breaks is explicitly not falsification per ADR 0016.
Daily closes are shown for context. Reference levels are deterministic outputs of Sorbet's published ATR method, not analyst targets or advice.
2025-07-28 → 2026-08-31
$147.99
Short-term levels use 14d ATR and the 200d average. The 3y projection compounds the current revenue-growth rate with no multiple expansion. Missing inputs stay blank.
Revenue growth + FCF yield, not the conventional FCF-margin formulation. Visible for judgment, but not wired into selection.
The available history does not support a directional trend classification.
| Quarter | Revenue YoY | Gross margin | FCF margin | Operating margin |
|---|---|---|---|---|
| 2026-03-31 | 22.89% | 75.09% | 40.56% | 13.34% |
| 2025-12-31 | 20.91% | 76.63% | 56.05% | 12.42% |
| 2025-09-30 | 21.25% | 77.28% | 16.70% | 16.79% |
| 2025-06-30 | 21.49% | 77.48% | 16.36% | 11.14% |
| 2025-03-31 | 17.68% | 78.92% | 46.57% | 14.60% |
| 2024-12-31 | 19.66% | 78.66% | 46.40% | 12.65% |
ServiceNow's trajectory is anchored in converting its dominant ITSM installed base into an agent-execution layer — the Now Platform already carries the incident, change-request, and approval-chain records that autonomous workflows need, and every new agent SKU sold is monetising state the company has owned for years rather than building net-new content. To compound as the thesis demands, ServiceNow must demonstrate that its AI agents are writing back into those records reliably enough that customers treat the platform as the authoritative control plane rather than a human-assisted dashboard — measurable as rising consumption revenue attached to agentic API calls, not just seat expansion. The outstanding gap is P4: the platform's structural verbs (resolve, escalate, approve, reopen) are rich internally, but third-party agent frameworks still interact with ServiceNow largely through broad REST endpoints rather than a published, agent-optimised MCP surface, meaning the machine-readability advantage is partially locked inside the walled garden. Until ServiceNow ships a first-class MCP server or equivalent — giving external orchestrators the same named-verb fidelity Atlassian has signalled — the P4 gap represents both a risk to interoperability and an unproven pillar that the portfolio will continue to monitor against the thesis diagnostic.
ServiceNow Has Quietly Shaken Off The AI Apocalyptic Fears
The headline reports that ServiceNow's AI monetization is accelerating, directly supporting the thesis that Systems-of-Record platforms
Source: SeekingAlpha
ServiceNow: Winning The AI Race, Watching Its Wallet
The headline 'Winning The AI Race' directly supports the thesis that incumbent SoR platforms (like ServiceNow) are becoming the agent control plane and monetizing their existing records through agent SKUs, which is the core structural claim.
Source: SeekingAlpha
ServiceNow and Google Cloud expanding partnership to launch interoperable AI agents directly validates the thesis that incumbent SoR platforms (ServiceNow) are becoming the agent control plane; the news supports P4 (structural verbs / API-driven domain operations) and P5 (queryable history via agent automation).
Source: Insider Monkey
Can ServiceNow Sustain Its Growth Amid Rising AI Competition?
The news explicitly ties ServiceNow's strategy to governance, security, and enterprise integration — the exact moat (incumbent records + permissions + approval chains) the thesis says will compound as agent budgets grow. This supports P3 (ownership/permissions) and the ITSM bucket's structural advantage over greenfield agent platforms.
Source: Yahoo
positive signal but thin coverage (only P4) — hold for confirmation.
positive signal but conditions not met (coverage solid, trend neutral, drift on_target) — hold.
positive signal but conditions not met (coverage solid, trend neutral, drift on_target) — hold.
positive signal but thin coverage (only P4) — hold for confirmation.