I'm a cannabis data analyst and independent builder focused on practical tools for one of the messiest data environments around: cannabis retail, lab testing, inventory, menus, and compliance-adjacent workflows.
My work is about turning inconsistent industry data into clean, repeatable systems that operators, analysts, and developers can actually use.
A C# parser for cannabis Certificates of Analysis.
The goal: take messy COA PDFs and convert them into structured, testable data that can support downstream reporting, validation, and automation.
Current focus:
- Lab-specific parsing adapters
- Product type classification
- Cannabinoid and chemistry extraction
- Batch testing across real COA fixtures
- CLI output for JSON/CSV workflows
- Parser reliability through repeatable tests
A shared cannabis math library implemented across multiple languages:
- C#
- TypeScript
- Python
The goal: consistent cannabis calculations with shared test expectations across ecosystems.
Focus areas include potency math, weights, dosing, pricing, packaging, taxes, and rounding logic.
A cannabis-focused calculator/tooling project for common retail and product math workflows.
Built to support practical calculations around cannabis products, potency, weight, pricing, and retail logic.
- Clean data pipelines
- Practical automation
- Cannabis retail intelligence
- Parser reliability
- Repeatable test coverage
- Tools that reduce manual work
- Operator-friendly workflows
- Making cannabis data less painful to work with
- C#
- .NET
- Python
- TypeScript
- SQL
- PostgreSQL
- Docker
- GitHub
- CLI tooling
- Data parsing
- CSV/JSON workflows
- Retail analytics
I'm building open-source cannabis data tools that solve real operational problems: messy lab documents, inconsistent product data, fragmented menus, and manual reporting workflows.
The industry has enough chaos. The data doesn't need to add more.