Why we exist
We kept seeing the same three failures.
Training that happened and nothing changed on Monday. Article 4 deadlines sitting on roadmaps with no named owner. Market options built for boards of directors, not for the person in HR or operations who actually has to run a literacy programme next quarter.
AISO Learn is the answer to those failures. It is built for the European SME and mid-market team that needs its people to use AI well, keep evidence of that use, and not pay enterprise fees for the privilege.
Where we sit inside AISO Group
AISO Learn is one of four brands inside AISO Group. Each one does a single job.
AISO Hub
The orchestration platform our operators use internally and with clients.
AISO Dev
Custom AI development for teams that need something built.
AISO Buzz
Content and distribution, for teams that need reach.
AISO Learn
Training - the brand you are reading right now.
The four brands share people, methods, and standards. If a Learn cohort surfaces a governance question that belongs with Dev, the handoff happens. We try not to dress it up.
How we teach
Our method is practitioner-led and role-specific. A Learn session is run by a teacher who does the work, not someone who has read about it.
The teacher manifesto
- Taught against real work - the work a team brings is the training.
- Role-specific, not generic - legal learns what legal needs; HR learns what HR needs.
- Honest about scope - training changes what people can do, not the tools or the org chart.
That is why we call ourselves teachers and not consultants.
Who teaches
AISO Learn is led by Greg Stoos, founder of AISO Group, alongside a small group of senior teachers we know well and trust to run a room.
We do not publish specialist bios yet. We will when the roster is stable and the teachers have agreed to the framing. Until then, Greg is the named point of contact for every engagement. You will know who is teaching your session before you commit.
Our claims discipline
What we do not say, and why.
- We do not sell completion record as an outcome. Article 4 does not ask for a completion record; it asks for evidence that staff are sufficiently literate. Those are different things.
- We do not say “AI will transform your team.” It will change some tasks. The rest of the work is still the work.
- We do not quantify outcomes in advance. After a cohort, we report what moved and what did not. Before a cohort, we are honest that we do not yet know which tasks will stick.
What we do say: we leave behind the evidence, we report plainly on what changed, and we tell you the parts that did not change.
The evidence we leave behind
Every Team Engagement leaves a compliance lead with a short, defensible pack: a written AI literacy policy scoped to the team, a training record with dates and content, an assessment artefact tied to real work, and a refresh cadence.
That pack is the Article 4 answer. It is not a completion record. It is the kind of document a regulator or an revisor can read and form a judgement about.
Cross-link: the Article 4 pillar for the full working definition of what “sufficient literacy” looks like.
What is next for AISO Learn
A qualitative roadmap signal, without commitments.
- More cohorts, as demand and teacher bandwidth allow.
- Localised delivery pilots in Portuguese and French, alongside English delivery. (Training itself is delivered in English at launch. Supporting materials will exist in PT and FR as we build them.)
- Continued expansion of the Article 4 content library on the resources hub.
We will post updates as they land. We will not promise dates we are not certain we can hit.
Starting points
Three honest paths from here.
Take the Scorecard
10 questions, 4 minutes - a plain-language read of your team's current band, plus a 3-page action plan.
Book a discovery call
20 minutes, a teacher on the other side, zero pitch.
Read the Article 4 pillar
If you are the compliance or HR lead, start there.
Questions teams ask before booking
Are your trainers actual practitioners, or career consultants?
Practitioners. Every Learn session is run by someone who does the work - not someone who has only read about it. Greg Stoos is the named point of contact for every engagement.
Do you document learners?
No, and that is intentional. Article 4 of the EU AI Act asks for evidence that staff are sufficiently literate, not a completion record. We leave behind a defensible Article 4 evidence pack: policy, training record, assessment artefact, refresh cadence.
Can you deliver in Portuguese or French?
At launch, training is delivered in English; supporting materials and the public site exist in EN, PT, and FR. Localised delivery pilots in PT and FR are on the roadmap as teacher bandwidth allows.
How big can a cohort be?
A typical Team Engagement is one team of 8-25 people. We can run multi-team programmes via the Enterprise route. We do not run open revisoriums - small rooms with role-specific work is the whole point.
How do you measure outcomes?
After the cohort, we report what moved and what did not - AI tasks shipped, time saved, evidence captured. We do not quantify outcomes in advance because we do not yet know which tasks will stick for your team.
Two honest paths from here
Score your team in 4 minutes with the Article 4 Scorecard, or talk to a practitioner about what a cohort would look like for your team. Both routes start the same way: a clear read on where you stand, no pitch.