ServiceNow Didn't Conquer the Enterprise. The Enterprise Walked In On Its Own.

Sometime around 2005, an IT manager somewhere fixed a problem the software was never sold to fix. He'd bought a tool to manage IT tickets — who reported the broken laptop, who closed the request, how long it sat. But the thing was so easy to bend that he realized he could point it at something else entirely: the HR team drowning in onboarding requests, or marketing's intake forms. So he did. Then he told a colleague. That small, unauthorized act of repurposing, repeated thousands of times across thousands of companies, is the actual origin of a business that reported $10.984 billion in revenue in 2024.¹ ServiceNow is usually described as a company that strategically marched out of IT and into the whole enterprise. It's closer to the truth to say the enterprise marched in on its own.

The official story is a triumphant adjacency strategy: a smart company spots that IT-ticketing logic applies to HR, to customer service, to security, and deliberately conquers each in turn. The real story is humbler and more interesting. The product was built so plain and so configurable that non-IT departments adopted it before anyone had drawn up a plan for them. The strategy didn't create the expansion. The architecture did.

A founder who'd already watched one fortune evaporate

Fred Luddy did not arrive at ServiceNow as a wide-eyed first-timer. He spent over a decade as CTO of Peregrine Systems, a company that also owned Remedy — the dominant IT help-desk software of its era.⁶ Then Peregrine collapsed in accounting fraud, and Luddy's reported net worth, said to be around $35 million, went with it.⁶ He'd spent years inside the incumbent way of building IT software: heavy, customized, consultant-laden, expensive to change. When he started over — as Glidesoft in 2003, incorporated in California in 2004 — he was the only employee, and stayed that way until mid-2005, when a $2.5 million check from JMI Equity let him hire five people.³ A company of six does not write a master plan to dominate seven enterprise software categories. It builds one good thing and tries to survive.

Read that line carefully, because the strategy is hiding inside it. Luddy's insight wasn't a market — it was a constraint he imposed on the product: make it simple enough to adapt. The consequence is what mattered. IT managers, by Luddy's own account, started recommending the tool for HR, marketing, and other departments. The IT department became the beachhead, not because anyone sold it that way, but because IT held the keys and IT could see how far the thing would bend.⁵

Why a workflow engine spreads where a feature can't

Here is the mechanism, worked all the way down. Most software is built around a domain — an HR suite knows what an employee is; a CRM knows what a deal is. The domain knowledge is baked into the schema, which makes the product powerful in one place and useless in the next. ServiceNow inverted that. The Now Platform is, underneath the branding, a generic engine for the same primitive over and over: a request comes in, it routes to someone, it moves through states, it closes, and a record persists. IT incident, HR onboarding, a customer complaint, a security alert — strip the labels and they are the same shape.⁸ Build the engine for the shape, not the domain, and a department doesn't need to buy a new product to handle a new kind of work. It just configures another flow. The expansion cost the customer almost nothing — and that, not ambition, is why it kept happening.

Today the Now Platform openly spans IT service management, IT operations, customer service, HR service delivery, security operations, and more — a multi-domain footprint the company no longer hides.⁸ At its 2026 investor day, leadership described the CRM business on a path past $2 billion and the security-and-risk business surpassing $1 billion in cumulative annual contract value, growing 40% organically year over year.⁸ Those are not the numbers of a sideline. But notice the sequence: the categories were colonized after the engine had already proven it could host them, not before.

That backlog is the moat showing itself. The lock-in isn't a contract clause; it's gravity. Every new workflow a company builds — every approval chain, every integration into payroll or the badge system, every report a manager checks each morning — is another root the platform sinks into the organization. A rival can build a better HR module. It cannot easily rebuild the eleven other things the customer has wired around it. The switching cost compounds in exactly the way the adoption did: one flow at a time, nearly invisibly, until it's load-bearing.

Isn't this just survivorship dressed up as a thesis?

The fair objection is that 'emergent, not strategic' is the kind of story that's easy to tell after a company wins. Plenty of products were built to be flexible; almost none became a $10.98 billion platform. Maybe the real difference was execution — a relentless sales machine, the discipline of operators who turned organic interest into signed contracts. There's truth in that, and the honest version of this argument has to concede it: simplicity created the opening, but someone still had to walk through it, and ServiceNow's go-to-market under Luddy's successors was formidable. The point is not that strategy was absent. It's about which factor was upstream. A brilliant sales team selling a domain-locked product would have had to fight for each new category from scratch, against incumbents who owned that domain's schema. ServiceNow's team got to sell expansion the customer had often already started on its own. The architecture didn't replace the strategy — it changed what the strategy was selling against, from a cold pitch to a warm pull.

There's a temptation to give ServiceNow a heroic origin — the founder who lost everything in a fraud and willed an empire into being two cubicles at a time. The numbers invite it; among dedicated ITSM vendors, one estimate puts its 2024 share at 44.4%, far ahead of the field.⁷ But the cleaner lesson is quieter and harder to copy. ServiceNow didn't out-strategize the enterprise software market. It built a thing so unremarkably easy to repurpose that its own customers did the strategizing for it — and then it was disciplined enough to follow them. The grand pivot everyone narrates is real in its results and false in its order. The expansion wasn't planned and then executed. It was discovered, by the people using the product, and the company's genius was mostly in noticing.