Building a Narrative Around a New Product Category

A product without a category is a product the market has nowhere to file. When a prospect can’t answer “what kind of thing is this” in one sentence, they default to comparing it against whatever it superficially resembles — and if that comparison is unflattering or just wrong, you’ve lost the framing before you ever got to make your actual pitch. Building a category narrative is the work of giving the market a new mental shelf to put you on, before someone else defines that shelf for you, badly.

Name the enemy before you name the category

Every durable category narrative has an antagonist — not a competitor, but an old way of doing things that the new category exists to replace. Salesforce didn’t just introduce “CRM software”; the early narrative was explicitly against paper Rolodexes and disconnected spreadsheets. The category name is secondary to the enemy; the enemy is what makes the category emotionally legible.

Before naming anything, get specific about what the old way actually costs people, in their own language:

• What are they currently duct-taping together to solve this problem, and what does that cost them in hours, errors, or missed opportunities?
• What have they been told is “just how it works” that isn’t actually true anymore, now that your product exists?
• What’s the moment someone hits the wall of the old approach — the specific trigger event that makes them start looking for something else?

A category narrative built around a vague antagonist (“inefficiency,” “manual work”) doesn’t land. One built around a specific, visceral old-way pain (“the Tuesday-night spreadsheet reconciliation that takes three hours and is wrong half the time anyway”) gives people something to actually feel.

Resist the “like X, but for Y” framing longer than feels comfortable

It’s tempting to explain a new category by anchoring to something familiar — “it’s like Uber, but for dog walking.” This shortcut works for explaining a business model quickly, but it actively undermines category creation, because it tells the market you’re a variant of an existing category rather than something genuinely new. Once the market files you under the anchor category, you inherit that category’s price expectations, feature expectations, and competitive set — most of which don’t actually apply to you.

The discipline is using the analogy privately, internally, to align your own team on the shape of the idea, while building external messaging that stands on its own without leaning on someone else’s category name. If your product only ever gets explained in reference to something else, you haven’t built a category — you’ve built a niche inside someone else’s.

There’s a real cost to getting this wrong that shows up months later, not immediately: sales cycles that keep getting benchmarked against the anchor category’s pricing (“why does this cost more than [the thing you compared yourself to]”), feature comparisons against a competitive set that never actually competes for the same buyer, and analysts who, once they’ve written you up as “a flavor of X,” rarely revisit that categorization even after your product has clearly outgrown it. Correcting a category assignment after the market has already made it is dramatically harder than avoiding the assignment in the first place.

A category needs a point of view about the future, not just a product description

Category narratives that stick tend to make a claim about where the world is headed, not just what the product does today. “The way teams will collaborate is changing from documents to canvases” is a category claim. “Our tool has a canvas view” is a feature description. The former gives analysts, press, and prospects a bigger idea to repeat and build on; the latter is forgettable the moment someone closes the tab.

This point of view needs to be falsifiable and specific enough to be interesting, not so vague it could apply to any product in any category. “The future is more efficient” says nothing. “The next generation of [function] will be event-driven instead of batch-processed, because [specific reason tied to a real shift in the underlying environment]” gives people something to agree or disagree with — and disagreement is often how a narrative first gets attention.

Where founders overcorrect: manifesto without mechanism

A common failure mode on the other side of the vague-antagonist problem is the opposite one: a bold, well-written point of view about the future that never connects back to a concrete mechanism for how the product actually delivers on it. “Documents are dead, canvases are the future” is a compelling sentence, but if the only evidence offered is the sentence itself, sophisticated buyers and analysts read it as marketing copy rather than a real market thesis.

The fix is pairing every future-facing claim with a mechanism — the specific technical, workflow, or economic shift that makes the claim true now when it wasn’t true five years ago. Not “collaboration is changing,” but “collaboration is changing because real-time multiplayer editing infrastructure only became reliable enough for non-technical teams in the last two years, which is why the canvas model wasn’t viable as a default before now, and is a viable default today.” The mechanism is what separates a category thesis from a slogan, and it’s usually the difference between an analyst taking a briefing seriously and filing it as a pitch.

Build proof before you build volume

