In 1975, a twenty-four-year-old Kodak engineer named Steve Sasson built the first digital camera. It was the size of a toaster, captured a black-and-white image at 0.01 megapixels, and took twenty-three seconds to record a single photograph to a cassette tape. Sasson showed it to his managers. Their response, as he later recalled, was essentially: that’s cute, but don’t tell anyone about it.
Kodak was not a stupid company. It was a dominant one. At its peak it held 90 percent of the American film market and 85 percent of camera sales. Film was not just a product line — it was the entire economic architecture of the company. Processing fees, paper, chemicals, the retail relationships built around the assumption that photographs needed to be developed. Digital threatened all of it simultaneously. So Kodak did what dominant companies do when confronted with a threat they can’t absorb into the existing model: they managed it. They ran studies. They filed patents. They made incremental moves. They protected the thing that was working rather than building the thing that would work next.
Kodak filed for bankruptcy in 2012. The digital camera had been sitting in their own archives for thirty-seven years.
Nokia’s version of the same story has a different texture. Where Kodak’s failure was about protecting a margin, Nokia’s was about identity. Through the 1990s and into the early 2000s, Nokia was mobile phones — not a major player, but the category itself. At its peak it held over 40 percent of the global handset market. The company had navigated a remarkable transformation earlier in its history, shedding paper mills and rubber boots to become a pure technology company. It knew how to change. It had done it before.
What it couldn’t do was change from a hardware company into a software one. When the iPhone arrived in 2007, Nokia’s internal assessments were, by most accounts, accurate. They understood the threat. They had touchscreen prototypes in development. What they couldn’t manage was the cultural distance between building phones that were superb physical objects — durable, reliable, made to exacting standards — and building phones that were primarily platforms for software that other people would write. The excellence that had made Nokia great was manufacturing excellence. The game was becoming something else, and manufacturing excellence was not only insufficient for the new game; it was actively in the way, because it oriented every decision toward the object rather than the experience.
Nokia’s market share collapsed from over 40 percent in 2007 to under 5 percent by 2013.
Andy Grove, who built Intel into the dominant force in semiconductors, called it plainly: only the paranoid survive. He meant it as a prescription. His successors treated it as a trophy.
Both stories have the clean shape of settled history. We know how they end. The verdict is in, the lesson is available, and it’s easy to read them now as cautionary tales about obvious mistakes made by people who should have known better.
This is the wrong way to read them.
Kodak and Nokia didn’t fail because they were blind. They failed because they were standing on a fulcrum — a moment when the old game and the new game were both plausibly real — and they chose the wrong side. At the time, that choice was not obviously wrong. Film was still enormously profitable. Nokia’s hardware was genuinely superior. The rational case for staying the course was real, and the people making it were not fools.
The reason the Kodak story is still told fifty years later is not that the mistake was obvious. It’s that it wasn’t — and they made it anyway.
Which brings us to now. Because there is a fulcrum in front of the enterprise software industry, and nobody knows yet which way it tips.
The companies in question — Salesforce, ServiceNow, and most of the SaaS category built over the last twenty years — were constructed on a simple and powerful premise: that businesses would pay recurring subscription fees for software that managed their customer relationships, their workflows, their data. The premise was correct. It produced some of the most durable businesses in the history of technology.
The threat AI poses to this model is not subtle. If an AI agent can handle a customer service interaction, manage a workflow, or synthesize a CRM record without a human touching licensed software to do it, then the per-seat subscription model — the economic engine underneath all of it — starts to look like film processing in 2003. Theoretically intact. Quietly at risk.
The responses of these companies have been instructive, and they’ve diverged.
Here is the honest position: we don’t know yet. The fulcrum is still in motion.
It’s possible that Salesforce’s Agentforce is the Kodak digital camera — the real thing, built by the right company, that gets buried under the weight of protecting what already works. It’s possible that the SaaS model is more durable than the threat suggests, that enterprises will pay for trusted platforms regardless of the underlying labor model, and that the companies racing hardest to cannibalize their own revenue streams are making a different kind of mistake. It’s possible that ServiceNow’s consistency is discipline, or that it’s the Nokia instinct to keep building the best version of the thing that used to win.
What the Kodak and Nokia stories actually teach — not the simplified version, but the harder one — is that the mistake is never visible in the moment it’s made. It only becomes visible later, when the fulcrum has tipped and the choice that was once defensible has become permanent.
The coach who wins five championships holds the philosophy and rotates the players. The coach who wins one holds the players and calls it philosophy.
The enterprise software companies standing at this moment have a version of the same decision. The ones who make it correctly will, in twenty years, be the ones we cite as examples of adaptation. The ones who don’t will be the ones we cite as examples of something else.
We just don’t know yet which is which. That’s not a comfortable place to stand. It is, however, exactly where we are.
You must be logged in to post a comment.