Brand architecture: monobrand, subbrands and portfolio

Brand architecture and portfolio strategy are not the same

These two terms are constantly confused, although the difference is fundamental. Brand architecture answers the question 'how brands are related to each other visually, verbally and structurally' — who is under whom, who is independent, who simply uses the parent name as a quality stamp. Portfolio strategy is a managerial and financial decision about which brands to keep in business, which to buy, which to close, and where to invest money. Architecture is form. Portfolio is content and business logic.

It is possible to have a perfect architecture and a failing portfolio — for example, a beautifully structured subbrand lineup, half of which does not generate profit. And vice versa: a strong portfolio of profitable assets may suffer from chaotic architecture, when the consumer does not understand who the manufacturer is and why the brands are named differently. McKinsey's research showed that companies that properly structured the portfolio approach — that is, the distribution of resources between assets, not only their visual linkage — increased revenue growth by 2–5 times and saved up to 20% of the marketing budget. Architecture without portfolio logic is simply design.

Four basic types of architecture

How to choose the architecture: step-by-step analysis, not intuition

Most articles on this topic explain how the architecture looks, but do not provide a tool for selection. In practice, decisions are made based on specific metrics, not the feeling 'we like this better.'

1. Calculate the overlap of audiences between products. If more than 70% of customers of one product are potential customers of another, monobrand reduces promotion costs and works more efficiently.
2. Compare price positions. If the difference between products exceeds 3–5 times in price, a single brand begins to confuse the perception of quality — a subbrand or separate brand is needed here.
3. Assess the reputational risk. If the failure of one product can drag down the entire product line (as happened with Samsung Galaxy Note 7, damaging the entire Samsung brand's image), it is advisable to separate responsibility through a house brand or at least a supported architecture.
4. Check the cost of building a brand from scratch. A separate brand means a separate website, SEO promotion, an app, and a media budget. For a growing company, this is an expensive luxury.
5. Look at regulatory and cultural barriers of markets. If a brand is entering a country where the name sounds bad or conflicts with local norms, a subbrand or a separate name is justified even within a single company.

If, after this analysis, most answers point in one direction — the decision is usually obvious. Problems arise when a company grows faster than it can recalculate these parameters.

Hybrid architecture is not a compromise, but a working model

In most materials, the hybrid is described as an 'intermediate variant between extremes,' which is unfair: for many large companies, this is a conscious and sustainable strategy, not a temporary solution. Marriott is a good example: Courtyard by Marriott and the Marriott Bonvoy program clearly bear the name of the parent company, while Sheraton and Westin operate as fully independent brands without mentioning Marriott in their communications. This allows simultaneously protecting the reputation of the flagship brand and covering segments where the Marriott name is excessive or unnecessary.

Nestlé uses a similar but different mechanism — a supported brand. Nescafé and Nesquik have their own visual identity and advertising campaigns, but the Nestlé name appears as a quality mark, usually in small print on the packaging. This is cheaper than building completely independent brands from scratch, and more effective than a pure monobrand, because it doesn't mix products with different audiences under one name. P&G went further and manages 43 brands, including Head & Shoulders, Eukanuba and Max Factor — most consumers don't even realize these are all from the same company. Such an architecture protects each brand from reputation issues of its neighbors, but requires a separate budget for promoting each name.

Brand cannibalization: the cause is not in the name

The key mistake in understanding cannibalization is looking for its source in similar brand names. In fact, cannibalization usually arises from product function similarities, not names. Two brands with completely different names will compete with each other within one portfolio if they solve the same task for the same buyer at a similar price.

From this practical conclusion: control over functional product differentiation is more important than working on name uniqueness. Before launching a new brand or sub-brand, it's worth building a simple 'price × need' matrix and checking whether the new product falls into the same cell as an already occupied portfolio asset. If it does — the problem won't be solved by renaming, only a review of the function set or target segment will help.

• Check products based on the problem they solve for the client, not on marketing positioning.
• Develop brands across different entry points: price, sales channel, usage moment.
• Introduce a single portfolio owner who monitors feature intersections between brands before launch, not after sales drop.

Digitalization is changing the economics of architecture choice.

This factor is rarely examined in detail, yet it increasingly decides the question faster than strategic considerations. Every additional brand in the portfolio is a separate website, separate SEO promotion from scratch, a separate mobile application, and a separate advertising budget for reach. For a well-established conglomerate like P&G, this is managed cost. For a growing company, it is often an unaffordable luxury that blurs the already limited marketing budget between several digital presences instead of concentrating the weight of one domain and one reputation in search.

That is exactly why many fast-growing brands in the digital environment lean toward monobrand or supported architecture: the accumulated SEO weight, trust in search engines, and volume of content work for one name, not scattered among several. This is not an absolute rule, but a substantial argument that should be considered on par with classic Aaker criteria.

Typical mistakes and how to spot them early

The failure of Samsung Galaxy Note 7 showed the main risk of monobranding: the failure of one product struck the perception of the entire Samsung lineup, including smartphones and household appliances completely unrelated to the problem. United Airlines experienced a serious reputational crisis in 2017 year, but thanks to the brand architecture within the holding, it did not affect other airlines in the group — this is a direct illustration of why brands should be separated at all.

Common mistakes in building architecture look almost identical across different companies:

• Launching a new brand solely for marketing effect, without analyzing audience overlap and functions with existing products.
• Lack of a single owner of the architecture—decisions are made at the level of individual product teams, and the portfolio structure expands organically.
• Ignoring the cost of digital presence when launching a new sub-brand or individual name.
• Renaming a product as a way to 'solve' cannibalization instead of reviewing its functions or segment.

These problems can be identified at an early stage if, on a regular basis, at least once a year, the portfolio is run through the same five questions from the architecture selection section above—audience overlap, price difference, reputational risk, cost of digital promotion, and barriers to entering markets. As soon as the answers to two or more questions change, it is time to review the architecture, without waiting for sales to drop or a reputational crisis to occur.