FIELD GUIDE / Brand architecture
How to structure a multi-product SaaS brand system
Separate the shared rules from the product-specific decisions.
SaaS founders & brand designers
Datamotive / 3 products · 16 documented foundations
A product family needs enough consistency to feel like one company, and enough distinction to help buyers choose. Datamotive connects three cloud products through a shared identity, diagram standard and website. This playbook turns those visible decisions into a workflow you can adapt.
Map the buying decision before the palette
Write down the problem each product solves, the people who evaluate it and the evidence they need. Separate the company promise from product-specific claims. If two products sound interchangeable in this table, another colour will not solve the positioning problem.
Make a three-column brief: product, buyer question, proof. Test it with someone outside the project before drawing a product mark.
Separate shared foundations from product choices
At Datamotive, the hexagon, cube and teal preserve recognition. Typography, spacing and layout behaviour connect the products. A useful starter structure has shared base values, semantic roles such as surface and action, and explicit product overrides. Keep the override list short enough to review.
Create one shared product-page template. Swap the product name and content first; add a visual difference only when it helps identification.
Give diagrams a grammar
A technical diagram should explain a relationship. Define what a node means, what an arrow means and which direction a reader follows. Use labels alongside colour. Keep replication, recovery and return paths distinct through line style and wording; a decorative arrow should never imply a technical capability.
Ask an engineer to trace one complete journey through the diagram. Record every correction before polishing it.
Carry the same decisions into production
The Datamotive case documents 16 foundations, from logo use and colour tokens to diagrams and developer handoff. Treat the website, sales deck and social graphics as tests of those decisions. Name a token by its role and document valid foreground/background pairings rather than leaving future teammates to guess.
Review a product page, a deck slide and a diagram together. Fix the shared rule when the same inconsistency appears in more than one place.
THE HANDOFF CHECK
Ready to put it to work?
Use this checklist as you review your own project.
0 of 5 checked
BACK TO THE RECEIPTS
The method, in context.
See the actual design decisions, original artwork and documented outcomes in the Datamotive case study.
An adaptable guide informed by the linked case study. Client source files are not included.