Several names compete to explain the same buyer choice.
Brand architecture
Give every brand, product, service, and offer a role the buyer can understand.
Architecture work is for a brand stack that grew faster than its logic. It makes the parent, sub-brands, products, services, and offers easier to navigate without creating more names than the market can learn.
The parent, product, and offer links are obvious internally but invisible publicly.
New services, acquisitions, or markets keep adding exceptions to the system.
Use this when
The work starts with the business decision, not a design preference.
These are the conditions that make brand architecture work worth opening.
Parent-brand confusion
The company name and customer-facing brands fight for priority.
Offer sprawl
Every new service receives a name, page, and logo before earning a distinct role.
Acquisition integration
A known acquired name has value, but its relationship to the parent is unclear.
Product hierarchy
Products, editions, features, and plans use inconsistent naming levels.
Market expansion
Country, industry, or buyer variants are multiplying the public structure.
Sales friction
Teams explain the organization before they can explain the useful offer.
Engagement unit
The packet defines the public naming system.
The result shows which names lead, which names support, and which names should disappear.
What the packet can include
- Current architecture map with buyer-facing friction.
- Role definitions for parent, endorsed brand, sub-brand, product, service, and offer.
- Architecture options with recognition and operating tradeoffs.
- Recommended naming hierarchy and endorsement logic.
- Migration notes for website, sales, product, support, and search.
Boundaries
- Not a new logo for every internal unit.
- Not an organization chart presented as a buyer system.
- Not a naming convention without ownership and governance.
- Trademark and legal entity questions require qualified review.
Method
One decision moves through four working stages.
The relevant decision owner joins the review. Scope, participants, and timing are confirmed after the private fit review.
Inventory the stack
List every public name, role, owner, audience, and surface.
Find the collision
Identify where buyers, search, sales, or teams misread the relationship.
Compare models
Test branded house, house of brands, endorsement, and hybrid options against the evidence.
Write the operating rules
Define who can create names, where each level appears, and how future additions are governed.
Related work
Open the page that owns the next decision.
Private request
Bring the live decision and the surface where it is failing.
The initial request is used to evaluate fit. Do not place trade secrets or highly confidential material in the form. No public price and no checkout; the next step is a private reply when the work fits.