Skip to curriculum

Est. MMXXVI  ·  Twenty Courses  ·  £99 one-time or £19/mo for all

Intermediate · 30 Hours · 46 lessons

Multi-Agent Orchestration

Making agents cooperate to finish real work.

Our most demanding intermediate course. You will design systems where several specialised agents plan, execute, criticise and verify — and you will learn the far harder discipline of keeping such systems reliable, bounded in cost and observable when they go wrong.

Read the syllabus
Multi-Agent Orchestration — abstract study in translucent light

Level

Intermediate

Time to complete

30 Hours

Format

Online video, self-paced

Access

Lifetime, one payment

Section 01

The visionary syllabus

Our most demanding intermediate course. You will design systems where several specialised agents plan, execute, criticise and verify — and you will learn the far harder discipline of keeping such systems reliable, bounded in cost and observable when they go wrong.

Multi-Agent Orchestration runs to roughly 30 hours of guided video across 8 modules and 46 lessons, taught at intermediate level. Every lesson is recorded as a screen-led demonstration: you watch the work happen, pause, and do the same thing with your own material. Nothing is presented as theory that cannot be performed within a few minutes of hearing about it.

This course sits in The Agentic Workflow, our intermediate track. Intermediate here does not mean programming; it means you will configure systems that act on your behalf, and you will be responsible for what they do. That responsibility is why evaluation, cost control and monitoring appear in every course in this track.

Enrolment is a single payment of £99 and it does not expire. That covers the full video library, the written workbook, the prompt and template pack used in the demonstrations, the student community, and every re-recorded lesson we publish as the tools change. There is no subscription, no upsell ladder and no separate certification fee — when you finish, your certificate is issued automatically.

Section 02

Who this course is for

We wrote Multi-Agent Orchestration for a specific person: someone who has read enough about artificial intelligence to be convinced it matters and has not yet found a course that treats them as an adult with limited time. If you have watched hours of free video and still cannot point to something in your week that changed, that is not a failure of intelligence — it is a failure of sequencing, and sequencing is what a structured course provides.

You will be comfortable here if you can use a browser, a spreadsheet and email. Because this is an intermediate course you will also be asked to work inside settings screens, read logs, and connect one service to another using keys and permissions. We show every step, but we do not pretend it is effortless — the reward for that difficulty is a system that keeps working after the lesson ends.

You will not enjoy this course if you are looking for a passive overview of the field, an inspirational lecture series, or a promise of income without work. Every module carries an artefact — a document, a system, a page, a report — and the course is only useful in proportion to how many of those artefacts you actually build.

Students who benefit most tend to share one habit: they bring their own real material to the lessons. Your own inbox, your own product, your own client, your own messy spreadsheet. The techniques transfer, but the confidence only arrives when you have watched them work on something you care about.

Section 03

What you will be able to do

Learning outcomes are easy to write and hard to honour, so each of the statements below is tied to a specific lesson and a specific artefact you produce. If you can perform all of them without referring to the videos, you have finished Multi-Agent Orchestration, whether or not you watched every minute.

  • Decompose a business process into agent roles with clear contracts
  • Choose between a single strong agent and a multi-agent system honestly
  • Implement planner, worker and critic patterns
  • Bound cost and runtime with budgets, timeouts and step limits
  • Instrument runs so a failure can be diagnosed after the fact
  • Add human approval at the points that carry real consequence

We deliberately keep the list short. A curriculum promising thirty outcomes is usually promising familiarity rather than capability, and familiarity is what free content already provides in abundance. The value of a paid course is the small number of things you can reliably do afterwards.

Section 04

The technical blueprint, module by module

The course is built in 8 modules, sequenced so that each one depends only on what came before it. You can skip forward, but the order below is the order in which the material compounds, and students who follow it finish materially more often than those who graze.

  1. 01

    When multi-agent helps

    The honest answer: less often than the demos suggest. Criteria for choosing it.

  2. 02

    Roles and contracts

    Specialisation, inputs, outputs and explicit handoffs.

  3. 03

    Planner and worker

    Decomposition, delegation, aggregation — and the loops that make it fail.

  4. 04

    The critic

    Self-review and verification steps that measurably improve output quality.

  5. 05

    Memory and state

    What each agent should know, for how long, and what must never persist.

  6. 06

    Cost and time control

    Step caps, budgets, timeouts, caching and the economics of an autonomous run.

  7. 07

    Observability

    Traces, logs and replay so a bad outcome becomes a fixable bug.

  8. 08

    Human in the loop

    Designing approval gates that catch consequences without destroying the automation's value.

Each module contains between three and six lessons, a short written summary, the exact prompts and templates used on screen, and a single exercise that produces the artefact for that stage. Exercises are designed to take between fifteen and ninety minutes; anything longer has been split, because the most common reason a course is abandoned is an exercise that felt like a project.

The 30 hours figure is an honest estimate of guided video plus exercises for a student working carefully. Some finish in two focused weekends; others take a term at two lessons an evening. Both patterns work, and neither is penalised.

Section 05

The tools you will actually use

Tools change quickly, so Multi-Agent Orchestration teaches the underlying operation first and the current tool second. When a demonstration goes out of date we re-record it, and your access includes those updates permanently — that is the main practical reason our courses are sold once rather than rented monthly.

The stack used in the demonstrations is listed below. Wherever a free tier can complete the coursework, we use the free tier and say so. Where a paid plan is genuinely required for a specific lesson, we tell you the cost in advance, show what it unlocks, and provide an alternative path so no lesson is gated behind a subscription you did not plan for.

  • Agent frameworks
  • Orchestration platforms
  • APIs
  • Logging and tracing tools

