Contact
Book a 30-minute call about your system. No slide deck.
Tell me what you are building and where it is in the lifecycle. I will be straight about whether my scope is the right fit and, if not, where you would be better served.
Contact Details
Location
Achtseweg Zuid 159R, 5651 GW, Eindhoven, The Netherlands
Frequently asked questions
Practical questions that come up most often before a discovery call. For lifecycle entry points and what each engagement looks like in detail, the Engagement page goes deeper.
What does TaoQ AI specialise in?
AI architecture and delivery, with a sharper focus on security, governance and evaluation. I design, build and secure AI systems for European tech companies. They need those systems to hold up to a regulator, an auditor, a customer or an attacker. The work covers EU AI Act conformity, ISO/IEC 42001 management systems, agent red-teaming and evaluation.
Do you write code, or just review it?
Both. I sit with your engineers, close the specific findings, write Annex IV evidence alongside the code, and stay until the system can stand up to scrutiny. The remediation model is collaborative; a report without closed findings leaves you with the same risk you started with. I also design and build the system itself when that is the engagement. It is principal-led, with security, governance, and evaluation engineered in from the start rather than retrofitted.
Do you work with companies outside the EU?
Yes. I am based in the Netherlands and EU AI Act conformity is my regulatory specialism, but the architecture and red-teaming work is jurisdiction-agnostic. Non-EU teams typically engage when European customers, partners, or expansion plans bring the AI Act into scope.
How do you work with an existing security or legal team?
Alongside, not instead of. The engineering side of EU AI Act conformity, agent red-teaming, and security architecture complements an in-house security team focused on traditional perimeter and a legal team focused on regulatory interpretation. I coordinate with them on shared deliverables.
How do you handle confidentiality and client references?
NDAs are signed before any technical material changes hands. Public case studies are sanitised and client names are withheld unless explicitly approved, and technical detail is generalised so it cannot be back-traced to a specific deployment.