Skip to content
In-house team training

No-Code AI Agents Training

Hand the processes your team still runs by hand to an AI agent you build yourself, without code. Everyone leaves with one running on a real task.

Rebuilt on your team's work

Starting point
New to AI agents
Length
½, 1 or 2 days
Delivery
On site, Remote, Hybrid
Group size
5 to 20 participants
See all courses

Run privately for your team, on dates and at a length that suit you.

What your team will be able to do

Every module ends with something participants can repeat on Monday morning in their own work and tools, so the team gets more done without adding people.

  • Build something that runs

    Leave with a working agent handling a real task from your own week, built around a process of your own.

  • Pick the right task

    Tell the processes worth automating from the ones where the automation becomes the new problem.

  • Connect your systems

    Wire an agent into the apps and records your team already uses, with sign-off placed where it belongs.

  • Test before trusting

    Try to break your own agent deliberately, before it gets the chance to break something of yours.

  • Contain what goes wrong

    Set out what it may do unsupervised and what stops for a person, then configure that rather than hope for it.

  • Own it afterwards

    Know who maintains it, what it costs to run, and how the team would notice if it stopped working.

Is this course right for your team?

Who it is for

  • Operations people already keeping a stack of repetitive processes running by hand.
  • Finance, HR and administrative teams with well-defined work that never gets prioritised for real software.
  • Team leads deciding whether to let their department build these things at all.

What to have ready

  • No programming experience whatsoever.
  • A laptop, and permission to sign up for the platform we use on the day.
  • One process you know inside out and would like to stop doing by hand.

What the course covers

Most of the time goes on hands-on exercises. Module order and depth are set for your group before the first day.

75% hands-on
Module 1

What an agent is, in plain terms

From half a day
  • An agent without the jargon: a task, some tools, and a decision at every step
  • How this differs from the rule-based automations your team may already run
  • The kinds of platform available, grouped by what each is good at
  • What this category does today, and what is still only a convincing demonstration
Module 2

Building your first one

From half a day
  • Picking a first task small enough to finish and real enough to matter
  • Putting one together out of blocks, one step at a time
  • Trying to break it on purpose before anybody else gets to
  • Switching it on, and deciding who else is allowed to use it
Module 3

Connecting it to your work

From 1 day
  • Mail, calendar, storage and whatever else your process already touches
  • Giving it your own documents and records without giving it everything
  • What sets it off: a schedule, a message, a file appearing somewhere
  • Where a person signs off, placed so it does not stall the whole thing
Module 4

When it goes wrong

From 2 days
  • The silent failures, which are the expensive ones
  • A weekly look at what it did, in a form somebody will keep doing
  • What each run costs, and how that changes once it becomes popular
  • Who owns it after the person who built it changes jobs

Choose how far the team goes

Every length uses the same modules. A longer booking takes the team further through the same curriculum.

Essentials

Half a day

A morning that ends with everybody having built an agent that runs, and a clear view of what this kind of tool is for.

Modules covered

  • What an agent is, in plain terms
  • Building your first one

Core

1 day

Adds the connections that put an agent to work: your apps, your data, and the approvals in between.

Modules covered

  • What an agent is, in plain terms
  • Building your first one
  • Connecting it to your work

Complete

2 days

Adds what happens when one goes wrong, what it costs to keep running, and who in the team owns it once the enthusiasm has moved elsewhere.

Modules covered

  • What an agent is, in plain terms
  • Building your first one
  • Connecting it to your work
  • When it goes wrong

We settle the length when we talk about your team, and it can still change afterwards.

Your team's version of this course

Your version builds agents for tasks your team repeats every week, on the platform your organisation allows, connected to the systems you already use. If your IT has licensed a platform, we build on that one.

How a booking works

What gets adjusted

  • Depth of each module
  • Your tools, code or content
  • Group size and seniority mix
  • Length and how days are split
  • English or German
  • On site, remote or hybrid

How the training is delivered

On site

In your office, with the team in the room. Best for a first rollout.

Remote

Live over video, in shorter blocks across several days.

Hybrid

A day on site to start, then shorter remote sessions on real work.

Optional add-ons Certificate of participation

Every course runs privately for one team, on dates we agree together.

Does this match your team's work?

Every module can be rebuilt on your team's own work and tools. Tell me what the team works on and I will tell you what I would change.

Luka Breitig, AI agent trainer and software engineer
Your trainer

Luka Breitig

AI agent trainer and software engineer

At the marketing agency I co-founded, I automated the recurring work until a core team of 11 could run more than 150 freelancers, with 80% less manual work.

  • Ships production software every day
  • Delivers in English and German
  • Speaker at Nomad Summit

Questions about this course

What teams ask before they book.

None. Everything is assembled visually, and a morning is enough to reach something that works. What the course does ask for is that you know one of your own processes well, because that is the raw material.

One chosen to fit your group and your IT constraints, from the current no-code agent builders. The technique transfers, which matters in a category that changes this fast. If your organisation has already licensed one, we use that and the day gets more useful for it.

Vibe coding builds you an application: a thing with screens that people open. This builds a worker: something that runs on its own and does a job over and over. Different tools, different ways of failing, and a team may well want both.

Every booking works inside your policy, so bring it along: the platform, the sign-ups and who may use what you build all go through it. From the one-day booking on, a module covers which data may reach these platforms, what they keep, where approvals belong, and how to get a proposal through your own IT department.

The agents built on a real, well-understood process have the best chance, and the course is set up around those. In the two-day booking, the last module covers what to write down, who owns it, and how anyone would notice if it stopped. If a task turns out to be a poor fit for automation, you find that out in a workshop instead of a quarter.

Have a question about your team's setup?

Get more out of the team you already have

Tell me what your team works on and how it uses AI today. A few lines are enough. I reply myself, usually within a day, and if this course is the wrong one I will point you to the one that fits.

Download trainer profile

In English or German, on site, remote or hybrid.

No-Code AI Agents Training

A few lines are enough