Name the product or the company? A brand-architecture decision guide

Name the company — and let the products ride on it. That’s the right default for most founders: one master brand that fronts everything you ship, with products wearing plain functional labels underneath. Branding people call this a branded house; the alternative — a stable of independently named brands with the parent company hanging back — is a house of brands. Strategy decks treat the choice as a positioning question, but for a small team it’s equally a money-and-domains question. A branded house means one name to find, one domain to buy and defend, one set of handles to claim. A house of brands means all of that, multiplied by every brand you create. Only when a product genuinely needs to stand apart — a different audience, a different risk profile, a name that arrived via acquisition — does the multiplied bill start earning its keep.

Branded house or house of brands?

A branded house puts one master brand on everything. Google, at the product level, is the canonical example: Maps, Drive, and Docs are barely names at all — they’re descriptions hanging off one enormous brand, living at addresses like maps.google.com and docs.google.com. Apple runs its product line the same way: the iPhone, iPad, and Mac each have their own flavor, but Apple does the talking, and every product page lives under apple.com. FedEx stamps the master name onto its services — FedEx Express, FedEx Ground. In a branded house, every launch borrows the master brand’s trust on day one and deposits its own winnings back into the same account.

A house of brands does the opposite: independent brands out front, parent in the background. Procter & Gamble owns Tide, Pampers, and Gillette; Unilever owns Dove, Hellmann’s, and Axe (sold as Lynx in the UK). Most shoppers couldn’t match parent to brand, and that’s deliberate — each brand is tuned to its own audience, shelf, and price point, with its own website on its own domain, and none inherits the others’ baggage. The parent is a holding structure, not a face.

Between the two sit endorsed brands and sub-brands. Sony’s PlayStation is a sub-brand with enough gravity to carry its own domain and identity while the parent stays visible on the box. Amazon keeps Prime and Alexa clearly inside the family — distinct names, unmistakably Amazon’s. And the “Courtyard by Marriott” construction is endorsement at its most literal: a new name with the parent’s trust attached by a preposition. The middle path exists because the pure architectures trade against each other. A branded house compounds — every product strengthens the same name — but it also couples: one product’s failure splashes onto everything wearing the logo. A house of brands isolates — each brand says exactly what its audience wants to hear, and trouble in one aisle doesn’t stain the rest — but nothing compounds: every brand starts from zero and stays a separate mouth to feed.

One distinction worth keeping crisp: this is not the question of whether your domain must match your registered company name — legal names, trading names, and domains live in different systems entirely. This piece is about something upstream: how many brands you’re maintaining in the first place.

What does each choice cost you in domains?

A branded house is one domain, full stop. The company name is the domain; products live at subpaths or subdomains — acme.com/analytics, or app.acme.com when the product needs its own surface. The mechanics of that placement, and when a project has outgrown it, are covered in subdomain or new domain, but the economics are simple. Both are free and instant. A subpath like acme.com/analytics inherits everything the parent has earned directly — its recognition, search authority, email-domain reputation, and TLS. A subdomain like app.acme.com rides on the recognition but is treated as more separate: it may need its own certificate (or a wildcard), search engines pass it authority less directly, and its sending reputation can start cold — which is sometimes exactly why teams reach for one. Either way, your defensive registrations — the matching .com if you launched elsewhere, one obvious typo — are bought once and protect every product simultaneously, and there are only two or three of those worth buying anyway.

A house of brands multiplies every line item. Each new brand needs its own naming search, trademark screen, domain, small ring of defensive registrations, social handles, DNS and email setup, and — the expensive part — its own marketing budget, because a name nobody has heard of does nothing until you spend to change that. None of these is large alone. Multiplied across five brands, it’s a real portfolio with real carrying costs, and someone has to track every renewal. Procter & Gamble pays this bill gladly because isolation and shelf coverage are worth more to it than compounding. For a three-person startup, the same bill buys mostly fragmentation: five small names nobody knows instead of one name everybody you’ve reached knows.

When should a product get its own name?

A separate brand earns its cost in a few specific situations — and honestly, only these:

• A genuinely different audience. If the buyer of the new product would be confused or put off by your existing brand — enterprise software from a consumer-cute name, a budget line under a premium label — sharing the name costs more than it saves.
• A different risk profile. An experiment that might fail publicly, a product in a regulated or controversial category, a bet you may need to kill loudly — isolating it protects the master brand from the splash.
• It arrived with the name. Acquired products come with recognition already attached to their existing name and domain. Renaming an acquisition burns the equity you just paid for; keeping it turns you into a small house of brands whether you planned one or not.
• A sub-brand outgrows the parent. Occasionally a product becomes bigger in the customer’s mind than the company behind it. That’s a good problem, discovered with evidence — not something to architect for on day one.

The endorsed brand is the cheap first step when one of these half-applies. “Meridian, by Acme” gives the new thing its own name and its own domain while borrowing your existing trust — and you can quietly drop the endorsement once the new name stands on its own, or fold the product back in if it doesn’t.

What should most founders actually do?

Default to the branded house, and spend your naming energy on one great master brand. That name has a harder job than any product name: it has to hold products that don’t exist yet, which is why the abstract, ownable names score well — short, pronounceable, spellable after one hearing, and not welded to a single feature you might pivot away from. How to name a startup walks the full process, and our methodology shows exactly how those traits get scored. Products then take functional labels that ride on the master brand — Acme Analytics, Acme Send — which cost nothing to launch, nothing to kill, and no new domain either way. Add architecture only when one of the triggers above actually fires; brand structure should follow traction, not precede it. And if you’re a serial builder running genuinely unrelated bets, that’s not a house of brands — it’s a portfolio, with its own hygiene and carrying costs — but the same arithmetic applies: every separate name is a separate bill.

If you’re at the step this article keeps pointing back to — finding the one master brand worth hanging everything on — Domain Yoga turns a plain description of what you’re building into around 250 availability-checked, brandability-ranked name ideas in seconds. One strong name, chosen once, is the cheapest brand architecture there is.