ServiceNow Didn't Expand Beyond IT. IT Was Just the Door It Walked In Through.

Before there was an HR product, customers built one anyway. They took the IT help-desk app they already owned from ServiceNow, dropped it into their HR department, and started routing onboarding tickets and benefits questions through it.⁵ No one in IT had been asked to do this. The software just turned out to be good at the thing every department secretly needs: a form, a queue, an approval, a record. ServiceNow noticed, and built the dedicated HR product around what customers were already doing to it. The expansion wasn't a strategy memo. It was a confession the product had been making all along.

The official story is that ServiceNow was an IT service-management company that cleverly expanded beyond its core. That framing is tidy and almost backwards. The IT product was never the core - it was the first thing a general workflow engine happened to be sold as, because IT was the department most obviously drowning in tickets and most willing to pay.

That sentence is the whole thesis. When Fred Luddy started the company in 2003 as Glidesoft - it was formally incorporated in California in 2004, a distinction worth keeping straight - he was not solving IT's problem.¹ He was building a forms-and-workflow platform and looking for a door to walk through.⁷ IT was the door. It was never the room.

Why the beachhead beats the destination

Here is the mechanism almost everyone misses. A normal software company that wants to grow buys or builds new products and bolts them on - separate codebases, separate data, separate logins, and a sales pitch that starts from zero each time. ServiceNow grew the opposite way. Because HR, security operations, and customer service were all instantiated on the same workflow engine and the same underlying data model, each new department it entered wasn't a new sale standing alone - it was another set of records, approvals, and identities pulled onto a platform the company already ran. The IT team's CMDB, the HR team's case files, the security team's incidents: one schema, one platform, talking to each other. That is why the expansion compounds instead of merely adding. Each non-IT workflow makes the IT core stickier, and the IT core makes the next workflow easier to land.

The expansion was customer-led, then made deliberate

The early moves looked accidental because they were. Customers were repurposing ITSM for HR before ServiceNow had an HR product - the demand revealed the adjacency, not the roadmap.⁵ What turned a happy accident into a machine was structure. ServiceNow began carving each adjacency out as its own general-manager-led business unit - HR first, then Security Operations, then Customer Service Management, then the Creator layer that lets customers build their own apps on the platform - a GM model instituted under CEO Frank Slootman.⁸ Each GM owned a workflow, but every workflow ran on the same foundation. The result is a portfolio that looks like four products and behaves like one.

What the financials confirm - and what they don't

The platform thesis shows up in the contracts, not just the slogans. ServiceNow reported full-year 2024 revenue of roughly $11.0 billion, with about $10.6 billion of it subscription and growth above 22%.³ More telling than the top line is the backlog: remaining performance obligations of $22.3 billion, and nearly 500 customers each spending more than $5 million a year.⁴ Those are not the numbers of a help-desk vendor. They are the numbers of a platform that, once inside an enterprise, keeps absorbing more of its work - and the more workflows it absorbs, the larger and more locked-in each account becomes.

But the data also disciplines the hype. A popular line holds that non-IT workflows are now the majority of ServiceNow's business. They aren't. By the company's own ACV mix, Technology Workflows - the IT-centric segment - still account for about 53% of total ACV, with employee and customer workflows around 30% combined and the Creator layer about 17%.⁶ Non-IT grew from over 20% of revenue in 2017 to nearly half by 2021, which is remarkable - but 'nearly half' is not 'the majority.'⁵ IT remains the largest single segment. The beachhead is still the biggest beach.

Isn't this just a vendor selling more software to the same buyer?

The fair objection is that this is ordinary land-and-expand dressed up as architecture. Every enterprise vendor cross-sells; ServiceNow simply has a wide product line and a good account team. There's truth in it - selling a fifth module to a CIO who already trusts you is not a unique trick. But the objection misses where the moat actually lives. In a bolt-on portfolio, each module a customer drops costs them only that module. In ServiceNow's model, the modules share a data model, so ripping out HR weakens the security workflow that reads the same employee records, which weakens the IT workflow that depends on both. The switching cost isn't additive; it's entangled. That entanglement is exactly what the 2003 design choice purchased - and it's the reason a competitor can't simply out-feature one workflow at a time. They'd have to replace the connective tissue, and the connective tissue is the product.

ServiceNow priced its IPO in mid-2012 at $18 a share, valued at around $2 billion, and was sold to the market as the company that finally made IT tickets bearable.² That was true, and it was the smallest true thing about it. The durable advantage was never the help desk. It was a workflow engine patient enough to look like a help desk until the enterprise had already built its HR, its security, and its customer service on top of it - and discovered, too late to mind, that it couldn't pull any one thread without unraveling the rest. ServiceNow didn't expand beyond its core. It was always the core, quietly waiting for the rest of the company to walk in.