Search
magnifying-glass
SimplifyMBA
Log in
Subscribe
Home
Archive
Tags
SimplifyMBA
/
News
Aug 2, 2026
ServiceNow: The Workflow Lock-In Machine
ServiceNow: The Workflow Lock-In Machine
00:00
10:00
Transcript
0:00
ServiceNow finished the second quarter of 2026 with six hundred and fifty-eight customers spending more than five million dollars each in annual contract value.
0:10
Enterprise software rarely reaches that scale because one department likes a ticketing tool. It reaches that scale when several departments depend on the same records, rules, and integrations to keep work moving.
0:22
That is the system behind ServiceNow. One governed workflow creates operating context. That context makes the next workflow cheaper to deploy.
0:32
With each expansion, the platform becomes more useful and more difficult to remove. Start with an ordinary request. An employee needs a laptop. A customer reports an incident. A security team receives an alert.
0:47
Email can carry the message, but email does not reliably record who owns the next action, which approvals are required, when a service deadline expires, or how the case ended.
0:59
ServiceNow turns the request into an operational record. The record has a state, an owner, a route, and a history. That sounds administrative. It is also the smallest unit of the moat.
1:12
Once a company defines what an incident, change, asset, or customer case means, it has created a working model of the operation. Managers can see the queue. Employees can check progress.
1:24
Auditors can reconstruct a decision. Every finished case leaves structured history for the next rule or automation. The second part of the system appears when work crosses departments. Consider employee onboarding.
1:37
Human resources starts the process, but identity, security, facilities, finance, payroll, and the hiring manager may all touch it.
1:47
When every handoff refers to the same record, each team receives the relevant approvals and context. The initiating team sees progress without building a parallel spreadsheet.
1:58
Over time, the company accumulates service catalogs, escalation routes, configuration records, knowledge articles, and performance history.
2:08
ServiceNow reported thirteen point two billion dollars in current remaining performance obligations at the end of Qtwo twenty twenty-six, up twenty-one percent from a year earlier.
2:19
The scale is consistent with customers extending the platform well beyond a single queue. Shared context alone is useful. Rules and integrations turn it into behavior.
2:30
A company adds assignment logic, approval policies, service-level timers, permissions, notifications, dashboards, and connections to identity systems, device inventories, finance software, and source code tools.
2:46
Each configuration translates a piece of company policy into an action the platform can execute. A joiner workflow might create accounts, request hardware, notify payroll, and store proof that every step happened.
3:00
Replacing the coordinator means rebuilding the sequence and proving that the replacement handles every exception. AI agents fit into the same architecture.
3:10
An agent can choose an action while the platform supplies permissions, operational context, controls, and an audit record. The value of the agent depends on the quality of the system around it.
3:22
More autonomy without reliable context creates faster mistakes.
3:26
Once the first workflow works, the second one starts with reusable components: a data model, identity controls, integration patterns, administrators, and a governance process. A new team does not begin from zero.
3:41
That reuse explains ServiceNow's land and expand economics better than seat growth alone.
3:46
The company ended Qtwo twenty twenty-six with twenty-nine billion dollars in total remaining performance obligations, also up twenty-one percent year over year.
3:56
Multiyear commitments become plausible when customers place several critical processes on the same foundation. Expansion still has to produce operating value. A consultancy can recommend a large implementation.
4:09
A customer can buy entitlements faster than employees adopt them. Contract growth without active workflows weakens the internal case for renewal. The fifth step is migration cost.
4:21
Software lock-in is often described as a data export problem. ServiceNow's harder layer sits around the data: status definitions, legal approvals, exception routes, access rights, reporting, and downstream actions.
4:36
Moving one departmental queue is manageable. Moving incident response, employee onboarding, customer cases, security investigations, asset records, and executive reporting at the same time creates operational risk.
4:51
Running two systems during the transition adds reconciliation work and breaks the shared context that justified the platform. This does not make customers permanent.
5:01
Migration friction only raises the bar for a replacement. ServiceNow still has to save time, improve control, or enable work that the organization could not coordinate before.
5:12
Friction turns into resentment when price rises and operating results stay flat. Three warning signs tell you that the system is weakening. First, implementation drag. Deployment time and customization backlog rise
5:28
while cycle time and error rates do not improve. Second, user workarounds. Employees return to chat, email, and spreadsheets, so the official record loses the context that automation needs.
5:40
Third, weak control over agentic actions. Autonomous software creates permission breaches, audit gaps, or unrecoverable errors faster than governance can respond.
5:51
Here is the decision rule: A workflow platform earns durable expansion when every completed process leaves behind reusable records, policies, integrations, or decisions that reduce the cost of deploying the next workflow.
6:05
If adoption only adds forms and licenses while cycle time, error rates, and control remain unchanged, the customer is accumulating software surface. It is not building an operating system.
6:18
There is a practical way to test which side of that line a company is on. Choose one workflow that crosses at least three teams.
6:26
Employee onboarding is a useful example because the process usually touches human resources, identity, security, finance, facilities, and a manager. Follow one completed case from request to closure.
6:39
Count the handoffs that happen inside the governed record. Then count the handoffs that escape into email, chat, and spreadsheets. The second number tells you how much of the operation the platform can actually observe.
6:53
Next, inspect what the completed case leaves behind.
6:57
A useful workflow should improve at least one reusable asset, a routing rule, a permission model, an integration, a knowledge article, a performance baseline, or an exception decision.
7:09
If every new process requires the same implementation effort as the first, the expansion loop is weak. Then test whether the system changes operating outcomes.
7:19
Measure the time from request to resolution, the share of cases that miss a service target, the number of manual corrections, and the effort required to produce an audit trail. License growth is secondary.
7:31
A workflow platform creates value when those operating measures improve. Finally, run a replacement exercise before renewal. Exporting records is only the first task.
7:43
List the approval logic, integrations, dashboards, access rules, and exception paths that another system would have to reproduce. This separates genuine process dependency from contractual friction.
7:56
The result should fit on one page.
7:59
Record the percentage of work captured in the platform, the reusable assets created by each completed process, the operating measures that improved, and the components that a replacement would have to rebuild.
8:11
Three patterns usually appear. In the first, the platform is a system of record. Most cases enter through the right channel, ownership is visible, and managers can trust the reporting.
8:23
That is valuable, but the benefit still depends heavily on disciplined use. In the second, the platform is a system of action.
8:31
Rules route work, approvals run automatically, integrations update other tools, and exceptions return to a governed queue. This is where reuse begins to lower the cost of the next workflow.
8:43
In the third, the platform becomes an operating layer. Several departments use the same definitions and controls, so a policy change can be applied across many processes.
8:54
New automation or AI agents inherit that context instead of reconstructing it for every task. The distinction matters when a vendor proposes the next module.
9:04
A system of record does not automatically become an operating layer because another license is added. The new workflow must reuse context from the old one and leave behind an asset that improves the next deployment.
9:16
Ask the implementation team to name that asset before approving expansion. If the answer is a shared identity rule, integration, service catalog, data model, or governance control, the proposal may strengthen the loop.
9:32
If the answer is only more seats, more forms, or a larger contract, the economic case is incomplete. That page gives leaders a better renewal conversation.
9:42
They can invest in the workflows that compound, repair the ones that leak context, and remove licenses that add surface without improving the operation.
9:52
You can see the complete ServiceNow system map, evidence, and failure tests at simplify.mba.
SimplifyMBA: Business Systems Decoded
Recent episodes
No results found