A category narrative without customer proof reads as a hypothesis, no matter how well-written the manifesto is. Before pushing a category narrative broadly, get a small number of customers who’ve actually experienced the new-category outcome and can describe it in their own words, unprompted. Three specific, credible customer stories that independently describe the same shift in their own language do more to validate a category claim than any amount of founder-authored thought leadership.

Sequence it: narrow proof first (a handful of case studies with real numbers), then narrative amplification second (content, analyst conversations, conference talks). Reversed, you get a narrative that sounds compelling but collapses the first time a skeptical prospect asks “who’s actually doing this today.”

A useful bar for “real numbers” in that first wave of proof: a customer quote alone (“this changed how we work”) is weak evidence; a customer quote attached to a specific, checkable metric (“we cut reconciliation time from three hours a week to twenty minutes, verified against our own timesheets”) is strong evidence, because it survives a skeptical prospect’s follow-up questions. If your early case studies can’t survive a prospect asking “how did you measure that,” the proof stage isn’t actually finished yet, whatever the narrative timeline says.

Give analysts and press a term, not just a story

If you want a category name to spread beyond your own marketing channels, it needs to be usable by other people — short, memorable, and specific enough that a journalist or analyst can drop it into a sentence without having to explain it from scratch every time. Vague or overly clever category names die quietly because nobody else wants to be the one who has to define them for their audience.

Test candidate category names against a simple bar: can someone who’s never heard of your company use the term correctly in a sentence after hearing it once? If the name requires a paragraph of explanation every time it’s used, it’s not a category name yet — it’s still a slogan.

Expect the category to attract competitors, and treat that as validation, not threat

The moment a category narrative starts working, competitors will begin describing themselves in similar terms — sometimes explicitly borrowing your language. This is uncomfortable but it’s actually a sign the category is taking hold; a category with only one company in it isn’t a category, it’s a product. The strategic move isn’t to fight this, it’s to make sure you’re positioned as the origin and the clearest articulation of the category when it does expand, which is why the proof-and-narrative sequencing above matters — being first to say something is far less durable than being first to prove it.

How to sequence the actual rollout

Category narrative work tends to fail when teams try to do all of it simultaneously — naming, proof, press, analyst outreach — in the same quarter. A more durable sequence:

1. Internally align on the enemy and the future claim first, using the anchor analogy privately to make sure the whole team (not just marketing) can articulate the idea the same way. If sales, product, and marketing describe the category differently in the same week, external audiences will notice the inconsistency faster than internal teams expect.
2. Get three to five proof points before any public narrative push — this is the stage most teams try to skip because it’s slow and unglamorous compared to writing the manifesto.
3. Test the category name and framing in live sales conversations before committing to it in permanent collateral (website, pitch deck, press materials). A name that reads well in a blog post can still land flat or confusing the first time a rep says it out loud to a skeptical buyer — sales conversations surface that fast.
4. Only then go to press and analysts, armed with proof and a name that’s already survived real conversations, not a name that’s untested outside the marketing team’s own meetings.

Measuring whether the category narrative is actually working

Category creation is slow enough that teams can convince themselves it’s working based on internal enthusiasm alone. A few concrete signals to check instead:

• Prospects using your category term unprompted on discovery calls, before a rep has introduced it — this is the clearest sign the language is spreading beyond your own channels
• Competitors adopting similar language in their own positioning, which, as above, is a lagging but real indicator the category is taking hold
• Analysts referencing the category (not just your company) in reports covering the broader space, which signals the category has escaped being synonymous with a single vendor
• Sales cycles where prospects stop comparing you primarily to the old-way incumbents and instead compare you to other category entrants — a sign the market has actually re-filed you onto the new shelf rather than the old one

Revisit the narrative as the market’s understanding shifts

A category narrative built for a market that’s never heard of the problem looks very different from one built eighteen months later, once dozens of companies are using similar language and prospects have basic category literacy. The early narrative needs to do more foundational education — naming the old way, making the case that things need to change. The later narrative can assume category awareness and instead focus on differentiation within it. Companies that keep running the “educate the market that this category exists” narrative long after the market already understands it sound out of step with a conversation that’s moved past them — revisit the narrative at least annually and check it against how prospects are actually talking about the space in sales calls, not just how your own team remembers first pitching it.