Why We Created Eryon: A Look Back at the Project’s Origins

📅 published on 14/08/2025
⏱️ 3 min read

Before Eryon, there were hours of proofreading. Too many hours.

Not the kind spent advancing a project or designing a strategy. No, the kind spent document after document, checking phrasing, hunting down regulatory inconsistencies, reviewing scientific citations, ensuring every element was compliant, aligned, and up to date. We experienced these hours firsthand—I, Gabin, at Ypsomed, and Hugo at LFB. And it wasn’t the exception; it was the norm.

We weren’t in regulatory roles per se. Yet, every launch, every document, every initiative inevitably went through this process: read, correct, wait for feedback, reread, submit, validate. A time-consuming, fragmented process that created tension between departments and discouraged even the most skilled teams.

The Idea Behind Eryon: Automate to Focus on What Matters

It was in these moments that the idea for Eryon took root. If we spend so much time repeating such unrewarding tasks, isn’t that a sign that a tool is missing? And if this need is shared across multiple organizations, isn’t it a sign that the model needs to be rethought? As Elon Musk puts it: “You should automate tasks that are repetitive and boring, because that’s what computers are for.” In his interviews, he often emphasizes that humans should focus on high-value tasks and leave repetitive or monotonous work to machines.

A Symbiosis Between Human and Machine

Hugo and I compared our experiences, methods, and frustrations. We quickly realized that the solution couldn’t be purely human or purely technological. It had to be a symbiosis of human and machine. It had to meet the demands of our industry, its regulatory sensitivity, and its scientific rigor. And it had to be sovereign, because health data is not just any data.

The Birth of Eryon: A Concrete Response to a Real Need

So we did what we do best: structure, test, iterate. We sought a technical partner capable of elevating this vision to the standards of the healthcare sector. That’s how Adrien joined us, with rare expertise in secure environments and software architecture tailored to the constraints of the healthcare world.

Today, Eryon is the answer to a need we experienced from within. A solution born not from abstract intuition, but from concrete operational experience. We didn’t want to create just another generic AI tool. We wanted to build the tool we wished we’d had when we were on the other side.

A Vision Driven by Experience

And this guides every decision we make. We chose sovereignty, performance, and adaptation to the real needs of regulatory and medical teams. Because every minute saved on repetitive tasks is another minute to innovate, to care, to move forward.