Brand Architecture Development: Build It Around Revenue, Not Org Charts

Brand architecture development is the process of defining how a company’s brands, sub-brands, products, and services relate to each other in the market. Done well, it reduces internal confusion, sharpens customer perception, and makes commercial decisions easier. Done poorly, it produces a tidy diagram that nobody outside the marketing department ever looks at again.

The distinction matters because most architecture work is driven by internal politics, not market logic. The result is a structure that reflects how the business is organised rather than how customers actually buy.

Why Most Brand Architecture Fails Before It Starts

I’ve sat in more brand architecture workshops than I care to count. The pattern is almost always the same. A senior stakeholder opens the session by saying something like “we need to tidy up the portfolio” or “we need to make sure our brands are aligned.” What follows is a two-day exercise in mapping what already exists, not in questioning whether it should exist at all.

That’s the first failure mode. Architecture work that starts from the current state and works forward will almost always preserve the status quo with a fresh coat of paint. The harder question, which most organisations avoid, is whether the current portfolio structure serves the customer or just the business.

The second failure mode is treating architecture as a naming exercise. Renaming things, adding a parent brand prefix, or creating a tiered sub-brand system does not constitute architecture. Those are cosmetic decisions. Architecture is about clarity of purpose, role differentiation, and the commercial logic that connects everything together.

If you want a broader foundation for how brand strategy should be constructed before you get into architecture decisions, the work I’ve covered in brand positioning and archetypes sets the context for why these structural choices matter so much.

What Are the Three Core Brand Architecture Models?

There are three models that most textbooks describe, and they’re worth understanding precisely because most real-world situations require a hybrid of all three.

The branded house puts one master brand across everything. Virgin is the classic example. The parent brand carries the equity, the sub-brands (Virgin Atlantic, Virgin Media, Virgin Money) borrow credibility from the parent and contribute back to it. The commercial logic is efficient: one brand to build, one reputation to manage, shared marketing investment. The risk is equally clear: one brand to damage. When Virgin Trains lost its franchise, it was a Virgin story, not a trains story.

The house of brands operates the opposite way. Procter and Gamble is the textbook case. Tide, Pampers, Gillette, and Ariel exist as independent brands with no visible connection to the parent. Each can be positioned, priced, and targeted independently. The parent absorbs the risk of any single brand failure. The cost is significant: you’re building multiple brands from scratch, each requiring its own investment, team, and strategy.

The endorsed brand model sits between the two. The sub-brand has its own identity but carries a visible endorsement from the parent. Marriott’s portfolio uses this extensively. Courtyard by Marriott, Ritz-Carlton (a Marriott company), and Westin Hotels and Resorts (part of Marriott Bonvoy) each carry distinct positioning while the parent endorsement provides a quality signal. The tension here is managing how much the parent endorsement helps versus constrains each brand’s ability to occupy a specific position.

None of these is inherently better. The right model depends on your customer base, your competitive environment, your growth strategy, and honestly, how much marketing budget you have to sustain the structure you choose.

How Does Portfolio Complexity Become a Commercial Problem?

When I was running the European hub of a global network, we had a portfolio problem that looked nothing like a brand problem on the surface. We had grown quickly, from around 20 people to close to 100, and we had acquired capabilities faster than we had integrated them. The result was a set of service lines that each had their own identity, their own language, and their own way of presenting to clients.

From the outside, we looked fragmented. Clients who came to us for one service had no clear line of sight to what else we could do for them. The architecture problem was costing us revenue, not because our work was weak, but because the portfolio wasn’t legible to the people buying it.

That’s the commercial reality of poor architecture. It creates friction in the buying process. Prospects can’t self-sort. Existing clients can’t expand their relationship with you because they don’t know what you do. Sales conversations get longer and more complicated than they need to be.

BCG’s research on brand strategy and customer experience makes the point well: clarity of brand role directly shapes how customers experience a company, not just how they perceive it. That distinction matters. Perception is about awareness. Experience is about commercial behaviour.

