Find a safe next change in the software already running

An inherited application can contain valuable working behaviour alongside a frustrating fault. We investigate the problem and the dependencies before recommending replacement. The first useful result may be a repaired export, a reliable form or a clearer release process.

Reconstruct the operating picture

We establish the source, hosting, data, file storage, connected accounts and the people who currently keep things moving. A repository alone does not explain which scheduled task sends reminders or which staff member corrects a failed transfer every Friday. Those details matter when the business depends on the system.

For an illustrative Dutch service company, a planning tool might work for ordinary appointments but fail around a date change or a particular account role. We record a reproducible example using safe information and distinguish a data issue, integration failure and interface problem before deciding how far the repair should reach.

Make a controlled improvement

Scope can include diagnosis, focused code repair, dependency updates, a small replacement component and regression checks for affected tasks. Where a larger migration is justified, we separate immediate continuity work from the later architectural change. A build passing does not by itself establish that customers can still complete their work.

Leave the next maintainer less guessing

We document the changed behaviour, important configuration names, release steps and limitations. Provider access and a representative test environment influence what can be verified. Support hours and response arrangements are agreed explicitly; this page does not promise round-the-clock incident coverage.

Share the last known working behaviour, what changed recently and who controls the source and hosting accounts. Do not send passwords or private customer records in the first enquiry. If the handover is incomplete, a bounded assessment can establish what is known and which access decisions the owner needs to make next.