At a dinner party, someone announces they have invented a new way to eat breakfast. The table waits. “It’s a bowl,” they say, “but with ingredients.” Everyone nods, relieved to have found the cupboard where the idea belongs.
Businesses launching new products can make a similar mistake. They describe the invention as if a buyer has no familiar reference point, then wonder why visitors cannot explain it. Before claiming to create a new category, name the job or familiar category the product relates to. Then show the difference that matters.
Start with the job the customer already recognizes
Ask potential buyers what they do today when the problem occurs. Do they use a spreadsheet, hire a consultant, combine several tools, ask a colleague, or ignore the task? Their current workaround reveals the category through behavior, even if no one uses the company’s chosen label.
Interview people who have recently experienced the problem. Ask when it happens, what they try first, what is frustrating about the current approach, and how they know the job is done. Avoid asking whether they like your idea before they understand it. Early enthusiasm can be polite or hypothetical.
Use their language to establish an anchor: “a planning tool for…” or “a service that helps teams…” This is not a permanent positioning decision. It is a starting explanation that lets a buyer orient themselves.
Explain what is different in observable terms
After the familiar category, describe the difference. Is the product designed for a particular user, works with a different kind of data, reduces a manual step, offers a new workflow, or changes who can complete the job? Choose a distinction that users can observe or verify, not merely a label like “next-generation.”
Then show how the difference affects the customer’s task. A feature is not inherently valuable because it is novel. Explain which step becomes possible, faster, clearer, or less risky, and under what conditions. If the product does not yet do that reliably, call it an early capability rather than a dependable outcome.
Do not invent a category because the old one feels crowded
A new category can help if customer needs genuinely differ and buyers need a new way to compare options. But a new label can also add cognitive work. If a visitor has to learn the category before understanding the product, the page may be asking for too much too soon.
Try three explanations: a familiar-category version, a hybrid version that names the category and difference, and a fully new label. Ask people to paraphrase each and say what they expect the product to do. Do not ask which phrase sounds most impressive. The useful evidence is what they understand and what they still wonder.
GOV.UK’s service guidance recommends describing user needs in language people recognize. That offers a grounded principle for category explanations, though public-service guidance is not commercial evidence of conversion effects. User-needs guidance.
Give the buyer a concrete example
Use a short scenario that shows the task before and after, but label it accurately. If it is hypothetical, say so. If it comes from a customer, obtain permission and provide context. A screenshot, sample workflow, or demo can make the category tangible, but it should show what a user can actually do today.
Explain limitations as well. Which data sources are required? What does the product not replace? What skill or setup is needed? A trustworthy category story includes the boundaries that help a buyer decide whether the product fits.
Test the explanation at more than one stage
First, test comprehension with people who resemble the intended user. Can they describe the category and who should care? Next, test the product with a realistic task. Does the experience deliver what the explanation led them to expect? Then look at behavior: do the right users return, complete a core action, and recommend it for the intended job?
These are separate tests. A clear explanation can increase signups without improving retention. A useful product can still be described poorly. A new category may be understood but lack sufficient demand or budget. Track the stages rather than treating visits or waitlist growth as proof of product-market fit.
An Indie Hackers founder described a launch where visitors could not tell what the product did quickly. The post illustrates the value of checking comprehension, but it cannot prove the product’s category or demand. Founder discussion.
Build the category into the site without jargon
Use the familiar category in the headline or opening sentence. Explain the distinctive capability next. Organize pages around users, use cases, or decisions people already recognize. Put technical details lower on the page for buyers who need them, with definitions where terminology is unavoidable.
Keep naming consistent across the website, product interface, pitch deck, and customer support. If a feature changes category depending on the channel, buyers may suspect the offer itself is unstable. Give the sales team a concise explanation and invite them to capture the phrases prospects use in response.
Know when the category is truly changing
A new category story may be warranted when customers have a new job, a familiar comparison fails to explain the product, and the business can demonstrate a meaningful difference. Even then, teach the category through useful examples over time. Do not rely on a coined term to do the teaching by itself.
If prospects understand the familiar category and see no reason to switch, the challenge may be differentiation or value rather than naming. If they understand the difference but do not need it, revisit the audience or product. If the team cannot agree on the job, conduct more research before creating a category manifesto.
Make novelty easier to understand
The buyer should not need to applaud the invention before knowing what it does. Give them a familiar handle, show the change, and let actual use establish whether the difference matters. If the category is genuinely new, understanding is the first milestone; adoption is a separate one.