Wie aufwändig ist der Einstieg in so eine agent-fähige Struktur?

Wir starten klein. Meist mit einem klar abgegrenzten Inhaltsbereich, der heute am meisten Ausleitungs-Druck hat — Produkte, Leistungen, Standorte oder FAQ. Der erste agent-fähige Ausschnitt steht in Wochen, nicht Quartalen. Von dort wächst das Modell organisch in Ihrer Geschwindigkeit.

Verlieren wir damit die Möglichkeit, einzelne Seiten individuell zu gestalten?

Nein. Individuelle Gestaltung bleibt möglich, sie verlagert sich nur. Gestaltungsregeln leben stärker in Templates und Designsystem, Inhalte sauber in Feldern. Dadurch bleiben Marke und Bild konsistent, auch wenn dieselben Inhalte an verschiedenen Stellen auftauchen.

Unsere Redaktion arbeitet seit Jahren im klassischen Backend. Ist der Umstieg zumutbar?

Ja, wenn er schrittweise geschieht. Wir verändern das Backend nicht über Nacht, sondern reduzieren und strukturieren entlang der echten Arbeit. Die meisten Redakteurinnen und Redakteure atmen nach wenigen Wochen auf, weil Masken endlich zu ihrer Tätigkeit passen und nicht umgekehrt.

Was ist ein MCP-Server und warum sollte uns das interessieren?

MCP ist ein offener Standard, über den KI-Agenten strukturiert mit Ihren Systemen sprechen können. Für Sie heißt das: Agenten ziehen Inhalte nicht länger unkontrolliert per Scraping, sondern greifen über eine von Ihnen definierte Schnittstelle zu. Sie behalten die Hoheit darüber, was wie erscheint.

Heißt das, wir müssen unser bestehendes TYPO3 ablegen?

Nein. Wir empfehlen nicht den Wechsel des Systems, sondern die Neuausrichtung seiner Nutzung. TYPO3 ist eine hervorragende Grundlage für strukturierte Inhalte und agent-fähige Schnittstellen. Wir ergänzen es genau an den Stellen, an denen Ihre Redaktion heute reibt.

When AI consumes your content: does your team still need a classic CMS backend?

AI agents are increasingly reading your content directly. What does that mean for the role of classic CMS backends in mid-market editorial teams?

22. March 2026

We currently sit in many projects where AI agents read more content than people do. Not in the future, but today. Buying assistants research product data, sales assistants pull company information, employee assistants answer internal questions on the basis of website content. The honest question we ask alongside our clients is uncomfortable: under these conditions, does your editorial team really still need a classic CMS backend in the form we've known for the past 20 years?

The hasty answer is usually “yes, of course”. The honest answer is: it depends what work your CMS backend actually still does, and whether that work is even the right work in an agentic world.

What CMS backends were originally built for

Classic CMS backends are designed for people building pages. An editor opens a page, places an element, drops an image next to it, writes teaser texts, clicks save, navigates to preview, publishes. Every interface element, every permission setting, every workflow is optimised for this act of human page composition.

In a world where AI agents consume content directly and where front-end output is increasingly composed dynamically from structured data, that model is only part of the truth. Content is no longer thought of primarily as pages, but as structured information that gets used in many places: on your website, in your app, in agent answers, in MCP interfaces, in your internal search.

What really changes for your editorial team

We tell clients very clearly that CMS backends won't disappear. But their role is shifting noticeably. The emphasis moves from “building a page” to “maintaining and releasing content”. And that means a different interface, different workflows and different roles.

Your editors will spend less time making layout decisions in a backend, and more time maintaining structured content cleanly: product facts, people, locations, service descriptions, FAQ entries. Output to channels will increasingly happen rule-based. Some of your content will never appear as a classic website page and will still generate revenue, because it gets found through agents.

What we currently recommend to our clients

Our line is pragmatic. We don't tell anyone to abolish their CMS backend. We do tell people to recalibrate it.

1. Think of content as structured

We migrate content step by step from free rich-text blocks into clean fields and types. That reduces input errors, makes content reusable and is the basis for AI agents being able to understand your content at all.

2. Align backend UX with the real work

We slim down backend forms to what your editorial team actually does. Fewer options, clearer workflows, fewer “just in case” fields. A leaner backend isn't less professional, it's simply closer to reality.

3. Build agent-capable interfaces

We extend your CMS with MCP servers and structured APIs. That way agents can access your content without scraping your website, and you keep control of what is published how. This is part of our CMS-as-a-Service platform and is already in production use today.

4. Strengthen editorial governance

If less is decided in layout, more has to be decided in content structure. We help your editorial team shape content models, mandatory fields and approval paths so that they hold up in an agentic world.

Why this isn't a threat to your team

We often see the worry that this shift makes editorial roles obsolete. Our experience is the opposite. Editors who maintain structured content today become more valuable to their organisation, not less. They are the ones determining how your organisation shows up in agent answers. In effect, they decide on digital visibility. That is an upgrade, not a downgrade.

The honest realignment just has to happen. Anyone investing now in content models, clear field structures and agent-capable interfaces creates room to manoeuvre. Anyone who carries on grooming every pixel in the backend loses time to a task that has less and less impact.

[Translate to English:] Aufgeräumter Redaktions-Arbeitsplatz von oben mit gestapelten gedruckten Magazinen neben einem ausgeschalteten Monitor.

A look at your backend through agents' eyes.

Let's talk about your editorial team

If you have the impression that your CMS backend creates more day-to-day problems than it solves, we'd be happy to look at your specific situation together. 30 minutes, no pitch, no slides. We listen, ask questions and sketch out what an agent-capable editorial setup could look like in your organisation.

Book a slot directly →

Häufige Fragen

Was uns Kundinnen und Kunden zu diesem Thema am häufigsten fragen — offen beantwortet.

How much effort is the move to an agent-capable structure?+

We start small. Usually with a clearly bounded content area that today has the most rendering pressure — products, services, locations or FAQ. The first agent-capable slice is in place in weeks, not quarters. From there the model grows organically at your pace.

Do we lose the ability to design individual pages individually?+

No. Individual design remains possible, it just shifts. Design rules live more strongly in templates and the design system, content lives cleanly in fields. That keeps brand and imagery consistent, even when the same content shows up in different places.

Our editorial team has worked in the classic backend for years. Is the changeover reasonable?+

Yes, if it happens step by step. We don't change the backend overnight; we reduce and structure it along the real work. Most editors breathe easier after a few weeks because forms finally fit their work, not the other way round.

What is an MCP server and why should we care?+

MCP is an open standard through which AI agents can talk to your systems in a structured way. For you that means: agents no longer pull content uncontrolled via scraping, but access it through an interface you define. You keep authority over what is rendered and how.

Does that mean we have to drop our existing TYPO3?+

No. We don't recommend changing the system, we recommend recalibrating its use. TYPO3 is an excellent foundation for structured content and agent-capable interfaces. We extend it precisely where your editorial team experiences friction today.