Software engineering studio
The file your business runs on was never designed for this
We build the operational software of companies that run on far too much data. You talk directly to the engineer who designs yours — never to a salesperson, never to a junior learning your industry at your expense.
Five signs the limit is behind you
If three of them land, you already know why you are on this page.
- 01
Your decisions rest on a file nobody can confirm is up to date.
- 02
Your teams spend their days retyping data from one tool into another.
- 03
A spreadsheet circulates by email between your teams, your suppliers and your customers.
- 04
Nobody can say where your business stands today without rebuilding a file first.
- 05
Your tools cannot tell a field agent apart from a director.
There are two more, and the detail of each one — read the full article
From a file to software
The road is almost always the same. Here is what it looks like.
It starts as one file
A single version, held by a single person. Everyone works from it. At this stage, it works beautifully.
Then it starts moving
It goes out by email. Someone corrects it. Someone else takes a copy so as not to break the original. Three weeks later five versions coexist and nobody can say which one is authoritative.
And it breaks in silence
A formula points at a deleted sheet. A cell gets overwritten by accident. Nothing warns anyone — and decisions keep being made on it.
We replace it with software
One set of data, current, with a history of who changed what. Your teams work in it at the same time, each seeing only what concerns them: a field agent sees their round, a director sees all four territories.
| Ref. | Description | Surveyed | Agreed | Variance | Status |
|---|---|---|---|---|---|
| 4412 | Semi-skimmed milk 1L | 2.14 | 2.06 | +0.08 | Cleared |
| 4418 | Long grain rice 1 kg | 3.90 | 4.02 | −0.12 | Cleared |
| 4501 | Sunflower oil 1L | 5.25 | 5.10 | +0.15 | Check |
| 4507 | Plain flour 1 kg | 1.48 | 1.45 | +0.03 | Cleared |
| 4512 | Caster sugar 1 kg | 1.92 | 1.88 | +0.04 | Cleared |
| 4530 | Macaroni 500 g | 1.15 | 1.19 | −0.04 | Check |
| 4544 | Ground coffee 250 g | 3.68 | 3.52 | +0.16 | Cleared |
| 4551 | Unsalted butter 250 g | 2.84 | 2.71 | +0.13 | Cleared |
And the data starts talking
The same numbers, but readable. Where your business stands, right now, without anyone having to rebuild a file to find out.
| Ref. | Description | Surveyed | Agreed | Variance | Status |
|---|---|---|---|---|---|
| 4412 | Semi-skimmed milk 1L | 2.14 | 2.06 | +0.08 | Cleared |
| 4418 | Long grain rice 1 kg | 3.90 | 4.02 | −0.12 | Cleared |
| 4501 | Sunflower oil 1L | 5.25 | 5.10 | +0.15 | Check |
| 4507 | Plain flour 1 kg | 1.48 | 1.45 | +0.03 | Cleared |
| 4512 | Caster sugar 1 kg | 1.92 | 1.88 | +0.04 | Cleared |
| 4530 | Macaroni 500 g | 1.15 | 1.19 | −0.04 | Check |
| 4544 | Ground coffee 250 g | 3.68 | 3.52 | +0.16 | Cleared |
| 4551 | Unsalted butter 250 g | 2.84 | 2.71 | +0.13 | Cleared |
Custom operational software
Your processes as they actually run — not a market product you have to bend yourself into.
Dashboards and reporting
Where your business stands, right now, without anyone rebuilding a file to find out.
Artificial intelligence
Assisted checking, extraction, internal assistants. Hosted on your own infrastructure if your data demands it.
Mobile applications
Data captured where the work happens: in store, on the round, out in the field.
Integrations
Accounting, your existing database, e-signature, payments, team messaging.
Infrastructure
We deliver end to end, hosting included, in France where that matters.
Work
Four companies that no longer pass a single spreadsheet around.
price surveys collected in the field, verified and analysed.
of trade promotions steered every year.
pieces of data left the authority, while its staff use AI every day.
in daily service, uninterrupted, since delivery.
They handed us a critical process
Not the side project. The one that stops the business when it stops.
The entire field data chain
Every price survey feeding their analyses, on four territories. If capture stops, the business stops.
€100M of trade promotions
Contracts, agreed revenue and supplier settlement. An error here is an error on an invoice.
Their administrative documents
An AI assistant staff use daily, on documents that are not allowed to leave the authority.
Why a studio rather than a consultancy
Six differences that come from the structure, not from the pitch.
The chain is short
You talk to the engineer who designs your software. At a consultancy there is an account manager, a project manager and often a junior developer between you and the code.
No juniors on your projects
A consultancy’s business model is margin on developers learning your industry at your expense. There are five of us, all senior.
Decisions take hours
Not steering committees. A call asked for in the morning is settled the same day.
We stay
Our oldest application has been running for ten years, every day, without an interruption of service.
The price stops moving
Once the scope is agreed, the figure is firm. No mid-project top-ups, no surprise variations.
It all goes into engineering
For the same budget, your money funds senior development rather than a sales organisation.
How it works
You never sign for a whole project without having seen the software run.
- 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. You keep the document.
- 02
Design
We come back with a complete proposal: what we build, in what order, on what schedule and at what price.
- 03
Sign-off
You decide what goes into the first version and what waits. The price becomes firm.
- 04
First scope
A small contract, and working software in your hands. You judge on the evidence and you are free to stop there. If it does not suit you, it is not invoiced.
- 05
Build
In short iterations, with versions to try throughout. You watch the software grow; you discover nothing at the end.
- 06
Delivery and maintenance
Go-live, training for your teams, then fixes and evolution over the long run.
What we commit to
- The price is firm once the scope is agreed.
- The first prototype is not invoiced if it does not suit you.
- Your teams work in the new tool before the project ends.
- A defect in what we delivered is never re-invoiced.
There are five of us. That is the argument.
You know who builds your software, and you speak to them directly.
Your point of contact, from the first call through to go-live.
Julien MarchandSenior software engineerData-heavy back ends. The one who makes three million rows answer in under a second.
Antoine BerthierSenior software engineerMobile and field capture. Builds for patchy signal, gloves and bright sunlight.
Mei TranSenior web engineerInterfaces and integrations. Connects what you already run rather than replacing it.
Claire AubertinUX / UI designDesigns for the people who will use it eight hours a day, not for a screenshot.
- 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
What we hear before signing
The three objections, and our answers.
“We will do it in-house”
Often the right call — when you already have the team. Otherwise, count the hiring, the months before a developer is genuinely productive in your industry, and what happens the day they leave with the only knowledge of the code.
We ship a first version in weeks, and we stay.
“We are not sure it will pay for itself”
Nobody can be sure before seeing the tool run. That is exactly why we start with a small scope and a working prototype.
You decide what happens next with the software in front of you, not a quote.
“We will look at it later”
It is the most expensive decision, because it does not show up anywhere. Another year is another year of retyping, entry errors and decisions taken on stale numbers.
The cost of waiting is something we can put a number on together, in two hours.
2hours
to find out what your spreadsheets really cost you
Remote or on site. We map your flows, identify what can be automated and in what order, and put a number on the time being lost. You keep the document.
No commitment · no automated follow-up · the document is yours