Not a prototype. Not a demo. A production platform — running real samples in a real accredited lab, generating real compliance documentation, enforcing real regulatory frameworks. In one week. By having a conversation with an AI.
I graduated high school. I was diagnosed with ADHD and dyslexia at an age when most people just called it something else. I spent a career learning to read rooms, spot patterns, and solve problems that the credentialed people couldn’t see — because they were trained to look at the wrong thing.
I run BRS Lab Services. A real lab. Dual-licensed. Michigan and Ontario. We test real samples for real clients and we sign our name to results that matter — food safety, environmental compliance, microbial contamination. The kind of work where a wrong answer isn’t a rounding error. It’s a liability. It’s someone’s health. It’s a business that doesn’t open tomorrow.
I needed software. The legacy LIMS vendors quoted me $50,000 and two years. I sat with that for about five minutes. Then I ran out of patience — and started typing.
- 200,000+ lines of production code
- 106 AI agents doing real lab work
- 14 compliance frameworks enforced at the architecture layer
- 811 automated tests — published publicly every month
- 10 live verticals across regulated industries
- HL7 FHIR R4 EMR & Salesforce connectivity
- 21 CFR Part 11 architecture review passed
- EU AI Act compliance module — Articles 9–17
- Major testing organizations across 4 continents now evaluating it
That didn’t happen because I’m exceptional. It happened because the barrier to building something real is no longer technical ability. It never was — we just accepted that it was, because the people who controlled the tools needed us to believe it.
What it actually takes is knowing what the problem really is. Being willing to ask the right question. And refusing — flat out refusing — to accept that the answer requires someone else’s permission.
ADHD made me impatient with things that don’t work. Dyslexia made me see structure where other people see noise. Forty years of working in regulated industries — where the rules exist because lives depend on them — made me understand compliance not as a burden but as a design constraint. I don’t resent ISO 17025. I don’t resent 21 CFR Part 11. I build around them. They’re not the enemy. They’re the architecture.
The Marine Corps taught me something that most software companies never learn: you don’t wait for perfect conditions. You execute with what you have, you adapt in real time, and you do not stop moving forward.
I am furious that the lab industry has been held hostage by legacy vendors who charge $50,000 to set up software and then charge by the hour to change it. I am furious that small labs — doing critical work, protecting public health, running on thin margins — have been told for decades that enterprise-grade compliance infrastructure is not for them. That it costs too much. That it takes too long. That they need a consultant just to get started.
That is over.
The gatekeepers of the technical world no longer get to decide who builds things. Not because someone passed a law. Not because the industry had a change of heart. Because the tools changed — and the people who were shut out for decades are the ones who know exactly what to build with them.
I built AILS because I run a regulated lab and I knew what was broken. I built it because I refused to wait two years for a vendor to build something I could start using today. I built it because every small lab director who has ever sat through a LIMS sales pitch and done the math and walked away defeated deserved better.
To every person who was told their brain worked wrong — it didn’t. The tools just finally caught up.
