Skip to content
In-house team training
New to AI agents Rebuilt on your team's work

AI Agents for Leadership Teams

Grow the business faster than headcount. Decide as a leadership team where AI agents add output in your company, and how to bring your people with you.

Starting point
New to AI agents
Length
½, 1 or 2 days
Delivery
On site, Remote, Hybrid
Group size
3 to 12 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.

See what agents do today

Know what agents can and cannot do today, from watching them work on your company's tasks rather than on a vendor's demo.

Find the extra output

Map the work in your company and name the parts agents can take on, so growth stops depending on the next hire.

Pick the first use cases

Rank candidate use cases by impact and risk, decide whether to build or buy, and know what each will cost before committing.

Rules that hold up

Set data protection, quality checks and sign-off so the company stays on the right side of GDPR and the EU AI Act.

Teams that adopt it

Understand why people resist agents, and change roles and incentives so your teams use them rather than work around them.

A written 90-day plan

Leave with a 90-day rollout that names owners, a budget and how output will be measured.

Is this course right for your team?

Who it is for

Founders who want the company to grow faster than they can hire.
Managing directors of small and mid-sized companies who decide on the budget and carry the risk themselves.
Leadership teams who need one shared view of AI agents before every department buys its own.

What to have ready

  • The people who decide on budget and priorities, in the room themselves.
  • Three or four real processes from your company, described in a few lines beforehand.
  • A laptop with a browser. No technical knowledge is assumed.

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.

60% hands-on
1

What agents do today

From half a day
  • Agents working live on research, documents, the inbox and data
  • Demonstrated on tasks your company sends in beforehand
  • Where they fail, and what that failure looks like in practice
  • Telling a real capability from a vendor's promise
2

Where agents add output

From half a day
  • Mapping where the hours in your company go
  • Separating volume work from work that needs judgement
  • Growing without growing headcount: what the arithmetic looks like
  • The bottlenecks that cap growth today, team by team
3

Choosing the first use cases

From 1 day
  • Weighing impact against risk on a single page
  • Build, buy, or use what you already pay for
  • Licences, usage charges and the hidden cost of looking after it
  • Settling on three use cases worth starting with
4

Risk and governance

From half a day
  • Data protection and GDPR: what may go to which provider
  • The EU AI Act: which obligations apply to a company like yours
  • Quality control for work nobody wrote by hand
  • Who signs off what, and who answers for it when it goes wrong
5

People and change

From 1 day
  • How teams adopt agents, and what makes a rollout stall
  • Fear of being replaced, and how to talk about it openly
  • How roles change when the volume work moves to agents
  • Incentives that reward using agents rather than working around them
6

The rollout plan

From 2 days
  • The first 90 days, written down week by week
  • Measuring output rather than counting logins
  • A budget for licences, training and the time it takes
  • One owner per use case, and a date to review it
How the course is shaped

Your team's version of this course

The curriculum above is where we start. Before anything is booked I find out where your team stands and rebuild the course around it: a team already running agents every day needs different modules from one that installed the tool last week.

  1. Step 1

    A call about your situation

    Before anything is agreed, we talk through what your team already uses, what has gone wrong so far, and what you need it doing differently afterwards.

  2. Step 2

    Workflow review

    I look at your tools, your process and the work itself, from repository and review flow to content pipeline, and rebuild the exercises on your material.

  3. Step 3

    Curriculum reshaped

    Modules get dropped, deepened or added. You see the adjusted outline and sign it off before the date is fixed.

  4. Step 4

    Delivery and follow-up

    We run the course. Afterwards I check in with the team on the questions real work has raised.

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

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.

Choose how far the team goes

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

Briefing

Half a day

A morning for the leadership team: agents working live on your own tasks, where they would add the most output, and the rules that need to be in place before anyone starts.

Modules covered

  • What agents do today
  • Where agents add output
  • Risk and governance

Workshop

1 day

Adds the decisions: which use cases come first, build or buy, what they cost to run, and how your teams will take to working alongside agents.

Modules covered

  • What agents do today
  • Where agents add output
  • Choosing the first use cases
  • Risk and governance
  • People and change

Programme

2 days

Adds the plan: two days that end with a written 90-day rollout, with owners, a budget and the numbers you will measure it by.

Modules covered

  • What agents do today
  • Where agents add output
  • Choosing the first use cases
  • Risk and governance
  • People and change
  • The rollout plan

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

How the training is delivered

The material is the same in every format. The format decides how fast the team puts it to work.

On site

I come to your office and work with the team in the room. For a first rollout this works best, because side questions get answered as they come up.

Remote

Live over video, split into shorter blocks across several days, with shared screens and hands-on exercises on your own work.

Hybrid

A day on site to get everyone moving, followed by shorter remote sessions once the team is applying it to real work and hitting real friction.

Optional add-ons Certificate of participation

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

When would it suit your team?

Send me your team size and a rough month. I reply myself, usually within a day, with my availability and a written proposal.

Luka Breitig, AI agent trainer and software engineer
Your trainer

Luka Breitig

AI agent trainer and software engineer

I train engineering, marketing and leadership teams to hand real work to AI agents, and I use the same agents to ship production software every day. The material comes from that work.

Before going freelance I spent six years as co-founder and CTO of a marketing agency, where the automation I built meant 80% less manual work for an 11-person core team running 150+ freelancers. I also studied psychology, so the courses spend as much time on how people adopt agents (review, guardrails, rollout) as on prompting.

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

Questions about this course

What teams ask before they book.

No. I do not resell software or take commissions, so the build-or-buy module can end with "use what you already pay for" without anyone losing out. The tools shown are the ones that fit your work, and the recommendation is yours to take or leave.

It helps, but it is not required. Whoever looks after your systems should join the governance module, and in the workshop and programme the use-case module too, because that is where questions about data and access get settled. If you have no IT people at all, that is a finding in itself, and the plan accounts for it.

More than the subscription price suggests. Licences are the visible part; the rest is usage charges and the time someone spends looking after each agent. In the workshop and the programme, the use-case module puts a monthly figure on every candidate, so the decision is made on numbers instead of a list price.

Yes, in part. Every company that uses AI has to take steps so its people understand the tools they work with. Customer-facing chatbots and published AI-generated content carry transparency duties of their own. Most uses in a small or mid-sized company sit outside the high-risk category, so certification rarely comes into it. The governance module goes through your planned uses one by one, gives you orientation, and tells you where a lawyer should take over.

The plan belongs to your team, and your team can run it alone. If you want the order and the build-or-buy calls worked out across departments, that is implementation consulting; if you want a use case built, that is development. Both are booked separately, and only if the plan calls for it.

Three to twelve. The briefing works best with the leadership team alone. For the workshop and the programme, add the heads of the teams whose work is most likely to change, because people carry out a plan they helped to write.

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.

AI Agents for Leadership Teams

A few lines are enough