Heading 1

Why This Moment Matters

Five years before New York's adult-use launch, Canada walked the same arc: a license rush, a regulatory catch-up phase, then a clear divergence between operators who built real operational infrastructure early and operators who didn't. The first group is still scaling. Many in the second group aren't.

New York is in the catch-up phase right now. The state has transitioned from BioTrack to Metrc, OCM has tightened GMP expectations, and lab capacity, packaging rules, and recall readiness have all moved up the inspector's checklist. In the background, wholesale prices are compressing on the same trajectory CO, MI, and CA walked once supply caught up with demand. The decisions cultivators and processors make in the next two quarters will look small in the moment — and large in 18 months.

Who This Applies To

Whatever your license type, the next 12 months will reward operators who treat compliance infrastructure as a margin lever and punish the ones who don't.

The Four Operational Questions

1. Can you actually see what's happening on your floor — in real time?

Every mature US cannabis market eventually teaches its operators the same lesson, and it always comes through price compression. Colorado lived it. Michigan lived it. California is still living it. New York hasn't fully felt it yet — and that's the window.

Wholesale prices in mature markets compress every year supply expands faster than demand. NY is on the same trajectory; the only variable is timing. The operators in CO, MI, and CA who held their margin and picked up shelf space when compression hit all had one thing in common: real-time visibility into yield, COGS per SKU, labor productivity, and inventory accuracy. The ones running on month-end reconciliations between fragmented systems and tribal knowledge didn't.

The window for NY operators is now. Building operational visibility while you still have pricing power is dramatically easier than building it under margin pressure — when every dollar of CapEx and consulting spend is being scrutinized, and your QA team is already stretched.

What it costs to get wrong. Decisions made on lagging data. Yield gaps nobody catches until the variance shows up in a reconciliation report. Cost-per-gram that's a guess, not a number — which means your pricing strategy is a guess too. Margin compression you can't explain to your board because the underlying data lives in three disconnected systems.

What good looks like. A single operational system where every plant, package, transfer, and waste event is logged at the point of activity. Variances flagged the moment they occur, not at month-end. Yield, labor, and COGS visible to leadership in real time. Reporting cycles that get faster, not slower, because the data is right the first time.

2. Are your existing SOPs and records actually GMP-grade — or just good enough to get the license?

The SOPs you wrote to clear licensure are not the same SOPs that pass a third-party GMP audit. Licensure was a paper-and-facility check. The 12-month GMP audit is a live evaluation of how your operation runs day to day — an accredited third party walking your floor, opening your batch records, and asking your team how they handle deviations.

Most processors don't fail the audit. They pass — eventually. The strategic question isn't whether you'll get certified, it's what that certification is going to cost. And the cost is set almost entirely by how prepared you were before the audit clock started.

What it costs to get wrong. The bill scales directly with how much foundational work you skipped upfront. Operators who treated licensure SOPs as "good enough" end up paying consultants to rebuild documentation, redesign batch record workflows, retrain staff against GMP-grade procedures, and reconcile fragmented production data — all on a deadline. That's how a routine certification turns into six figures of consulting spend, a quarter of suppressed batch release velocity, and conditional certifications that delay every next move. The cost most teams don't see coming is the second-order one: when you're remediating GMP under audit pressure, every other initiative on the table slows down with it — capital raises, multi-state planning, product launches. The audit becomes the project.

What good looks like. Batch records captured electronically on the production floor. Every input, yield, loss, and QA event tied to a lot number that connects through to the Metrc package. SOPs that live in the system, not in a binder. Deviation logs your auditor can pull on the spot. The audit becomes a documentation exercise rather than a remediation project.

Safari Flower Co. had to answer this exact question when they pursued EU GMP — a regulatory bar materially stricter than NY's. Their CEO, Brigitte Simons, put it plainly: "We realized that the former solution just had too many errors that were untraceable that would never meet EU GMP standards." They moved to a system that could carry the audit weight, were live in six weeks, and now run under 1% inventory variance on lots exceeding 100,000 units. The lesson for NY operators: if your system can pass EU GMP, NY GMP is a non-event. If it can't pass NY GMP, your growth ceiling is already set.

3. If a recall hit tomorrow, could you scope it in hours instead of weeks?

Most operators believe they could execute a recall if they had to. Most can't — at least not in the timeframe regulators, distributors, and insurers expect. Under 9 NYCRR §133.4, OCM has authority to issue stop-work orders, quarantines, and full recalls, and your inventory tracking system has to be capable of supporting that on demand — not in two weeks, on demand.

What it costs to get wrong. Pulling more SKUs than necessary because you can't isolate the affected lots quickly. Distributor relationship damage when you're slow to respond. Insurance premium hikes after the event. Brand damage in a market where every dispensary buyer is paying attention. And — the line item that goes straight to your CFO's stress level — the recall scope itself, which can run into six or seven figures if you can't surgically scope it.

What good looks like. Full lot genealogy: every finished SKU traceable backward to its inputs, processing steps, equipment, operators, and distribution destinations. One-click recall scope reports. Batch isolation in minutes. The recall becomes a contained operational event, not a multi-week crisis. That's also the story your insurance underwriter, your board, and your acquirer want to hear when you're talking valuation.

4. Is your team running the business in your operational system — or running Metrc with the operational system on the side?

This is the question most operators don't realize they're answering, and it's the one that shows up most clearly on the P&L over time. It's also the case our co-founder and CEO Amar Singh has been making publicly — and the question that shaped what we built at Elevated Signals.