Every brand or sub-brand you add to a portfolio is a cost centre. It needs budget to build awareness, content to maintain relevance, and management attention to stay coherent. When organisations add brands without a clear commercial rationale, they dilute the investment available to the brands that actually drive revenue. The portfolio grows, the budget spreads thinner, and everything performs slightly worse than it should.

What Questions Should Drive the Architecture Decision?

Architecture decisions should be driven by five questions, in this order.

Do these offerings serve the same customer or different customers? If the answer is different customers with genuinely different needs, separate brand identities may be justified. If the answer is the same customer at different stages of their relationship with you, a single brand with a clear product hierarchy is almost always more efficient.

Does the parent brand help or hurt each offering? This is the question most organisations avoid because the answer is sometimes uncomfortable. If your parent brand carries associations that actively undermine a specific product’s positioning, you have a real architecture problem. If the parent brand simply isn’t well known enough to add value, that’s a different problem with a different solution.

What does the competitive set look like for each offering? A product competing in a market where the parent brand is unknown needs to build its own credibility. A product competing in a market where the parent brand is respected can borrow that equity. The competitive context should shape how visible the parent brand is in each case.

What can you actually afford to sustain? This question rarely appears in brand architecture frameworks, which is a significant oversight. Building brand awareness is expensive and slow. If you create a sub-brand that you can’t fund adequately, you haven’t created a brand. You’ve created a name on a website.

What happens to this structure when the business changes? Acquisitions, new product lines, market exits, and strategic pivots all put pressure on architecture. A structure that can’t flex will either constrain your options or require expensive restructuring later. Building in some flexibility at the outset is not a sign of indecision. It’s practical.

How Do Acquisitions Complicate Brand Architecture?

Acquisitions are where brand architecture gets genuinely difficult, and where the gap between theory and practice is widest.

When you acquire a business, you inherit its brand equity, its customer relationships, and its reputation. Sometimes that equity is an asset you want to protect. Sometimes it’s a liability you want to distance yourself from. Often it’s both, depending on which customer segment you’re talking about.

The default in most acquisitions is to move too fast in one direction or the other. Either the acquired brand is absorbed immediately into the parent, destroying the equity that made it worth acquiring in the first place, or it’s left entirely separate with no integration, which means you’ve paid for something that delivers no collaboration at all.

The more considered approach is to map the equity that exists in the acquired brand and be specific about what you’re trying to preserve. If the acquired brand has strong customer loyalty in a segment you don’t currently serve, that loyalty is the asset. Disrupting it by forcing a rapid rebrand destroys the very thing you paid for.

I’ve seen this go wrong in both directions. A network I worked within acquired a specialist agency and immediately began pushing the parent brand forward. Within 18 months, the acquired agency’s senior team had left, taking their client relationships with them. The acquisition had been valued almost entirely on those relationships. The architecture decision, made without adequate consideration of what was actually valuable, destroyed the investment.

BCG’s work on brand strategy and go-to-market alignment highlights how brand decisions made in isolation from commercial strategy consistently underperform. Architecture is not a marketing decision made after the commercial strategy is set. It’s part of the commercial strategy.

What Role Does Visual Coherence Play in Architecture?

Visual identity is where architecture becomes tangible to customers, but it’s also where organisations tend to confuse execution with strategy.

A visual system that signals the relationship between brands in a portfolio is useful. Shared colour systems, consistent typographic conventions, and a coherent design language across a portfolio tell customers something real about the relationship between the brands they’re interacting with. Building a visual identity toolkit that’s flexible and durable is harder than it looks, particularly when you’re managing a portfolio with different audiences and different competitive contexts.

The mistake is treating visual coherence as the goal rather than the output. I’ve reviewed brand architecture projects where the entire deliverable was a visual system showing how the logos relate to each other. That’s design work, not architecture work. The visual system should express decisions that have already been made about brand roles, relationships, and hierarchy. If those decisions haven’t been made, the visual system is just decoration.

