Sub-Brand Architecture: How to Run Six Brands Under One Parent
Most groups confuse multi-brand with multi-logo. Real architecture is about which decisions belong to the parent and which belong to the sub-brand.
Most companies that talk about "multi-brand" actually have multi-logo. They've drawn five marks for five products and called it a portfolio. There's no architecture — just five things stacked.
Real sub-brand architecture is a decision framework, not a design exercise. It answers one question per asset: does this belong to the parent or to the sub-brand? Color palette? Voice? Pricing presentation? Lead-capture flow? Each one belongs somewhere — and where it belongs decides whether the system holds or fragments.
I built one for a group with six sub-brands across two markets — UAE and KSA, B2B and B2G. The framework that worked had three layers. The parent owned the spine: master color, type, and tone. The sub-brand owned the personality: accent palette, mark, and voice. The product owned the deliverable rules: deck templates, social formats, lead-form structures.
This three-layer split made everything else solvable. New sub-brand to launch? It inherits the spine, picks an accent, and follows the deliverable rules. Product team needs a one-pager? They pull from sub-brand templates that already follow parent rules. The system makes the answer obvious — that's the whole point.
The mistake to avoid: endorsement everywhere. "By [parent]" plastered on every sub-brand asset. It feels safe but it dilutes both brands. The parent never builds independent equity, the sub-brand never builds standalone authority. The relationship should be felt, not labeled. If your architecture is strong, you don't need to announce it.
The other mistake: copying corporate-Goliath playbooks. Procter & Gamble runs hundreds of brands with no visible parent. That works because of distribution scale and shelf real estate. If you're a regional group running six sub-brands, you're not P&G. You need the parent gravity — but you need it as a system, not as a watermark.
If you're building sub-brands, start with the question "which decisions belong to the parent" before you draw a logo. Architecture first, identity second. The reverse is what produces six logos and zero coherence.
The parent provides the system. The sub-brand provides the difference.