Brand Naming Systems: Does Every Service Need a Name?
A growing firm does not need a new brand for every service. A naming system sets the rules for what deserves a separate identity, how names relate and who approves exceptions. Start with customer differences and existing recognition, then build the smallest portfolio your business can explain and support consistently

On this page7 min left
A new department is not automatically a new brand.
Brand naming systems set the rules for which parts of a business need separate names, how those names relate and who can approve another identity. For a growing advisory firm, the first decision is whether a service needs anything beyond a clear description.
A separate identity can be justified. Siemens Healthineers, the medical technology company, announced in November 2026 that its diagnostics business would adopt Olyrian Diagnostics as it prepares to become a standalone organisation.
Siemens Healthineers also announced a planned change to Healthineers. Those are different structural decisions, not reasons to rename every service line.
Make that structural decision before starting the brand naming process. Otherwise, a workshop can produce an answer to a question the business never needed to ask.
What are brand naming systems?

A brand naming system governs names across a business portfolio. Brand architecture defines the relationships between brands; the naming system expresses those relationships through approved wording and decision rules. WARC, the marketing research publisher, describes brand architecture as the structure specifying brand roles and relationships.
- Eligibility rules determine when a separate identity is justified.
- Naming conventions define how approved names are constructed.
- Governance assigns approval rights and records exceptions.
Brand naming systems define when separate names are justified, how names relate and who controls naming decisions across a portfolio.
The recommendation here is to build the smallest system that communicates the differences customers need to recognise. That is an editorial decision rule, not a proven formula for higher revenue.
Does the service need its own name?
Start by writing the service in ordinary language. “Employment tax advice” is a useful starting point. An invented word can wait.
An invented service name creates another explanation in the sales conversation: what the name means, what the service does and how the service relates to the practice. That explanation may be worth making. Require a customer reason.
Use the following gate before commissioning a shortlist.
- Different buying decision: does the service address a distinct buyer, need or purchasing process?
- Meaningful separation: does the service have a proposition that a plain descriptor cannot communicate adequately?
- Existing recognition: is there already a name customers recognise and use?
- Support: who will fund and maintain the identity after launch?
- Structural need: must the business prepare for separate ownership, operation or sale?
These are prompts for judgement, not a points-based test. A future separation may outweigh several arguments for consistency.
The Olyrian Diagnostics announcement illustrates that exception. Siemens Healthineers described a staged rollout, with the diagnostics business remaining within Siemens during the transition.
The announcement supports a structural rationale for a separate identity; the announcement does not establish a financial return from renaming.
A hypothetical advisory firm: three launches, different answers
Take Northbank Advisory, a hypothetical UK practice employing 120 people. Assume Northbank Advisory has an established parent name, is introducing a tax service and is acquiring a regional consultancy.
For the tax service, “Northbank Advisory — Employment Tax” may adequately explain the offer. The service does not receive a separate brand simply because the service has a new leader.
For the acquired consultancy, assume customers regularly refer to the acquired practice by name. Immediate replacement would require a better justification than visual tidiness. A temporary endorsed relationship deserves consideration while the leadership team investigates recognition.
For a subscription software product, assume that the buyer, support model, and future ownership plan differ from those in the advisory practice. Those differences justify investigating a separate identity. The differences do not settle the decision without buyer and commercial evidence.
One company. Different naming needs.
“But our new service needs to stand out”
A distinct name can help express a distinct proposition. The objection is reasonable.
The question is whether the service needs a separate identity or clearer communication.
WARC’s account of Deloitte’s capital-markets campaign describes under-recognised services, research into buyer concerns and a communications programme that secured advisory roles.
The case concerns communications, not a naming experiment, but it provides a useful alternative diagnosis: poor awareness does not, by itself, prove that another name is required.
Before approving a new identity, ask the service leader to show what buyers currently misunderstand.
Test a clearer description alongside any proposed branded version.
How should parent, service and acquired names relate?

Choose relationships according to the buying situation, then write naming rules that express those relationships.
WARC’s architecture spectrum distinguishes independent brands, endorsed brands, sub-brands and a branded house.
In a branded house, the master brand has the dominant role, and subordinate wording describes the offer. An endorsed brand retains an identity while showing an organisational connection.
For a mid-sized practice, consider three practical arrangements:
- Parent name plus descriptor: suitable when customers buy the practice’s expertise and need to identify a service.
- Retained name with endorsement: worth considering when an acquisition has recognition that should not be discarded without investigation.
- Independent identity: worth considering when the buyer, proposition or ownership plan requires separation and the business can support the identity.
An endorsement shows a relationship. An endorsement does not create legal or reputational insulation.
Before retiring an acquired name, examine named referrals, buyer interviews and recent pitches—separate familiarity with the practice name from loyalty to an individual partner.
If referrals attach mainly to a partner, preserving the practice name may solve less than the acquisition team assumes.
“We have acquired three firms. Surely one name is simpler?”
One name can simplify the portfolio chart. Customer understanding is a different question.
The acquisition team should record what each existing name contributes before choosing a transition.
Set conditions for review: buyer understanding of the parent relationship, continued use of the acquired name in referrals and evidence from live sales conversations.
Avoid a permanent collection of exceptions created to keep everyone happy. Equally, avoid deleting a useful name because the new website would look neater.
Where a retained name is justified, specify the endorsement wording and review conditions in the internal nomenclature governance guide.
What belongs in a naming-system blueprint?
A portfolio diagram shows the intended relationships. A blueprint must also tell the next service leader what to do.
The proposed blueprint has five parts.

