GmbH Guru

A platform that collects knowledge and practical tools for running a company carries two demands at once. It has to look professionally sound, because its subject matter comes from an advisory field. It also has to stay approachable, because the people reading it are business owners looking for an answer rather than a treatise.

There is a second layer. An offering like this sits next to an existing company. It needs its own address, its own name and its own appearance, while still making sense next to where the expertise comes from. In naming work that means four requirements at the same time: the name has to be easy to say, hint at the subject, be legally available and work as a domain. Those four rule each other out more often than expected.

The hardest decision comes early and concerns tone. Tell a technical subject in a friendly voice and you risk not being taken seriously. Tell it strictly and you lose everyone approaching it for the first time. Everything that follows, from imagery to the structure of the platform, is decided against that choice.

In this project the answer took the form of a character. The GmbH Guru was designed as a mascot, a personification of the offering itself. The head of the figure draws on Mr Klaus Viehbacher, LL.M., which gives the brand a personal and at the same time professional note.

Using a character to carry a brand has a practical advantage that only shows up in daily use. A character can be reused. A logo sits on a page; a figure can explain something, greet a visitor, point at a detail or illustrate a situation. That gives a platform a visual vocabulary without inventing a new one for every topic.

For this to hold, the figure has to be governed early: which poses exist, which crops are allowed, how it relates to text, how it stays legible at small sizes. Without those rules, variants accumulate over time that no longer belong together. Because the figure is modelled on a real person, a second requirement applies: every application has to portray that person appropriately.

Projects that run from naming through to launch share one trait. Decisions made during the brand phase turn into technical requirements months later. A colour system has to survive a contrast check, a wordmark has to work inside a navigation bar, an image language has to hold up once an editorial team maintains the content.

Once webinars and bookings enter the picture, the centre of gravity shifts. A site with a booking section is no longer a brochure but a sequence: find the offer, understand the date, register, receive a confirmation, cancel if needed. Every one of those steps has edge cases, and the edge cases decide whether the offering is usable in practice.

Platforms of this kind are rarely decided at launch. They are decided in the months after it. Anyone publishing content and dates regularly needs input forms that need no manual, and a set of rules that keeps the design intact when many hands work on it. So the end of such a project is not only the finished platform, but the handover of the rules by which it keeps growing.