Technical teams
Six days for the teams that ship: four on site, two of follow-up, four to six seats, €25,000 excluding tax. Everything runs on your own repository, never on a demo project.
Who it is for
For the teams that ship: developers, ops, data, and the people who keep production standing. Roles where the tool is already installed on the machines, where everyone has their own way of using it, and where none of that is written down anywhere.
The track runs on your own repository. That is the only way to surface what the tool understands about your codebase and what it misreads, which a sample repository never shows.
Four to six seats. An extension is decided at the framing stage, never promised in advance.
The format
Six days: four on site, then two full follow-up days. The four on-site days are held within a month so the momentum holds, and each one leaves an artifact behind it. The two follow-up days are placed within two months of the last on-site day, and they really are days rather than two-hour blocks: they pick the repository back up as it has become in the meantime.
Six days and not eight, as on the management and business track: a technical team moves faster on its own repository. The tooling is already installed, the participants read code all day, and what is seen in one session is replayed on real tickets before the next one. That head start is what explains the gap in price between the two tracks — €25,000 excluding tax here, €29,000 for eight days on the business side — not a thinner programme.
What it is not
It is not training on a tool. The vendor changes, the interface changes, and a team that only learned an interface starts from scratch at the next switch.
It is not a workshop on a toy project. A sample repository answers everything well, which is exactly the problem: the interesting questions only show up on a codebase that has a history.
And it is not a velocity promise. We publish no percentage gain: what can be measured honestly is what stays written down and replayable after the track.
What is left after the track
A shared meta-repository, built with you during the track and owned by you: the methods kept, the contexts worth reusing, the cases tried and then dropped.
Alongside it, the usage charter and the access split decided with you, and a written report with the slide deck, delivered within five days.
What it includes
- 6 days in total, 4 of them on site, held within a month so the momentum holds
- 4 to 6 seats, on your own repository and never on a demo project
- Framing session and short interviews before day 1, programme written after the diagnosis
- 2 full follow-up days, placed within 2 months of the last on-site day
- Shared meta-repository built with you during the track, and owned by you
- 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
The Monday after
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.
Stop re-typing what already exists somewhere else in the company.
Know which parts of the repository and which data are never handed to an external tool.
How we work
Before day 1, we find where the hours go
A framing session with you and a few short interviews in the team, to spot what genuinely costs time: picking up code nobody on the team wrote, reviewing diffs, documentation left behind, incident write-ups, repetitive tasks. The programme is written after that diagnosis, not before.
Four on-site days, on your own repository
Your repository, your tickets, your incidents. Nothing is demonstrated on a sample project, so what comes out of the sessions holds up in your codebase the next day. The four days are held within a month, and each one leaves an artifact behind it.
Two follow-up days, within two months
The two remaining days are placed within two months of the last on-site day. They pick up the repository as it has become, the tickets handled since, and what the meta-repository was actually used to replay, to check that the method holds once we are no longer in the room.
What gets handed over
The shared meta-repository built with you and owned by you, a written report and the slide deck within five days, and the usage charter and access split decided with you.
Price, billing and what sits outside
€25,000 excluding tax, a fixed package for one cohort of four to six seats and six days: four on site and two of follow-up. The price does not move with the seat count inside that range: it is a cohort package. Billing is split in two equal halves: 50% at signature, 50% on the last day.
Six days here against eight on the management and business track, billed at €29,000: the gap comes from the pace, not from the content. A technical team works on its own repository with the tooling already in place and replays between sessions what it has just seen, where business teams need more time together to reach the same point.
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 and to the repository is needed during the days themselves, since everything runs there.
The exact number is fixed with you at the framing session, against how the team actually works. An extension beyond six seats is also 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.
On this track the subject is handled where the code and the data actually travel: which parts of the repository can be handed to an external tool and which cannot, what gets reviewed before it is merged, and who answers for what ships. 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.
The other tracks
For a leadership team that has to decide, without a line of code.
For the people who carry the files, on real working material.
Frequently asked questions
Who is the technical track for?
Developers, ops and data teams who own a codebase and a production system. The track assumes participants read and write code every day: everything runs on your own repository, with your tickets and your incidents.
How much does the technical track cost?
€25,000 excluding tax, a fixed package for one cohort of four to six seats and six days. Billing is split in two equal halves: 50% at signature, 50% on the last day. Editor licenses and travel costs sit outside the package.
How are the six days split?
Four days on site, held within a month so the momentum holds, then two full follow-up days. They are whole days, not two-hour blocks: the follow-up is there to pick the repository back up as it has become. The two days are placed within two months of the last on-site day; after that, the momentum has gone.
Why six days, when the business track runs to eight?
Because a technical team moves faster on its own repository. The tooling is already installed, the participants read and write code all day, and what is seen in one session gets replayed on real tickets before the next one. It takes less time together to reach the same place: six days at €25,000 excluding tax here, eight days at €29,000 on the management and business track. The programme is not thinner, the pace is different.
Do you really work on our repository?
Yes, and that is a condition of the track. A sample repository answers everything well and never shows what the tool misreads in a codebase that has a history. The access needed is settled at the framing session, and the usage charter written during the track states which parts of the repository are never handed to an external tool.
How does this differ from the other two tracks?
This one runs on your repository, for four to six seats over six days. The leadership track runs over five days for two to four seats, without a line of code, at €15,000 excluding tax. The middle management and business track works on your files rather than on code and needs eight days, at €29,000 excluding tax: two days more, because a team without a repository at hand takes longer to replay on its own what it has been shown.
What is left once the track ends?
A shared meta-repository built with you and owned by you, a written report and the slide deck, the usage charter and the access split. We publish no productivity gain percentage: what can be checked is what the team replays without us.
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.