Company names, product names, and the difference that changes everything

A company name and a product name are developed through the same naming process: analysis, strategy, creation, evaluation, and trademark protection. What differs is not the method, but the reach. A company name must carry an entire business: across decades, across markets, and across product cycles. A product name can be tighter, more specific, and quicker to understand. And a technology name often falls somewhere in between: too technical for marketing, too marketing-oriented for the development department.

Anyone who underestimates this difference will pay the price. Not right away, but at least when the name no longer fits and making a change ends up costing more than the original development.

When I ask my clients which decision in their company has the longest-lasting impact, “the name” is not often mentioned. But that is exactly what it is. A company name appears on contracts, in business registries, and on buildings. It is cited in press releases, used by employees, and recommended by customers. Or not.

In my experience, the biggest challenge when it comes to company names isn’t creativity. It’s long-term thinking. A company name needs to be open enough for growth, and at the same time, precise enough to work today. It shouldn’t describe what the company is currently doing, because that can change. It must convey what the company stands for.

This has implications for trademark protection. Company names are generally protected broadly: across multiple trademark classes and in multiple countries. Descriptive or generic terms are difficult to enforce under trademark law. For this reason, company names are often more abstract than product names: associative, symbolic, or artificial.

This confuses some customers at first; they would prefer something that’s easy to understand. But things that are easy to understand are often hard to protect. And what you can’t protect isn’t really yours.

What it feels like to change a company name after 23 years—and why the old name was still the right choice. You can read the story behind atares’ name change here or listen to it as a podcast episode.

Product names offer a different kind of freedom, and in the naming team we enjoy this freedom in our creative work. Product names can be more focused on benefits, more concrete, and more direct. A product name can convey a feature, refer to a technology, or appeal to a target audience. It doesn’t have to represent the entire company; it has to sell the product.

This often makes product naming easier during the creative process. But it complicates the evaluation process. This is because product names never stand alone. They exist within a portfolio, among other product names, under a corporate brand. They must fit in without getting lost in the crowd or dominating the space; they must stand out without disrupting the system.

What I see regularly: Companies come up with product names in isolation. A name for this product, a name for that one. Without tying them to a naming strategy, without looking at the overall portfolio. That works for the first product, and maybe the second. By the third, things start to get confusing. By the fifth, it’s chaos.

How a functional briefing turned into a strong product name: The story behind DARCO Movilo—from the blue-footed booby to a brand name. Read the full story on our blog or listen to the podcast on Spotify.

I come across technology names all the time in B2B and industrial projects. And the story is almost always the same: engineers and developers name their technologies internally using acronyms, project codes, or functional descriptions. These working titles stick. Eventually, they end up in sales presentations, then on the website, then in the proposal. And suddenly, an internal code name becomes a brand name—without review, without protection, without strategic alignment.

I call this the “creeping brand.” It doesn’t arise from a conscious decision, but from habit. And getting rid of it takes more effort than it would have taken to use the proper name from the start.

A good technology name finds the right balance between technical jargon and accessibility. It must hold up in an engineering context and work in marketing. Descriptive terms are rarely helpful here: they’re too generic to be protected and too replaceable to be distinctive.

Before I start the creative process, I go over three questions with the client. They may sound simple, but they set the overall direction.

A company name should last for decades. A product name, on the other hand, may be tied to a product cycle: three, five, or ten years. Its expected lifespan determines how broad or specific the name can be.

A company name must work internationally, across industries, and across all touchpoints. A product name must work in its target markets and with its target audiences. These impose different requirements in terms of pronunciation, transcription, and cultural compatibility.

A standalone product name requires different criteria than a name that is part of a naming architecture. Within the system, what matters is recognizability, scalability, and structural consistency. On its own, what matters is distinctiveness.

It sounds obvious, but I see it in almost every second initial meeting: the client treats a company name like a product name or the other way around. A founder who chooses a company name that’s too specific, too descriptive, too closely tied to the current product offering. A product manager who expects a product name to represent the entire company.

The process of naming companies and products follows the same professional approach. However, the briefing, the weighting of criteria, and the creative approach differ fundamentally. Recognizing this helps to avoid the most costly of all naming mistakes: the wrong name in the right place.

Are you trying to choose a name and unsure about the requirements? We’ll help you to ask the right questions before the creative process begins.