Services
Move an ageing system to modern architecture one slice at a time, with the old and new running side by side until the last switch.
Most of the platforms we modernise are the ones the business can least afford to turn off: payments cores, routing engines, order management. A two-year rewrite with a single cutover is the riskiest way to replace them, and it usually stalls in the second year when the business still needs new features.
We do it the other way. We map what the system really does, pick the slice that gives the most value for the least risk, build its replacement beside the old code and switch traffic across only when the two agree. Each slice is live within weeks, so the business sees progress every month and can stop or change course at any point.
Your engineers work with ours from the first day. By the time the last slice moves, they know the new platform better than we do.
Three weeks tracing every flow in and out of the system, with your architects, operations and risk teams.
Slices ranked by value and risk, with a target architecture you can explain to the board on one page.
Each new service runs on a copy of live traffic while we compare every result with the old system.
Traffic moves across once results match, with a one-click route back. Then the next slice.
Time and materials after a fixed-price discovery. Each slice is estimated in advance and we report spend against it every fortnight.
Day rates per person
Day rates exclude 5% VAT. Where a rate sits in its range depends on experience; rates are the same in all three studios and fixed for 12 months from signing. Every engagement is quoted in writing before work starts.
Ask for a quote
Ruwaq BankFinancial services
Instead of a rewrite, we replaced the old core service by service, running both side by side until the last switch.
Qafila ExpressLogistics
Qafila’s routing engine fell over every November sale. We rebuilt it as event-driven services on their existing cloud, shipping the first slice in five weeks.
Rewrites deliver nothing until the end, and the end keeps moving. Replacing a system slice by slice means value from the first month, and you can stop at any point with a working system.
Yes, and they should. We agree which parts of the code are frozen for each slice, usually for a few weeks at a time, and everything else carries on as normal.
Yes. We’ve replaced COBOL batch jobs, licensed payments and warehouse systems, and Oracle Forms applications. We read the old code ourselves rather than relying on documentation.
The one your team already knows or can hire for. We’ve no reseller agreements with any cloud provider, so we don’t gain from the choice either way.
Describe the problem in a few lines. A partner replies within one working day.
We use essential cookies to make this site work. With your permission we’d also use analytics cookies to see which pages help people most. Cookie policy