[ LEGACY MODERNISATION ]

Replace the old system without switching it off.

Replace an ageing system one workflow at a time while it keeps running. Built after a 2-week discovery, in phases of 6–10 weeks, one phase per workflow.

[ WHAT WE BUILD ]

What we build.

  • A web application that takes over the old system one workflow at a time
  • Each new workflow runs alongside the old one for a month
  • The old screen is switched off only after that month
  • Built in Next.js, Node.js and PostgreSQL
  • The old system stays in use throughout

[ HOW IT RUNS ]

Discovery, then phases.

1. Discovery

Two weeks, for a fixed €7,500. You get a clickable prototype of the riskiest flow, an architecture note and a phase plan with prices.

2. One phase per workflow

Each workflow is its own phase of 6–10 weeks, with scope and price fixed before it starts. You see a demo every week. A new request goes into the next phase, priced separately.

3. A month alongside

The new workflow runs next to the old one for a month. The old screen is switched off only after that. Every phase is followed by 60 days of free fixes.

[ RELEVANT CASE ]

An order system for a freight forwarder.

2 of 5 workflows moved, no downtime

A freight forwarding company, UK

A Delphi desktop order system had been in use for about twenty years, and one person was left who could change it. Since May 2026, now in its 7th month, a web application in Next.js, Node.js and PostgreSQL has been taking over one workflow at a time. 2 of 5 workflows have moved (quoting, then bookings) with zero hours of downtime; invoicing is next.

Order system modernisation

Nothing was switched off until its replacement had run alongside it for a month.

— IT Manager, freight forwarding company, UK

[ WHAT WE DECLINE ]

What we decline.

Tell us what you need built.

We reply within 1 business day.