A line item got promoted to a brand because a launch deck needed a headline. Now it demands its own marketing budget.
MORE THANONE BRAND?THE JOINTS ARELOAD-BEARING.
When you have more than one brand, product, or audience, we sort out how they relate, because in a family of brands the relationships are the structure. Brand architecture organises brands, sub-brands, product lines, and extensions into one system that carries weight. Engineer the joints and every launch lands on solid framing. Leave them undecided and every marketing decision downstream gets harder.
most portfolios were never designed. they accreted.
Brand architecture decides what’s a brand, what’s a product name, what’s an ingredient claim, and what’s just a SKU. Most companies never decided. They accumulated. And accumulation has a signature: cracks that follow the joints nobody ruled on.
Two names, one customer. Every dollar spent on the second name is rent paid against the first.
Is it a brand? A product name? An ingredient claim? Nobody ruled, so every team answers differently.
Most mid-stage brands are wrong about which structure they are. They insist “branded house” and operate “endorsed.” The first thing we agree on is what’s actually true today: the survey before the engineering.
SAME COMPANY. THREE STRUCTURES. THREE DIFFERENT PHYSICS.
One worked example, a hypothetical parent, Paragon Co., drawn three ways. Each structure changes what the customer sees, what marketing pays for, and how much room you have to launch.
- BEARS
- One audience. One category. Reinforcement at every touchpoint: every floor strengthens the mast.
- FAILURE MODE
- A miss on the parent brand taints every extension. One crack travels the whole core.
- BEARS
- Distinct audiences, price points, or categories that shouldn’t blend. Each tower stands or falls alone.
- FAILURE MODE
- Marketing efficiency plummets. You pour a separate foundation (and pay) for every brand.
- BEARS
- Sub-brands with their own meaning; the parent lends credibility without dominating. Tension, tuned.
- FAILURE MODE
- Easy to muddle. Demands clear rules for endorsement weight: slack cables read as no cables.
We recommend one (branded house, house of brands, endorsed, or a hybrid tuned between them) based on what the structure must bear, not on taste.
Five stations. One diagram at the end.
- ST-03.01AUDIT
We map every brand, product, and extension you have today: the full inventory, down to the last SKU. Nothing gets engineered from memory.
- ST-03.02PERCEIVE
We map how your customers actually see them. That drawing almost never matches the org chart, and the customers’ drawing is the one bearing load.
- ST-03.03PROPOSE
We recommend a structure (branded house, house of brands, endorsed, or hybrid) chosen for what it must bear, never for taste.
- ST-03.04CODIFY
We write naming rules so every future product has a place before it exists. The structure stays true after we hand over the drawing.
- ST-03.05MIGRATE
We plan the transition: what renames, what sunsets, what launches. Load is transferred member by member, never dropped.
Four rules, written so every future product has a place.
The rulebook is the calibration that keeps the structure true after handover. Each rule is a gauge: a name either passes through the thread, or it doesn’t ship. No committee required.
Parent + descriptor
the floor bolts straight to the mastDistinct, no overlap
two members can’t share one seatNo franken-modifiers
bolted-on suffixes shear off firstOwnable in-category
a member must hold its own groundA STRUCTURE IS ONLY PROVEN UNDER LOAD.
The test of an architecture isn’t the day it’s presented. It’s the day something heavy arrives. We load the recommended structure with tomorrow before you commit to it.
The next launch
Every future product has a place before it exists. The new thing lands on the deck, finds its naming joint, takes its seat. No emergency rebrand, no eleventh name.
The acquisition
Something new and foreign arrives with its own mass. The structure already says where it bolts on, what it’s called, and how loudly the parent signs it.
The internal argument
Someone insists their project deserves its own brand. The document answers: not a meeting, not a referee, not you at midnight.
The brand architecture document
The structure itself (what’s a brand, what’s a product name, what’s an ingredient claim, what’s a SKU) drawn, argued, and decided.
The naming rulebook
The codified joints: rules written so every future product has a place, and so the structure stays true long after handover.
The migration plan
The transfer of load: what renames, what sunsets, what launches, sequenced so nothing bearing weight is ever cut before its replacement holds.
- You don’t referee internal arguments.
- You don’t manage the rollout.
- You don’t lose sleep over whether this is brand or sub-brand.
The structure holds so you don’t have to. That’s the point of structure.
Have more than one brand in play?
We’ll map what’s standing. Then we’ll engineer what holds, and hand you the drawing.
DWG I.03 · ISSUED FOR CONSTRUCTIONor take the free assets first
