CompoundIQ
503B facility lifecycle tracking from a single FDA spreadsheet, modeled into history you can monitor, query, and trust.
View case studyI design intelligence and optimization systems for compound drug procurement: where pricing, compliance, and operations intersect.
Focus Areas
Portfolio
503B facility lifecycle tracking from a single FDA spreadsheet, modeled into history you can monitor, query, and trust.
View case studyTurning a fragmented licensing portal into a searchable, enriched directory and market analysis of California sterile compounding capacity.
View case studyA lightweight procurement calculator for sterile drugs that turns messy dosing, vial, and compliance rules into fast, defensible purchasing math.
View case studyA privacy-first, offline Android application for medical inventory tracking built for solo providers and mobile practices.
View case studyA privacy-first, browser-based tool for diagnosing and fixing spreadsheet data quality—no accounts, no uploads to third parties.
View case studyThe Challenge
Compound pharmacy data is fragmented, overwritten, and often released in formats that resist automation. Pricing behaves non-linearly due to aggregation agreements. Regulatory signals are buried in PDFs and portals with no historical continuity.
Most analytics approaches fail because they assume clean inputs and stable definitions. I design systems that assume the opposite.
Philosophy
In regulated markets, data quality isn't a nice-to-have—it's the foundation of defensible decisions. I build validation into every layer of a system, not as an afterthought but as a core design principle.
This means explicit data contracts, automated anomaly detection, and clear lineage from source to output.
Machine learning has genuine applications in pharmacy analytics—demand forecasting, anomaly detection, entity resolution. But ML models in regulated environments require guardrails that most implementations lack.
I'm skeptical of black-box predictions for high-stakes decisions. Models should be interpretable and validated against domain expertise.
The best decision systems don't replace human judgment—they augment it. In procurement and compliance, context matters in ways that algorithms can't fully capture.
I design systems that surface relevant information, flag anomalies, and suggest actions, but preserve space for expert override.
Not every problem needs a distributed data platform. Some of the most effective decision systems I've built run on surprisingly modest infrastructure because the architecture was matched to the actual requirements.
Complexity should be earned, not assumed.
In healthcare procurement, decisions have real consequences—patient safety, regulatory compliance, financial exposure. Systems that can't explain their recommendations aren't trustworthy enough for these contexts.
I build systems where every output can be traced to its inputs and where assumptions are explicit.
Principles
If you're working on procurement strategy, supplier risk, or market intelligence in compound or sterile drugs, I'm always open to thoughtful conversations and can be reached on LinkedIn.