Start from the problem

Replatform a legacy ERP

Off a system nobody will support next year.

The system still works. That is what makes this hard to argue for. But support is ending, the people who know it are retiring, and every change costs more than the last one. Replatforming is a decision about the next ten years, taken while the current one is still limping along.

The signals

How you know it is time

  • Support is ending

    A version nobody will patch next year, or a vendor that has moved on to the successor product.

  • Change is expensive

    Every request becomes a project because the customisations fight each other.

  • Knowledge is thin

    One or two people understand it, and neither of them is junior.

  • Workarounds are the process

    The real system of record is a spreadsheet somebody rebuilds every month.

How we work

Discovery, design, build, run

The first stage matters most here. A replatform that starts by copying the old system into a new one has already failed.

  1. Discovery

    We look at what you actually have, and what has to still be true afterwards. There is no meter running on discussion time here. You get as many sessions as it takes to understand what is being built and why.

  2. Design

    Written down before anything is built. Scope, the shape of the solution, and the things we have agreed not to do.

  3. Build

    In the open, against real data, in increments you can look at. Nothing arrives as a surprise at the end.

  4. Run

    Live, then supported. Monitored, maintained, and extended as the business changes.

What you get

What is on the table at the end

  • A written case for the change, or against it
  • Field level mapping from the old system to the new one
  • A reconciliation you can run yourself
  • A rehearsed cutover, not a first attempt on the night
  • Documentation for the system you end up with
  • Support from the team that built it

Engagement

How this gets bought

Four ways

Fixed price, time and materials, retainer, or managed service. There is no minimum engagement size, so a single integration is a real conversation and not a rounding error.

What you are paying for

Senior people on the actual work, not a pyramid with one architect and fifteen juniors. Large firms charge a premium that has more to do with their overhead than with the quality of the delivery. The same work can be done properly for less, and that is the reason this company exists.