Consistent brand voice is the other dimension that visual identity work often neglects. A portfolio of brands that looks coherent but sounds inconsistent creates a different kind of confusion. Customers experience brands across multiple touchpoints, and the voice is often more present than the visual identity. Getting the tonal relationship right across a portfolio requires the same level of deliberate thinking as the visual system.

When Should You Simplify a Portfolio Rather Than Architect It?

This is the question that most brand architecture engagements never properly confront. Simplification is often the right answer, but it’s rarely the answer that gets proposed, because it involves removing things rather than adding them.

Portfolio rationalisation is uncomfortable because it requires admitting that some brands, products, or services aren’t pulling their weight. In organisations where individual teams or business units have ownership of specific brands, rationalisation feels like a political threat rather than a commercial decision. The result is architectures that carry brands nobody would create today if they were starting from scratch.

The test I’ve used in these situations is straightforward: if this brand didn’t exist today, would we create it? If the answer is no, the question becomes whether the cost of maintaining it is justified by the revenue it protects. Sometimes it is. Legacy brands with genuine customer loyalty can be worth sustaining even if you wouldn’t build them from scratch. But that should be a deliberate commercial decision, not an accident of history.

Brand equity, as Moz has explored in the context of Twitter’s transformation, can erode surprisingly quickly when the coherence of the brand experience breaks down. A simplified portfolio that’s well-funded and clearly positioned will almost always outperform a complex portfolio where investment is spread too thin to build real equity in any single brand.

The Effie Awards process, which I’ve judged, consistently rewards campaigns where the brand role is clear and the strategy is coherent. The entries that struggle are rarely the ones with small budgets. They’re the ones where the brief itself reflects a confused architecture, where the brand is trying to be too many things to too many people because the portfolio decisions upstream were never properly resolved.

How Should Architecture Development Be Structured as a Process?

The process matters because architecture decisions have long time horizons and significant downstream consequences. Getting the process wrong produces a document that looks authoritative but doesn’t hold up when it meets reality.

Start with the commercial context. What is the business trying to achieve in the next three to five years? Which markets, customer segments, or revenue streams are priorities? Architecture should serve those objectives. If the business is planning to enter new markets, the architecture needs to be able to accommodate that. If the business is consolidating around a core offering, the architecture should reflect that focus.

Map the current portfolio honestly, including the brands and sub-brands that exist informally. In most organisations, the official portfolio is smaller than the actual portfolio. Teams create micro-brands, product names take on their own identity, and campaigns generate brand associations that weren’t planned. Getting a complete picture of what actually exists is harder than it sounds, and it’s essential before making any structural decisions.

Then audit the equity in each brand. What do customers actually associate with each brand? What do they value? What do they expect? This is not the same as asking internal stakeholders what the brand stands for. Internal perceptions and customer perceptions diverge more often than most organisations want to admit. Understanding where brand awareness actually sits in your portfolio, rather than where you assume it sits, changes the architecture conversation significantly.

From there, test the structural options against the commercial objectives. Not “which model is theoretically correct” but “which structure best supports the revenue and growth goals we’ve set.” The answer is almost always a hybrid, and the detail of how you manage the transitions between brand roles matters as much as the model you choose.

Finally, build the governance model. Architecture without governance degrades quickly. Who has authority over brand decisions? What’s the process for adding a new brand or sub-brand to the portfolio? How are brand standards enforced across business units, markets, and agencies? The governance model is unglamorous work, but it’s what determines whether the architecture you’ve built actually holds.

Brand architecture is one of the more consequential decisions in brand strategy, and it connects directly to the broader positioning questions I’ve explored across The Marketing Juice brand strategy hub. If you’re working through a portfolio review or a repositioning, the framing there will give you the strategic context that architecture decisions need to sit within.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions