Compliance lives across systems.
State traceability, ERP, sales, production, laboratory, and finance records rarely agree without deliberate controls and reconciliation.
Cannabis systems & technical operations
I help cultivators, manufacturers, distributors, retailers, and multi-entity operators connect the technology, data, controls, and workflows required to run with less friction.
The operating reality
Cannabis systems cannot be designed as if compliance, inventory, facilities, and workforce realities are separate concerns. They collide in the same workflow.
State traceability, ERP, sales, production, laboratory, and finance records rarely agree without deliberate controls and reconciliation.
Cultivation, manufacturing, packaging, distribution, and retail each create transfers, conversions, labels, and exceptions that must remain auditable.
Cameras, retention, networks, access control, devices, scales, and facilities technology have to work continuously—not just pass a checklist.
Duplicative platforms and manual workarounds become especially expensive when operators are already managing price compression and regulatory overhead.
Proof from inside the operation
Anonymous cannabis inventory case study
An entire room of bulk biomass could be traced in the state system, yet packaging, storage, and bulk-sales teams still lacked a consistent, at-a-glance way to understand what each container held and what should happen next.
A Metrc sticker, a separately purchased single-color grade label, and a handwritten batch ID met individual needs without creating one reliable operating standard. Key dates, strain, and complete quality information were not consistently visible.
I built a Google Sheets record connected to a Brother labeler. The standardized label carried the full Metrc tag ID, quality grade, expiration date, strain, and harvest date while keeping regulated and internal records aligned.
Teams could see grade, age, harvest origin, and strain directly on the bag before committing it to a production input.
Expiration and quality information made it easier to organize the room around what needed attention instead of relying on tribal knowledge.
The complete Metrc UID could be scanned into downstream systems, reducing label inconsistency and production communication gaps.
Allocation to return
Anonymous cannabis processing case study
The critical control was not another compliance entry. It was linking each employee’s starting allocation to completed flower, trim, waste, and returned material while the batch was still being processed.
Completed weights were later entered through forms, and form responses sometimes needed modification. The process recorded work, but it did not create a timely percentage-return measure for finding loss or comparing batch results.
I used 232key to send the scale reading into the tablet form and added a controlled allocation workflow. Aggregating those responses created a returned-weight percentage that could be compared across employees, batches, grades, rooms, and facilities.
Immediate allocation-to-return audits sharply reduced product loss. Payroll used completed weights for commission checks, processing provided grade feedback, and cultivation received batch-level yield evidence instead of a disconnected retrospective report.
Rounded operating metrics; the cannabis operator remains anonymous.
The completed workflow made flower yield per square foot or per plant available on every finished batch. That became a critical cultivation decision point: Did the finished yield justify the space, plants, labor, and time invested?
Relevant experience
My scope has included business systems, data, infrastructure, physical security, access, vendors, governance, and the frontline work required to make changes stick across active facilities.
Multi-state operating scope
I held senior technology responsibility across one Nevada operating entity, four California cultivation entities and licenses, and a processing, packaging, and distribution site operating under two additional Metrc licenses.
Cultivation, processing, packaging, distribution, wholesale, retail, laboratory, finance, and executive reporting workflows.
Metrc traceability, surveillance retention, access control, auditability, inventory reconciliation, and business continuity.
Canix, Metrc, LeafLink, Aroya, Confident LIMS, SAP Business One, Acumatica/MaxQ, Shopify POS, and BigQuery.
Systems in context
I map the real operating flow across applications, data, people, devices, and regulated records so that no vendor’s software is mistaken for the whole business.
Metrc · Canix · Aroya · Confident LIMS
LeafLink · SAP Business One · Acumatica/MaxQ · Shopify POS
BigQuery · Looker Studio · Sheets · Apps Script · APIs · SQL
Google Workspace · Meraki · UniFi · Brivo · NVRs · MDM · scales · IoT
How I help
Map workflows, systems of record, access, compliance dependencies, data gaps, vendor cost, and operational risk.
Build repeatable checks between regulated records and the operational systems teams actually use.
Unify fragmented data and automate recurring reporting, reconciliation, and decision visibility.
Translate cultivation, manufacturing, distribution, retail, and finance realities into usable configurations and controls.
Strengthen identity, networks, devices, cameras, access control, retention planning, and site continuity.
Provide practical cross-functional leadership without forcing the cost or structure of a full executive technology team.
Questions before we start
The first conversation can focus on one recurring compliance, inventory, production, data, or infrastructure problem.
I work with cultivators, manufacturers, processors, distributors, retailers, brands, and multi-entity operators. My experience spans California and Nevada operations, from cultivation and production through wholesale, retail, compliance, finance, and executive reporting.
Yes. I map how packages, production conversions, labels, transfers, sales, and adjustments move across Metrc and the systems used by operations and finance. The goal is a controlled reconciliation process with clear ownership, not another manual report.
I support requirements, selection, implementation, integration, rescue, adoption, and governance across cannabis ERP, traceability, cultivation, sales, inventory, data, and infrastructure platforms. I am vendor-neutral and recommend the level of system the operation can sustain.
Yes. A focused assessment of one inventory, production, reporting, or compliance workflow is often the fastest way to identify the real constraint and prove value before expanding.
Start with the real problem
You do not need a finished scope. Describe the operational friction, compliance risk, blind spot, or technology cost you need to get under control.
Technology and operations consulting; not legal or regulatory advice.