What must the review clarify for the decision?

Due diligence may examine system dependencies, change rights, data handling, supplier reliance or transformation needs. The available material, interviews, timetable and expressly excluded areas are agreed before work starts.

  • Which technical assumption could change the transaction decision?
  • What evidence is available, and what remains unverified?
  • Which dependencies or handovers warrant particular attention?
  • What conclusions can responsibly be reached within scope?

Experience connecting technology and business questions

Documented project experience includes programmes up to €30m and a core-system review for a Malta e-money institution. The 2021 review identified limited usable functionality, one unprotected database instance and licensor ownership of enhancements — factors relevant to the system decision.

A bounded assessment, not a legal opinion

The outcome is a technical and organisational assessment based on information supplied and agreed conversations. It does not replace legal, tax or audit advice, nor the decision of a buyer, seller or board.

A considered next step

Clarify the question before choosing the scope.

An initial conversation is for clarifying the issue, the available information and the boundaries. If another format is a better fit, that will be said plainly.

Discuss a due diligence question