McLaren Automotive and McLaren Racing have been two different companies with two different owners since the sale closed in April 2025. Abu Dhabi's CYVN bought the road-car business outright; Bahrain's Mumtalakat kept control of the F1 team. On Tuesday the two of them shipped a single identity, "one connected expression" across both, and Grande Prêmio spent the week asking whether McLaren needed a new wordmark at all.
Wrong question. The wordmark is the least important thing that changed.
What changed is that two P&Ls with two cap tables agreed to look like one company, and put it in writing. That's the deliverable. Which is the thing I keep having to explain to founders three products in: brand architecture is the rebrand decision that actually carries money, and most growth-stage companies make it by accident, one launch at a time.
The part McLaren decided, and the part they decorated
Craft verdict first. They kept the Speedmark and the papaya, which was the right call and the only call; those two assets are doing all the recognition work, and the Grande Prêmio review was correct that the familiarity comes from them, not from the adjusted lettering. The new wordmark is lifted from the sign above Bruce McLaren's father's service station in Remuera, Auckland, with an underlined C as the tell. It's a lovely story. It's also a story you need the press release for, which is fine when you have sixty years of recognition to spend and useless when you have three.
The decision underneath the decoration is the one worth studying. Racing and Automotive had drifted into two expressions of the same name, and the ownership split made the drift structural. Left alone, that ends one way: two visual systems, two tones, and a customer who buys a 750S wondering why it doesn't feel like the car Norris drives on Sunday. The identity is now the most valuable thing the two companies share. It had to be designed as one system on purpose, because nothing in the org chart was going to do it for them.
That agreement, about how many things you are, is the architecture. The logo just wears it.
The Series B version has no press release
I've watched this happen from inside the build at least a dozen times, and it never looks like a decision while it's happening.
Product one has a mark. Product two ships eighteen months later, the PM wants a launch moment, so it gets its own mark, usually a different shape in a slightly different color "so it feels distinct." A platform tier arrives with a third. Now the pricing page has three logos, the nav has a dropdown, and the sales deck has a slide whose only job is to explain the family. Nobody chose a house of brands. It just accreted, one Figma file at a time, and every added mark was a claim about how the company is organized that no one signed off on.
Atlassian is the counterexample, and the date matters: September 2017, when they rebuilt logos for fourteen-plus products as one family and said out loud that the system had to "account for future acquisitions." Architecture designed ahead of the org chart, so that whatever they bought next would land inside the system instead of beside it. Agora did the smaller, more relatable version this year with The Collected Works. The brief for an API company selling voice, video, chat and conversational AI was explicitly "connective tissue" across a sprawling product set, and Justin Colt's position on it is the whole job: creating something disruptive for the sake of being different would not have been the right solution here. The client needed the products to read as one company, and the new look was incidental to that.
Masterbrand until a customer proves otherwise
There are three ways to organize this and I'll recommend one. Monolithic (everything is [Company] [Noun]), endorsed (product brands with a "by Company" tag), or a house of brands (separate identities, parent invisible). For a growth-stage B2B company the answer is monolithic almost every time, and the reason is arithmetic. At $5M to $50M ARR your recognition is thin. Every sub-brand you introduce splits that recognition across another surface and doubles the guideline burden for a team that hasn't finished the first one. You are spending equity you don't have yet.
The trade-off is real and you should name it: under a masterbrand, product two inherits product one's reputation in full, the good and the bad. If product one is known for being slow to onboard, product two starts slow. That's the cost. It's still cheaper than teaching the market two names.
The one legitimate reason for a sub-brand is a buyer who would be repelled by the parent. A security product sold to CISOs living under a brand built for growth marketers, say. But notice what that actually is. It's a positioning problem wearing a naming costume, and it should be solved as positioning first. If the parent can't credibly hold both buyers, the question is which one you're building for, not what to call the second one.
The so-what for founders
Open your pricing page and your product nav, and count the marks. If the number is greater than one, you've already made an architecture decision. Write down the rule you used to make it. If you can't, the rule was "whoever launched last," and that rule is currently in your sales deck as a slide that explains who you are.
Then adopt the one that holds until you've earned an exception: one mark, and every product is your company's name plus a plain noun. You get to break it the day a customer says a product name in a sales call without your company name in front of it. Until then, the second logo is a tax on the first.
Reply with your pricing page and I'll tell you how many companies a buyer thinks you are.
