Skip to content

AI agents for small and midsize companies in Germany

I build AI agents that take routine work between your systems off your staff, such as data they copy from one tool into the next. The agents work under written rules, and a person approves each change to live data. I take this on as freelance project work, remote from Frankfurt with on-site days. Let's talk about your needs in a free 30-minute video call.

Portrait of Michael Wutzke, AI Agent Developer in Germany
Michael Wutzke, AI Agent Developer in Germany

What I build for your company

  • Experience with connected systems

    For more than twenty years I have connected systems, from the payment connections of online shops to an existing CRM. I start with the step where your staff copy data by hand today.

  • Agents in client work

    I help a client rebuild its platform with Claude and Codex as coding agents, and I set up agents with roles on a control plane for the same client. The rules on this page come from that work.

  • Live data behind a confirmation

    An agent works on a test system first. A change to your live data waits for a person's confirmation outside the chat, and each approval covers one change.

  • Results checked by a script

    An agent can do the work right and report the wrong number. A read-only script checks each result, and its number counts over the agent's report.

  • Access through MCP servers

    I teach building MCP servers at Claude Hacker House. An MCP server gives an agent access to one of your systems, with the rights you grant it.

What an AI agent does in a small company

An AI agent is a language model that works through a task with tools until the task is done. It can read an order confirmation from an email and enter the delivery date in the customer record of your CRM.

The agent chooses its next step itself. That makes it useful where the input varies, such as emails in free text or PDFs in different layouts. It is also the reason an agent needs limits that a fixed program does not need.

Script, workflow tool or AI agent

Many routine tasks need no AI. Before I build an agent, I compare it with the two simpler options, and the task review uses this table.

ScriptWorkflow toolAI agent
InputOne fixed formatFixed formats from several systemsVaries: free text, scans, different layouts
RuleFixed and simpleFixed, with branchesWritten in words, needs judgment
Who changes itA developer edits the codeStaff edit the flowStaff edit the written rule
Cost per runServer timeServer time and the tool’s licenseServer time and model usage
Typical failureStops at an unknown formatStops at an unknown formatGoes on with a wrong reading, so a check follows each run
Pick it whenThe format stays the sameA fixed path runs across several systemsA person reads and decides today

A task can use all three. A script fetches the files, the agent reads them, and a second script checks the result before anything reaches your live data.

How I keep an agent within bounds

An agent in your company gets the limits of a new colleague on the first day. These are the layers I use in client work:

  • Rights at the system: a database role that only reads, and API keys for the test system.
  • A test system first. The agent runs its jobs there until the trial run shows its results match your staff’s.
  • A confirmation outside the chat before any change to live data. An approval that the agent quotes from the chat does not count.
  • A read-only script that measures each result. When the script and the agent disagree, the script’s number stands and the agent runs again.

A written rule alone does not bind an agent. It follows the rule most of the time, and a machine check catches the cases where it does not. Details: AI agents under the same rules as humans.

Who I am

I am Michael Wutzke, an AI engineer in Frankfurt with more than twenty years in IT and media. At Policen Direkt I designed the interfaces of a contract management portal and connected it to an existing CRM system. Today I help a client rebuild its platform with Claude and Codex, and I teach building MCP servers and virtual organizations of agents at Claude Hacker House. I am also interested in open-source AI models that a company runs on its own servers. Details: Career stages.

How an agent project runs

  1. Free video call

    In 30 minutes we talk about the routine work you want to hand over and the systems it touches.

  2. Task review together

    We go through the task with the table on this page and check which of your systems have an interface the agent can use.

  3. Quote and order

    The review ends with a quote. When you accept it, the build starts.

  4. Build on a test system

    I connect the agent to your systems with the rights of a new colleague and write down the rules it works under.

  5. Trial run

    The agent does the task on the test system while your staff do it as before, and we compare its results with theirs.

  6. Live operation

    The agent works with live data. Each change waits for a confirmation from the person you name.

  7. Handover

    Your team receives the written rules and the checking script and can change both without me.

Questions companies ask

What is the difference between an AI agent and a chatbot?

A chatbot answers in a chat window. An agent acts: it calls tools and systems until a task is done, and for that reason it needs limits that a chatbot does not need.

Which systems can an agent work with?

Systems with an interface, an export or a database the agent may read. A system with only a screen for people is harder to connect, and the review shows whether the effort pays off.

Which AI model does the agent use?

A cloud model such as Claude, or an open-weight model on your own server when data may not leave the company. The page Self-hosted LLMs such as DeepSeek covers the second case.

Can the agents run on open-source software?

Yes. The page Open-source AI agents describes agents with roles on a control plane that runs on your own server.

Which engagements do you take on?

Freelance project work, part time or full time. I work remote from Frankfurt and come for on-site days anywhere in Germany.

Details on the work behind this page

Your AI agent developer in Germany

I am Michael Wutzke, an AI agent developer in Germany, based in Frankfurt. In a free 30-minute video call we talk about the routine work your staff want to hand over, and you learn whether an agent, a script or a workflow tool fits it.

Portrait of Michael Wutzke, AI Agent Developer in Germany

Searches this page answers

  • AI agents for SMEs
  • AI agents for SMBs
  • AI agents for business automation
  • AI agents for business process automation
  • AI agents for business processes
  • AI agents for business operations
  • AI agents business process integration
  • best AI agents for automating business processes
  • custom AI agents
  • custom AI agents for business
  • AI agent use cases
  • AI agent use cases for business
  • agentic AI for small business
  • agentic AI use cases for small business
  • AI agent implementation
  • AI agent implementation guide
  • AI agent implementation strategy
  • AI agent integration
  • AI agent integration MCP
  • AI agent for data entry
  • AI agent to automate data entry
  • AI agent workflow
  • AI agent workflow example
  • AI agent workflow automation
  • AI agents vs automation
  • AI agent vs automation workflow
  • AI agent vs chatbot
  • AI agent vs chatbot difference
  • what can AI agents do for businesses
  • how can AI help small businesses
  • AI workflow automation for small business