About us

A trajectory in two stages

Agerix has its origins in May 2009. Eric Lamy, working as a sole trader, in Bordeaux, on a simple premise: business applications deserve the same care as the processes they serve. For six years, the venture remains solitary — one developer, clients, projects. What began as a side activity becomes a main one, then one that calls for structure.

In July 2015, the move to a limited company seals that shift. The team grows with the projects; today, fifteen people make up the engineering practice, from our offices in Lormont, near Bordeaux. Seventeen years on, what has not changed between the sole-trader beginnings and today's engineering practice can be said in a single sentence: care for the singularity of each line of work comes before attachment to any particular tool.

What we are: an engineering practice

The label deserves a pause. We are not an agency — an agency sells production. We are not a software vendor — a vendor defends its product. We are not an integrator — an integrator deploys what others have designed.

An engineering practice does something different. It studies. It asks questions, observes processes, identifies constraints and objectives, and outlines what should be built before a single line of code is written. That is the practice we have carried for seventeen years, under a single baseline — an engineering practice specialising in custom business applications.

What we stand by

Let us begin with rigour. An application project is not won when the code gets written. It is won earlier — when we accept to ask the right questions before writing anything at all. Scoping, prioritising, identifying what is structural and what can be settled later — this is the work that distinguishes an application that lasts from a product to be rebuilt three years on.

Then listening. Your processes do not belong to us. We arrive with a method, but the knowledge of your business is yours. The first conversation is not something to get through before the real work begins: it is the work. We ask questions, we rephrase, we rephrase again, until what you want to build has taken a form that can be both expressed and arbitrated.

Reliability is tested over time. Seventeen years of activity, one hundred and fifty projects delivered, clients who come back and applications still running — this is the material from which a promise of reliability is made. Delivering what was announced, on the schedule that was set, within the budget that was stated: this is the first form of respect we owe a project.

Last comes technical honesty. It shows in the simplest possible way: we know how to say that a project should not be built, or not in this form, or not now. An off-the-shelf product may serve better than a custom application. A more modest scope may produce more value than an ambitious one. Saying so is part of the work — including when the short-term commercial interest would suggest otherwise.

Our position on AI

Application development is changing. Generative artificial intelligence has shifted the centre of gravity of the work: what used to take hours to code now takes minutes, and yesterday's difficulty — producing code — becomes a secondary factor next to the difficulty that remains, and that is becoming sharper: formulating the right problems and orchestrating the right answers.

We have brought these tools into our practice, without euphoria or wariness. AI is powerful where thought has preceded it; it is much less so where thought has not. It saves time on what is clear, and it produces quick errors on what is not. We know what it accelerates, we know what it hallucinates, and we keep our hands on what is structural — architecture, the steering of choices, integration with the information system.

Application development has become more demanding in judgement, not less. That judgement is what makes our work.

The practice before the individual — Where this leads

What matters is not the story of a founding. It is what the practice does, today, for the projects entrusted to it. Three pages extend this presentation, in the natural follow-on of the argument.

On our approach, you will find in detail how a project unfolds, from the first questions to deployment, and which decision frameworks we draw on to arbitrate the choices you would rather not arbitrate alone.

On custom business applications, you will find what this offering actually covers — extranet portals, sector platforms, dedicated internal tools — and the situations in which it makes sense over off-the-shelf software.

On our selected work, you will find the projects we have carried over recent years, with their contexts and outcomes. It is probably the fastest way to know whether we are the engineering practice you are looking for.