All use cases
// Custom Software Development

Legacy system rebuild

Old software rebuilt, its data carried across.

Engagement that fits
Fixed-scope build, Product partnership
Stack
TypeScriptNestJSNext.jsPostgreSQLDrizzlePlaywright

// Overview

Where this product fits

// Audience

Who it is for

Businesses that run on an ageing system nobody wants to touch, where every change feels risky and the people who understood the code have long since moved on.

// Problem

The problem

The old system still holds the data and the rules the business depends on, so it cannot simply be switched off, and each fix on top makes the next harder.

// Deliverables

What we would build

  • A review of the code and the data

    We read the old code and its data to map every rule the business relies on, before anything is changed or switched off.

  • A rebuild on a modern, typed stack

    The system is rebuilt in typed, tested code on a current stack, so your team can change it again without fear of breaking it.

  • Migration with checks on every record

    Data moves from the old system to the new one with automated checks on every record, so nothing is lost or silently changed on the way.

  • Single sign-on for your staff

    Staff sign in with the accounts they already have, and their access to the new system follows their role in your organisation.

  • Reports rebuilt from the old system

    The reports people depend on are rebuilt to give the same answers, and checked against the old system before anyone relies on them.

  • Tests that pin the business rules

    Automated tests capture the rules the old system followed, so a later change that breaks one is caught before it reaches your users.

// Process

How it works

  1. 01.

    We read the old code and map its rules

    Every screen, job and rule in the old system is listed, so nothing it quietly does is forgotten in the rebuild.

  2. 02.

    The new system is built module by module

    Each part is rebuilt and tested on its own, so the business keeps running on the old system while the new one grows.

  3. 03.

    Data moves across and is checked

    Records are migrated in batches, and automated checks compare the old and new systems until they agree on every value.

  4. 04.

    Users switch over as each part is ready

    Teams move to each new module once it is proven, and the old system retires one part at a time.

What's next

Let's build
your product.

Tell us what you're building and where it stands. We'll scope it with you on a call and give you a straight answer on fit.

  1. 01

    Book a call

    Pick a time on our calendar and tell us what you want to build.

  2. 02

    Shape the scope

    Together we name the users, the first release and what success looks like.

  3. 03

    Get a proposal

    We send a written plan with the scope, the steps and the engagement that fits.

  4. 04

    Start the work

    We begin with Discovery and show you working software early and often.