Christoph Sauerborn

For agencies still rebriefing their AI

Your agency’s AI foundation, installed in 30 days.

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

I install shared client context, reusable instructions and approved connections to reduce that repetition. Your team creates, checks and finishes the work.

See what gets installed
Prefer a smaller first step?
Christoph SauerbornBuilt and handed over by me.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 offerAgency AI Infrastructure — Install

Claude Code & Cowork.
Your agency’s own accounts.

What gets installed

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.Explain the answer, 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

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. Your team prepares and checks the context; I set up its home and loading.

Less explaining what is already known.

One place to keep it current.

Versions & shared updates

Brand files and working instructions have a shared source with a history of changes. Your team updates that source, reviews what changed 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 tool connections

Agreed connections let the team’s AI retrieve information from 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

Roles define access to each client’s material. A named owner, review rule and onboarding workflow give the team a way to keep the system 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.

  • OpenAI
  • Anthropic
  • Hermes Agent
  • OpenClaw
  • GitHub
  • Cloudflare
  • Brixon

Agency AI Infrastructure — Install

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

You make the access and workflow decisions. I build the agreed infrastructure and hand it over into your agency’s own accounts, with the routines to keep it running.

The installation, in concrete terms.

  • A shared home for your contextYour agency BrandOS and first two client contexts, with automatic loading for Claude Code and Cowork.
  • Access and agreed connectionsA role and access model, plus up to three approved system connections.
  • Instructions the team can reuseYour first three Skills in an installable Plugin, with an update and review routine.
  • A system your team can carry forwardThree reference setups, a named owner, governance and an onboarding workflow.

Your team supplies and checks the brand context. Content, presentations, creatives and websites are work your team produces with the system; they are outside the Install.

  1. 01 / You decide

    Kick-off & intake.

    A 30-minute kick-off, your inputs and a specification you confirm in writing.

  2. 02 / I build

    The agreed system.

    Context loading, access, connections and Skills, built from those decisions.

  3. 03 / We hand over

    Into your accounts.

    Your GitHub organisation. Your Cloudflare account. Your credentials, entered by you.

Purchase to handover: within 30 days, including the time for your inputs. The 14-day fix window starts at handover. Your team then runs the next onboarding using the delivered workflow.

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 programmed 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. This was not a Builder-only result, and 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 have worked in SEO since fourteen, founded an agency at nineteen and put AI to work in critical processes at Bosch. Today I build and hand over the agreed foundation for other agencies.

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.

Want AI to start with your client’s brand context?

Build a client BrandOS
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

A smaller first step

Build your own
AI foundation.

Start with one client’s brand context, or follow the plan to build your agency’s shared infrastructure yourself.

BrandOS Builder €9

Give AI the client context you keep re-explaining.

Work through one client’s offers, audience, voice and rules with the guided Builder. Turn verified material and decisions into reusable BrandOS files. Build a separate context for each next client; you can use it for your agency’s own brand too.

Build a client BrandOS

Agency AI Infrastructure Blueprint €99

Build the agency setup around your brand context.

Follow the build order for shared context, access, connections and reusable Skills. You get the manual and templates to set it up yourself in your own accounts.

Get the AI Infrastructure Blueprint

Included if you choose the Install.

Before you decide

Questions about
your AI install.

Will you create our client work?

I install and hand over the agreed infrastructure. Your team uses it to create content, presentations, creatives or websites. Those deliverables are not part of the Install. New information, decisions and the final professional review stay with your team.

What do we need before the Install?

A named system owner, a usable agency BrandOS and the first two client contexts, prepared and checked by your team. You create your agency’s GitHub organisation and Cloudflare account, choose access and approved connections, and enter your own credentials at handover. The full offer explains the supported environment and all inputs.

Do we have to buy the Builder or Blueprint first?

No. You can prepare your brand context with the Builder or your own method. The Blueprint is included with the Install as the manual. A previous Blueprint purchase is not credited toward the Install.

Which AI environment does it support?

The standard Install covers Claude Code and Cowork, with automatic context loading checked on three reference setups. The supported environment is agreed in the written specification. Other environments and extra connections are scoped separately. Your AI and service accounts are separate costs.

What happens after handover?

Your team runs and maintains the system. You receive the Blueprint, component recordings and troubleshooting notes. For 14 days from handover, one written fix round covers reported acceptance-check failures in what I installed. Credentials, your internal systems and ongoing support are outside that scope.

Can I read everything before deciding?

Yes. The full Install offer sets out the scope, responsibilities, timing and acceptance checks. Questions can be raised in writing before payment. There is no sales call. The purchase is one-time, net EUR, with applicable VAT shown at checkout. 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 in your accounts.
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