Christoph Sauerborn

For agencies whose team already uses AI

Your agency needs a system behind the AI your team already uses.

Every new chat starts without your clients’ context. So someone explains the brand again, pastes the same PDF again and fixes the same tone again.

I build the system that holds that knowledge once: each client’s BrandOS, loaded into your team’s AI through MCP, shared Skills for recurring tasks and access per client. Your team keeps creating, checking and finishing the work.

See what gets installed Christoph SauerbornI build it with you and hand it over myself.Christoph Sauerborn · AI Systems Engineer for Agencies
A shared starting point
An ivory architectural model connects an open book, creative outputs and two people on one shared foundation.
Shared context. Agreed instructions. Connected systems.
People doing the work.

From a client brief to work ready to send

The first AI draft is only
part of the job.

Floating ivory drafts, source documents and a feedback bubble surround two paper figures reviewing the work together.

Client brief First AI draft

Then your team spends time on…

  1. Finding the missing context.Track down the current offer, brand rules and past feedback.
  2. Checking the first draft.Read it, verify the facts and compare it with the brief.
  3. Asking a colleague. Waiting.Get the detail or decision needed to move the work forward.
  4. Rewriting and prompting again.Pass the answer back to the AI, correct the work and produce the next version.
  5. Reviewing and resolving feedback.Check the revision with the team. Work through another round if needed.

And sometimes, back around again.

Internally checked. Ready to send.The first draft was one step. Your team carried it through.

A better starting point for the next task

Automate context work
for your AI.

The aim is less repeated work between the client brief and an internally checked version ready to send. Shared context and instructions can reduce searches, repeated briefing and corrections caused by missing or outdated information.

The client knowledge.

Shared brand & client context

Current offers, audiences, tone and design rules live in shared brand files, and your team checks them before anyone relies on them.

Less explaining what is already known.

One place to keep it current.

Versions & shared updates

Brand files and working instructions live in a versioned repository: every change has an author, a review and a way back to the earlier version. Your team updates that source and makes the approved version available to the setups that use it.

An update reaches beyond one person’s laptop.

The way you do the task.

Skills & update routines

A Skill records the inputs, working steps and review rules for a recurring task. Colleagues can use the same maintained instructions and improve them together.

Reuse an approach your team has agreed on.

The information you need.

Approved MCP connections

MCP connections can let the team’s AI look things up in approved systems, such as file storage or a project tool, within the access you allow.

Fewer manual searches and handovers.

Who can use and change it.

Access & ownership

Shared AI context does not mean everyone gets access to everything. Roles set who can read, change and approve each client’s material; a named owner, a review rule and an onboarding workflow keep it current.

A shared setup your agency can maintain.

Still your team’s job

New information. Judgement. Final review.The system gives people a shared foundation to work from. They still do the client work.

Agency System Install

Every client job starts with
what your agency already knows.

Today that knowledge sits in a few heads and a lot of old chats. After the Install it sits in one system your team’s AI works from, and I build it with you.

Three client brands, ready from the first prompt.

Each gets its own BrandOS. Your team’s AI loads it through MCP, so the brand guide stops living in copy and paste.

The Skills your team keeps asking for.

Core Skills for GitHub and brand work, so recurring tasks run the way your agency agreed on.

Your tools, connected.

Your own MCP portal. I connect up to five of the systems you already use, and your team can add more.

Built with you in three calls.

Kick-off, mid-point and handover. It ends with a functional check of what we set up.

€3,990 net one-time, or 8 instalments of €599 net (€4,792 in total). Continued operation of Brand Center, the Feedback tool and the Skills costs €199 net per month, including the three brands set up in the Install, plus €29 net per month for each further brand; it starts after the handover and runs for at least six months. A fixed package: existing content is not migrated, and your agency brings the sources, access and one owner. It is not available to buy yet.

See what gets installed
Christoph Sauerborn on stage, pointing at a slide that reads: Context is the difference.
Christoph Sauerborn
AI Systems Engineer for Agencies

Why I build this

My AI account managers got the drafts to roughly 80 percent.

In my own agency I built autonomous agents, one AI account manager per client. The drafts reached roughly 80 percent. That is okay. It is not first-class.

Getting those drafts to first-class took almost as long as doing the work by hand. So I stopped trying to replace the person and started giving the person what the AI was missing: the client’s context, agreed instructions and the right tools.

At Brixon, different context and setups had given us inconsistent results, and that became BrandOS. We had tried ordinary folders, prompt libraries and custom agents first. What held was current brand context and focused Skills that the whole team works from.

The moment I knew it worked: a non-technical colleague built a coded qualification questionnaire on a client’s website, emails included, in the client’s brand and tone, for a subject she did not know. She directed the AI and did the work herself, using our wider internal setup with task-specific Skills. A questionnaire or website is not part of the Install.

I started doing SEO at fourteen, founded a full-service agency at nineteen, trained as a mechanical engineer at RWTH Aachen and worked in Bosch Industry 4.0.

More about my background

Three ways to start

Pick the step that fits where your team is now.

Each one stands on its own, and none is required before another.

For one brand

BrandOS

Your brand in every chat, from the first message.

  • Generated from your website, profiles and documents
  • Loads into your AI through MCP
  • Preview and edit it in Brand Center
  • Self-service, one year of access

€29net, one-time, one year of access

Not available to buy yet.

See BrandOS

For teams working in files

Marketing Engineering Starter Kit

GitHub for the files your team makes with AI.

  • Setup Skill and GitHub workflow Skill
  • Prompts so your AI helps along the way
  • Versions, reviews and a way back
  • You set it up yourselves, in the terminal

€129net, one-time, licence per company

In preparation. Not available to buy yet.

See the Starter Kit

For agencies of 3 to 30 people

Agency System Install

Your agency’s shared system, built with you.

  • Three client brands with BrandOS
  • Core Skills and your MCP portal
  • Three calls from kick-off to handover

€3,990net, one-time, or 8 × €599 net (€4,792 total)

Not available to buy yet.

See what gets installed

Prices exclude tax. Any applicable tax is shown at checkout before you pay. None of the three is available to buy yet.

Before you decide

Questions before
you pick a route.

Will you do our client work for us?

No. Your team creates, checks and finishes the client work. Each route gives your team brand context loaded into its AI, a shared way of working on files or a set-up system to work from.

What does each route cost?

BrandOS costs €29 net, one-time, with one year of access. The Starter Kit costs €129 net, one-time. The Install costs €3,990 net one-time, or 8 instalments of €599 net (€4,792 in total). Continued operation of the Install costs €199 net per month, starts after the handover and runs for at least six months. Prices exclude tax.

When can we buy?

BrandOS becomes available first. None of the three is available to buy yet; each page opens its checkout when its route is ready.

Do we have to start with one route before another?

No. Each route stands on its own and can be bought directly. The Starter Kit works with the BrandOS MCP; if you do not have BrandOS yet, it is offered in the Kit checkout. Earlier purchases of BrandOS or the Kit are not credited towards the Install.

Which AI tools do they work with?

BrandOS, the Starter Kit and the Install work with Claude, ChatGPT and Copilot.

Is there a sales call?

No. There is no sales call, application or demo booking. When a route is ready, you buy it through the checkout on this site. The Install has three delivery calls after purchase: a kick-off, a mid-point call and the handover. All sales are final.

From a quick draft to work ready to send

Finish client work with
less repeated briefing.

I install the shared foundation your team works from.
Your team uses it to create, check and finish the work.

See what gets installed

Follow the work first? Read about my weekly agency email