AI Agents

Use AI for your business.

I build AI agents for marketing, sales and internal teams as a temporary team member: in your systems, aligned with IT and the AI team, approved by your people.

  • I buildconcept, code and tests, in your systems
  • Your team approvesin the review queue, without writing prompts
  • IT signs offarchitecture and security; deployment and operations with me on request
Plan an AI projectA checked project plan for your idea in 10 minutes, free of charge.

Felix Zeeb, Zurich. Since 2019 I have been building marketing and sales systems from SMEs to large groups, today mostly AI agents. In my own companies I sell myself, for example at NativeAI, with a B2B CRM I built. About me

Companies I have had the privilege to work for since 2019: Swisscom · NZZ · Allianz · Suva · PwC · CH Media · Groupe Mutuel · Mobility and many more. Reference calls on request.

How I build an agentic setup

Anatomy of an agent service

The same architecture behind the sales agent, the multichannel agent and the Business Context Layer.

Example View
Channels E-mail Web chat WhatsApp Teams / Slack On-site In-app WhatsApp only with opt-in and approval by your data protection. Brief InboundAuth, rate limit,queue Draft Team reviews and approves Guardrails in code, not in the prompt Agent service Roles: brief, draft, variants Tools: templates, brand, file the draft Memory: campaign history Company knowledge Brand guidelines, tone of voice, templates. Customer data stays in your systems. asks context Language model Switzerland or EU, on request your infrastructure. No training data. If it fails: fixed flow. Your systems CRM and ERP Marketing automation Website, shop and app Data warehouse (read only) Through your existing platforms, vendor-neutral. reads & updates Every write access only with approval,as a service identity with minimal rights. Log PII mask Tracing and quality assurance Every conversation: review queue, test cases, regression test before every release. Learning loop Feedback and errors become test cases, the agent gets better. Logs self-hosted or EU, with retention periods. In your tenant. Code and tests belong to you.

Plan your project and experience how I work.

Data and accountability

What can go wrong and what prevents it

Risk Control in the setup The agent sends nonsense to customers. Guardrails in code and tests before every releasecatch errors, and a person approves beforeanything goes out. Customer data ends upat the model provider. Models in Switzerland or the EU withouttraining on your data, self-hosted forsensitive data. Personal data is masked. I am unavailable orout of capacity. Code, runbook, tests and infrastructure staywith you. Your team is prepared from day oneshould you want to end the collaboration, andshould I suddenly drop out, a partner I haveworked with for years steps in. IT blocks it. Sign-off by IT. Architecture and securityagreed up front. Service account withminimal rights instead of full access. Regulated industry:insurance, banking, health. revFADP, FINMA, professional and insurance secrecybuilt in from the start; approvals in several stages. Dependence on the model provider. You use the model of your choice and canswitch it at any time; no lock-in,code and infrastructure stay with you. The team does not use the agent. Usage and approval rate measured from day one;the team shapes it in the review rounds.
The agent sends nonsense to customers.

✓ Guardrails in code and tests before every release catch errors, and a person approves before anything goes out.

Customer data ends up at the model provider.

✓ Models in Switzerland or the EU without training on your data, self-hosted for sensitive data. Personal data is masked.

I am unavailable or out of capacity.

✓ Code, runbook, tests and infrastructure stay with you. Your team is prepared from day one should you want to end the collaboration, and should I suddenly drop out, a partner I have worked with for years steps in.

IT blocks it.

✓ Sign-off by IT. Architecture and security agreed up front. Service account with minimal rights instead of full access.

Regulated industry: insurance, banking, health.

✓ Swiss data protection act, FINMA, professional and insurance secrecy built in from the start; approvals in several stages.

Dependence on the model provider.

✓ You use the model of your choice and can switch it at any time; no lock-in, code and infrastructure stay with you.

The team does not use the agent.

✓ Usage and approval rate measured from day one; the team shapes it in the review rounds.

For MarTech and AI teams

Who is responsible for what?

During the build I work in your repository, tracing and eval stack, and where they do not exist yet, I set them up for you. As long as I run operations, I deliver releases with a report. After that:

TaskBusiness teamMarTech or AI teamITMe, until handover
Daily operations: review and approve drafts●
Flag errors, maintain knowledge and examples●
Test cases and evaluation●●
Releases after a passed regression test●
Code review of every pull request●●
Deployment, keys and access, monitoring●

responsible on request

Repository, runbook and infrastructure as code are with you from day one.

Example: review of a planned agentic AI implementation with the AI team of a telecoms group.

Agents that measurably improve with every conversation

The learning cycle

Generate, evaluate, optimise, also after go-live: live data shows cases nobody thought of. On the right, the report before every release.

Release v12 Business team reviews, without writing prompts
  1. ConversationThe agent works in daily operations.
  2. TracingEvery case is logged.
  3. Automatic evaluationA checker model rates every case.
  4. Review by the business teamThe business team reviews without writing prompts.
  5. Test caseNotable cases become test cases.
  6. OptimizationExamples and rules are improved.
  7. Regression testWith synthetic users against all cases.
  8. ReleaseAnd round again.
Regression reportSample values

Drafts sent without changes. The share of drafts the team approves without correction. When it rises, the team saves time and the agent gets content and tone right. The other values must not drop meanwhile.

Drafts sent without changes
61%
Answers correct to company knowledge
88%
Tone of voice and brand
90%
Ø review rounds until passed (lower is better)
Ø 1.8
Handover to a person when needed
84%
Services · one system, three layers

One system, three layers

Data, CRM and AI belong together and depend on each other: one stack, not a menu of offers.

The context layer as the foundation

Everything that defines your company, in one place: data warehouse and events, ERP, website, shop and app, brand guidelines, template and content libraries, product knowledge and the definitions of your audiences. Without this context, agents guess.

CRM as the engine

Salesforce Marketing Cloud, HubSpot, MoEngage, Dynamics. Lifecycle, journeys, triggers.

Agentic AI as the accelerator

Request agents, campaign agents, assessments. In your channels, with a human gate.

Scrolling pulls the system apart
Context layerEverything that makes your company
Data warehouse
ERP
Website · Shop · App
Brand guidelines
Libraries
Audiences
CRM & marketing automationSFMC · HubSpot · MoEngage · Dynamics
Agentic AIRequests · campaigns · assessments
E-mail
Web chat
WhatsApp
Teams / Slack
On-site
In-app
Open source on GitHub

Building blocks for agentic systems, open source

I developed these Claude skills myself and make them available to everyone who works with agentic systems. Anyone who wants to develop them further with me is warmly invited.

All repositories on GitHub ↗

Try it yourself

The AI Project Planner is an agentic flow itself: one agent asks, a second writes the plan, a third checks it. You get a plan including an effort estimate for internal use and see along the way how I build such systems.

CONTACT

Let's talk about your project.

Tell me about your idea: on a video call or over lunch, in Zurich and across German-speaking Switzerland. I'll tell you straight away how I would build it.

I reply within one working day with a proposed time.

Prefer email? felix.zeeb@geistzeit.ch