More than a decade in regulated environments, last position Head of IT: I designed the infrastructure, ran it, owned the budgets, and met FDA- and EMA-grade audits with my signature on the line. Before that and alongside it: software development delivered as project manager for German healthcare infrastructure projects. GxP and GDPR: problems I have solved before, from the side that had to answer for them. NIS2 and the AI Act are brand new for everyone: I approach them with the same validation and qualification lens that made the older regimes provable.
Something happened or is about to. A regulator letter, a departing IT head, an AI budget nobody can govern, a migration that cannot fail.
What I take, what I do not take, what "done" means. Agreed before work begins. A fixed figure, agreed before work begins. The figure does not move.
Claims get tested against evidence, not slides. What passes, passes visibly. What fails, fails early and cheap.
Every finding, test and decision documented. The record survives the engagement, the employee and the vendor.
The engagement ends. You keep the evidence and the capability. I do not become infrastructure.
One line describes every job: I take the mandate, I verify or steer the work, I hand over the record, I leave. Every decision stays with your management, together with the responsibility that comes with it. What I deliver is the ground the decision stands on: signed, traceable, mine to defend.

ENGAGEMENT 1
The customer questionnaire arrived, the insurer wants evidence at renewal, the authority is asking, or your board just learned about personal liability. I test whether your measures are configured right, run provably, and hold under load, across NIS2, GDPR, ISO 27001 or the AI Act. I sat on the accountable side of that table for more than ten years, last as Head of IT: I designed the infrastructure, ran it, and defended it in FDA- and EMA-grade audits, with signatures on the line. I know how auditors read your estate because it was my estate on the table. You get a written Qualification Report: what you can actually prove, gaps named by severity, and a remediation path with effort estimates. Typically five working days. No access to your systems required: you run the protocols, I assess the evidence.

ENGAGEMENT 2
The budget is approved, the pilots are multiplying, and nobody in the room can answer: what runs where, who verified it, what happens when it is wrong. I run my own AI stack end to end: owned hardware, own weights, own logging, local inference every day. So the governance questions get answered from the person who operates what you are buying, not from a slide. Architecture decisions made defensible. Deployments verified, not demonstrated. Vendor claims tested, not attended. Plus the regulated-industry discipline the AI Act actually requires: the same qualification spine I applied for over a decade under FDA and EMA scrutiny. Your management gets an AI posture it can defend; your auditors get a record they can trace.

ENGAGEMENT 3
A datacenter move, a cloud exit or entry, an ERP decision, a vendor swap where breakage is not an option. I designed and ran exactly these estates for thirteen countries and several hundred staff, through migrations, consolidations and acquisitions. The baseline is captured before anything moves. Gates at every step. Rollback that is tested, not promised. You get the move, plus the record that proves why it was done right. Migrations fail quietly when nobody owns the verification. Here, somebody owns it: the person who built infrastructure like yours and kept it alive under auditors.

ENGAGEMENT 4
Your IT head is leaving. Or just arrived. Or an acquisition merged two estates nobody fully trusts. The outgoing party presents a clean story; the incoming party discovers problems later. Between those two stories sits the truth, and today nobody verifies it. I was the leaving party's chair for thirteen years: I know what gets documented, what quietly gets lost, and what only surfaces in the first outage after the goodbye. I capture the baseline before the departure: inventory, configuration, known issues, conformance tests. You get a handover record both sides sign, built by someone who has lived on both ends of the table. Cheaper than the surprise outage. Cheaper than the slow erosion of trust.

ENGAGEMENT 5
A strategic IT decision is on the table and no internal capacity owns it. Or the leadership gap is longer than your patience and shorter than a hiring cycle. I was the Head of IT who made those calls and signed the outcomes: budgets, vendors, exits, rebuilds, across international environments and distributed teams. I step in with the authority the situation needs and none it does not. Decisions framed, options measured, consequences named. Implementation steered until your own people can carry it. You get executive-grade IT judgment from someone who carried the badge himself, and a team that can hold it afterward. Judgment by outcome, not presence sold by the day.
The team that built it cannot certify it. The vendor that sold it cannot audit it. The manager who inherits it cannot prove what they received. The board that funds it cannot see through it. Every organization needs this check. No organization can generate it from inside. That is the practice: independent by structure, not by claim.
Why you should not trust an ordinary IT consultant with this.
Your management stays responsible for your company. That boundary is the service. What I carry is my verdict and the evidence behind it: written for authorities, auditors, and the worst case, when an insolvency administrator reads every page.
Former Head of IT, international CRO. Project manager for software development in German healthcare infrastructure. Independent mandate office for AI and IT governance.
More than ten years in environments where FDA- and EMA-grade scrutiny was normal work, not a project. I owned the accountable side of those audits, signed when the evidence was sufficient, and knew when it was not. Managed and audited vendors across thirteen countries, several hundred staff, distributed delivery. I build and run my own local AI lab today: the governance claim on this site is lived, not licensed. The one lesson from regulated industry that changes everything when it moves into your company: when it fails, what counts is not the excuse. It is the record.
More than ten years in FDA- and EMA-grade environments where the signature on the qualification meant something. That reflex is now applied to your AI stack.
I know the full lifecycle of an IT budget and spot flawed planning early, because I defended those numbers myself.
I uncover the hidden costs that never appear on the datasheet, because I paid them across continents.
Local AI runs on owned metal here daily: the sovereign-infrastructure claims on this site pass through my own evidence first.
A short fit check: describe your trigger in your own words, read five descriptions, and see which mandate your situation actually matches. Runs entirely in your browser. Nothing stored, nothing sent. It ends with one answer: this is mandate X, or none of them. If it is one of them, the first conversation starts where the fit check stopped. If it is none of them, you saved us both the time.
No. A consulting firm sells availability and slides. This is a small office that takes mandates: a defined trigger, a scope agreed in writing, gates the work must pass, and a written exit. Verification, qualification, migration control, handover assurance - the tools come from the situation, not from a service catalog. The invoice follows a finished outcome, never the calendar.
No. I take defined work and end it. You keep the evidence and the capability. If an engagement ever starts to feel like permanent staff augmentation, stop it. If I notice first, I will tell you.
NIS2 and GDPR are only the ones with deadlines. Insurers, corporate customers and boards now apply regulated-grade scrutiny without any statute behind it. The method is the same either way.
A package price tells you that something generic was sold before anyone understood the situation. What you get instead: a fixed figure agreed before work begins, defined scope, no hourly billing, no lock-in. The figure does not move. I take a limited number of engagements per year. If the calendar is full, you will hear that immediately.
Yes. The first conversation establishes the trigger, the scope, and whether I am the right office for it. If we are not the right fit, you hear that in the call, not on an invoice.
An interim manager fills a seat. I take work with gates and an exit. The seat is paid for presence. The work is paid for findings and handover.
By design: the person who assesses your situation is the person who does the work, with no handoff to juniors. If I cannot deliver, you hear it on day one, not mid-engagement. That is the trade you make for a personal guarantee instead of a brand guarantee.
Jan Richter. Sole practitioner. The only name on the work is mine.
Not a lead form. A description: what happened, what is coming, what cannot be solved inside. We respond quickly. If this is not something I should take, you will hear that first.