Skip to content

What our clients got, measured, and what they kept when we left.

For buyers in Europe, the US or the UK who want proof before a video call. Eight engagements, seven named clients, several of them public institutions whose work is on record. Where a figure was measured, it is here with its source.

Three measured results

platform uptimeExpertise France. Measured over the duration of the operation
100%
management applications rebuiltCFAO. Wave by wave, never a big-bang cutover
10+
resident reports collectedLiège metropolitan area. During the tramway works
3000

1 + 2local project manager and developers recruited and trained on the project

Case record, Expertise France engagement

Expertise France, French government development agency, for Cameroon

Cameroon got its addressing system, and kept the code.

The problem
Cameroon needed a sovereign digital addressing base and an urban platform for its cities, for about thirty million people. Neither existed as a product, and the institution set one non-negotiable condition: control of the source code and the hosting.
What was delivered
Both systems built, robust on intermittent networks: the addressing base in production, the urban platform being delivered. A local Cameroonian project manager and two developers recruited and trained on the project, and the sources handed over so the country could host the systems itself.
Custom software, built so that you keep it

Seven more engagements, seven different starting points.

Each one in the order you would ask about it: where the client stood, what we built, and what stayed with them.

  1. CFAO

    International distribution group, subsidiaries in many countries

    10+management applications rebuilt, one wave at a time

    Legacy modernization
    Where they stood
    A group IT department running its management applications on operating systems and middleware that had reached end of support, across subsidiaries on several continents. Nothing could stop: the applications ran the business in markets where continuity is not negotiable, on servers that did not even share the same OS versions.
    What we built
    More than ten management applications rebuilt wave after wave, one application at a time, never in a single high-risk cutover. Hosting consolidated onto one cloud.
    What they kept
    A supported technical base, and a category of operational risk moved to a hosting provider contractually accountable for it.
  2. Liège metropolitan area

    Public authority, Belgium

    3000reports collected during the works

    Custom software development
    Where they stood
    A tramway construction program across the whole metropolitan area, 24 municipalities and 650 000 residents, and no structured way for residents to report what the works were doing to their street. The system had to be running while the construction was, not after it.
    What we built
    Our existing reporting platform adapted to the program and deployed across the area, for residents and for technical reports from the field.
    What they kept
    A running system for the duration of the works, covered by the Belgian press at launch.
    The Liège tramway, with the reporting platform open on a phone
    The reporting platform deployed for the Liège tramway works.

    Press coverage at launch, La Dernière Heure (in French)

  3. Welfarm

    Animal welfare NGO, France

    2600+field reports documented since 2020

    Custom software development
    Where they stood
    Volunteers and citizens needed to report livestock transports in a heatwave, and no available tool covered the whole need: robust geolocated reporting, statistics the Ministry could use, and alerts pushed to citizens. The statistics had to hold up in front of the French Ministry of Agriculture, a harder test of data quality than any internal dashboard.
    What we built
    TruckAlert: structured field capture across all of France, and localized notifications sent to citizens when a heat alert is active in their area.
    What they kept
    Field data the administration actually uses.
    A hand holding a phone with TruckAlert open on its report screen
    TruckAlert on its reporting screen (interface in French).

    Press coverage, Le Parisien (in French)

Four more, described in words.

leads.frThe whole role, internalized. No residual retainer, which is the part most interim arrangements quietly avoid.

B2B lead generation

Fractional CTO
Where they stood
A product team whose cycles kept lengthening, and a management that no longer knew what to ask of its developers. Restart delivery without breaking the rituals that still worked, and leave on a date rather than become the team.
What we built
Product management taken back in hand, the backlog scoped, delivery moving again, and an internal product owner recruited and trained alongside.
Insight SiPTools in daily production use by its teams.

Electronic component manufacturer

Custom software development
Where they stood
An industrial company that needed a web presence, a sales channel and internal management tools. Not six vendors who each own a piece, but one architecture that holds together.
What we built
The communication site, e-commerce and management tools, built by one team on one architecture, on a fixed fee with a commitment on the outcome for the agreed scope.
French Ministry of JusticeSites in production, and people who built them. For you, it is the reasonable proxy for whether we can transfer skills to your team as well as write code.

Public institution

Where they stood
A reintegration program run by the Ministry, in which participants learned to build websites. Real projects that went into production, not exercises that went nowhere.
What we built
Supervision of participants building real sites, delivered and put online.
Industrial company, 15 to 30 peopleOne person internally who changes the business rules without us.

Industry and B2B services

Custom software development
Where they stood
A spreadsheet ran the company: quotes, stock, scheduling, all in one file that one person understood. Replace it without stopping the business, and without losing the history.
What we built
A connected business tool, with the CRM and the accounting system wired together through their APIs so the same data stopped being entered twice. History rebuilt during migration, with a two-pass quality check.

Anonymized composite: a pattern observed across several engagements between 2023 and 2025, published as a representative case because the underlying clients are not public.

After the handover, not one of them had to call us back in an emergency.

Measured in July 2026, across every engagement delivered since 2019: no client has had to call us back on an emergency after handover. The few follow-on contracts extended a warranty or widened the knowledge transfer, never to repair something we had left behind. A first-party number: treat it as a claim we are accountable for, and raise it in a reference call.

The fair questions about this page, answered.

Why are several of these public institutions?

Because those engagements are a matter of public record, which means you can verify them rather than take our word for it.

Expertise France is the French government development agency, Liège is a Belgian metropolitan authority, and the Ministry of Justice is what it sounds like. Public procurement leaves a paper trail, and that is a deliberate part of what we publish.

How do you decide which numbers to show?

A number appears as a result only if we measured it or the client published it: uptime over the program, applications rebuilt, reports collected.

Where an engagement has no figure we can stand behind, it is described in words. Inventing a plausible figure would be the easiest thing on this page to do, and the most damaging.

Do you have client testimonials in English?

One, on our home page. The recommendations written about our work are in French, so any quote in English is a translation: the one we publish, from Cyprien M., who worked alongside Laurent in CFAO’s IT department, is marked “Translated from French” and links to the original.

Several clients on this page are named, and for a serious engagement we can arrange a reference conversation, which is worth more than any quote on a page.

These are mostly French and European. Have you delivered in the US?

Not yet, and pretending otherwise would be a poor start. The work travels: infrastructure modernization, interim technology leadership and custom software are not jurisdiction-specific, and one of these engagements delivered national infrastructure on another continent.

What we do not have is a US client list; if that is a requirement for you, we are not the right fit for this project.

Recognize your situation in one of these? Describe the rest.

Tell us what you are dealing with and where your data and customers are. You get a plain answer on whether we have done something close enough to matter, and whether we can help.