CompanyGraph
ServiceNow, Inc.
NOW · NYSE Arca · United States
Runs one shared database that connects and controls IT, HR, and security workflows across large companies.
ServiceNow runs a single database — called the CMDB — that maps every IT asset, HR workflow, and security event inside a large company into one shared schema, so that service requests, incident approvals, and change management all route through that same structure rather than through the separate systems they replaced. Because IT operations, HR service delivery, and security response all depend on the same schema simultaneously, pulling the platform out requires rebuilding every asset relationship, every approval chain, and every custom automation — written in a scripting language that cannot be exported — inside a replacement system before the original can be switched off, a process measured in months of parallel operation. That same architectural choice cuts both ways: a prolonged outage or data corruption event does not disable one function while the others keep running, it disables all three at once, which is the sharpest argument a customer would have for moving to separate tools that fail independently. The business scales cheaply on the software side — workflow templates built for one customer can roll out to others without new code — but each new enterprise customer still requires a custom configuration mapping their specific legacy systems into the platform's data models, so the number of new customers that can go live in any given period is capped by how many people ServiceNow has available to do that setup work.
How does this company make money?
Customers pay an annual subscription fee based on how many named users access the platform. Companies that want premium add-ons — like Security Operations or Customer Service Management — pay extra on top of the base fee. The company also charges for the professional services work involved in setting up the platform and building custom workflows for each customer.
What makes this company hard to replace?
The CMDB holds a complete map of all the customer's IT asset relationships — rebuilding that map inside a competing platform would take months. Every custom automation the customer has built uses the Now Platform's own scripting language, which cannot be exported, so those automations would have to be rewritten entirely. On top of that, every role-based access rule and approval chain embedded in the platform would need to be reconfigured from scratch. All of this has to happen in a working replacement system before the original can be switched off, which makes the switch practically prohibitive.
What limits this company?
Before a new customer can go live, someone has to manually connect the customer's existing IT, HR, and ERP systems to the Now Platform's data models. That mapping work is different for every customer and cannot be standardized. So the number of new customers the company can bring on in a given year is capped by how many implementation specialists it has, not by how much the software itself could handle.
What does this company depend on?
The platform runs on Amazon Web Services for cloud hosting. It connects to Microsoft Active Directory to handle who can log in and what they can access. It pulls data from Oracle and SAP databases for ERP system integration, links to Salesforce for CRM workflow synchronization, and routes service requests through Microsoft Teams and Slack integrations. Without any one of these connections functioning, a meaningful part of the platform's day-to-day operation breaks down for customers who depend on it.
Who depends on this company?
Fortune 500 IT operations centers rely on the platform to manage every incoming incident in one place — without it, they would lose centralized incident management and have to track problems manually. Enterprise help desk teams depend on the workflow automation to route support tickets; if the platform went down, they would fall back to manual processes. Compliance officers at regulated companies use the platform's audit trails to meet SOX and GDPR reporting requirements, and those reports would disappear if the platform stopped working.
How does this company scale?
Workflow templates and AI automation models built for one customer can be rolled out to new customers without writing new code, so the software side scales cheaply. What does not scale automatically is the setup work — every new enterprise customer still needs a custom configuration that maps their specific systems into the Now Platform's data models. That implementation step stays slow and labor-intensive no matter how large the company grows.
What external forces can significantly affect this company?
GDPR and SOC 2 rules keep pushing the company to add more detailed audit trail features to its workflow automation tools. Federal risk management guidelines require the company to offer on-premises deployment options for government customers, which adds infrastructure complexity. Supply chain cybersecurity executive orders are pushing companies to build vendor risk assessment directly into procurement workflows, which creates both a requirement and an opening for the platform to expand into that area.
Where is this company structurally vulnerable?
Because IT operations, HR service delivery, and security incident response all run through the same CMDB at once, a serious platform outage or data corruption event does not hurt just one of those functions — it knocks out all three simultaneously. If that happened at several large customers at the same time, those customers would face real regulatory trouble under SOX and GDPR audit requirements, and they would start looking at separate point tools that fail independently rather than all at once — which is the exact opposite of what the unified-schema approach promises.