Christoph Sauerborn

For agencies still rebriefing their AI

Your team already uses AI. Your agency still needs a system.

AI gets your team to a draft. Finishing client work can still mean finding the same facts, explaining the same decisions and filling the same gaps.

I install the foundation underneath your team’s AI: versioned client context in BrandOS, Skills for recurring tasks and role-based access per client. Your team creates, checks and finishes the work.

See what gets installed
Prefer a smaller route?
Christoph SauerbornI do the build and the handover 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.

The main offer · working nameAgency System Install

Being prepared for release.
Not available to buy yet.

About the Install

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.
Illustration: the work between one prompt and the next.

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.

Why context comes first

80 percent is okay.
It is not first-class.

In my own agency I built autonomous agents with one AI account manager per client. By my own estimate, the drafts reached roughly 80 percent, which is okay but not first-class, and getting AI drafts to first-class quality took almost as long as doing the work by hand. That estimate comes from my own experiments; it is not a measurement, a market fact or a client result.

So the context and rules every AI works from come first. Automation is used only where a step is suitable and its inputs are reliable; judgement, review and the final call stay with your team. Automation does not fix bad inputs. It distributes them faster.

A better starting point for the next task

Make client context
available to 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. I name an AI environment as supported only after my own end-to-end test of it has passed.

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 · working name

Get your agency’s AI system
ready for the team.

I configure the shared system for the client work we agree on. The planned scope: client workspaces and approved brand sources, released Skills that fit that work, named supported connections, access rights, owners and the routines to update, review, restore and hand over. Your agency supplies the sources, access, approvals and an accountable owner.

In preparation and not available to buy yet. The exact boundaries, terms and price are set out before it is offered.

See what gets installed
Christoph Sauerborn working at his desk.
Christoph Sauerborn
AI Systems Engineer for Agencies

Why I built this

A colleague built the
client’s questionnaire.

One of my non-technical colleagues built a coded qualification questionnaire on a client’s website, including the emails that went with it. She directed the AI and did the work herself.

She used our more extensive internal setup, with task-specific Skills and workflows. A finished questionnaire or website is not part of the Install.

That is the work I care about: the person responsible for the task having the client knowledge, instructions and tools to carry it through. BrandOS and the shared infrastructure grew out of building that environment at Brixon.

I started doing SEO work at fourteen and founded an agency at nineteen. I trained as a mechanical engineer at RWTH Aachen and worked in Bosch Industry 4.0. Now I am preparing that foundation for other agencies as the Agency System Install.

More about my background

A small, real piece of the system

The BrandOS design rule
used on this page.

This excerpt comes from my own brand. For agency client work, start with one client’s verified brand material and keep each client’s context separate.

guidelines/design.mdMy BrandOS
Cards, inputs, chips and badges have generous radii, hard ink borders and down-right offset shadows without blur.
From my REAL BrandOS

Two smaller routes

Two smaller routes,
each on its own.

Neither is a required first purchase. Both names are working names, and neither route is available to buy yet.

BrandOS Light

Brand context for one client brand, prepared for you.

You supply the client’s website and permitted documents and name one approver. I prepare a source-based BrandOS, including the design context that already exists, and mark what is missing instead of inventing it. You approve it and receive it as a dated export and through an MCP connection, then use it on one real task. It is for your own use, not shared team access. I name an AI environment as supported only after my own end-to-end test of it has passed.

Not available to buy yet.

About BrandOS Light

Marketing Engineering Starter Kit

GitHub templates and workflows for your agency’s client work.

For agencies with approved brand context that want to set up shared client work themselves: two repository templates, four workflows (start, review, hand over, restore) and one complete exercise, so a second person can review and take over related client files. It runs on GitHub, and your team does the setup.

In preparation. Not available to buy yet.

Before you decide

Questions about
the three routes.

Will you do our client work for us?

No. Your team creates, checks and finishes the client work. Each route gives your team prepared context, a shared way of working or a configured system to work from.

When can we buy?

BrandOS Light, the Starter Kit and the Install are being prepared, and none is available to buy yet. Once one is ready, its scope, terms and price are stated before checkout.

Do we have to start with one route before another?

No. Each route stands on its own. The Starter Kit needs usable, approved brand context, which can come from BrandOS Light or another source. The Install reuses any work your agency has already done with Light or the Kit.

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. 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