I am an IT expert witness based in London. I help courts, tribunals and legal teams understand what actually happened inside the technology at the centre of a dispute.
Areas of expertise
I have worked as a Technical Director in web and software agencies, eCommerce retailers and SaaS companies. If it is not clear whether a matter fits one of these areas, ask.
Disputed functionality, defects, code quality and failed delivery.
Multi-system integrations, bottlenecks and architectural failure.
Data accuracy, loss, manipulation and the reliability of reported figures.
Authenticity, provenance and metadata of emails, messages and files.
Adequacy of controls, breach causation and regulatory reasonableness.
Model behaviour, automated decisions and AI governance.
Representative engagements
Anonymised summaries. Client and matter details are confidential.
High Court, CPR Part 35
Instructed in a matter involving a major bank to determine whether an individual had ever held an account or funds with the institution. Conducted a full technical investigation and produced a CPR 35 compliant expert report.
United States, litigation consultant
Acted as a litigation consultant in a high-profile US copyright dispute involving allegations of code manipulation and disputed authorship. Advised on version control systems, commit integrity, source and object code analysis, and DNS forensic evidence, with findings presented through memoranda, expert declarations and technical presentations.
DIAC arbitration and CPR Part 35
Supported matters involving alleged manipulation of communications across WhatsApp, Telegram, email platforms and device databases. Conducted detailed forensic reviews, built NLP similarity scoring tools, and contributed to DIAC-compliant and CPR 35 compliant reporting on authenticity and manipulation risks.
How I work with clients
From early advice before proceedings start, through to written evidence and the hearing.
AI governance only works when the whole organisation owns it. How ISO/IEC 42001 and the EU AI Act translate into evidence across the board, legal, data protection, security, procurement, HR and engineering, and what the evidence looks like when governance existed only on paper.
AI coding assistants have changed how software is written, but not what production software has to be. Why MVP standard is not production standard, what provenance evidence exists for AI-generated code, and what a reasonably competent team does now.
Whether a development team followed its own process can usually be shown from Git, CI and ticketing records. But that evidence is only as trustworthy as the IT estate it runs on: unmanaged devices, missing DLP and absent endpoint protection undermine both the software and the record of how it was built.
Let's work together
Send a short outline of the matter, the parties and any deadlines. I will run a conflict check and reply, usually within one working day.