Answer
A check makes sense when the project scope depends heavily on unknown data, external systems or existing source code. Examples include a legacy application without documentation, a complex ERP–shop connection or a company-wide process with several contradictory variants. Without an investigation, a binding implementation price would be either riskily high or unrealistically low.
The check is limited as a separate work package. Possible results are a process map, a system and data inventory, technical feasibility, a list of risks, a first scope of delivery, acceptance criteria and options with cost ranges. It must not turn into an endless consulting phase without a decision. The customer should receive the results in a usable form and then be able to decide whether, with whom and in what order to implement.
As of 3 September 2026
Further reading
Related topic: Our approach