Innovation without chaos: standardised individuality
Why innovation in the mid-market doesn't need wild-west freedom but standardised individuality — and how we put this principle into practice.
"Innovation" is one of the big words of our industry. In most organisations we look into, teams first associate it with freedom: "everyone should be allowed to do what they think is right." In our experience, this interpretation rarely leads to innovation. It leads to variance, and variance leads in operations to friction that eventually eats the organisation.
We've spent enough time in chaos in our own 14 years as an agency to say that honestly. And we've taken our lesson from it: innovation grows best where it sits on a load-bearing standard foundation. We call this standardised individuality, and it's the principle that carries our entire offering.
Two common fallacies
The first fallacy is to equate innovation with the freedom of the wild west. Every developer, every project decides autonomously about stack, patterns, and approach. That feels like a fresh start. The costs show up two years later: unmaintainable systems, roles that can't be filled because every onboarding is unique, and an operations organisation that's always running behind.
The second fallacy is the opposite: total standardisation. One platform for everything, no exceptions. That's efficient on the slides, but fails the moment a customer has a real individual need. Then weeks are needed to push an exception through the processes, and months until it's actually lived.
Standardised individuality solves this contradiction by dissolving it instead of choosing a side.
What the principle means in practice
We standardise the foundations radically. And we deliberately leave room where the difference of your brand lives.
What we standardise
Platform, operations, security architecture, release processes, CI/CD pipelines, monitoring, backup, upgrade paths, base extensions, secret management, bot access policies. All of that is the same for all our customers. No customer pays for a bespoke hosting setup. No customer gets a bespoke upgrade procedure because "their case is so special". If we did that, innovations like our Level 5 Agent-Native rollout would not be economically viable.
What we individualise
Content, content models, templates, integrations into your system landscape, automations for your processes, your business logic. This is where the differences arise that make you competitive. This layer is deliberately open, but it sits on a foundation that isn't up for debate.
The ratio is roughly 80 to 20. Around 80 percent of what we do runs in standardised lanes. In the remaining 20 percent the value emerges that your organisation expects from a digital agency. Both parts only work together.
Why this benefits your organisation
For your business, standardised individuality means above all one thing: reliability in operations, without your brand management being constrained.
You get updates faster, because we build them once for everyone and roll them out in a controlled way. You get security at a higher level, because we only have to build it in one place and not 50 times individually. You get innovation faster, because new capabilities like an agent-capable CMS come as part of the platform and not as a bespoke project per customer. And at the same time your brand, your look and feel, your processes, your content can be as individual as suits your business model.
How you'll notice the principle is working
Organisations that have arrived in our model typically have three observations. The first is calm: the same recurring everyday issues disappear. The second is speed: new requirements can be implemented faster because they land on a familiar foundation. The third is clarity in responsibilities: at any moment it's clear what sits at the platform layer, what sits at the CMS layer, and what belongs to the customer's individuality.
For us as a service provider, the model is just as important. We can only deliver production-quality workshops to our customers, run upgrades on weekdays, and bring new capabilities into the field if we are tidy in the standard. Without this tidiness, we'd have similar stomach aches to the teams we help today.
![[Translate to English:] Reihe identischer heller Keramik-Objekte im Studiolicht, bei der ein einzelnes Stück leicht nach vorne versetzt und wärmer getönt ist.](/fileadmin/_processed_/2/6/csm_f1105610729d8e2caceb89f1ab2cd689a34cdcc4840ca4e5db3c30fe74ceb155_95244bf8c4.webp)
If you're stuck between chaos and corset
If you have the feeling of being trapped either in a too-individual mess or in a too-rigid standard corset that doesn't carry your brand, a conversation is worthwhile. We'll show you what standardised individuality looks like with us in concrete terms, and what a transition could look like for your organisation.
30 minutes, no pitch.
Frequently asked questions
What customers most often ask us about this topic — answered openly.
What does this mean for our internal developers?+
Your internal team works on the same standard foundation we do. That makes collaboration, onboarding and knowledge sharing easier. We hand over documentation, ADRs and runbooks so your developers can keep building independently at any time — without being tied to us.
Can we keep using our existing extensions?+
In most cases yes. We review every extension for maintainability, security and compatibility with our upgrade paths. What is justifiable stays. What can no longer be carried we replace with an equivalent standard solution — transparently and documented.
How expensive is the move to this model?+
The transition runs in steps with us, not as a big-bang migration. From the very first iteration you benefit from standardised operations while your individual layer is brought across cleanly. In many cases the costs are refinanced through lower operating effort and the elimination of bespoke solutions.
What happens when we really do have a special case?+
Special cases belong in the individual layer, not in the platform foundation. We discuss every special request at the right place in the model. What needs to stay individual stays individual — and what is generalisable moves into the standard, where everyone benefits.
Does standardisation restrict us in our brand work?+
No, on the contrary. We standardise operations, security and release processes — exactly the things that don't make your brand visible. Look and feel, content models and your business logic stay yours. You gain freedom where it has impact.