We are deliberately tool-agnostic about the parts that matter. A student who understands why a retrieval step failed can fix it in any product; a student who memorised one interface is helpless the moment a menu moves. Expect to be taught the reasoning, then handed the shortcut.

Section 06

How the teaching works

Every lesson in Multi-Agent Orchestration follows the same four-beat structure: the problem in plain terms, the demonstration on screen with nothing edited out, the failure mode you should expect, and the exercise on your own material. The failure mode beat is unusual and it is the one students mention most often — being shown what a bad result looks like is what makes a good result recognisable.

Video is the primary medium because this subject is watched more easily than it is read. You see the actual screen, the actual prompt, the actual moment the model gets it wrong and the correction that fixes it. Alongside the video, each module ships a written companion so you can revisit a step without scrubbing a timeline, and a copyable asset pack so you never retype a template from a video frame.

Assessment is practical and self-paced. At the end of each module you check your artefact against a short rubric — not a quiz on terminology, but a description of what a competent version of that artefact contains. Students who want feedback beyond that post their work in the community, where the same rubric is used for peer review.

There are no live sessions to miss and no cohort to fall behind. That is a deliberate choice: cohort courses have better completion statistics and worse accessibility, and we would rather a shift worker or a parent of young children finished in four months than dropped out in four weeks.

Section 07

The market context

Autonomous agents are the most over-promised and under-engineered area in applied AI. Impressive demonstrations are easy; systems that run every day for a month without producing an expensive mistake are not. The teams succeeding are those importing ordinary engineering discipline — contracts, budgets, tracing, tests — into a probabilistic setting.

That is a real and growing labour market. Organisations that have already deployed a grounded assistant now want processes handled end to end: research compiled, tickets triaged and resolved, reports assembled from several systems. The constraint is people who can design those systems responsibly, and the shortage is acute enough that the skill commands a premium.

The course therefore spends as much time on restraint as on capability. Knowing that a single well-briefed agent with two tools often beats an elaborate committee of five is exactly the judgement that separates a practitioner from an enthusiast, and it is the reputation we want our graduates to carry.

Section 08

Where this leads

Agentic-track graduates are the ones who tend to change roles. Shipping a grounded assistant or an automated process inside an organisation is visible, measurable work, and it frequently converts into a new title, a consulting engagement or a retainer. The skills are also the current bottleneck in the market, which is unusual leverage for a course of this length.

A sensible study path continues sideways rather than upward. Students often pair Multi-Agent Orchestration with one course from a different track — a foundations student adding a marketing course, an agentic student adding a masterclass — because capability in this field compounds across domains rather than deepening in one. Every course is the same £99, so combining two is a decision about time rather than budget.

On certification: your certificate of completion names the course, the level, the estimated hours and the date, and it links to a public page describing the curriculum so anyone can see what it involved. We make no accreditation claims. It is a credible record of work done, which is precisely what it should be.

Section 09

A realistic study plan

The most common mistake students make is starting on a Sunday with unlimited enthusiasm and no schedule. Multi-Agent Orchestration is designed to be completed in fixed blocks, and we recommend booking them the way you would book a class you had paid to attend in person — because you have.

Two sessions of ninety minutes a week finishes this course comfortably inside a couple of months. One session a week finishes it too, more slowly. What consistently fails is watching several modules in a single evening without doing the exercises — the videos feel productive and nothing is retained, because the learning lives in the artefact rather than the viewing.

Keep one document for the whole course. Every artefact, every prompt that worked, every note about something to revisit. By the end it is the most valuable thing you own from the course — more useful than the videos, because it is written in your own context and about your own work.

Section 10

What £99 includes

One payment of £99 for permanent access to Multi-Agent Orchestration. We price every course in the college identically, at a level a working adult can decide on without a meeting, because the alternative — tiered pricing designed to make the middle option look sensible — is a sales technique rather than an education policy. Prefer to subscribe? Every course in the college is also available for £19/mo, with the same access and the same updates, cancellable at any time.

  • Lifetime access to every video lesson in the course, including all future re-recordings
  • The written module companion and exercise workbook
  • The complete prompt, template and asset pack used on screen
  • Access to the student community for peer review and questions
  • Certificate of completion with a public curriculum page
  • No subscription, no upsells, and a 14-day refund on unwatched enrolments

If the course is not right for you, write to us within fourteen days and we will refund it. We ask only that you tell us what was missing; that feedback is how the curriculum has been revised each term since the college opened.

Section 11

Questions students ask before enrolling

A short, honest set of answers. If yours is not here, the admissions team replies to every message — the contact page reaches a person, not a queue.

Is this course technical?
It is our most technical. You will configure APIs and read logs, though we provide working scaffolds throughout.
Which framework do you teach?
The patterns are framework-neutral, demonstrated in the current mainstream orchestration tools.
How long do I have access?
Permanently. Enrolment is a one-time £99 payment with no renewal, and it includes updated lessons as tools change.
Is there a monthly option?
Yes. If you would rather not pay per course, every course in the college is also available for £19/mo, cancel anytime. The one-time £99 enrolment is the better value if you plan to keep the material.
Is the teaching live?
No. Every lesson is recorded video you take at your own pace, with a written companion and an asset pack for each module.
Do I get a certificate?
Yes — a certificate of completion for Multi-Agent Orchestration, issued automatically, with a public page describing the curriculum.
What if I want a refund?
Fourteen days, no argument, provided you have not completed the course. Email admissions and tell us what was wrong.

Also in The Agentic Workflow

Multi-Agent Orchestration

Intermediate · 30 Hours · Lifetime access