Concrete AI trainingto multiply theproductivity of your team.

It is not just two days: the path has three moments and it starts before we meet. Two weeks ahead each person fills in a ten-minute assessment, and from it we know who already uses AI and who does not, which software you really use and how many hours a week go into repetitive work: on those answers we build the room and a different template for each person. Then come the two days at your offices, at the keyboard and everyone on their own files: on day 1 each person builds their second brain connected to their software, on day 2 they automate the repetitive tasks they declared. After the days the path continues: personalised coaching for the people pulling adoption along, recorded courses for everyone, and two or three weeks later the same assessment run again to count the hours recovered.

Two days, which can be spread across three half days if stopping the team for two days in a row is a problem. They are preceded by an assessment the team fills in two weeks earlier, ten minutes each, and followed by continuous monitoring. On top of that the team gets access to recorded material to follow when they have more time.

Each person leaves with their own second brain working and with at least one automation running on their inbox and their files. The second brain is a folder on the computer, not a course on a tool: the same folder keeps working even if the leading model changes.

No, and none of your people will write a line of code. In the room at Truck Italia we had the CEO, the general manager, the CFO and the heads of eight sites: not one technical person. The initial assessment calibrates the content on each person’s real level and our engineers work alongside every participant.

Because it is not a slide course. Slides take about an hour, then you build. The room is calibrated on an assessment filled in beforehand, each person has a template built on their own results, and the second day is entirely dedicated to building automations on real work.

In the initial assessment, for each person, the repetitive tasks and the hours a week spent on them are already written down. Two or three weeks after the days we run the same count: same people, same tasks, same hours. The difference between the two columns is the return. Not a satisfaction questionnaire and not a certificate.

Often yes, at least in part. Inter-professional funds, vouchers and regional grants cover AI training paths, and for many companies the investment drops considerably. In a call we check together which instruments are available for your situation and we support you through the process.

During the training sensitive data does not enter at all: we work on Claude Team without uploading confidential documents, and that plan does not train models on the organisation’s content. Only in a later phase, if it makes sense, do we build the Company Brain on European infrastructure in the company’s tenant and with its keys. Governance and privacy notices are handled by a partner law firm.

Continuous training, which is the phase where adoption either consolidates or gets lost. In every company three or four people out of ten come out of the two days wanting to go further: those are the ones we work with, through personalised coaching and the recorded courses. Anyone who needs hands as well as guidance moves to Engineering as a Service.

The size of the group is defined during the assessment, based on the company’s processes and structure. We typically work with complete teams, because each person builds their own second brain: the format adapts to whoever actually works inside the processes involved.

It is the objection we hear most often. The two days can be spread across three half days over two weeks, if stopping everyone together is a problem. Anyone who misses a piece catches up on the recorded material, which stays available. And the other arithmetic matters more: the hours the team loses every week to repetitive work add up to more than two days a month.

True, and we do not hide it: our channel is public. What you will not find on YouTube is the implementation on your data and your software, and a team that starts together at the same moment and gets unblocked when it stalls. YouTube gives you the information, it does not make you adopt anything. If you have the time to do it alone, do it alone.

After the assessment we build a personalised template for each person, on their software and their tasks: we start from each person’s real level, not from a lesson that is the same for everyone. People who are already ahead work on their own things, people starting from zero do not fall behind.

In this first phase no sensitive documents come in: we work on the possibilities and on the first use cases without touching the company’s information assets. With Claude Team there is SSO and admin control over connectors, so no tools used on the sly. The level of data goes up only afterwards, when the infrastructure is configured and logged.

That is the real risk, and it is why phase three exists. At the end of the two days three or four people out of ten want to keep going: we work with them through personalised coaching, and the whole team has access to the recorded courses. Anyone who needs hands as well as guidance moves to Engineering as a Service.