Four services, depending on the state your software is in — including when it does not exist yet.
01 · The situation
“We looked. Nothing out there does this. We’re told six months, and nobody will commit to the result.”
What we hear — programme director
What you were told
What it means
What we do about it
“You should adapt an existing product”
You will pay a licence for the half you do not need, and the other half will still have to be built
We write what you do, not what a product happens to do
“Allow a year and ten developers”
That estimate predates the collapse in the cost of producing software
A first increment in service within weeks, not quarters
“We can provide you with developers”
The risk stays with you, and the meter keeps running
A written scope, a metric in the contract, payment on results
“It’s not standard enough for us”
Your need matters to only one client: you
That is exactly why we exist
02 · What sets us apart
A small team
The person who writes the scope is the person who delivers. No intermediate layer between you and the people who write the software.
Payment on results
What will be measured, against what threshold and by what date is written into the contract. If the result is not achieved, the conditional portion is not due.
Delivery in weeks
You judge an increment in service, not a mock-up or a committee.
Sovereign EU delivery
No subcontracting outside the European Union, at any level. Managed from Aix-en-Provence and Paris.
What we do not offer
✕Staff provision, in any form
✕A generic information system overhaul
✕A project billed for time spent, even with a cap
✕A licence to rent
03 · Our four services
Four situations, one mechanism: a short first step, a written scope, a fixed price and a result written into the contract.
Build
Nothing exists yet: the work is done by hand, in a spreadsheet, or not tracked at all. We build the software no vendor has any reason to write.
Something exists — rented packaged software or software built in-house — and it no longer does the job. We replace it or extend it, and you take back control of your roadmap.
It runs, but nobody wants to touch it any more, or is able to. We take over the code after reading it: the knowledge no longer sits in one person’s head, and development gets moving again.
Run
What we have built or taken over, we maintain and keep evolving with your business — a volume of changes that you direct.
04 · How it works
01
A thirty-minute call
Free, and no demo. We listen to your situation and tell you whether we are the right people to help. If we are not, we say so.
02
Scoping
Two to three weeks, at a price stated before we start. You receive the written scope, the breakdown into increments and a fixed price for the first one.
03
The first increment
You decide on it with the scope and the price in front of you. It goes live rather than being demonstrated, and is judged on real use before the next one begins.
04
The following increments
One increment at a time, each priced before it starts. You can stop at the end of any of them, and we can then take over maintenance.
Scoping
The exact scope, the breakdown into increments, what is excluded
We spend time with the people who do the work today, and come away with the written scope, broken down into increments — with a fixed price for the first one.
Preceded by a free thirty-minute call. The price of scoping is stated before we start; the fixed price of the first increment is given once scoping is complete.
05 · What protects you
▪The source code can be placed in escrow with a third party.
▪Documentation is delivered with every increment, not at the end.
▪Reversibility is written into the contract.
▪The technologies we use are standard and non-proprietary.
The answer to the question of our durability is not to promise you that we will last. It is to make sure it does not matter.
06 · They chose us
A government ministry, a rail operator, two CAC 40 groups, a regional health agency, a software vendor. Very different settings — it is the range that counts.
IMA
07 · Frequently asked questions
“You only show a limited number of situations. Can you do anything else?”
The pages of this site describe situations we come across often enough to have built tools for them. The rest of our work is what is described here, and historically it has been the largest part.
“How long before we see something?”
The first increment goes into service; it is not a demo. The order of magnitude is a few weeks after scoping, and it is set down in writing before you commit.
“Who writes the code?”
We do, with engineers who have worked with us for years. Within the European Union, with no subcontracting outside it.
“What happens if the scope changes?”
It changes through a costed amendment, agreed before the work is done. Never silently, and never at the end of the project.
“How much does it cost?”
The first call is free. Scoping has a price, stated before we start. The price of the first increment is fixed and given once scoping is complete: it depends on the scope, not on who is asking.
