01 / Independent technical opinion

Twenty years of code that ships.Now read carefully, and on the record.

Independent technical expert for software and AI matters, engaged by counsel, courts, arbitrators and boards across Switzerland and Germany. I work from the code, the infrastructure and the contracts themselves, and follow each claim back to what is actually in them.

ITDR-listed technical expert · itdr.ch
02 / Three roles

One expert, three ways to be instructed.

I

Parteigutachten

Independent technical opinion, instructed by counsel.

When
Civil litigation, commercial court matters, international arbitration. When you need a defensible technical opinion that survives cross-examination.
Deliverable
Written Gutachten, typically 30-80 pages: Auftrag, Methodik, Sachverhalt, Befunde, Würdigung, Kernbefunde. Filed under your firm cover, with oral readiness for hearings.
Fee
Time and materials at CHF day or hourly rates, cap agreed up front.
Typically for
Litigation counsel, in-house counsel, arbitration teams.
II

Werkvertrags-Gutachten

Independent acceptance expert, named by both parties.

When
Software procurement and works contracts where both parties designate an independent expert to assess delivery against specification.
Deliverable
Prüfschema developed from the contract annexes, structured Abnahmeprüfung, written Gutachten with Bewertungsmatrix. Optional Nachprüfung after Nachbesserungen.
Fee
Pauschal fixed fee, split between parties.
Typically for
Contracting parties (procurer + supplier), public sector procurement.
III

AI / technology due diligence

Independent technical assessment for capital decisions.

When
M&A buy-side or sell-side, primary investments, board-level risk reviews, post-acquisition value creation diagnosis.
Deliverable
Maturity scoring across 5 pillars (architecture, team, ops, security, AI exposure), verification matrix against vendor claims, IC-ready value creation thesis or risk register.
Fee
Fixed fee; 3-10 working days depending on scope.
Typically for
PE / VC investment teams, boards, family offices, M&A advisors.
03 / How an opinion is produced

Four phases, clear handovers, documented methodology.

  1. 01 · Intake

    Confidential call

    Thirty minutes. Matter type, jurisdiction, deadline. Conflict declaration. Engagement letter and scope.

    Within 48 hours
  2. 02 · Evidence

    Documents and access

    Contracts, source repositories, infrastructure access. First impressions call within 5-7 working days. Question catalogue iterated with you.

    Days 1-10
  3. 03 · Opinion

    Structured Gutachten

    Auftrag, Methodik, Sachverhalt, Befunde, Würdigung, Kernbefunde. Two review cycles standard. Track changes welcome.

    Weeks 2-6
  4. 04 · Delivery

    Report and hearings

    Final report under your cover. Oral readiness for hearings or steering committees. Available DE / EN. Aftercare on follow-up questions.

    On hearing date
04 / Matters

Where the opinion rests on the code.

  • Software acceptance and delivery disputes
  • Works-contract acceptance against specification
  • Software copyright and code-derivation questions
  • AI system claims and vendor capability checks
  • Infrastructure forensics
  • Contract versus implementation comparisons
Domains

Seven areas where my technical depth holds up under examination. For matters outside these, I say so up front.

  • Healthcare & clinical software

    Clinical information systems, regulated medical software, hospital deployments, data residency, multi-disciplinary teams. Multi-year operational experience inside the largest CIS in Switzerland.

  • Financial services

    Payment platforms, regtech, AML / fraud automation, fintech AI features. Production AI in regulated environments. Risk-aware vendor and architecture review for boards.

  • Legal technology, IP & code forensics

    Contract lifecycle management, document review automation. Founded an AI-native CLM platform, fluent on both the platform side and the regulator-facing side. Open-source license compliance, code-derivation analysis and copyright assessment for software disputes.

  • Public sector & procurement

    Software acceptance for cantonal and federal contracts, Power Platform, ERP modernisations. Werkvertrags-Gutachten experience for joint procurer / supplier mandates.

  • AI safety & frontier model risk

    OpenAI Red Team Network alumnus. AI policy and abuse-resilience review, model card analysis, safety governance for portfolios deploying frontier models.

  • Sovereign + private AI

    Production experience deploying on-prem and VPC inference for regulated workflows: custom-trained local NER, fine-tuned small language models, audit and provenance by default. I review private-AI strategy because I have shipped it (DocIQ Shield, KISIM AI), not because I read about it.

  • Mid-market software, PE-backed

    AI maturity assessments, Agentic SDLC introduction, post-acquisition value creation diagnosis. Daily exposure to portfolio software companies across DACH.

05 / Common questions

What counsel ask first.

How quickly can you respond to a new matter?

Initial confidential call within 48 hours. Engagement letter usually within 5 working days of intake. Accelerated matters can start the same week if the conflict declaration clears.

How do you handle conflicts of interest?

Every intake includes a structured conflict declaration step listing parties, counsel and adverse parties. I check against my active engagements and a documented prior-mandates list before accepting. If a conflict exists I decline and explain.

What does an engagement cost?

Parteigutachten bill on a time-and-materials basis at CHF day or hourly rates, with a cap agreed up front. Technology due diligence is a fixed fee, scoped at 3-10 working days. Werkvertrags-Gutachten are typically a pauschal fixed fee, split between procurer and supplier. Specific numbers shared on the intake call.

Confidentiality and data handling?

Default NDA before any case material is shared. Source code reviewed only in environments under your or your client's control. No client material on third-party AI services without written consent. Working notes destroyed on engagement close, except as required by professional retention rules.

Will you appear at hearings?

Yes. Oral readiness for the Gutachten is part of the engagement. I attend hearings, steering committees and arbitration sessions in DE or EN, in CH and DE typically, occasionally further afield by arrangement.

What if my matter falls outside your domain expertise?

I say so on the first call. Where it makes sense I refer to other ITDR-listed experts or specialist co-experts and stay involved in the technical-review chain only if useful.

Do you accept opposing-party engagements after a prior mandate?

Prior parties stay on a documented seven-year list, checked at every intake. Where that check turns up any reasonable conflict, I decline. In practice that rules out most opposing-party work.

06 / Confidential intake

Open a confidential intake.

For counsel, courts, arbitrators, boards and investors. The form is a structured replacement for a first call; it tells me whether I can act, on what, and how fast. NDA before any case material is shared.

Notice

Submitting this intake creates no engagement and no privileged relationship. I treat the contents as confidential and will respond within 48 hours, including if I have to decline.

Confidential intake

Matter type, jurisdiction, deadline. Thirty minutes.

A confidential first call with a conflict declaration before any document changes hands.