Skip to content

Trainings

Your team corrects an AI agent once, and the pipeline makes it a rule.

An advanced agentic engineering course for teams already using coding agents: two days building your first shared delivery pipeline from your own backlog.

  • Markus Rother
  • Luis Fernando De La Torre Delgado
  • Malte Burkert
  • Oliver Tischlinger
Get an offer

EUR 1,500 per participant

  • Two days
  • remote or on site
  • handpicked trainer
The workshop was inspiring and pushed me to think big. The end-to-end migration pipeline example really stayed with me. We're using Claude Code far more aggressively now.
Dr. Jan Henrik Ziegeldorf (opens in a new tab)
CTO & Co-Founder aedifion

What you get in two days

Each engineer already has their own way of working with agents. In two days the team builds one delivery pipeline everyone runs the same way, from parts it can inspect: skills, subagents, state and contracts. The first tickets from its own backlog run through it before the training ends.

Software is built by teams. The Software Factory describes how a team works with agents: more output, and beyond that, results you can rely on and less stress for a team that has been stretched for too long.

Who it's for

Engineering teams that already work with coding agents and want one delivery pipeline the whole team runs the same way.

It builds on Agentic Engineering for Developers and QA, so participants should know what that course covers: LLM fundamentals, the agent loop, setup, prompting, project configuration, context management, subagents, and integration over MCP and CLI. Teams already fluent with agents can start here.

What your team takes away

  • One delivery pipeline the whole team runs the same way, made of parts you can inspect: skills, subagents, state and contracts. First items from your backlog have run through it.
  • A first factory, ready to grow toward production
  • The handout
  • Each participant gets their own certificate of attendance

What changes

Each fix your team makes by hand becomes a pipeline rule. Reviews stop piling up. Engineers spend the day on intent and gates.

What the days cover

Day 1: Your first software factory, small and observable
  • Factory basics: why solo agent use does not carry over to the team, and what a factory is.
  • State and planning: the spec and issue hold the pipeline's state and act as the contract between stations.
  • A minimal pipeline: planner, refine and implement, built against a sandbox, one supervised step at a time.
  • Observability: see time, token cost, failure rate and retries for each step before the factory grows.
  • Challenge before code: an adversarial review of the plan, against weak plans and scope drift.
Day 2: Review, gates and your own backlog
  • Review and rework: a review loop around implementation that escalates to a person after a capped number of rounds.
  • QA and codify: QA is the functional gate. Each delivery updates the rules and docs for the next.
  • Orchestration: an orchestrator runs the stations in order, caps loops, escalates and persists state.
  • Your backlog items: real items from the team's backlog go through the factory, not the sandbox.
  • Share-out: each team shows how far it got and what goes into its next sprint.

How it runs

  • Hands-on

    First a sandbox pipeline, then your own backlog.

  • The first pipeline in two days

    Ready to grow toward production.

  • Real code in your stack

    Your team practises on its own code or on one of our training codebases: Python, Java/Spring Boot, Angular/.NET, Kotlin/Vue, PHP, Next.js or embedded C. With its own code, it uses its own machines and licences, and the code stays in your repositories.

  • Mentoring as your team applies it

    We stay with your team while it puts what it learned to the test in real work. Sessions follow the team's progress on real work.

  • Lifetime access to our community

    Free for every participant: people from other teams share what works in the hackers&wizards community.

Runs in Claude Code, Codex, GitHub Copilot, Gemini CLI or Cursor.

Trainings by tool

Who delivers it

Delivered by one of our more than 70 trainers. For each group, we propose a trainer based on technical fit, language and seniority, and on whether they will get on with that group. In our experience, the personal fit matters most. You accept or decline, then you get to know them and we prepare the training together.

A selection from our trainer pool.

AboutAll trainers

What it goes with

Agentic Software Factory: Advanced Team Training builds on Agentic Engineering for Developers and QA. Leaders, product people and the rest of the company learn the same terms in their own formats, so specs, gates, budgets and reviews match. For a team that wants agents to handle work end to end, the Factory Pilot and a rollout are the next offers on top.

What clients say

What clients say about our trainings

We brought in hackers&wizards to help our engineering team get under the hood of agentic tooling, and the session delivered real value. The content was technically deep without being abstract, and the team left with practical ideas they could immediately start exploring. For a regulated environment like ours, the balance of innovation and pragmatism was particularly welcome. A genuinely worthwhile investment of the team's time.
Jim Holmes (opens in a new tab)
VP Technology Skin Analytics
From my point of view, day 2 was a success. I think it was very inspiring for all participants. The spark definitely caught, and that was the goal.
Florian Sauter (opens in a new tab)
CTO EGYM

Questions before booking

Who is Agentic Software Factory: Advanced Team Training for?

Engineering teams that already use coding agents. You should know the basics from Agentic Engineering for Developers and QA, or already be fluent with agents.

How long does it take, and where?

Two days, remote or on site, handpicked trainer

What does it cost?

EUR 1,500 per participant. Team training, EUR 15,000 at most for the two days: up to 12 people attend, and you pay for 10 at most. Net, plus VAT. On site, plus travel at cost.

A team of fewer than eight pays the same EUR 750 per participant and day, or brings a neighbouring team along.

Remote or in person?

Both. Remote runs on your Microsoft Teams or Google Meet, cameras on, in a shared repository. On site, we come to you and bill travel and accommodation at cost.

Which tools do you teach?

Our engineering, product and leadership trainings run in the coding agent your team already uses: Claude Code, Codex, GitHub Copilot, Gemini CLI or Cursor. We have delivered each of these trainings in every one of these agents. Agentic Workflows for Business Teams uses a desktop app: Claude, ChatGPT or Microsoft Copilot.

The instruction files, settings and approval modes differ by agent. We set them up with your team on day one. The practice is Agentic Engineering, and it carries over to whatever your company standardises on next.

No coding agent yet? We bring one that fits your team. Licences are on you, whether you supply them or we do.

Is this a transformation project?

No. The training is two days with your team, followed by mentoring while the team puts it to work. Everything the team builds stays in your repository. A bigger change, with an assessment, a pilot and a rollout, is a separate engagement you can decide on later.

How quickly can we start?

Plan on about four weeks from the order to the first training day. We agree the date with you, and your team's calendar usually decides it. It can go faster: in 2026, our quickest start came 11 days after the order.

Is funding available?

German companies may qualify for support under the Qualifizierungs­chancen­gesetz, depending on the company and the participants. We look at the route with you.

Not sure where to start? Take the self-check