You run quality in pharma, biotech or a CDMO and have 1 or 2 AI systems in use or planned
You get early access to the working prototype, my own hands on the first validation and a say in what the product becomes.
The AI drafts. A person signs.
It classifies an AI system by GxP risk, sizes the validation to that risk and drafts the evidence set. A named person reviews and signs every record.
AIV runs the 4-tier method from my book, Validating AI in GxP Environments: A Practitioner's Handbook, the same way every time.
A classifier, a vision model, an LLM application, a RAG assistant or an agent, built in-house or bought from a supplier. Each step leaves a record.
4 questions set the GxP risk tier by a published rule, from what happens when the output is wrong.
The tier decides how much validation the system gets. A dashboard nobody acts on gets a light touch. A system that routes a CAPA gets the full treatment.
Intended use, acceptance criteria, protocols and records come out ready for review. The AI layer drafts them.
Every signature carries a name, a role, its meaning and a timestamp, the shape 21 CFR Part 11 asks for. Nobody can approve their own work.
After release, monitoring watches for drift and sends the system back for reclassification when its scope, its data or its performance changes.
The AI layer drafts documents, proposes acceptance criteria and extracts facts from the material you give it. It never classifies a system, never signs a record and never lowers a criterion.
Your data trains nothing. The AI layer runs on a private endpoint, and what you put into AIV stays in your evidence record.
Design-partner conversations are open with 2 kinds of organisation. Both get the same thing and are asked for the same thing.
You get early access to the working prototype, my own hands on the first validation and a say in what the product becomes.
You get one validated method your customers can inherit, my own hands on the first validation and a say in what the product becomes.
What I ask in return: one real AI system, honest feedback and permission to describe the outcome without naming your company.
Answer 4 questions about one AI system and see its GxP risk tier and the validation shape it calls for. A simple model can sit higher than a complex one.
1. Does the output influence a GxP decision at all?
2. If it were wrong on 10% of records for 6 months without anyone noticing, would patient safety, product quality or data integrity be at material risk?
3. Does a qualified human review and approve every output before a GxP action is taken?
4. Can a human override the decision through an exception path that exists in the live workflow?
This is the classification step. AIV takes it from here: it sizes the validation, builds the evidence set and records the execution.
Pilots begin with a conversation about one real AI system.
If you'd rather talk, book a conversation with Sachin and bring the system with you.
No. AIV sits beside your existing validation platform and handles the AI-specific part: the risk tier, the evidence set an AI system needs and the controls that keep it in check after release. Your ERP, LIMS and equipment validation stay where they are today.
No. AIV takes the numbers your own tools produce, such as accuracy on a test set or drift readings in production, and turns them into evidence with acceptance criteria, a tester, a timestamp and a signature.
No. Nothing you put into AIV trains a model, ours or anyone else's. The AI layer runs on a private endpoint, and what you enter stays inside your evidence record.
AIV is in development, and design-partner conversations are open now. Dates will be shared with design partners. If you have an AI system you need to validate, ask about a pilot and we'll talk about whether it fits.
Security, data handling and the company behind AIV are on the AIV product site.