Get your team fluent in AI
In-person training shaped around how your team works, so people use AI on their real tasks the next morning.
I'm Jo, an AI engineer who came in from the business side. After audit and banking consulting, I led the team behind a major Belgian bank's digital assistant and got hooked on what AI can do inside a company. Since 2024 I've built AI products, from voice agents and chat-based insights on large datasets to security research. Now I bring that experience to companies: I train your teams, build the agents they need and test them for security holes before they ship.
In-person training shaped around how your team works, so people use AI on their real tasks the next morning.
Most teams don't lack AI tools. They lack someone who sits next to them and makes it work on their own files, their own clients, their own week. That is what this training does, in person, team by team.
Buying licences is the easy part. The hard part is the months after, when a few people try the tools and everyone else carries on as before. Enablement is that part.
It starts by mapping where AI saves real hours in your teams and agreeing the tools and usage rules with IT and compliance. Then each team is trained in person, with follow-up visits until the new way of working holds.
An adoption plan your managers can follow, teams that use AI on their own work, and clear rules on what goes into which tool.
For companies that know AI matters but don't know where to start, or that started and saw it fizzle out.
One session gives people ideas. Habits take repetition on real work, so this runs over several weeks.
Short in-person sessions per team, on your own files, clients and processes. People practise between sessions and come back with real questions. No coding experience needed.
People who use AI on their daily tasks, each with their own knowledge base connected to your company's information.
For teams where only one person uses AI today.
Small groups, real work, no slide decks. People bring a task from their week and we build an AI workflow for it on the spot, so everyone leaves with something that works the next morning.
Practical talks on building with AI agents and using them safely at work.
English, Dutch or French.
For teams, company events and conferences.
RelatedAI training for teams
From a working prototype to production: agents for your staff and your customers, model-agnostic by design.
In production, tools fail and inputs get messy. These agents are made for that: the model proposes, deterministic code checks and acts, and a person signs off on anything that matters. Evals, automated tests of the agent's work, run on every change, so imperfections are captured before your customers see them.
Agents that do real work inside your company: assistants that handle internal requests for your staff, and chat or phone agents that answer your customers. They work in the tools you already run, and speak Dutch, French, English or German.
We start with one process that has a clear owner and a known cost, and automate it with AI agents in stages:
Evals score every change along the way, so imperfections are captured and fixed. Every release ships as code, with a rollback ready.
When a tool fails, the agent says so instead of inventing success. Your systems stay the source of truth, not the model, so every outcome can be traced and explained.
For companies with work a machine should be doing, or customers waiting on a phone line.
ICM, or Interpretable Context Methodology, organises your company knowledge so people and AI agents can both find their way in it. Instead of a separate agent per task, one strong model works from that knowledge base and follows the same structure your people do.
Your knowledge stays in plain files you own, readable by people and easy to audit. You can switch model or provider without reconfiguring anything. And as models improve, one model on good context gets better, while a web of separate agents only gets harder to maintain.
For teams with scattered docs who want AI to work from what they know.
RelatedSecond brainA personal agent
An agent that works for one person. It handles mail, calendar and documents, runs scheduled tasks and reports back on the channel they already use. It runs on infrastructure you control and keeps its own knowledge base. It sees the names of your keys, never the values.
For executives and key staff whose week is full of small, repeatable work.
A working web or mobile app in your users' hands, not a demo. AI goes in only where it beats plain code, and the code, documentation and deploys are yours.
For teams that need it live, not just a demo.
A second pair of eyes on your code and your running systems, with findings you can act on.
AI-written code runs. That doesn't make it safe: leaked keys, broken auth, an agent that does whatever a web page tells it to.
A review of your source code and architecture from the inside. White box means the review sees what your developers see. Apps built with coding agents included.
Every finding is reproduced before it reaches you, ranked by severity, with the fix.
Coding agents write code that runs, fast. They also skip the dull checks. A review before release costs far less than an incident after it.
For teams that built fast, often with coding agents.
A test of your running systems from the outside. Black box means the test starts with what an attacker would have: no code and no inside access. Websites, APIs, apps and the servers behind them.
We agree the scope in writing first. Agents map your attack surface, everything reachable from the outside, and probe it for weak spots. Every finding is reproduced by hand, so nothing in the report is a guess. For each one you get the exact attack path, step by step, with a proof of concept that shows how the vulnerability is exploited, and a concrete suggestion for how to patch it. After your fix, a retest confirms the hole is closed.
You see your systems the way an attacker does, before one does. Findings stay private, and nothing outside the agreed scope is touched.
For companies with systems already in production.
RelatedStateCtrlSoftware review
Two things that go beyond a review. First, a check of your AI assistants, for your staff or for your customers: that they share only what they should (no other customers' data, internal documents, prompts or keys), and that they hold up against poisoning, where someone plants instructions or false information in what the assistant reads. Second, wider governance, risk and compliance (GRC) work and security operations (SOC) support.
Your assistants are tested together with a partner firm that specialises in chatbot poisoning, the way a curious user or an attacker would: crafted questions, instructions hidden in documents and web pages, and attempts to reach data outside a user's rights. Extended GRC and SOC compliance runs with StateCtrl's other partner firms, so one team covers the AI layer and the compliance around it.
An assistant connected to company data can leak it in a single answer. Auditors and regulators now ask how your AI is controlled, under GDPR and the EU AI Act; this gives you the evidence to show them.
For companies running AI assistants on internal or customer data, or preparing for an audit.
Co-founder
Phone agents that answer calls in Dutch, French, English or German and book, move or cancel appointments.
Read more →Founder
AI security company.
Read more →An Obsidian vault that AI agents file, link and search, from a Mac, a phone or a VPS.
Read more →Team · Project owner · Project for Tasco JSC
Long-distance rides in Vietnam, with rider, driver, fleet and admin apps on iOS and Android.
Read more →I started in audit, moved into banking consulting and ended up leading the team behind a bank's digital assistant. That taught me early that real users ask what you didn't plan for.
Since then, I've been building. If it doesn't work for the real user on the real device, it isn't done.
English · Dutch · French
Have a question or a project in mind? Send me a message.