Middle management and business teams
Eight days for the people who carry the files. Same format as the technical track, but run on your own real material rather than on a code repository.
For the people who carry the files: team leads, project managers, account managers, sales administration, procurement, human resources, legal. Roles whose output is made of documents, reports and decisions, and where the hours go into re-typing, digging out what was already said, and formatting.
There is no code repository in this track, and none is needed. The work runs on real material: a live tender, a committee report, a client file to pick back up after three months away.
Eight days, four of them on site, four to six seats, €29,000 excluding tax. It is the format of the technical track carried over to the business side: same duration, same standard, but on files rather than on a repository.
Follow-up is cut into two-hour blocks rather than whole days, because a team working through requests cannot free up a full day in one go. It is used up within two months of the last on-site day: after that the momentum has gone and the sessions turn back into a conversation.
It is not a list of formulas to copy. A shared prompt document ages in three months and teaches nobody anything.
It is not a conference either. Thirty people watching a screen produces enthusiasm on the day and no change at all on the Monday. Four to six seats, never a room, and we would rather run two cohorts.
Finally, it is not a technical track in disguise. Nobody walks out writing code: people walk out handling faster what they already handled, and knowing what should not be handed to the tool at all.
A written method the team replays without us: the tasks where the tool genuinely saves time, how to phrase a request, the checks to run before anything is circulated, and the point where a person re-reads and puts their name to it.
The usage charter and the access split, decided with you. A written report and the slide deck, delivered within five days.
- 8 days in total, 4 of them on site, held within a month so the momentum holds
- 4 to 6 seats, on real working material and never on a sample dataset
- Framing session and short interviews before day 1, programme written after the diagnosis
- Follow-up in 2-hour blocks, used up within 2 months of the last on-site day
- Usage charter and access split decided with you
- AI literacy module (Article 4 of regulation 2024/1689), as a working framework
- Written report and slide deck delivered within 5 days
- Editor licenses (Cursor, Claude…) and travel sit outside the package
Pick a client file back up without re-reading all of it: history, commitments made, open points.
Write a specification the technical team can read without rewriting it.
Prepare a steering meeting from the real project material.
Work through the queue of repetitive requests without losing the week to it.
Know what should not be handed to the tool, and be able to explain it to the team.
Before day 1, we find where the hours go
A framing session with you and a few short interviews in the teams concerned, to spot the tasks that genuinely cost time: re-typing, digging through archives, formatting, summarising, repetitive requests. The programme is written after that diagnosis, not before.
Four on-site days, on real working material
Real documents, real reports, live files. Nothing is demonstrated on a sample dataset, so what comes out of the sessions is reusable as-is the next day. The four days are held within a month, and each one leaves an artifact behind it.
Follow-up in two-hour blocks
The rest of the track is cut into two-hour blocks rather than whole days, because a team working through requests cannot free up a full day in one go. The blocks pick up the cases participants bring, on whatever they are working on that week. Follow-up is used up within two months of the last on-site day.
What gets handed over
A written report and the slide deck within five days, the usage charter and the access split decided with you, and the methods recorded during the track, replayable by the team once we are no longer in the room.
€29,000 excluding tax, a fixed package for one cohort of four to six seats. Billing is split in two equal halves: one at the start of the track, one at the end.
Two things sit outside the package: 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. Access to the tools is needed during the days themselves, since the work runs on real material.
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.
On this track the subject is handled where the material actually travels: which documents can be pasted into a tool and which cannot, when a human re-read is mandatory, and who signs what leaves the building. 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.
Who is this track for?
Middle management and the business teams: team leads, project managers, account managers, sales administration, procurement, human resources, legal. People whose work produces documents, reports and decisions, and who neither need nor want to write code.
Do we need to know how to code?
No. The technical track works on a repository; this one works on files. Participants are never asked to write a line of code, and the exercises run inside the tools they already use.
How much does the management and business track cost?
€29,000 excluding tax, a fixed package for one cohort of four to six seats and eight days. Billing is split in two equal halves, one at the start and one at the end. Editor licenses and travel costs sit outside the package.
How are the eight days split?
Four days on site, held within a month so the momentum holds, then follow-up cut into two-hour blocks rather than whole days. The follow-up is used up within two months of the last on-site day: after that, the sessions turn back into a conversation.
Why cap the track at four to six seats?
Because dilution is the first cause of failure for this kind of training. Beyond six, the facilitator can no longer unblock each person on their own work and the session turns back into a demo. We would rather run two cohorts.
How does this differ from the leadership track?
The leadership track runs over five days, three of them on site, for two seats, and works on what a leader spends the day doing: preparing a board meeting, reading a long memo, preparing a vendor decision, setting the usage charter. This one runs over eight days, for four to six seats, and works on the files the teams handle every week.
What is left once the track ends?
A written report, the slide deck, the usage charter and the access split, plus the methods recorded during the track, replayable by the team without us. The tool does not do the job: judgement, trade-offs and the signature stay human.
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.