Category Creation Is Mostly a Tax — Name the Workflow Instead
Founders love the idea of creating a category. The market in 2026 doesn't reward it. The companies winning are the ones that named a workflow nobody else owned, then quietly dominated it. The category, if there is one, gets named after them later.
A founder pitched me her positioning in a kickoff last quarter. The deck spent the first six slides arguing that her product belonged in a new category — call it "AI-native revenue intelligence." The seventh slide had a 2x2 with her logo in the upper-right corner. The eighth slide was the manifesto. Her sales cycles were averaging eleven months. Her win rate was 14%. The category narrative was supposed to be the differentiator. It was actually the friction.
We rewrote the positioning in two days. The new pitch wasn't "we're inventing a category." It was: "we replace the manual work your RevOps team does in Salesforce every Monday morning, and we cost less than the analyst who does it." Same product, different frame. The eleven-month cycle became four. The 14% win rate became 31% within two quarters. The category language never came back.
This isn't an indictment of category creation as a practice. It's a recognition that the market reward for category creation has collapsed. Vertical and workflow-specific positioning now beats horizontal category creation for almost every B2B SaaS company outside the largest market caps. The reason is buyer behavior. The fix is workflow naming.
The Category Tax
Category creation costs money and time before it pays. The classic playbook — name the category, define the criteria, position yourself as the leader, evangelize until analysts adopt the language — was a five-to-seven year campaign with a payoff that came late if it came at all. Companies like Drift, Gong, and HubSpot pulled it off. Hundreds of others tried and didn't.
The 2026 buyer doesn't want a new category. They want a vendor that solves a known problem. When the buyer asks ChatGPT "what tools help with X workflow," they don't want the engine to explain a new category. They want a list of vendors that handle X. Companies that lead with category narrative get filtered out as "doesn't fit my use case."
The economics don't work for most companies. Category creation requires sustained marketing investment over multiple years before pipeline catches up. Most B2B SaaS companies don't have the runway, the patience from the board, or the attention span from the market. The investment ends before the payoff.
The competition for attention is structurally harder. Buyers research with LLMs. LLMs cite established categories. New categories take 18–24 months to enter the LLM's reference set, by which time the buyer has bought from a vendor in an established category that named the workflow correctly.
What's Replacing It: Naming the Workflow
The teams winning in 2026 don't create categories. They name workflows that existing categories don't own.
A workflow is specific, recognizable, and ownable. "Revenue intelligence" is a category. "Catching at-risk renewals 60 days before the customer churns" is a workflow. The workflow is concrete enough that a buyer either has the problem or doesn't, and the answer to "do you have this problem?" is binary.
Workflow ownership produces faster sales cycles. Buyers who recognize their problem in your positioning don't need to be educated. They need to be confirmed. Confirmed buyers close in weeks; educated buyers close in quarters or never.
Workflow ownership produces sharper product roadmaps. When the workflow is the unit of focus, every feature request gets evaluated against whether it deepens or distracts from the workflow. The roadmap stays focused. Horizontal category-creating products tend to bloat — every feature request looks reasonable in a "platform" frame.
Vertical SaaS is the extreme version of this and it's working. "Vertical SaaS" — products built for a single industry's specific workflows — is increasingly described as the only durable moat in B2B. Horizontal products are getting commoditized; industry-specific tools that own the deep workflow are not. The reason is the same: the workflow is the moat, not the category.
Where This Shows Up in Practice
Pricing pages. Pages that lead with category naming ("the leading AI-native X platform") underperform pages that lead with workflow specificity ("automate weekly QBR prep across your top 50 accounts in 8 minutes"). The second answers a buyer's question. The first announces a brand.
Sales positioning. Reps who pitch "we're a category leader" lose to reps who pitch "we replace the three hours your team spends on X every Monday." The buyer can't evaluate the first claim. The buyer can immediately evaluate the second.
Outbound messaging. Subject lines that name a workflow break through. Subject lines that name a category get filtered. "Re: your QBR prep workflow" outperforms "Re: revenue intelligence" by significant margins on real datasets we've tested.
Investor decks. The category-creation slide reads to current investors as scope. It used to read as ambition. The frame has flipped. Investors now ask "what specific workflow do you own?" before they ask "how big is the category?" The TAM slide is no longer the narrative engine.
Content strategy. Content that goes deep on a workflow ("how to run a QBR for an at-risk enterprise account") cites well in AI engines and converts well on the page. Content that argues for a category ("the rise of revenue intelligence") cites poorly and converts worse.
What to Actually Do About It
Name the workflow you own. Sit down with the founding team and write the workflow in one sentence. "We replace [specific manual work] for [specific role] in [specific tool / context]." If you can't write this sentence in one try, the workflow isn't sharp enough.
Use the buyer's language, not the analyst's. Buyers describe workflows in operational terms — "what I do on Monday morning," "the report I send my CRO every quarter." Analysts describe workflows in framework terms. Buyers don't read analyst reports. Use the buyer's words.
Pressure-test the workflow against the disqualification rule. A workflow is real if some plausible companies don't have it. If "every B2B company has this problem," the workflow is too broad — it's a category in disguise. Narrow until some companies clearly don't qualify.
Drop the manifesto from the home page. Replace it with a statement of the workflow and a demo of the product solving it. Buyers who arrive at your home page in 2026 are not in the mood for a manifesto. They want to confirm in 90 seconds whether you solve their problem.
Structure the content around the workflow. Every blog post, comparison page, integration page, and case study should ladder up to the workflow you own. Disjointed content produces a brand that's hard to summarize. Workflow-anchored content produces a brand that the AI engines summarize for you, in your favor.
Reserve category language for tier-3 use cases. Category language is fine in analyst briefings, IPO prospectuses, and investor pitches at the late stage. It's a liability in early-stage marketing, sales conversations, and content for buyers. Use it where it pays. Skip it where it costs.
The Stakes
The companies that try to create categories from a position of weakness — limited brand, limited budget, limited patience — burn the runway and miss the deals. The companies that name a workflow and own it ruthlessly produce predictable pipeline, faster sales cycles, and sharper product roadmaps. The category, if it ever crystallizes, ends up named after the workflow leaders. Drift didn't lead "conversational marketing"; they led "live chat for B2B." The category came later.
The market won't reward you for naming a category in 2026. It will reward you for owning a workflow buyers can name in their own words. That's a smaller, more concrete, more defensible bet — and it's the bet that's actually closing deals.
Stop trying to create a category. Name the workflow. Own it. The category, if it matters, will be named for you later.