Compare two complete operating choices

A replacement can look cheaper when the estimate covers new screens but omits the work needed to carry the business across. A repair can look cheaper when it omits recurring investigation and the limitations that remain. Compare the operating result of each choice, not just the first development invoice.

For a fictional bilingual catalogue, the current site has confusing editing controls but dependable product references and established links. A new platform offers a cleaner editor. The decision depends on whether those references, documents and enquiries can be preserved through the move.

Establish the baseline worth keeping

List the customer tasks that work and the records needed to continue them. Include shared links, language counterparts, downloads, ongoing enquiries and staff exports. Some dependencies will be invisible in the main navigation.

Then describe the demonstrated fault and its frequency. A reproducible failure supports a repair estimate; a vague impression that the technology is old does not explain what must change.

Price the missing work in each option

A repair might include a supported update, revised editing controls and regression checks. It also needs a clear statement of which constraints persist. Replacement needs data preparation, route handling, permissions, training and a method to reconcile changes made during the transition.

The business should decide who owns those activities and whether any require an external provider. They are not automatically included merely because a proposal says “migration.”

Test the assumptions before committing

Move a representative product set in a private trial, including an awkward document relationship and a record with missing information. Inspect what the new system retains and what it cannot express. Compare that with a bounded repair experiment on the old workflow.

Do not treat a successful sample as proof that every record will migrate cleanly. It identifies the next questions and gives the estimate a firmer basis.

Consider a staged boundary

The useful choice may be to improve public pages while retaining the current product system, or replace one failed connection while postponing a larger platform move. A staged plan needs explicit ownership across the boundary so the business does not end up maintaining two competing sources indefinitely.

Repair services can begin with the observed failure. Scope planning helps identify the assumptions that must be settled before either option is approved.