jo saillier Contact

agents that work.

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.

Jo Saillier, AI engineer
Jo SaillierRemote or on site

Services.

Trainstart here

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.

Train · in detail

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.

Track record

  • A large Southeast Asian bank: trained analysts to query their data in plain language through Looker, on a governed semantic model where every metric is defined once.
  • In-person trainings where people with no coding background left with their own knowledge base, connected to their company's information.
  • An AI lead-generation workflow that finds commercial real estate clients in China, for a corporate client.
  • A major Belgian bank: grew its digital-assistant team from 4 to 14.
Ask about training

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.

How it runs

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.

You leave with

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.

RelatedAI training for teamsAgent-ready knowledge base

One session gives people ideas. Habits take repetition on real work, so this runs over several weeks.

How it runs

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.

You leave with

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.

RelatedAI enablementWorkshops and talks

Workshops

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.

Talks

Practical talks on building with AI agents and using them safely at work.

Languages

English, Dutch or French.

For teams, company events and conferences.

RelatedAI training for teams

Build

Agents and apps that ship

From a working prototype to production: agents for your staff and your customers, model-agnostic by design.

Build · in detail

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.

Track record

  • Vox4AI: phone agents in four languages.
  • A major Belgian bank: 80,000 conversations a month on its digital assistant.
  • ĐiĐiRide: rider, driver, fleet and admin apps, in public beta on iOS and Android.
  • Second brain: a knowledge base that AI agents maintain, in daily use.
Ask about a build

What

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.

How

We start with one process that has a clear owner and a known cost, and automate it with AI agents in stages:

  1. Supervised: a person validates every step of the workflow.
  2. Checked: the workflow runs end to end, and a person verifies the result before it is accepted.
  3. Autonomous: the workflow runs on its own, with continuous randomised test runs that a person reviews.

Evals score every change along the way, so imperfections are captured and fixed. Every release ships as code, with a rollback ready.

Why

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.

RelatedVox4AIDaily AI StandupAgent-ready knowledge base

What

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.

How
  • Structure: folders and documents laid out the way your teams already work.
  • Routing notes: short files that tell any agent where things live and what to read first.
  • Boundaries: what agents may read, what they may change, and what never leaves.
  • Skills: written procedures the agent follows for recurring work.
Why

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

What you get

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.

How it works
  1. We list the recurring work worth handing off.
  2. The agent is set up with its channels, memory, skills and schedules.
  3. A week of real use, then a round of fixes and tuning.

For executives and key staff whose week is full of small, repeatable work.

RelatedSecond brainSesameAgent-ready knowledge base

What you get

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.

How it works
  1. We agree the scope and what done means.
  2. Short release cycles, tested early on real devices with real users.
  3. Handover: code, documentation and one rule file that every coding agent on your team follows.

For teams that need it live, not just a demo.

RelatedĐiĐiRideBuinui

Secure

Checked before it ships

A second pair of eyes on your code and your running systems, with findings you can act on.

Secure · in detail

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.

Track record

  • Private disclosures in open source: 10 reporter credits across 6 projects, 276K GitHub stars combined.
  • Named once fixed and public: Dokploy (Critical 9.9) and ToolJet (Medium 5.3).
  • Live production assessments for private clients in Vietnam, through StateCtrl.
Ask about a review

What

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.

How
  • Secrets: keys and tokens in code, logs or the browser.
  • Access: login, sessions and who can reach which data.
  • Agents: prompt injection, and tools an agent should not have.
  • Architecture: choices that will hurt at the next feature or the next audit.

Every finding is reproduced before it reaches you, ranked by severity, with the fix.

Why

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.

RelatedStateCtrlVulnerability assessment

What

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.

How

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.

Why

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

What

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.

How

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.

Why

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.

RelatedStateCtrlCompany agentsSoftware review

Selected work.

Vox4AIvoice agents

Co-founder

Vox4AI

Phone agents that answer calls in Dutch, French, English or German and book, move or cancel appointments.

Read more →
StateCtrlsecurity research

Founder

StateCtrl

AI security company.

Read more →
Second brainin daily use

A second brain that AI agents maintain

An Obsidian vault that AI agents file, link and search, from a Mac, a phone or a VPS.

Read more →
ĐiĐiRidepublic beta

Team · Project owner · Project for Tasco JSC

ĐiĐiRide

Long-distance rides in Vietnam, with rider, driver, fleet and admin apps on iOS and Android.

Read more →

From the business side.

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

Path
  1. 2026 to nowFreelance, and founder of StateCtrl · AI enablement, agents, security
  2. 2026Vox4AI · co-founder
  3. 2025 to 2026Analytics engineer · Joon Solutions, contract
  4. 2024 to 2025Vietnam · business development, AI startup co-founder, data and AI engineering course
  5. 2022 to 2024Digital assistant lead · major Belgian bank, via Avertim, Brussels
  6. 2020 to 2021Audit · PwC Belgium
  7. 2015 to 2020MSc Business Administration · KU Leuven
Contact

Get in touch.

Have a question or a project in mind? Send me a message.