Name the company, product, or both.
The question is not really about typography but about architecture: do you want to build a common roof or several separate units?
This decision pertains to brand architecture, not name creation. If resources are limited and product lines share the same spirit and target audience, focus on one company name to consolidate communication power. Only assign separate product names when the line targets a distinctly different audience, operates in a different price segment, or needs to isolate reputational risks from the parent company.
- Limited resources, products with the same spirit and customer base
- line targets a completely different customer segment or price range
- Want a guarantee from the parent name for the sub-brand.
- give unique names to every small product, diluting resources
- name products without considering the brand architecture beforehand
When clients ask Sinh Vũ, "What should I name it?", the question often hides a larger unresolved issue: naming what, and where does that fit within the entire structure of your brand. Skipping this step means you will name it and then have to rename it, or by the third line, things will start to get confusing.
Foundational question: architecture first, typography second.
Brand architecture is how you organize brands, product lines, and names within a single business, determining which ones borrow credibility from others and which stand alone. According to Wally Olins, most businesses fall into three main architectural types:
- Branded house: One parent name covers everything, with all product lines sharing the same name and identity.
- Endorsed brand: each line has its own name, but the parent company stands behind it to guarantee credibility.
- House of brands: each line is completely independent, and customers often do not know they are under the same ownership.
Choosing architecture is not the creative department's job. It is a business decision, as it determines how you will allocate your communication budget for many years to come.
When to consolidate into one name, when to separate
Three common mistakes when naming
- Set unique names for every small product: each SKU (individual product unit) with a different name is the quickest way for none to be strong enough. Resources are diluted, and customers do not remember.
- Set names before having a structure: by the third line, you realize the three names have nothing in common, forcing you to start over.
- Confusing internal names with commercial names: Technical names or internal codes sometimes leak out as customer-facing names. The commercial name should be decided proactively, not just a convenient name given during project setup.
Sinh Vũ's viewpoint
Sinh Vũ always asks architectural questions before textual questions. How many lines will you have in the next three years? Are they in the same file or different files? Which lines borrow credibility from which, or does each line stand alone?
In corporate language system projects, Sinh Vũ builds a naming architecture for multiple brands simultaneously and establishes conventions, which are a set of rules regarding suffixes, prefixes, and name structures, so that when launching a fourth or fifth new line, the internal team can name correctly without needing to start from scratch.
For chains, Sinh Vũ also establishes naming conventions for lower levels such as dish names, branch names, and combo names, so that when expanding to ten or twenty points of sale, the entire system still communicates in a unified voice.
Adding another name means taking on another brand to nurture. You should only separate if the benefits of doing so outweigh the costs of resource dispersion.
The principle of brand architecture, Sinh Vũ.
If you are in the early stage with a single product: name your company well, so it also serves as the commercial brand. Only revisit the architecture when the second line is different enough to require a separate name.
Decision checklist
Topic: Should you name the company, the product, or both? Sinh Vũ guide, sinhvu.com
Select each item you find appropriate, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
References
Wally Olins, Brand Architecture; Lexicon Branding, Corporate Naming: A Strategic Guide; Sinh Vũ's practical experience through corporate language system projects and chains.
Frequently asked questions
For a newly launched startup, should the company name be established before the product name?
If there is only one product or a single line, let the company name also serve as the trade name. Separate them from the beginning when resources are thin, as it only adds to the burden of maintaining the brand without any benefit. When you introduce a second line that is distinctly different, then it is time to reconsider the architecture.
Does naming each product help sell better?
Not necessarily. A separate name only helps when that line needs a completely different personality from the parent company or needs to separate risks. Conversely, if you give a separate name to every small product, the communication resources become dispersed, and no name is strong enough for customers to remember.
My company already has a name, but now we want to launch a new line. How should we name it?
First, determine if the new line shares the same customer base and spirit as the existing name. If so, using the company name along with a descriptive line name is sufficient. If it is significantly different, consider a guarantee model: the new line name stands first, with the parent company name following in smaller text to borrow credibility without complete uniformity.