Answer
With unknown software, a binding offer cannot be based on screenshots and a feature list alone. The effort depends on whether the system can be built reproducibly, which dependencies are outdated, how data is stored, whether tests exist and which parts are critical in day-to-day use. This information has to be checked in practice.
A technical check is therefore not a hidden down payment on a rebuild that has already been decided. It is a limited work package with its own results: a system inventory, key risks, outstanding access, prioritised immediate measures and realistic options for stabilisation, further development or replacement. This gives the customer a better basis for decisions – even if no large project with schukai follows. The scope and depth of the check must be agreed in advance; an unlimited analysis would be as useless as an unverified promise.
---
As of 3 September 2026
Further reading
Related topic: Taking over existing software