When ServiceNow signed up over 1,000 customers for its AI agents within months, the story looked like validation of vertical platforms over horizontal frameworks. Better integration. Faster deployment. Enterprise-ready from day one.
ServiceNow's advantage has nothing to do with whether its agents are technically superior to what you could build with LangChain or AutoGen. It's about owning the workflow layer where agents operate. When you're automating incident management or change approval processes inside ServiceNow, those workflows already live in ServiceNow's data models, security policies, integration points. The agents don't cross platform boundaries. They operate in a controlled environment where ServiceNow defines everything.
Switching costs compound in ways most enterprises don't see until they try to leave.
We build enterprise web agent infrastructure at TinyFish—systems that operate across thousands of external sites, handling authentication variations and bot detection at scale. Looking at ServiceNow's 1,000+ deployments, we see something specific: each customer that deploys ServiceNow agents becomes more locked into the ServiceNow ecosystem. Not because the agents are irreplaceable, but because they're now embedded in operational workflows.
Try moving those workflows to a competing platform. You're not just switching agent technology. You're rebuilding incident categorization logic. Recreating change management approval chains. Remapping security policies. Retraining the agents on new data models. The cost isn't the agent—it's everything underneath.
Salesforce's Agentforce closed 5,000 deals approaching $1 billion in revenue. Not because Salesforce built better agents than horizontal frameworks, but because Salesforce owns customer relationship workflows. Adding agents to existing CRM processes means no new infrastructure to manage, no new security reviews, no new vendor relationships. The deployment path is clear because the platform boundaries are already defined.
The question isn't who builds the best agents—it's who owns the workflows where agents operate.
Vertical platforms win workflows that live inside their boundaries. When the valuable work happens within a single platform's control, that platform can layer agent capabilities on top and call it innovation. What they're really doing is extending platform lock-in into the agent layer.
When we're operating web agents that monitor pricing across thousands of hotel sites, we're not competing with ServiceNow. Those workflows don't live inside any single platform. They require infrastructure that handles authentication across 50 regional variations, manages bot detection that changes weekly, maintains state across thousands of concurrent operations. ServiceNow's vertical integration advantage doesn't extend to workflows that cross platform boundaries.
The market structure emerging: vertical platforms own workflows inside their boundaries. Horizontal infrastructure wins workflows that operate across systems no single platform controls.
ServiceNow's agents work beautifully for ServiceNow workflows precisely because they're tightly coupled to ServiceNow's platform. That coupling is the feature and the constraint. It makes deployment easy while making it nearly impossible to move agent capabilities to competing platforms without rebuilding everything underneath.
Each of those 1,000+ deployments deepens ServiceNow's moat. The agents become operational dependencies. The workflows become harder to extract. The switching cost compounds with every process that gets automated.
Vertical platforms are winning deployment races by extending existing platform advantages. Horizontal tools are discovering which workflows actually require infrastructure that operates across boundaries—and building for those use cases instead.