ServiceNow: Broken Workflow Is the Invisible Tax of the Large Enterprise
ServiceNow goes public solving an administrative, hidden, recurring problem: the internal friction large companies pay every day.
June 29, 2012
ServiceNow: Broken Workflow Is the Invisible Tax of the Large Enterprise
ServiceNow begins trading today on the New York Stock Exchange. The symbol is NOW. The irony is appropriate. Large companies keep saying "now," but function in "later."
The market likes software that can be explained in a lazy sentence. Social network. Search. Mobile phone. Online store. Music. Photos. Public imagination is fed by things it touches, swipes, buys, or shows friends. ServiceNow does not have that advantage. The problem it solves is ugly, administrative, hidden, almost embarrassing. That is not a defect. It may be precisely the source of the opportunity.
Large companies do not die only because a competitor creates a better product. They die from accumulated friction. An internal request that needs three approvals. An IT incident nobody tracks properly. An expensive employee copying information between incompatible systems. An email that becomes an improvised database. A spreadsheet that becomes a clandestine nervous system. A request lost between departments pretending to be coordinated. A manager who does not know who approved, when it was approved, or why.
This is the invisible tax of the large enterprise.
It does not appear as a separate line on the income statement. It does not arrive with a government stamp. It has no official rate. But it is paid every day, in wasted hours, delayed decisions, operational risks, rework, useless meetings, painful audits, and intelligent people being used as human glue between bad software systems.
Modern capitalism learned to measure revenue, margin, cost of capital, and inventory. It still measures poorly the cost of internal disorganization. ServiceNow tries to turn that disorganization into something accounting can see, process can route, and software can renew. It begins with IT Service Management, but the thesis is not "help desk." Help desk is the side door through which the company enters the building. The correct question is whether that door leads to a broader operational layer.
The ordinary investor will see tickets. I see workflow.
Ticket is symptom. Workflow is anatomy.
Every large corporation has processes nobody designed cleanly, but everyone obeys out of fear, habit, or necessity. When a new employee joins, someone needs to provision access. When a server goes down, someone needs to record, prioritize, escalate, solve, and document. When a department needs approval, someone needs to turn intention into a trail. When compliance asks for evidence, someone needs to prove the company does not operate like an email-literate tribe.
Valuable software is not only the software that creates desire. Sometimes it is the software that reduces shame.
ServiceNow is really selling a simple promise: stop pretending internal processes can live inside inboxes. The inbox was a useful invention, then became a corporate landfill. Email does not know priority, ownership, SLA, dependency, permission, audit, or automation. It merely transports anxiety. The spreadsheet knows even less. It is where governance goes to die while looking like control.
Large companies hate admitting this. But they buy software so they do not have to admit it publicly.
The economic beauty is recurrence. If ServiceNow can become the place where operational work is recorded, routed, approved, automated, and measured, the customer will not merely be subscribing to a product. It will be rewriting habits. And habit, inside a large company, is more viscous than contract.
Switching software is easy in a competitor's sales presentation. In real life, switching a platform that carries flows, permissions, integrations, reports, approvals, and organizational behavior is surgery. One does not remove only a tool. One removes a way of working. The switching cost here does not live only in technology. It lives in employees' heads, managers' routines, and the legal department's fear.
That is what interests me.
The obvious risk is valuation. ServiceNow does not arrive hidden. The IPO was priced above the range, and the software market still likes to pay for growth as if growth were synonymous with inevitability. It is not. Growth bought with excessive sales, artisanal implementation, and platform promises can become a beautiful machine for destroying capital. Most software investors learn too late that recurring revenue does not absolve absurd price.
The second risk is the company becoming consulting disguised as SaaS. If every customer demands too much customization, if every deployment requires a human army, if partners capture the economics, if the product does not standardize the chaos it promises to organize, the thesis weakens. Software scales. Consulting fattens. There is a difference.
The third risk is narrative expansion. Many companies begin by dominating a specific problem and then convince themselves they are a "platform" before they deserve the word. Platform is a dangerous word. It inflates multiples, excites bankers, and reduces mental precision. ServiceNow must prove that it can move from IT into other corporate functions without losing density. HR, facilities, compliance, security, internal service, operations. The path exists. Execution decides whether it is a road or a mirage.
The fourth risk is competition. Incumbents will not stand still. BMC, HP, IBM, CA, and other corporate names know this territory. But incumbents age defending old margins. They often protect heavy products, tired interfaces, and contracts that survive through inertia. A company born in the cloud may have less respect for the bureaucracy of the past. That does not guarantee victory. It only creates asymmetry.
The correct thesis, therefore, is not "ServiceNow will rise because cloud is good." That is seminar thinking.
The thesis is more specific: ServiceNow may capture a growing portion of the invisible tax large companies pay to internal operational chaos. If it can turn that chaos into standardized, auditable, automated flows, it can become a recurring layer of corporate work. Not the layer where executives give speeches. The layer where work actually passes.
This distinction matters.
Wall Street often loves the software the end user desires and underestimates the software the organization needs. The first wins headlines. The second wins renewals. The first depends on fashion, interface, and delight. The second depends on budget, process, and fear of breaking something critical. There is no glamour in a well-designed approval flow. There is only economy. And economy, repeated every year, becomes value.
I would not buy at any price. That would betray the thesis at the moment of embracing it. The IPO already begins with enough attention. A strong opening can attract buyers who only want "the next SaaS." This kind of buyer does not understand the company. He understands the ticker. And those who buy tickers usually sell at the first hiccup in margin, lock-up, guidance, or market rotation.
My posture would be patient and suspicious.
I would initiate a small position only if the price did not require perfection. I would not try to win the emotional auction of the first day. An IPO is theater with a prospectus. The initial price serves sellers, banks, and narrative. The investor who enters later should serve only his own capital.
The ideal operation would be to build a position in stages, preferably after post-IPO volatility, lock-up expiration, or some quarter in which the market confused investment in growth with deterioration. I would not use leverage. I would not buy long calls as lottery tickets, especially in a newly listed company with possibly illiquid options and a price still dominated by flow. The clean form would be common stock, controlled size, with willingness to add only if the operational thesis improved and the price worsened.
That is rare. But it is what one seeks.
If the market offered a severe decline for a non-structural reason, I would consider selling out-of-the-money puts only when there was enough liquidity and real willingness to receive the shares. But that is secondary. The main asset here would be ownership, not a clever bit of engineering to look sophisticated. Excess sophistication is often cowardice dressed as mathematics.
What I would not do: short. One does not short a company with potential recurrence, category expansion, and rising switching costs merely because it looks expensive. Expensive is not a catalyst. Expensive is a condition. To sell, one would need to see deteriorating retention, artificial growth, excessive dependence on services, expansion without product, or aggressive accounting. Without that, the short would be only intellectual vanity.
I also would not make a large position immediately. A good company can be a bad investment when bought in haste. Discipline is not in recognizing quality. It is in refusing quality when the price demands sainthood.
What I want to observe in the next years is simple.
First, retention. If customers expand spend, the platform is moving deeper. Second, revenue mix. Subscription should dominate services. Third, subscription gross margin. If software economics appear, the thesis breathes. Fourth, expansion beyond IT. If ServiceNow remains only an IT tool, it can still be good. If it becomes the operating system of enterprise workflow, it can become something else. Fifth, customer language. When customers start describing the platform as internal infrastructure rather than an application, the game changes.
The market loves stories that are too large. I prefer small evidence repeated.
ServiceNow does not need to convince the world it is revolutionary. It needs to become necessary in places nobody likes to look. The broken IT department. The slow internal process. The frightened compliance team. The lost manager. The forgotten request. The expensive employee wasted. The work that exists but does not appear.
Some companies sell future. Some companies sell relief. Relief can be more durable, because corporate pain is recurring.
The large enterprise will continue proclaiming efficiency in presentations. Behind the scenes, it will continue paying tax to its own friction. If ServiceNow can become the private collector of that tax, today's market may be looking at a company too tedious to be understood early.
And that is exactly where, sometimes, the money hides.
Not in the spectacle.
In the workflow.
Leo Bentier