The studio

There are five of us. That is the argument.

Not a consultancy in miniature: an engineering studio. You know who builds your software, you speak to them directly, and nobody learns your industry at your expense.

(01)

Who builds your software

Five senior engineers. No juniors placed on your projects.

Laurent Roy
Laurent Roy
Managing director, architect and technical lead

Your point of contact, from the first call through to go-live.

  • Julien Marchand
    Julien Marchand
    Senior software engineer

    Data-heavy back ends. The one who makes three million rows answer in under a second.

  • Antoine Berthier
    Antoine Berthier
    Senior software engineer

    Mobile and field capture. Builds for patchy signal, gloves and bright sunlight.

  • Mei Tran
    Mei Tran
    Senior web engineer

    Interfaces and integrations. Connects what you already run rather than replacing it.

  • Claire Aubertin
    Claire Aubertin
    UX / UI design

    Designs for the people who will use it eight hours a day, not for a screenshot.

(02)

How we work

You never sign for a whole project without having seen the software run.

  1. 01

    Audit

    Two hours with you and your teams, remote or on site. We map your real flows — not the ones in the procedure manual. We look at who does what, with which file, and where it breaks.

    You getThe map of your flows, yours to keep, whether or not we work together.

  2. 02

    Design

    We come back with a complete proposal: what we build, in what order, on what schedule. We also say what should not be built yet.

    You getA written scope and a price.

  3. 03

    Sign-off

    You decide what goes into the first version and what waits. This is the moment the price becomes firm.

    You getA price that will not move.

  4. 04

    First scope

    A small contract, and software running in your hands. You judge on the evidence and you are free to stop there.

    You getWorking software. If it does not suit you, it is not invoiced.

  5. 05

    Build

    In short iterations, with versions to try throughout. Your teams get into the tool before the project ends, not on delivery day.

    You getA version to try, regularly.

  6. 06

    Delivery and maintenance

    Go-live, training, then fixes and evolution over the long run. Our oldest application has been running for ten years.

    You getSoftware in production, and someone on the end of the phone.

(03)

What you can hold us to

Four commitments, written down because they are checkable.

01

The price is firm

Once the scope is agreed, the figure does not move. No mid-project top-ups, no surprise variations.

02

The prototype is not invoiced if it does not suit you

You judge working software, not a presentation.

03

Go-live is progressive

Your teams work in the new tool before the project ends. You discover nothing on delivery.

04

Fixes are never re-invoiced

A defect in what we delivered is fixed as fast as we can, at no extra cost.

(04)

What our clients run on this today

100M€
of trade promotions steered every year
3.2M
price surveys processed
1,500
users on the software we have delivered
10yrs
of continuous production on our oldest application

Two hours, and you will know where to start.

Book a 2-hour audit