The most dangerous complimentI ever received

Near the end of my PhD, a German company heard about my work in fluid-structure interaction modeling. Simulations of red blood cell dynamics, heart valves, vascular flows. Complex, cutting-edge, scientifically rigorous. They were interested enough to travel to Montpellier and sit around a table with me and my supervisors to discuss a potential industrial collaboration.

I was excited. Proud, even.

The meeting didn't go the way I hoped. Not because the science wasn't good, it was. But because my work was essentially impossible to reuse in an industrial context. It had been built to prove things, to publish papers, to make a thesis as solid as possible. Not to be picked up by someone else and turned into a real product. They left without a deal, and I told myself it was fine.

Around the same time, my PhD supervisor said something I remember vividly. We were talking about the vascular simulations I had developed, models nobody else in the world was running at that level of complexity. He looked at me and said:

I took it as a compliment. I felt unique. Special. It fed my ego in exactly the way you'd expect a PhD student's ego to be fed.

It tooks me years to understand that it wasn't a compliment at all. It was an alarm.

The proof came shortly after, when a postdoctoral researcher was hired specifically to build on my work. Two years later, the project had produced nothing new. Not because the person wasn't capable, but because what I had left behind wasn't a foundation. It was a labyrinth that only I knew how to navigate.

My research had died with my thesis.

When the stakesbecame real

After my PhD, I joined a MedTech startup working on computational tools to help interventional neuroradiologists treat cerebral aneurysms. Real patients. Real stakes. For the first time, my simulations weren't going into a journal. They were going into a Software as a Medical Device used in clinical settings worldwide.

Everything changed. I had to become more rigorous. Results had to be reproducible, verifiable, validated under strict medical regulations: ISO 13485, IEC 62304, ASME V&V40. The science had to work not just when I ran it, but every single time, by anyone, under any conditions.

I learned. I grew. We shipped a product that succeeded.

Then came the pressure to scale. The team was expected to deliver more, faster, with the same resources. And slowly, a familiar pattern re-emerged. Engineers were developing individual scripts, notebooks, tools designed to last only on their own laptops. Smart, talented people building solutions that wouldn't survive their departure.

We were running fast, producing results, but structurally, we were rebuilding the same wheels over and over.

I watched brilliant innovations quietly fading away because there was no infrastructure to carry them forward. And I recognized the feeling. Not the pressure itself, but its underlying cause: the absence of a system.

The underground projectnobody asked me to build

So I did something that wasn't in my job description.

In parallel to everything I was supposed to be doing, I started building what I can only describe as an R&D system. A proper software architecture for our research tools. Not scripts and notebooks scattered across five laptops. A real collaborative project, with functional specifications, software specifications, unit tests, version control, modular architecture. A platform the whole team could work on, contribute to, and rely on.

It was built in the margins. Not sanctioned by management. Not part of my objectives. But it worked.

Our tools became reliable. Our results became reproducible. New team members could onboard in days instead of months. R&D cycles shortened significantly, and we unlocked the ability to generate scientific results at scale, turning what used to be isolated studies into industrialized workflows.

At some point, the regulatory team came to me and told me we needed to formally validate our software tools under IEC 62304. It wasn't a problem. We had already built the foundations.

The system I had constructed quietly, almost secretly, had become a core asset for the company.

The leap of faith

Leaving wasn't a decision I made lightly. I had spent more than nine years in that startup. I had built a team, shaped a methodology, shipped products being used in operating rooms. But a vision was haunting me:

I decided to bet on that vision.

I left to build nuRemics, an open-source Python framework designed to bring modern software engineering practices into scientific development. The kind of foundation I knew was necessary, available to every research team in the world, freely, openly, as a shared resource for the entire Deep Tech ecosystem.

SUFFISCIENS came next. The company, the ecosystem, the community around that core technology. But more than a company, it's a conviction: that the biggest bottleneck in Deep Tech innovation isn't the science. It's the infrastructure that carries the science forward.

The era of
R&D 4.0

We're living through a transformation.

AI is dismantling the barriers to entry for software development. Digital tools are becoming more powerful, more accessible, more integrated into every research workflow. And yet, most Deep Tech R&D teams still operate the way they did twenty years ago. Individual scripts, fragile notebooks, knowledge locked in the heads of a few people, tools that don't survive personnel changes.

The gap between scientific discovery and industrial-grade technology has never been more visible. Or more costly.

I believe we're at the dawn of what I call R&D 4.0: a new era modeled after the logic of Industry 4.0, where every Deep Tech team, regardless of domain, builds software-grade tools for their science. Where research is reproducible by design. Where knowledge becomes a scalable, institutional asset rather than a personal one. Where the leap from prototype to product is a managed process, not a miracle.

That's the world SUFFISCIENS is working to build. In ten years, if we get this right, SUFFISCIENS will be a global reference in the Deep Tech ecosystem, accompanying projects from their earliest research phase all the way through to the industrialization of their innovations.

I spent more than a decade watching brilliant research disappear. Watching innovations that could have changed lives quietly die because there was no system to carry them forward.

That ends now.