Siebel Systems owned CRM. In the late 1990s, Tom Siebel’s company held roughly 45 percent of the market for customer relationship software, installed inside the largest enterprises in the world, and it was the name every buyer knew (telcoDR). Then a smaller rival started selling the same job a different way, rented over the internet instead of installed on your own servers, under a slogan that insulted the entire incumbent model: “no software.” Salesforce did not invent CRM. It showed up years after Siebel had defined the product. Yet Salesforce closed fiscal 2025 with $37.9 billion in revenue and the top share of the worldwide CRM market for the twelfth year running, while Siebel was absorbed into Oracle and stopped being a company anyone competes against (Salesforce investor relations).
That reversal is the thing worth studying on a Monday you are supposed to spend on strategy. The company that ends up owning a market is frequently not the one that got there first. It is the one that named the category and set the terms everyone else was forced to compete on.
Owning a category pays far better than owning a product
The lopsidedness here is easy to underestimate. Christopher Lochhead and his co-authors at Play Bigger studied the market value of the technology companies that build and dominate new categories and reached a blunt number: the category leader, what they call the category king, “commands 76% of the market cap of the category” (The Marketing Journal). Not the leading share of revenue. The leading share of the money the market decides the whole category is worth. Everyone else, the second-place product with a comparable feature set and sometimes a better one, splits the remaining quarter.
That is why category creation, done deliberately, is the highest-leverage move in product strategy and not a branding footnote. Eddie Yoon, who has written more for Harvard Business Review on this than anyone, found the same concentration from the other direction: companies that create genuinely new categories, rather than fighting for share inside an old one, grow faster and earn a structurally higher valuation per dollar of revenue. In Yoon’s framing the difference is a flywheel. Companies that build one are worth roughly “5x market cap for every dollar in revenue” compared with companies that simply compete (Category Pirates). Keurig is the tidy consumer example: it turned a pod of coffee into a category so thoroughly that K-Cups sell for about ten times the per-cup cost of ordinary drip coffee, and by 2012 the machines and pods were a $3.8 billion business with more than 40 percent dollar share (HBR). People do not pay a ten-times premium for a feature. They pay it for a category they have decided they belong to.
First to build is not the same as first in the buyer’s mind
The reflex, once you accept that the category winner takes most of the value, is to sprint to be first. That is the wrong lesson, and I have made the case before that pioneering a market is closer to a coin flip than an advantage. The research is unkind to first movers: across decades of category histories, pioneers led the market in only a minority of the categories studied, and a large share of them failed outright while later entrants who arrived after the concept was proven went on to lead (Kellogg Insight).
Hold those two findings next to each other and the apparent contradiction dissolves. The category king captures most of the value, and the first mover usually is not the king. Being early to build a product and being the company that defines what the product category means are separate acts. Siebel was first and thorough and lost. Salesforce was late and won because it did the second thing. The first mover pays to teach the market that a new kind of product should exist. The company that names the category collects on that education, often using the pioneer’s own customers as proof the problem is real.
Category design is naming the problem before you sell the answer
So what did Salesforce actually do that Siebel did not? It reframed the buying decision. “No software” was not a product feature, it was a new axis of comparison. Once a buyer accepted that installing and maintaining enterprise software was a cost rather than a given, every incumbent looked expensive and slow by definition, and every conversation started on Salesforce’s turf. That is category design: you decide what problem the market is solving, you give it a name, and you make your strengths the criteria buyers use to judge everyone, including you.
This is why category creation is a strategy discipline and not a marketing campaign bolted on at launch. Lochhead and Yoon draw a sharp line between what they call mercenaries, who chase the fastest path to a valuation milestone, and missionaries, who care enough about a problem to spend years teaching a market to want something it did not know to ask for (Category Pirates). The Play Bigger data puts that timeline at six to ten years for a category to mature. That is a long time to hold a point of view, which is exactly why so few teams do it and why the payoff concentrates so heavily in the ones that do.
It also connects to something I keep coming back to on this site. A better product does not win on its own; distribution and framing decide most markets, and a roadmap that only matches a competitor feature for feature is a decision to compete forever inside a category someone else defined. Feature parity is the opposite of category design. One accepts the other side’s terms; the other rewrites them.
What I learned watching the frame decide the deal
Running operations at a large telecom, I sat through more vendor selections than I can count, and the outcome was usually settled before anyone compared specs. The vendor who won was the one who had reframed what we were buying. We would go into a procurement thinking we needed, say, a monitoring tool, and one supplier would quietly reset the conversation to “operational resilience” or “mean time to recovery,” and from that point every other bidder was answering a question that made the reframer look like the only serious option. The tools were often close to identical under the hood. The frame was not.
Later, doing fractional COO work through my own consultancy, I made the same mistake founders make. Early on I sold “operations consulting,” which is a category buyers already have a cheap mental price for and a crowded shortlist to fill it. The engagements that actually landed were the ones where I named a specific problem the owner felt but had no words for, the gap between a founder’s calendar and the company’s priorities, and sold the fix for that. Same work. Completely different willingness to pay, because it was no longer being compared to every other consultant in the region. Naming the problem is not spin. It is the part of strategy that decides which race you are even running.
The test: are you adding a feature or defining a comparison
Here is the question I would put to any team that says it wants to lead a market rather than rent a slice of one. When a prospect describes what you do, do they reach for a category that already exists and a competitor already owns, or do they reach for your words? If a buyer says “it’s like the incumbent but cheaper,” you have built a feature, and you are volunteering to compete on the incumbent’s axis, where the incumbent wins by default. If they say “it’s a different way of doing X, the one where you don’t have to Y,” you have the beginnings of a category, and the 76 percent is at least on the table.
Most products never get there, and that is a legitimate choice. Competing well inside an established category is a real business, and it is far more predictable than the six-to-ten-year missionary slog. But do not confuse the two strategies, and do not expect category-king economics from a fast-follower plan. The value concentrates around the company that named the game. Whoever shipped first rarely collects it, and whoever merely shipped a better version of someone else’s idea almost never does.