Acquire or take over.
Dependencies, access and continuity, before a sale.
Businesses and advisers: we examine your automated systems and AI to assess their reliability and anticipate risks.
Dependencies, access and continuity, before a sale.
Established causes, separated from hypotheses.
Discrepancies and missing safeguards, identified before an incident.
Each conclusion must be traceable to the material that supports it.
A missing record remains a limitation. It does not become proof.
Illustrative cases, to show the questions examined.
AWS infrastructure · Business takeover
Before a takeover, understand the AWS infrastructure and how it operates: recurring costs, technical debt, reliance on individuals, access rights and security risks.
The deliverable: a technical assessment and the issues to clarify before taking over.
Automated systems · Reliability and security
Data received and produced, rules, controls, traceability: we examine the entire process, whether automated or using AI, and the safeguards that protect your customers if it goes off track.
The report: observed discrepancies, identified risks and controls to strengthen, with the scope and limitations of the checks performed.
Have my system assessedMy experience in development, validation and automated systems supports a practical reading of how things work: what is intended, what is observed and what can be demonstrated.
Engagements are accepted according to scope, required skills and the absence of conflicts of interest. Specialist needs are identified during scoping.
Privately commissioned technical expertise · By quotation
One defined question, a limited set of material, a reasoned note.
System analysis, agreed tests, a report and its presentation.
A critical review of an existing report or results.
The scope, available records and depth of investigation determine the quotation. The assessment does not include implementing corrections; any further support is scoped separately.
The question, scope, access and deliverables are agreed in writing. Records are identified and copies preserved; observations, tests, alternative explanations and missing evidence are recorded. The report sets out the findings, the scope of the conclusions and their limitations; comments received and revisions are recorded in it.
Architecture, data flows, access rights, dependencies, controls and failure behaviour; tests are defined for the system and authorised access. Technical requirements and relevant obligations are identified for the case. For AI systems or personal data, evidence relating to the AI Act and GDPR is examined alongside your legal advisers. At launch: automated systems, digital architectures and artificial intelligence, within the agreed technical specialities; MedTech is excluded.
It describes observed behaviour within an agreed scope and set of scenarios, with the limitations of testing. Each conclusion identifies its supporting records and remaining uncertainties. It can identify discrepancies, drift or missing controls; it does not guarantee that the system will remain reliable indefinitely. The technical opinion informs the decision; legal characterisation is left to your advisers.
This is a privately commissioned technical assessment for a business or its adviser. Any use in proceedings is discussed with your lawyer; no admissibility or legal outcome is guaranteed.
The transfer channel, authorised recipients, retention and return arrangements are agreed before receipt. The initial exchange qualifies the request; sensitive documents should not be sent through the public form.