Brand architecture in the brandbook: master brand and sub-brands

What to do before opening the brandbook editor

Architecture cannot be drawn intuitively — first, a portfolio audit is needed, and this is a week- to two-week-long job, not a one-day task. Skipping it, a company gets a brandbook that beautifully describes logos but collapses at the first launch of a new product.

1. Portfolio audit: compile a list of all brands, products and lines, and record which ones generate revenue, which ones — recognition, and which ones exist «by inertia».
2. Defining the role of each brand: selling, protecting reputation, testing a new market, legacy after M&A.
3. Analysis of audience intersections: if two brands compete for the same buyer in the same category — this is a cannibalization signal that architecture should resolve, not hide.
4. Building a decision tree — a set of questions by which any new product automatically gets a status of «expansion», «descriptor», or «sub-brand».
5. Only after that — documenting the chosen model in the brandbook: naming, visual hierarchy, lockups, rules for adding and removing brands from the portfolio.

How to tell: sub-brand or just a descriptor

The mistake that most teams make is creating a new subbrand for each significant launch. In practice, this disperses the marketing budget: according to portfolio management studies, a focused approach allows reducing marketing costs by 20% with more efficient resource allocation, as each individual brand requires its own minimum threshold of investments in recognizability. Before creating a new name, the brandbook should compel the team to answer specific questions.

If at least two of these criteria indicate a 'subbrand' — a launch protocol for it must be ready in the brandbook: a unique name, a separate visual system, a clear rule, and whether the master brand is visible in communication at all.

Visual hierarchy and lockups for each model

This section of the brandbook is almost always written too generally — 'the subbrand logo combines harmoniously with the master brand.' Such a formulation solves nothing in practice. Precise rules are needed: size, position, minimum margin, cases when the master brand label is completely removed.

Boeing — a vivid counterexample of what happens when a monolithic architecture is applied without risk isolation: the crisis with 737 MAX did not hit a separate product line, but the entire brand, crashing stock prices and company reputation as a whole. That is why in the brandbook for Branded House a separate section on acceptable risk level is mandatory — if the product category is potentially dangerous to reputation, the monolithic model is not suitable at all, regardless of the visual system's aesthetic appeal.

Roles of brands in the portfolio and their place in the hierarchy

Brandbook rarely links visual hierarchy with the business role of the brand, and it's a pity — this is the direct reason why the system has to be redrawn after a couple of years. The logic of the BCG matrix works here literally: 'stars' and 'problem children' get priority placement in the brandbook navigation, a larger logo in the portfolio master table, and a separate section with guidelines. 'Cash cows' are fixed as stable — for them the rules are maximally strict and unchangeable, because the task is not to develop, but not to ruin what works. 'Dogs' brandbook must explicitly mark as candidates for merger with another brand or exit from the portfolio, otherwise the team continues to support the visual identity of the brand that has long ceased to be beneficial.

• Star — high priority of resources, a separate block of guidelines, permission to customize the visual system.
• Cash cow — stable role, minimal changes, fixed rules without the right to experiment.
• Problem child — test status, simplified lockup, mandatory role review once a year.
• Dog — 'exceptional' marking, description of the rebranding or merger process with another brand in the portfolio.

Organizational principles that sustain growth

A portfolio designed for the current size of the company breaks down at the first scaling. The brandbook must explicitly fix the principle according to which the architecture is organized — otherwise each new market or product will be added chaotically.

• By audience — separation of consumer and enterprise lines, different visual tones for B2C and B2B under a common master brand.
• By categories — product lines with their own color codes within a unified system, like those of industrial conglomerates.
• By geography — regional adaptations of the name or visual style while preserving the root identity.
• By platform or technology — a common recognizable technology that consumers identify regardless of the product (similar to 'Intel Inside').

Choosing the principle is not a decorative matter. It determines where exactly the new brand will be placed in the brandbook in three years: will it get its own guideline page or be embedded into an existing category table without a single new rule.

Four architecture models — the base, without which a decision tree cannot be built

Before documenting hybrid solutions, it is necessary to clearly understand the four basic models, because almost all real companies are their combinations, not pure forms

Hybrid models and governance rules within the brandbook

Pure models occur less frequently than is commonly thought in theoretical articles. Marriott is a classic hybrid: Courtyard by Marriott uses an explicit connection with the parent brand, while Sheraton and Westin exist in the portfolio as independent names without visible ties in consumer communication. This is not inconsistency, but a conscious governance decision — different segments and price categories require different degrees of proximity to the master brand

To prevent the hybrid from turning into chaos, a brandbook should contain not a description of the current portfolio state, but a working tool — a decision tree with clear branches: audience segment → risk level → price category → final brand status. And a separate block of governance rules, answering a question that is barely present in public materials: how to remove a subbrand from the system. Usually, this involves three steps — merging with the closest brand by audience, gradual rebranding through a transitional lockup over 12-18 months, and complete removal of the old name from all touchpoints, including legal documents and packaging of remaining product batches. Without this section, brand architecture is beautifully described once and never updated to follow real changes in the portfolio.