Home/Pune practice/Brand architecture
Service · architecture
Seven divisions should not sound like seven companies
Diversified groups usually have the opposite problem to single-product firms. There is plenty of material. Every division made its own, and a customer meeting three of them meets three different companies.
Untangle your group story See the structure
- Typical duration
- 8 to 12 weeks
- Built for
- Groups with 3 to 10 businesses
- Output
- Group narrative plus modular divisional system
- Solves
- Inconsistent introductions, invisible group strength
Diversified engineering group · architecture
Seven divisions, seven different companies
A group with seven business divisions. Each used a different presentation, a different visual style and a different version of the company introduction.
Customers were confused about what the group actually was. Employees were not much clearer. Cross-selling was near zero because nobody could introduce a sister division credibly, and the group's real advantage, its combined capability, was invisible in every meeting.
One corporate story, then a modular communication system per division. A shared opening that any salesperson could deliver, followed by the technical depth relevant to that audience.
Sales teams could introduce the group consistently and then move into their own detail. The businesses retained their individual expertise. The market finally saw the strength standing behind them.
The group was not weaker than its competitors. It was simply harder to understand, and in a tender that reads as the same thing.
The structure
Shared above the line, specific below it. The group story is fixed and identical in every division's material. Beneath it, each business keeps its own proof, its own applications and its own technical language.
The discipline is that nobody may edit the top box. Divisions get complete freedom below it and none above it, which is the only version of this that survives eighteen months.
The practical test: can a salesperson from the smallest division open a meeting for the largest one, credibly, in ninety seconds? If not, the architecture has not landed yet.
What gets built
The group narrative
Two hundred words that every division opens with. What the group is, what holds it together, and why that combination is worth something to a customer.
Naming and endorsement rules
Which businesses carry the group name, which are endorsed, which stand alone, and what happens to the next acquisition.
A modular presentation system
A shared opening block, then division-specific technical modules that slot behind it. One deck to maintain, seven meetings to serve.
Cross-referral material
The one-page each division uses to introduce a sister business without overclaiming. This is where the commercial return usually shows up first.
A unified capability document
The group's combined equipment, certifications and applications in one place, for tenders and large-customer conversations.
Governance
Who approves what, where the templates live, and how a new division gets brought in without a fresh redesign.
Before you ask
Our divisions compete internally. Will this survive that?
It has to be built expecting it. The architecture works when each division gains something visible from it, usually cross-referral and credibility on large tenders. If it reads as head office imposing uniformity, it will be ignored within a quarter and I would rather design against that from the start.
Should the group name go on everything?
Not always. Where a division serves a very different market or carries its own equity, endorsement rather than absorption is usually right. That judgement is most of the work.
We are about to acquire another business.
Then this is well timed. Architecture decided before an acquisition is far cheaper than architecture retrofitted after one, and the integration communication becomes a straightforward exercise rather than an improvisation.
How many versions of your introduction exist?
If the honest answer is one per division, there is a fairly contained piece of work here with a visible commercial return. Worth a conversation before the next tender.
Untangle your group story See case studies
Kunal Waghmare · Padmavati Hills, Mokai Vasti, Bavdhan, Pune, Maharashtra 411021
office@quiamo.com · +91 90216 02686