Brand architecture for a business with multiple services
Brand architecture explains how the main business, service lines and products relate.
AI-assisted practical guide · Editorial approach
The useful starting point
Brand architecture explains how the main business, service lines and products relate. Start with how customers choose and how the team sells, then decide which names need independence. A diagram should make navigation and ownership easier, not create extra brands without a business reason.
Understand the decision
Inventory every published name, logo and service description. Identify where customers encounter inconsistent relationships or cannot tell who delivers the work. Compare a shared master brand, named service lines and more independent products against audience overlap and operational ownership. Keep future possibilities separate from offers you can actually deliver now.
A practical approach
Write the decision before commissioning the asset. List the audience, the choice they face, the alternative they use today and the evidence you have. Separate observations from assumptions: a sales note is useful evidence of one conversation, not proof of an entire market. Compare a small number of viable directions against the same criteria. Ask a colleague who was not involved to explain the chosen direction in plain language. If they cannot, simplify the brief before refining the presentation.
- Map existing names and their owners.
- Identify shared and separate audiences.
- Choose a naming hierarchy customers can explain.
- Update navigation and documents alongside the diagram.
Illustrative example
A consultancy offering research, design and implementation to the same buying team might use one main brand with clear service labels. An independently operated software product could need its own identity and support route. The distinction comes from customer and operational needs rather than a desire for more logos.
A mistake to avoid
Avoid giving every internal team a public sub-brand. Customers should not have to learn your organisational chart to understand the offer.
What to review
Review whether visitors can identify the responsible business and whether sales teams use names consistently across proposals and pages.
Turn the guide into a working brief
Keep a one-page decision log containing the chosen audience, promise, proof, exclusions and unresolved questions. Assign an owner to each missing fact. Test the direction in one real touchpoint, such as a proposal introduction or service page, before rolling it across the business. Record what confused people and the changes you made. Revisit the decision when the offer or audience changes; do not change it merely because a new campaign needs a headline.
Common questions
What should I prepare before asking for help?
Start with this checklist: Map existing names and their owners. Identify shared and separate audiences. Choose a naming hierarchy customers can explain. Update navigation and documents alongside the diagram. Add your business context, existing materials and the decision you need to make. A useful initial brief can include uncertainty; you do not need to invent answers before discussing scope.
How should I judge whether the work helped?
Review whether visitors can identify the responsible business and whether sales teams use names consistently across proposals and pages. Keep the observation period and definitions visible. Use the responsible team's evidence alongside the website journey; do not attribute every change in results to one asset or article.
Sources & scope
AI-assisted practical guide. Examples are illustrative; business-specific facts and sector claims need the responsible owner’s approval.
- Google Search Central: helpful, reliable content
Reference for useful content, truthful authorship and evidence. The business methods and illustrative examples in this guide are original editorial material.
Use this guide to start your brief.
Share your business context, existing materials and what is still unclear. The guide title will be included so the conversation starts with the right problem.
Prefer email? Send a brief with this guide’s context.