AI Training
Three fixed-price AI training tracks, each in three levels, in very small cohorts: from €15,000 excluding tax for the leadership team, €25,000 for the technical teams, €29,000 for middle management and business teams. This page is where you pick one; each track then has a page of its own.
The starting point
The tool is not what is missing, the shared method is. In most of the companies we see, AI is already in the building: someone uses it for meeting notes, someone else for code, and nobody brings it up in a meeting. Each person relearns alone what a colleague worked out last week, and as much energy leaks away as gets produced.
So what the three tracks install is a shared method, not a tour of a tool: when to use it, when to leave it alone, how to phrase a request, what to verify, and the point at which a human re-reads and puts their name to it.
Which track for whom
The audience picks the track; the level follows the team's maturity. Each one has its own page, carrying the programme, the deliverables and the terms; below is enough to pick one.
Leadership team — €15,000 excluding tax, five days, three of them on site, two or four seats. For a board that has to decide, without a line of code.
Technical teams — €25,000 excluding tax, five days, three of them on site plus two of follow-up, two, four or six seats. For developers and ops, on your own repository.
Middle management and business teams — €29,000 excluding tax, six days, four of them on site, two, four or six seats. For the people who carry the files, on real working material.
The technical track fits into one day fewer than the business one, and that is what the gap between €25,000 and €29,000 reflects: a technical team moves faster because it works on its own repository, with the tooling already in place, and replays on real tickets between sessions. The programme is not shorter in substance, the pace is.
In all three cases the track opens with a framing session and ends with follow-up, used up within two months of the last on-site day.
Three tracks, three levels
Each track comes in three levels: Foundation, Associate and Advanced. Everyone starts at Foundation; the next two go deeper into the same track with fewer seats, for a team that has done the level below. Every cell leads to that level's detail, with its per-day and per-person maths.
| Track | Level 1 · Foundation | Level 2 · Associate | Level 3 · Advanced |
|---|---|---|---|
| Leadership teamThe three levels → | €15,0002 or 4 seats · 5 days | €30,0001 or 2 seats · 9 days | €60,0001 seat · 9 days |
| Technical teamsThe three levels → | €25,0002, 4 or 6 seats · 5 days | €45,0002 or 4 seats · 8 days | €60,0001 or 2 seats · 9 days |
| Middle management and business teamsThe three levels → | €29,0002, 4 or 6 seats · 6 days | €45,0002 or 4 seats · 9 days | €60,0001 or 2 seats · 9 days |
Prices excluding tax, per cohort.
How a track runs
You tell us the three tasks that cost your team the most hours; we tell you which ones training can fix, and at which level.
A few short interviews and access to your files or your repository: the programme is written after that diagnosis.
Held within one month so the momentum holds, each on your own files.
Written report and deck, delivered within five days.
Closed within two months of the last on-site day, four months at Advanced level.
Once the method holds without us, the Associate level, then Advanced, goes deeper into the same track.
What it covers
- A framing session and a few short interviews before day 1: the programme is written after the diagnosis
- On-site days run on your own files or your own repository, never on a sample dataset
- Cohorts of 1 to 6 seats depending on the track and the level, never a room
- Follow-up used up within 2 months of the last on-site day, 4 months at Advanced level
- Usage charter and access split decided with you
- Written report and slide deck delivered within 5 days
- Billing in two halves: 50% at signature, 50% on the last day
- Editor licenses (Cursor, Claude…) and travel sit outside the package
The Monday after
Prepare a board meeting in an hour instead of an evening, from your own documents.
Read a thirty-page memo and come out with the decisions it actually calls for.
Set the company usage charter, and be able to defend it in front of the teams.
Work on your own repository, not on a demo project.
Review a diff knowing what the tool understood and what it misread.
Write up an incident while it is still fresh.
Pick a client file back up without re-reading all of it: history, commitments, open points.
Write a specification the technical team can read without rewriting it.
Work through the queue of repetitive requests without losing the week to it.
How we work
Before day 1, we find where the hours go
A framing session with you and a few short interviews to spot the tasks that genuinely cost time: re-typing, digging through archives, formatting, summarising. The programme is written after that diagnosis, not before, and that is also where the track gets chosen.
The programme is written on your files
Real documents, real reports, a real repository. Nothing is demonstrated on a sample dataset, so what comes out of the sessions is reusable as-is the next day.
The on-site days produce artifacts
Three on-site days for the leadership team and the technical teams, four for middle management and business teams, held within a month so the momentum holds. Every day leaves something behind: written methods, checkpoints, the usage charter and the access split.
Follow-up so you can replay it without us
Two-hour blocks on all three tracks, in small groups of participants: a team frees up two hours more easily than a full day in one go. In all three cases the follow-up is used up within two months of the last on-site day: after that, the momentum has gone.
What sits outside the package
Prices are fixed packages, excluding tax, per track and per cohort, billed in two halves: 50% at signature, 50% on the last day. Two things sit outside: the editor licenses (Cursor, Claude and the rest), taken out in your own name and yours to keep, and travel costs for the on-site days.
At Foundation level, each track states the seat counts it sells (two or four for the leadership team, two, four or six for the other two, as the follow-up runs in pairs), and the price does not move inside it: these are cohort packages. The exact number is fixed with you at the framing session, when the programme is written and it is clear who has to be in the room. On the technical and management tracks, an extension beyond six seats is decided at the framing stage, never promised in advance, and is priced on quotation.
AI literacy and the AI Act
Since 2 February 2025, Article 4 of European regulation 2024/1689 on artificial intelligence requires providers and deployers of AI systems to take measures ensuring a sufficient level of AI literacy among the people who use those systems on their behalf. The text sets no programme, no duration and no level to reach: it is an obligation of means, to be sized against how the company actually uses these tools.
We turn it into a module of all three tracks, weighted towards the leadership one, and it ends with the usage charter, written with you. We cite the regulation as a working framework: this is not legal advice and does not replace your own counsel.
In the field
French industrial group (multi-site): fractional CIO — weekly operations steering, infrastructure reliability, cloud and AI framing, board committees.
French leader in refurbished-smartphone rental: migration assessment based on reading the actual code, funded by AWS MAP, then a priced modernization path (managed AWS services, domain-by-domain migration).
Frequently asked questions
Which AI training track should we choose?
The audience picks the track, the team's maturity picks the level. At Foundation level, the leadership track is for the people who decide: five days, two or four seats, not a line of code. The technical track is for developers and ops and runs on your own repository: five days, two, four or six seats. The middle management and business track works on your files rather than on code and needs six days, for the same number of seats. The framing session is also there to settle the question if you hesitate.
How do we choose the level?
Everyone starts at Foundation. Associate is for a team that has done it and wants to extend the method across the organisation; Advanced, in a very small group, goes all the way to production. Their prices are set out on each track page.
How much does corporate AI training cost?
Three fixed packages, excluding tax, per cohort. Leadership team: €15,000 for five days and two or four seats. Technical teams: €25,000 for five days and two, four or six seats. Middle management and business teams: €29,000 for six days and two, four or six seats. The technical track costs less because it is one day shorter: a team working on its own repository moves faster between sessions. Billing is split in two halves, 50% at signature and 50% on the last day. Editor licenses and travel sit outside the package.
How is this different from a generic ChatGPT course?
A generic course shows a tool on generic examples, and everyone leaves with notes they will never open again. Here the programme is written after looking at where your hours go, the exercises run on your own documents or your own repository, and what comes out is usable the next day. Two to six people depending on the track, not a room.
Why cap the number of seats?
Because dilution is the first cause of failure for this kind of training. Two or four seats on the leadership track, two, four or six on the other two: beyond that the facilitator can no longer unblock each person on their own work. The exact number is fixed with you at the framing session. On the technical and management tracks, an extension is decided at the framing stage, never promised in advance. To train more people we would rather run two cohorts.
Are AI licenses included in the price?
No. Editor licenses (Cursor, Claude and the rest) are taken out in your own name and stay yours: you keep control of the accounts and of what goes through them. Travel costs for the on-site days sit outside the package too. Access is needed during the days themselves, since the work runs on your own material.
Are we required to train our teams on AI?
Since 2 February 2025, Article 4 of European regulation 2024/1689 requires providers and deployers of AI systems to take measures ensuring a sufficient level of AI literacy among the people using them on their behalf. It is an obligation of means: no programme, duration or level is imposed. We cover it as a module of the tracks, as a working framework and not as legal advice.
Let's talk about your situation.
A 30-minute call with the founder, no strings attached. Reply within 24 business hours.
Your details are used only to answer your enquiry: never sold, never used for cold outreach. Privacy policy.