// AI training & upskilling
Train your teams to use AI in a controlled and responsible way
Our corporate AI training is built around your business and your use cases, so your people move quickly from discovery to practice. By training them on the tools, best practices, the limits of AI and the constraints of the AI Act, we give them a clear framework to move forward on their own.
Let's discuss your programme// the problem we solve
Why train your teams rather than depend on a provider for every AI topic?
Most companies adopting AI today do it piecemeal: a tool tested here, a subscription taken there, with no shared method or doctrine. The result is teams using AI at a fraction of its potential — or avoiding it out of mistrust, for lack of proper training.
At ezacae, we train because we use AI ourselves, every day, on real client projects: AI-assisted development in our low-code tools (WeWeb, Xano, FlutterFlow, Power Platform), process automation, AI agents. We pass on what we practise, not what we've read.
Who it's for?
A Digital Factory that wants its developers to code faster with AI, without sacrificing quality or losing control of the code produced A business team that wants to understand what AI can really do for them, without technical jargon An IT department that wants to set a framework for AI usage before every team starts testing tools on its own A company already working with us on a low-code or AI project, that wants its teams to take over once the project is delivered
// our formats
Three formats, one shared principle: no fixed catalogue
Each programme is scoped with you based on your starting level, your tools and your objectives. Here are the three formats we use most often — they can be combined.
Hands-on developer workshop
A short session (typically one to two days), in a small group, on a real use case from your team. You leave with prompts that work and workflows tested on your low-code tools, not with slides.
Business awareness session
A session designed for non-technical teams: what AI can concretely do for their processes, its limits, and how to use it without excessive risk or dependency.
Ongoing support
Mentoring over time, at the pace of your projects: we come back regularly, challenge usage patterns, and correct bad habits before they take hold.
Duration, number of participants, pricing: we scope all of that together during a first conversation, based on your context. Let's talk.
// frequently asked questions
Do our teams need to already use AI to take an ezacae training course?
No. Our programmes adapt to your starting level: some groups have never touched an AI tool, others already use one and want to structure their practices. We scope the content based on that starting point.
Are your trainings reserved for developers?
No. We offer both technical workshops for your developers and awareness sessions designed for business teams, with no technical prerequisite.
How long does a training course last?
It depends on the format and your objectives. Hands-on workshops generally last one to two days; ongoing support runs over several weeks or months, at the pace you choose. We scope the exact duration with you upfront.
Do you train on one specific AI tool?
We're not tied to a single tool. We train on AI applied to your use cases, often in connection with the low-code tools we work with (WeWeb, Xano, FlutterFlow, Power Platform) and the generative AI assistants on the market — without locking you into a proprietary solution.
Can training be combined with an ongoing development project with you?
Yes, this is actually a common setup: your teams build their skills while we deliver the project, so you can take over more quickly once the engagement ends.
// our day-to-day AI practice
We don't train on a theory we don't apply ourselves. Our team practises AI on its own projects before passing it on : read the first-hand account from one of our designers on what AI is really changing in her job.
// further reading on the blog
Citizen Dev & Power Platform: why governance is non-negotiable
What holds true for low-code holds true for AI : without a framework or training, team autonomy turns into risk.
How to convince your IT department to adopt no-code / low-code
The same governance arguments apply to adopting AI internally.
AI and UX design : my first-hand experience
What AI concretely changes in a designer's job, from the inside.
// our other expertise