Essay · 5 November 2026 · 4 min read

A second brand needs a second buyer

Most hosting and SaaS companies do not have a brand architecture problem. They have a naming habit. A new tier arrives and it gets a name. A backup add-on arrives and it gets a name, a logo and a colour of its own. Two years on, the pricing page reads like a catalogue from a company four times the size, and support spends its day explaining which of the four things the customer is already paying for.

The decision is simpler than most frameworks make it. A product earns its own brand when a different person buys it. Not a different team inside the same account, and not a different use case: a different buyer, with their own budget, their own shortlist and their own reason to care. If the same person buys it, on the same invoice, often in the same session, it is a feature with a label. Features get described, not branded.

When a new product needs its own brand

The test is about the buying, not the building. Engineering sees two separate systems. The buyer sees one supplier and one bill.

Ask who signs. A managed hosting customer adding object storage to an existing account is the same buyer making the same decision twice, with a smaller number attached. A company that starts selling a developer tool to people who have never bought hosting, who arrive through a different search and compare it against a different shortlist, has found a second buyer. That is when a second brand begins to earn its keep.

A sub-brand claims this is a different purchase. If it isn't, you have given your customers homework.

Our hosting work separates technical buyers, resellers and enterprise accounts, because those three want different things from the same company. That is the separation worth paying for: audience first. Products that all serve the same audience gain nothing from separate identities, and they cost something.

What a name actually costs

A name is not a line in a strategy document. It is an object that has to exist in every place the company meets the customer:

  • the pricing page and the comparison table
  • the control panel navigation, next to everything else you have named
  • the invoice line and the renewal email
  • documentation, support replies and the status page
  • a search result for a word nobody has typed before

Each of those has to agree with the others, and they drift. Marketing introduces the name on the website, the panel keeps the old word, and the customer now has two words for one thing. Technical buyers do not read that as untidy. They read it as a company that has lost track of its own product, and they arrive sceptical of hosting marketing already.

There is a legal cost, easy to skip when a name starts life as an internal nickname. GOV.UK's guidance on choosing a company name puts checking existing trade marks among the steps before you settle on one, and a product name you intend to own deserves the same check.

There is a search cost as well. An invented name has no demand behind it. Nobody types it until they already know you, so the page built for it can only be found by people who were not looking for it. A page called what the thing is, "object storage" or "managed backups", answers a query someone is actually entering.

Two tests before you name anything

Would someone buy this without buying anything else from you first? If the honest answer is no, it is an add-on, and add-ons get descriptive names.

Could you put the name on a shortlist beside competitors and have a buyer understand what it is up against? If not, the name is doing no work that the category word was not already doing.

A real sub-brand passes both. Everything else is a word your customers have to learn before they are allowed to buy.

The usual answer is a page

Most new things need explaining, locating and finding. That is a page, a line in the panel and an entry in the docs, which is a far smaller job than establishing a name and then defending it.

A parent brand that means something, with plain descriptions underneath it, is a system a small marketing team can run without a monthly argument about capital letters.

If your portfolio has grown the other way, start with subtraction. List every name you currently ask a customer to know, mark the ones a buyer could not complete a purchase without, and write plain descriptions over the rest. That list is usually shorter than the pricing page suggests, and rewriting it is the least glamorous brand work you will do this year, and the most useful.