Record the portfolio before setting naming conventions
Create an inventory of every customer-facing name: the parent brand, acquired practices, services, products and named programmes.
For each entry, record the approved wording, customer audience, owner, relationship to the parent and evidence supporting retention.
Include informal names used in proposals. An unofficial label can become familiar internally long before anyone formally approves a brand.
Keep legal entity names distinct from marketing names. The record should make the relationship explicit without implying that both names serve the same purpose.
Write naming conventions that describe the offer.
Specify the order of parent name and descriptor, permitted abbreviations, capitalisation and endorsement wording. Show acceptable examples and rejected examples with reasons.
Microsoft’s January 2025 changes demonstrate why roles matter beneath shared terminology.
Microsoft renamed the Microsoft 365 app as the Microsoft 365 Copilot app; Microsoft also distinguished Microsoft 365 Copilot Chat from the paid Microsoft 365 Copilot add-on licence.
Shared terminology connected the offers, but the app, chat offering and licence still required separate explanations.
For an advisory practice, the equivalent distinction might be between the service category, a fixed-scope engagement and an ongoing subscription.
Do not ask the name to explain every contractual detail. Use the name to identify the offer and supporting copy to explain what the customer buys. Document that division in the portfolio naming conventions.
Assign approval rights and record exceptions.
Appoint one accountable approver. Give the relevant service leader responsibility for the business case, with marketing maintaining the register and legal advisers reviewing legal questions.
Require an exception request to state:
- The customer problem the standard convention cannot solve.
- The proposed relationship to the parent.
- The resources committed to maintaining the identity.
- The evidence and conditions for a later review.
A partner’s preference can inform discussion. A partner’s preference should not quietly become a permanent portfolio rule.
Keep screening separate from legal clearance.
The blueprint should identify when preliminary screening happens and who commissions qualified advice. A naming approval meeting must not be mistaken for legal sign-off.
Keep detailed clearance work within the brand naming trademark strategy, rather than squeezing legal conclusions into a portfolio diagram.
Test the system against the next change.
Before approval, apply the proposed rules to an acquisition, a new service and a potential standalone product. These are test scenarios, not forecasts.
Can the leadership team reach a reasoned decision using the document? Does every scenario require an exception? A system that must be rewritten for each launch remains unfinished.
Start with the portfolio, not a naming workshop
Approve the reason for another identity before approving another name.
A service descriptor is a legitimate answer when customers mainly need to know what the practice provides.
A retained acquisition name can be justified by demonstrated recognition. A separate identity deserves consideration when the buying situation or ownership plan requires separation.
For a small, uncomplicated portfolio, the leadership team may be able to document the rules internally.
When acquisitions and overlapping services complicate the decision, Inkbot Design’s brand naming services can help establish the structure.
If the portfolio needs diagnosis first, request a free Brand Equity Audit™.
Start today by listing the names customers already encounter and the reason each name needs to exist.
Questions people ask
How is a naming system different from a naming framework?
In this article, a naming framework is used to evaluate or generate individual names. A naming system governs the portfolio: which identities should exist, how names relate and who approves changes. The terminology can overlap, so a project brief should define the expected deliverables rather than rely on the label alone.
Can naming rules be written before a rebrand?
Yes — naming rules can be proposed before visual identity work. Begin with the portfolio, customer audiences and intended relationships. Leave room to revise the rules when research identifies recognition worth preserving or a service distinction the proposed structure does not explain.
Does every service need its own logo?
No — a separate logo should be a justified identity decision rather than the default outcome of launching a service. Under the proposed approach, begin with the parent identity and a service descriptor. Consider additional identity elements only when a documented customer or structural requirement supports the extra complexity.
When should naming rules be reviewed?
Review naming rules when an acquisition, service launch, market entry or ownership change tests the existing structure. An exception request is another useful trigger. Keep the review tied to an actual decision; a scheduled meeting should not become an excuse to rename services without evidence of a problem.


