Apple sells a product called the iPhone. Apple does not sell a product called the Apple iPhone Pro 17, although that is sometimes how it is referred to in writing. The relationship between the parent brand and the product brand is deliberate, structured and consistent. It is also doing strategic work that most teams underestimate when they name a new product.
A surprising number of product naming projects start with the question “what should we call this new product?” That is the wrong first question. The right first question is “what relationship should this product have with our existing brand?” The answer to that question shapes everything about the name. Get the architecture decision right and the naming work becomes much faster. Get it wrong and the new product will fight the parent brand for years.
Four architectures, in plain language
There are four common ways to organise the relationship between a parent brand and a product. Each one asks something different of the product name.
Monolithic. The parent brand carries everything. Products are named descriptively, often with model numbers or short generic descriptors. Think of how a single big-tech company might call its products “Watch,” “Pencil,” “TV,” “Maps.” The parent brand does most of the strategic work. The product name only needs to identify the product clearly within the family.
Endorsed. The product has its own name, but the parent brand sits beside it as a visible endorsement. “Tide by Procter and Gamble” is a classic, simplified example. The product name carries its own meaning and equity. The parent brand provides backing. Both names need to work together without competing.
Sub-brand. The product has a strong, independent name that is clearly part of the parent’s family but operates with significant autonomy. Microsoft Xbox is a sub-brand example. The Xbox identity stands on its own in the marketplace, but its relationship to Microsoft is acknowledged in particular contexts.
Freestanding. The product has its own name with no visible connection to the parent brand. The parent brand exists, but it is invisible to most consumers. Many consumer goods companies operate this way. The product is the brand the customer sees.
Each architecture has a specific job. A monolithic system concentrates brand investment in one place and benefits the parent. A freestanding system protects the parent from product-specific risks and lets each brand develop its own audience. Endorsed and sub-brand systems try to balance the two.
The point is that the architecture decision is strategic, not aesthetic. It determines what the product name is for.
What each architecture asks of the name
A monolithic product name has the easiest job. The brand has already done the work. The product name has to be clear, short, easy to say and easy to fit into a category list. Adjectives, descriptors and model numbers are fine. Distinctiveness is not the priority because the parent brand is doing the differentiation.
An endorsed product name has to carry its own meaning while not competing with the parent. The endorsement only works if the product brand is strong enough to stand without it but flexible enough to sit alongside it. This is harder than it looks. Many endorsed brands lean too heavily on the parent and never develop their own identity, which means the endorsement was structurally pointless.
A sub-brand name has to feel like family without being absorbed. The most successful sub-brand names share an underlying sensibility with the parent, often a sound, a tone, a structural quality, even if the specific words are completely different. They can be lifted into the parent ecosystem when needed and operate independently when needed.
A freestanding product name has the heaviest job. It has to do everything a company name has to do, because to most customers it is a company name. Strategic positioning, distinctiveness, memorability, defensibility, future-fit. No backstop from the parent. This is why freestanding product naming is often a more involved project than a parent company naming, even though it looks smaller from the outside.
The descriptor question
A practical decision that comes up in almost every product naming project. Should the product name include a descriptor, or stand alone?
A descriptor is the part of the name that tells you what the product does. “Adobe Premiere Pro” includes a descriptor. So does “Microsoft Excel for Business” or “Air Force One.” A standalone name does not. “Tide” does not tell you what it is. Neither does “Niko” or “Octo.”
Descriptors solve a specific problem. They reduce the work the customer has to do to understand what the product is. They are useful when the product category is unfamiliar, when the parent brand is well-known but the product is new, or when the audience is sceptical or low-attention.
Descriptors also create a specific problem. They limit the future of the product. A name with a descriptor in it can be hard to extend when the product evolves. “Outdoor Camping Gear” is fine until the brand wants to be in urban performance wear. “Realm” can become anything the brand wants it to be.
The decision usually comes down to confidence in the parent brand and ambition for the product. High parent brand confidence and modest product ambition: descriptors are fine. Lower parent brand confidence or larger product ambition: a standalone name will earn its keep over time.
The sub-brand trap
There is one specific failure pattern we see often enough to call out. A team launches a sub-brand and gives it a name that competes with the parent rather than supporting it.
The most common version. A successful company names a major new product line with a name that is so strong, so distinctive and so well-marketed that within three years the customer thinks of the sub-brand as a separate company. The parent brand becomes a footnote. The strategic logic of the sub-brand, which was to use the parent’s equity to launch the new product faster, has been quietly inverted. The parent is now relying on the sub-brand for relevance.
Sometimes this is fine. The strategy may have evolved. The sub-brand may genuinely be the new flagship. But often, this pattern is the result of nobody having decided in advance how independent the sub-brand should become. The product naming was treated as a creative exercise rather than a strategic one, and the brand architecture was not protected.
The corrective is upstream of the name. Decide what the sub-brand is for. Decide how much independence it needs, and where the line is. Then choose a name that fits that decision. The brief for a sub-brand that is meant to remain visibly part of the parent family is different from the brief for one that is being prepared for partial independence. The same name can fit one brief and break the other.
A real-world parallel
Octo is a useful example to consider. The business is a consolidation of multiple industrial service organisations under one new brand. The naming decision was not only about what the unified entity should be called. It was about how each of the previous businesses would relate to the new parent.
The architecture chosen was a sub-brand approach with the new parent as the unifier. Each of the previous specialist businesses retains visibility for the audiences that already knew it, while the parent Octo brand carries the consolidated identity and the future growth. The name Octo had to do several things at once. It had to feel modern and confident enough to act as the umbrella. It had to be distinctive in the relevant categories. It had to have headroom for additional businesses to join the family. And it had to leave space for each sub-brand to retain its own personality.
The naming question was structurally similar to a product-within-a-brand problem. The new entity sits above the operating businesses. The strategic logic is the same. The architecture decision had to come first. The name came as a consequence of that decision, not the other way around.
The same logic applies whether the parent is a holding entity, a company brand or a product portfolio. The architecture frames the naming. The naming expresses the architecture.
A simple sequence for product naming projects
If you are about to name a new product, the sequence below will save time and avoid the typical traps.
One. Architecture. Decide where this product sits in the family. Monolithic, endorsed, sub-brand or freestanding. The answer is determined by where you want the brand investment to concentrate, how independent the product needs to be, and how much risk you want to keep at the parent level.
Two. Brief. Write a one-page brief that says what the product is, who it is for, what it needs to achieve and what relationship it should have with the parent brand. This brief is what you judge candidates against. Without it, you will judge by preference.
Three. Territories. Identify the strategic naming territories that fit the brief and the architecture. A monolithic product name lives in a different territory from a freestanding one. Be specific.
Four. Names. Generate candidates against the territories, not against the void. This is where most product naming projects come unstuck. The names are produced first and the territories are invented to justify them. The order matters.
Five. Assessment. Score against criteria including strategic fit, distinctiveness, parent-fit and future-fit. Parent-fit is the criterion that often gets missed. A product name that is strong on its own but inconsistent with the parent brand is a problem you do not see until the launch.
Six. Decision. The decision is informed by the assessment but made by the people responsible for the brand strategy. The naming process produces the conditions for a good decision. It does not make the decision automatically. That has to be a leadership call, and the decision report should be specific enough to defend.
The decision you can defend
Product naming sits inside a strategic conversation that most teams do not have early enough. The names you can choose from are constrained by the architecture you are committing to. Get the architecture decision right and the naming becomes lighter, faster and easier to defend. Get it wrong and the new product will spend years pulling against the brand that launched it.
If you are about to name a new product, the most useful thing you can do is take an afternoon to clarify the architecture decision before any names are produced. The conversation may not be glamorous. The names will be better, the launch will be cleaner and the long-term position of the brand will be stronger. Architecture is the strategy. Naming is the expression. The order matters.
Re:name’s Guided Strategic Naming process includes a project-type intake that distinguishes product, sub-brand and freestanding naming work from the start. The naming territories you generate against are appropriate to the architecture you are committing to, so the candidates you assess are strategically aligned before any creative judgement happens.