Category creation: how PMMs build markets nobody else owns

The board says delayed. No reason, no new departure time, no agent at the podium.

Two hundred people share one problem and not one of them can act on it. You can't go find food, because it might board in ten minutes. You can't rebook, because nobody knows whether this is an hour or the whole night.

Then the agent picks up the mic. The inbound aircraft is still on the ground in Denver, we're looking at 4:40, boarding at 4:15.

Nothing got better. The plane is exactly as late as it was thirty seconds ago. But now everyone can move.

That's what a category is. You don't invent one. You announce one.

The gate announcement

Call it the gate announcement. A category names the condition a market is already stuck in, plainly enough that the people stuck in it can finally do something about it.

Which makes the work narrower than the word "creation" suggests. A nicer name for an existing market doesn't count. Neither does a tagline, or a manifesto nobody forwards.

Buyers don't buy products. They buy answers to problems they can name.

So name the problem first and let the solution come second. "CRM" names a solution.

"Revenue intelligence" names a problem, the gap between what a sales team does all day and what shows up as revenue. "Developer experience" names a problem, the friction between writing code and shipping it.

A good category name is plain enough that buyers hear their own week in it, and distinct enough that it can't be confused with the market next door.

There's a cheap test for it. Show the name to ten buyers cold and ask what kind of company would help them with this.

If they describe roughly what we sell, we have a name. If they go quiet, we have a slogan.

A claim with an enemy

Every category that took hold had a claim about how the world works that made the current way look wrong.

Salesforce argued that software should arrive like a utility instead of being installed like infrastructure. Drift argued that a lead capture form is a strange way to start a conversation with a human being.

Both were arguable at the time. That's what made them useful.

"We believe customer data is valuable" is not a claim. Everyone believes that. A real claim has an edge on it, the kind a competitor would want to dispute in public.

The claim also needs a villain, and the villain can't be a competitor. Point at a rival and we look small. Point at the condition creating the problem and buyers recognize their own building.

Spreadsheet hell. Shadow IT. Reactive security. The meeting culture that eats the week.

Nobody needs convincing that any of those exist, which is exactly why they work.

Voices that aren't ours

A category isn't real until other people use the words without being asked.

Analysts, press, customers, partners, the vendors sitting next to us in the stack. When several of them describe the same problem the same way, the category stops being our marketing and starts being the market's vocabulary.

That's why analyst relations carries so much weight here. When a Gartner or Forrester report uses the term, thousands of enterprise buyers get the category legitimized at once, and every competitor has to answer a question we wrote.

Four moves do most of the work:

• Brief analysts on the problem long before pitching the product
• Give customers language for their own situation rather than for our product
• Find the adjacent vendors who grow when this category grows
• Put the words where people already search for the problem

The long middle

Two to five years. That's the honest timeline, and it's the reason most of this fails.

Most companies quit around month eighteen, because demand gen numbers haven't moved and the narrative feels like an expensive opinion. Then they walk back into the old category, now behind the competitors they left.

The category takes hold when the words become the default way buyers describe the problem, and that only happens through repetition in every place a buyer touches. The site, the sales call, the keynote, the customer quote.

A category has no launch date and no post-mortem. Run it like a launch and it burns out before it can compound.

We keep expecting a slope. What we get is a step.

The unlabeled light switch

Check into any hotel and you meet the same puzzle. Three switches by the door, none of them labeled, and a bedside panel of icons that mean nothing to anyone who didn't design it.

So we sleep with the bathroom light on, because that's the one switch we found.

Two category mistakes are the unlabeled panel.

The first is naming the category after ourselves. "The Acme Platform" is a product name wearing a category's clothes, and if the name stops making sense the day we're acquired, it was never a category.

Buyers just reach for the switch they recognize, which is whatever the analysts already call us.

The second is naming a problem nobody has. This one is seductive, because building the product genuinely does let us see the problem more clearly than the market does. Seeing it first is not the same as the market feeling it.

Do the buyer research before committing. If buyers have no language at all for the problem, that's a warning. If they have language that's fragmented and slightly wrong, that's the opening.

A market already named

Slack didn't name team communication. It walked into a market that already had a name and argued the incumbents were the problem, then let "the death of email" do the rest.

Figma did the same to design tools. The category existed, Adobe and Sketch owned it, and Figma made desktop-only software look like a constraint rather than a norm.

Call that invasion, and for most later entrants it's the better move. The mechanics are identical, with a claim, a villain, and other voices repeating it. The difference is that buyers already have the vocabulary, so we spend our years arguing about what should win instead of teaching people the problem exists.

What product marketing holds

Product marketing is the function that makes this possible and the one most likely to quietly kill it.

The narrative is ours to write. We're the people in the building who know the buyer, the alternatives, the product's real edge, and the macro pressure creating the problem, which is everything the naming requires. What comes out of it is a document that states the problem, names the villain, makes the claim, and explains why this company gets to be the one saying it.

Then it's ours to defend, mostly from ourselves. Sales reverts to features under quota pressure, demand gen reverts to whatever converted last month, and the CEO improvises a new framing at a conference.

None of it is malice. All of it dissolves a category.

The usual product marketing metrics won't tell us whether it's working. Watch search volume for the problem instead of the product, and watch whether prospects show up already using our words.

And watch the competitors. When they start using our category name, some of them claiming they got there first, that's the signal.

The plane is still late. Somebody has to pick up the mic.

What to do next

If buyers keep describing the same pain in five different broken ways, and the analysts keep filing us under a category that doesn't fit, there may be a name sitting unclaimed in that gap.

A Bare Strategy positioning audit is where we find out. We map how buyers actually describe the problem today, test whether a new name would hold, and say plainly when the honest answer is to compete inside the category that already exists.

If that's where you are, start here. The first conversation is free.