Skip to content

New: AI StudioSee AI Studio

Loading

    All use cases

    Updated

    Use case · SaaS Products & MVPs

    Product rebuild

    Replacing an ageing product with a new codebase, feature by feature, while the existing one keeps running.

    An illustration of the kind of software we can build, not client work.

    What is a product rebuild?

    A product rebuild replaces an ageing software product with a new codebase while the existing one keeps serving customers. Done well, it moves functionality across in stages, with the old and new systems running side by side, so that no single release has to carry the whole product at once.

    When it is needed

    A rebuild is worth considering when the current system is blocking the business: changes take far longer than they should, the technology can no longer be hired for or supported, or the architecture cannot meet a security or scale requirement. If the problems are confined to a few areas, improving those areas is usually cheaper and safer than starting again.

    What it includes

    1. An audit of the existing product and its data
    2. A migration plan that moves features in stages
    3. Automated tests around the behaviour that must not change
    4. Data migration with a rehearsed cut-over

    Before the build

    Decisions to make early

    1. Rebuild or refactor

      List what the current system prevents. If the list is short and local, fix those parts. A rebuild needs a reason that touches the whole.

    2. In stages or all at once

      Replacing one area at a time behind the existing interface limits risk. A single cut-over is simpler to plan and harder to survive.

    3. What not to carry over

      A rebuild is the moment to drop features nobody uses. Usage data should decide, not memory.

    What tends to go wrong

    • Behaviour that customers rely on but nobody documented, discovered only after it has gone.
    • Freezing the old product for so long that the business falls behind while waiting.
    • A data migration rehearsed once, on a small sample.

    Where it fits

    Typically connects to

    • Existing database
    • GitHub
    • CI/CD pipeline

    Teams that use it

    Industries

    • Any industry

    Services involved

    FAQ

    Product rebuild: questions and answers

    When should software be rebuilt instead of refactored?

    Software should be rebuilt only when its problems come from foundations that cannot be changed in place, such as an unsupported framework or a data model that no longer fits the business. Where the problems are local, refactoring those parts delivers improvement sooner and with less risk than a product rebuild.

    How do you rebuild a product without downtime?

    A product can be rebuilt without downtime by moving it in stages. New components are placed behind the same interface as the old ones, traffic is shifted to them gradually, and both systems run in parallel until the new one is trusted. Data is migrated with rehearsals and a tested way to roll back.

    Build it. Ship it. Grow it.

    Book a free 15-minute call. No sales pitch, just an honest conversation about where you are and what it would take to get where you want to be.

    Book a call. It's free

    15-minute call. No commitment.