Tax and social security calculation software turned into a web application, increment by increment: 16 modules in production, a 5-minute calculation cut to a few milliseconds, not a single day of downtime.
500firms use it today
Software modernisation
Legacy software modernisation: regaining control of the tool nobody dares touch.
We rebuild it increment by increment, without service interruption, and we are paid on results. The business knowledge built into the existing system is preserved, not reinvented.
Increment by increment, one at a time
Without service interruption
Paid on results
Sovereign EU deliveryCII accreditationContractual reversibility
01 · The situation
Software built ten or fifteen years ago, central to the business. The current team no longer has a grip on the code, every change takes three times longer than planned, and users have built spreadsheets alongside it to work around it.
The real cost is not maintenance: it is everything the organisation can no longer change.
- Nobody in the current team has a grip on the code any more
- Every change takes three times longer than planned
- Your best people refuse to touch it; the others don’t dare
- Users have built parallel spreadsheets to work around the tool
- Hosting costs are rising faster than what gets delivered
02 · What we deliver
What it is
- The software rebuilt increment by increment, in service at every stage
- The code, the documentation and the tests, all yours
- Your teams trained during the project, not after it
- Maintenance afterwards, if you want it
What it is not
- A complete rewrite delivered in one go, several years down the line
- Time-and-materials staffing, billed by the day
- Packaged software to configure
- An audit that ends in a slide deck
03 · 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.
04 · They chose us
IMA
05 · The questions we are asked
“Do we have to rewrite everything?”
Rarely. A step-by-step modernisation is almost always less risky than a complete rewrite. Scoping establishes what is kept, what is rebuilt, and in what order.
“There is no documentation.”
That is the most common case. Reading the existing code is the first step of scoping: it produces the documentation that was missing.
“How do you avoid regressions?”
Automated tests, a pre-production environment identical to production, and a gradual go-live in which the old and new systems run in parallel.
“Who owns the code at the end?”
You do. Knowledge transfer is written into the contract.
“How does payment on results work?”
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 payable.
“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.
Write to us
Describe your situation.
A few lines are enough. Your message goes straight to the engineers who will do the scoping, and the first call is free.