Amar's argument, in his own framing: most cannabis software built for US operators was designed around one question — how do we make Metrc easier? It's an understandable starting point. Metrc is painful. Operators hate it. So vendors built tools to make the reporting less awful, tick the compliance box, and keep regulators happy. He calls the result Metrc middleware — and it's everywhere.

The problem is that Metrc isn't your business. Your business is product innovation, yield, batch integrity, quality, margin, and customer loyalty. When software is built around a reporting obligation instead of your operation, the real problems don't go away — they hide behind a compliance checkbox while your team burns hours on manual workarounds that should never exist. Batch genealogy gaps still exist. COA validation failures still happen. GMP workflow breakdowns still get solved with spreadsheets and late nights.

We built Elevated Signals from the other direction entirely: start with what a world-class cannabis operation actually needs — real GMP workflows, batch traceability, quality controls, production execution. Build those properly, and Metrc compliance stops being a burden you manage. It becomes a byproduct of doing your job well.

Amar's question to ask of any software you're evaluating: was it built to make regulators happy, or was it built to make your operation genuinely world-class? The answer tells you what you'll actually get.

What it costs to get wrong. Your QA team spending more hours on cross-system reconciliation than on releasing product. Three tools doing the work of one. Batch release velocity capped not by demand but by software friction. And the longer-term cost: every workaround your team builds now becomes institutional debt that has to be unwound the moment you change software, scale, or move into a new state.

What good looks like. Real GMP workflows, batch traceability, and quality controls as the core of the system. SOPs, deviation logs, and quality gates embedded in daily operations, not bolted on for audits. COA hold/release controls that protect you automatically. Real-time visibility into yield, labor productivity, and COGS per SKU. Metrc becomes a reporting layer that runs in the background, not the system your team works in.

This is the question that compounds. The operators who answer it well protect margin against price compression, retain shelf space when the market consolidates, and walk into capital conversations with the kind of EBITDA story that protects valuation.

Diagnostic: Where Does Your Operation Sit?

Five questions for the leadership team. Honest yes/no answers only.

1. If OCM walked in tomorrow and asked for full batch genealogy on a finished SKU, could your team produce it in under 30 minutes — without anyone going to spreadsheets?
2. Can your team reconcile Metrc against physical inventory in real time, with zero ghost packages and zero open variance tickets?
3. If a stability or potency failure surfaced today, could you scope the recall to the exact affected lots in under an hour, with full distribution records?
4. Can your CFO see real cost per gram (or per SKU) in real time — not at month-end, not from a separate spreadsheet?
5. Does your team work in your operational system, with Metrc updating in the background — or do they work in spreadsheets and Metrc, with the operational system somewhere in the middle?

If you answered "yes" to four or five, you're in the camp building durable infrastructure. If you answered "no" to two or more, you have an 18-month problem that's already accruing interest.

Frequently Asked Questions

Is Metrc mandatory for all New York cannabis license holders now?

Yes. Following the state's transition from BioTrack to Metrc, all NY cannabis license types — cultivators, processors, microbusinesses, distributors, and retailers — are required to register with Metrc and report all plant, package, transfer, and inventory activity in real time.

Is GMP required for all New York cannabis operators?

GMP is required for processors. Within one year of commencing licensed operations, processors must submit proof of a qualified third-party GMP audit covering their extraction and/or manufacturing processes. Limited conditional exemptions exist for Type 3 processors whose activities are restricted to packaging, labeling, and branding of pre-ground or whole flower without on-site grinding (OCM Adult-Use GMP Guidance). Cultivators are not subject to the GMP audit requirement, though many of the same operational systems that pass GMP also protect cultivators in recalls and multi-state expansion.

What does OCM look at during a compliance inspection?

OCM inspections of cultivators and processors typically focus on Metrc accuracy reconciled against physical inventory, batch record completeness and traceability (9 NYCRR §123.6), SOP documentation and training records, packaging and labeling compliance (9 NYCRR §128), security and access controls (9 NYCRR §125.3), waste disposal records, and COA availability.

How long should a NY operator expect a GMP audit preparation to take if they're starting from scratch?

If the underlying systems aren't in place, expect three to six months of intensive remediation work, often with external consultants — typically running into six figures in consulting fees, plus the opportunity cost of suppressed production. If the systems are already running, the audit becomes a documentation exercise rather than a remediation project.

What's the most common reason NY operators struggle with their first audit?

Documentation fragmentation. Production data lives across paper batch records, spreadsheets, inventory tools, and lab reports — and the records don't agree with each other. Auditors don't need creative answers; they need fast, consistent ones. The operators who pass audits run on a single source of truth.

What is the recall authority in New York and how fast does an operator need to respond?

Under 9 NYCRR §133.4, OCM may issue stop-work orders, quarantines, orders of disposal or destruction, and full recalls. Licensees must maintain inventory tracking capable of supporting a full recall on demand, with the ability to identify and isolate affected lots and produce distribution records.

How should leadership think about software selection in this market?

Two questions. First: was this software built to make Metrc reporting easier, or was it built to run a regulated manufacturing operation? Second: does your team work in this system, or do they work around it? The answers tell you whether you're buying a compliance tool or operational infrastructure. Only one of those compounds in value.

Elevated Signals builds production and compliance software for cannabis cultivators and manufacturers — the kind that holds up to EU GMP, the strictest bar in the industry. The clearest picture of what that looks like in practice is in the Safari Flower case study: how they cleared EU GMP, hit under 1% inventory variance on lots over 100,000 units, and went live on a new operational stack in six weeks. If you're a New York cultivator or processor weighing the four questions, that's where to start.