When your company has one product, your brand is one thing. When your company has multiple products, you face a structural decision: how do the products relate to the company brand? Are they each their own brand? Are they all variations of the company brand? Something in between?
This is brand architecture. It's the structural decision behind every multiproduct brand. Sometimes made deliberately, often made by default. The architecture you choose shapes everything downstream: how customers experience the products, how marketing operates, how new products launch, how the company can evolve.
Here's the deep dive on the architectural options, when each works, and how to choose.
The three primary architectures
Architecture 1: Branded house. One master brand; products are sub-brands. Customers experience "[Master Brand] [Product]." Examples: Apple iPhone, Apple Watch, Apple Music. Google Search, Google Maps, Google Workspace. Adobe Photoshop, Adobe Illustrator, Adobe Lightroom.
The master brand is dominant. Products carry recognizable but secondary identity. Trust transfers strongly across products.
Architecture 2: House of brands. Many distinct brands, weakly connected (if at all) to the parent company. Examples: Procter & Gamble (Tide, Crest, Pampers, Gillette). Unilever (Dove, Hellmann's, Vaseline). The parent company is operational; customers experience the individual product brands.
Each brand operates independently. The parent provides infrastructure (manufacturing, distribution, finance) but doesn't visibly connect the brands. Trust accumulates per-brand.
Architecture 3: Endorsed brands. Products have distinct brands, but the parent brand visibly endorses them. Customers experience "[Product Brand] from [Parent Brand]" or "[Product Brand], a [Parent] company." Examples: Nestle endorses its product brands. Some early-stage Atlassian acquisitions used this pattern.
Middle path. Products get their own identity. Parent brand provides credibility umbrella without dominating.
How to choose your architecture
Four questions that point toward the right architecture:
Question 1: Do your products serve the same customer or different customers?
Same customer (one buyer wants multiple products): branded house works. The trust they have in your master brand transfers to new products. Cross-sell is easier.
Different customers (each product serves a distinct audience): house of brands or endorsed brands works. Each product brand can be positioned specifically for its audience without compromise.
Question 2: Could the success of one product hurt another?
Yes (brand contamination risk): house of brands. If a controversial position by one product would damage other products' acceptance, separate brands isolate the risk.
No (success is positive-sum across products): branded house. Connecting the brands compounds positive perception.
Question 3: How much marketing efficiency do you need?
High efficiency needed (small marketing team, limited budget): branded house. One brand to maintain. One marketing pipeline.
Efficiency less critical (resources available for parallel brand operations): house of brands. The duplication cost is acceptable because the brand separation produces sufficient differentiation value.
Question 4: How distinct are the products in customer mental models?
Products feel like family members (similar enough to be sibling products): branded house. Customers naturally group them.
Products feel like cousins (related but distinct enough that bundling feels wrong): endorsed brands. Acknowledged connection, distinct identities.
Products feel like strangers (no natural connection): house of brands. The connection would seem forced.
The branded house deep dive
Branded house is the most common architecture for software companies and the simplest to execute. Specific operational considerations:
Naming convention. Pick a pattern and stick to it. "[Master] [Product]" (Apple iPhone, Apple Watch) is common. "[Master] for [Use Case]" works too (Microsoft for Education). Mixed conventions confuse customers.
Visual hierarchy. Master brand identity dominates. Products may have small distinguishing elements (specific colors, icons) but the master brand visual system is the primary identity. Don't let products develop their own visual identities that compete with the master.
Marketing surfaces. Single homepage usually for the master brand, with clear navigation to product pages. Each product can have dedicated marketing pages within the master site rather than separate product sites.
The risk: brand dilution. If you keep adding products, the master brand has to stretch to encompass them all. Eventually the master brand can become vague. Meaning everything and therefore nothing specific. Adobe has navigated this carefully; many lesser-known brands haven't.
The house of brands deep dive
House of brands is the most flexible architecture but the most expensive to operate. Specific operational considerations:
Each brand is independent. Separate naming, separate visual identity, separate voice, separate marketing. Each brand has its own homepage, social presence, customer support.
The parent company is invisible. Most customers don't know which company owns Tide or Crest. Procter & Gamble operates them but doesn't brand them as connected.
Resource sharing happens behind the scenes. Manufacturing, distribution, R&D can be shared across brands. Customer-facing identity stays separate.
The risk: resource fragmentation. Operating many brands requires many brand teams. Quality varies. Brands that don't get enough investment fade. House of brands works at scale; struggles at sub-scale.
The endorsed brands middle path
Endorsed brands try to capture the benefits of both extremes. Specific operational considerations:
Product brand is primary. Customers experience the product brand first. The product brand has its own identity that feels distinct.
Parent endorsement is visible but secondary. Small text or accompanying logo signals the parent connection. "By [Parent]" or "[Parent] company" framing.
Cross-product navigation exists but is gentle. Customers can discover the parent's other products but aren't pushed toward them.
The risk: the worst of both worlds. The parent endorsement doesn't transfer much trust if it's too subtle, but if it's too prominent it competes with the product brand. The middle path requires deliberate calibration.
Architecture changes over time
Many companies start with one architecture and evolve to another:
Single product → branded house. The most common evolution. Company adds products as expansions; brands them under the master brand. Works as long as products genuinely fit the brand.
Branded house → endorsed brands. The master brand becomes too stretched. Some products get distinct identities while maintaining endorsement. Reduces stretch on the master while preserving connection.
Endorsed brands → house of brands. Product brands grow strong enough to operate independently. Parent connection fades to operational role only.
House of brands → branded house. Rarer. Usually happens after acquisition consolidation. Multiple independent brands get rolled up under a single master.
The right architecture depends on stage and strategy. The architecture that works at 5 employees doesn't necessarily work at 500. Planning for evolution from the start helps avoid forced transitions later.
The cost differences
Brand architecture has cost implications:
- Branded house: Most efficient. Single brand to maintain, single marketing pipeline. Total brand cost might be 5-8% of operating budget.
- Endorsed brands: Middle cost. Each product brand needs individual investment, but shared infrastructure helps. Brand cost typically 8-12% of operating budget.
- House of brands: Highest cost. Each brand fully separate. Brand cost can be 12-18% of operating budget at scale.
The cost difference is significant. Cheaper architectures don't necessarily produce worse outcomes. Branded house can be the right call even when house of brands would be more flexible, because the cost difference frees resources for other investments.
The customer-confusion problem
Inconsistent or unclear brand architecture confuses customers in ways that hurt:
- Customer of Product A doesn't realize Product B is from the same company; misses cross-purchase
- Customer evaluates Product B without giving credit to the trust they have in Product A's brand; conversion suffers
- Customer experiences inconsistent brand quality across products; assumes the company is sloppy
- Customer support gets confused; "wait, are these the same company?" wastes time and damages trust
The architecture decision affects each of these. Clearer architectures (whatever the choice) reduce these problems. Unclear architectures multiply them.
The first-product-extension decision
For single-product companies considering their first additional product, the architecture decision happens then. Most founders default to "we'll launch it under our brand" without examining whether that's the right architecture.
The right exercise: imagine three or four products extending from your current product over the next 5 years. Which architecture serves that future best? Then build the second product's branding to fit that architecture, not as a one-off.
Brand architecture is one of those structural decisions where the first move sets the pattern. Make it deliberately.
And whichever architecture you choose, commit to it. The companies that maintain consistent architecture as they scale produce brands that compound. The companies that flip architectures or operate inconsistently never get the compounding benefit.
Your brand kit, ready in 10 minutes.
Five quick taps. Free preview before you pay.
Start building free →