How Pharma and Cannabis Can Co‑Develop Cannabinoid Therapeutics Without Blowing Up Compliance

Cannabinoid therapeutics science is finally growing up, and the rules around it are slowly catching up. As that happens, more pharmaceutical companies and cannabis operators are looking for ways to work together. Pharma knows how to run clinical programs and manage regulators; cannabis companies understand the plant, the patients using it, and where the most interesting cannabinoid assets live.

But these organizations think about risk, speed, and compliance very differently, and if that isn’t handled upfront, a collaboration that looks promising on paper can easily stall or create new problems. This piece offers a straightforward, neutral playbook for leaders on both sides to design co‑development deals that move cannabinoid therapeutics forward without sacrificing compliance.

Why Co‑Development Is on Pharma’s Radar Now

Over the last several years, cannabinoid‑based products have moved from fringe to serious consideration in areas like pain, neurology, oncology support, sleep, and psychiatry. Regulators are under pressure to clarify pathways for cannabis‑derived products, and investors increasingly expect rigorous evidence and pharmaceutical‑grade quality if they are going to back “drug‑like” cannabinoid programs. At the same time, traditional pharma organizations are cautious about reputational risk and regulatory ambiguity, while cannabis companies often operate with consumer‑marketing mindsets and state‑level compliance frameworks.

The result is a growing interest in co‑development—pairing cannabis assets and insights with pharma development capabilities—but also a real risk that fragmented regulation and unclear ownership of compliance work can derail otherwise promising initiatives. Co‑development can work, but only if both sides explicitly design for compliance from the outset.

Three Regulatory Worlds, One Cannabinoid Therapeutics Program

Any serious cannabinoid therapeutic effort typically sits at the intersection of three regimes:

• Federal drug regulation, where agencies like FDA oversee investigational and approved human drug products, including requirements around INDs, NDAs, CMC, labeling, and promotion.
• Controlled substance regulation, where scheduling, quotas, storage, recordkeeping, and diversion control shape how cannabinoids can be manufactured, transported, and studied.
• State‑level cannabis regimes, where licensing, product rules, and marketing restrictions govern how plant‑derived and cannabis‑adjacent products are produced and sold.

For a single co‑development program, all three may apply at once. A formulation may be developed as an investigational drug under federal rules while related products are sold under state cannabis laws, and the same organization may have obligations under controlled‑substance rules. The first step for any partnership should be a joint mapping exercise where both sides list which agencies, licenses, and rule sets they believe apply, compare perspectives, and reconcile differences before term sheets are drafted.

Deal Architecture: Picking the Right Co‑Development Model

There is no single “right” structure for pharma–cannabis collaboration. Instead, partners should choose a model that reflects who needs control over regulatory strategy, who bears which risks, and how value will ultimately be realized. Common patterns include:

• Sponsored research and licensing, where the pharmaceutical company sponsors clinical work and owns regulatory filings, while the cannabis partner contributes a specific asset, formulation, or body of know‑how, and may receive milestones and royalties.
• Joint ventures or new entities, where both parties contribute IP, capital, and personnel into a shared vehicle that holds development rights and may eventually market the product.
• CDMO‑style supply relationships, where the cannabis company effectively behaves as a GMP supplier of API or finished product to the pharma sponsor, with the sponsor holding responsibility for the clinical and regulatory program.

In each model, partners should explicitly define who will be the regulatory sponsor, who will own and maintain key filings, who will lead agency interactions, and how safety reporting, pharmacovigilance, and post‑approval obligations will be managed. A useful high‑level lens: when pharma wants tight control over regulatory risk, sponsor/CDMO models may be preferable; when both parties are building a platform with shared upside, a JV or structured alliance may make more sense, provided governance is robust.

From State Compliance to GMP Reality

For a cannabis operator, the most significant shift in co‑developing therapeutics is often the move from state‑oriented compliance to systems resembling pharmaceutical GMP and GxP standards. Pharmaceutical partners will expect:

• Documented, consistently followed procedures for all critical operations.
• Complete batch records, including traceability for all materials and clear deviation handling.
• Validated equipment and processes, with change control and calibration.
• A functioning quality‑management system with defined responsibilities, audits, and continuous improvement.

This is where technology and infrastructure can do a lot of heavy lifting:

• Cloud‑based QMS platforms that standardize SOPs, deviation/CAPA workflows, and audit trails across cultivation, extraction, and manufacturing.
• LIMS and ELN tools to tie test results, batch records, and stability data together in a way that is usable for CMC sections of filings.
• Serialized packaging, RFID/barcoding, and integrated ERP/MES to give partners real‑time visibility into material flow and chain‑of‑custody.

Many cannabis businesses grew up in environments where speed to market, SKU proliferation, and state testing compliance were the primary drivers, and documentation practices may be uneven. Before entering serious co‑development discussions, cannabis operators should assess whether they can pass a basic quality and documentation audit, identify gaps, and prioritize upgrades. A simple internal checklist—covering batch record completeness, data integrity, change control, and the authority of quality leadership to halt non‑compliant activity—can prevent unpleasant surprises once a pharma partner begins diligence. Some operators are already moving toward bank‑grade, fintech‑style compliance infrastructure to close this gap.

Building Trial‑Ready Products and Data Flows

If a co‑development program will involve human studies, alignment on development strategy is essential early on. Partners should agree on:

• The target indication and patient population, including how that aligns with available preclinical and real‑world evidence.
• Route of administration and dosage form, especially if a product is being repositioned from a consumer or medical cannabis context into a drug‑like context.
• Endpoints and study designs that are appropriate for regulatory expectations, even at exploratory stages.

Digital infrastructure matters here as well:

• EDC and ePRO systems that can support GCP‑compliant data capture for cannabinoid studies.
• Safety databases and pharmacovigilance tools that can scale if the program moves from early‑stage studies into larger trials.

An early discussion should clarify whether the planned work requires an IND, who will be listed as sponsor, and how responsibilities for protocol authorship, safety monitoring, data capture, and regulatory correspondence will be divided. Cannabis partners supplying product must be prepared to document manufacturing, handling, and chain‑of‑custody in a way that can withstand inspection. Clarity here avoids later disagreements about who is accountable for which parts of the development pathway.

Messaging Firewalls: Keeping Drug Development and Retail Separate

One of the most sensitive areas in pharma–cannabis collaboration is communications. Cannabis companies are often accustomed to consumer‑facing marketing that pushes up against boundaries of structure‑function or efficacy claims, while pharmaceutical organizations operate within tightly controlled promotional frameworks. When a product or related asset is part of an investigational program, this tension can create real risk.

Partners should draw clear lines between:

• Educational communications about science, mechanisms, disease burden, and trial participation logistics, which are generally acceptable when carefully framed.
• Impermissible promotional behavior, including implying safety or efficacy beyond what is supported in labeling or protocols, or suggesting that retail products are equivalent to investigational or future approved products.

A practical safeguard is a joint review process for press releases, investor presentations, major conference talks, and any public messaging that references the co‑development program. Requiring sign‑off from both legal/regulatory teams before such communication goes out can prevent inconsistent or misleading narratives that might concern regulators or investors.

Contracting the Tech, the Data, and the Risk

Contracts are where expectations about compliance become enforceable. In addition to commercial terms, co‑development agreements should address:

• A quality agreement that sets out manufacturing standards, documentation expectations, audit rights, change‑control processes, and responsibilities around batch release and recalls.
• Data governance, including who owns clinical data, manufacturing data, and any real‑world evidence generated, as well as who may use which data for regulatory filings, publications, or other purposes.
• Intellectual property, clarifying background IP, ownership of new inventions and improvements, and how joint IP will be managed.
• Regulatory contingencies, such as what happens if laws change, a key license is lost, or an agency issues a critical finding that affects the program.

On the tech side, it is worth calling out which systems are “system‑of‑record” for quality, manufacturing, and clinical data, and how access will be shared or segregated between partners. Including a description of governance bodies—such as joint steering committees and risk/compliance sub‑committees—in the agreement helps ensure that decision‑making structures are not left to informal understanding alone.

Who Owns the FDA Conversation?

Even the best‑drafted contracts cannot anticipate every scenario. Effective governance is what keeps a co‑development program on track as science, regulation, and market conditions evolve. Many successful alliances rely on:

• A joint steering committee that oversees overall strategy, timelines, and major resource decisions.
• A dedicated risk or compliance group that monitors regulatory developments, safety signals, and emerging reputational issues, and has the authority to recommend or mandate changes.

Clear escalation paths should be defined for issues such as unexpected safety data, proposed changes to formulations or supply arrangements, or new marketing initiatives that could impact regulatory perceptions. It should be explicit who has veto rights in specific categories of decisions and how disagreements will be resolved within defined timeframes.

In a typical composite scenario, a promising co‑development initiative may be delayed for months because the partners have not clearly defined which organization is responsible for leading interactions with FDA about the program. Establishing ownership of such critical functions through governance structures and documentation can prevent avoidable delays.

Patterns You Want—and Patterns You Don’t

While confidential specifics vary, recurring patterns emerge in pharma–cannabis collaborations. Successful efforts often share several traits: the cannabis partner invests early in upgrading quality and documentation practices; the pharma partner takes time to understand state‑level realities and patient access channels; both sides articulate a phased development plan with clear go/no‑go points; and governance bodies meet regularly with meaningful participation from legal, regulatory, and operations leaders.

Less successful patterns tend to involve misaligned expectations and gaps in ownership. Examples include situations where consumer‑oriented marketing about related products raises concerns for pharma compliance teams, where documentation gaps make it difficult to support clinical filings, or where disagreements about regulatory strategy surface only after significant time and capital have been invested. An analytical look at these patterns suggests that early, structured conversations about compliance can mitigate many of these risks.

First Steps: A Pilot, a Gap Assessment, and a Plan

For organizations considering co‑developing cannabinoid therapeutics, a practical path forward is to start with a focused pilot project under a robust governance and quality framework rather than a broad, loosely defined alliance. Before formal negotiations, both sides can benefit from a joint readiness assessment that examines regulatory mapping, quality systems, data practices, and communication norms.

By treating compliance as a shared design constraint—something to build into the product, process, and partnership from the beginning—pharma and cannabis companies can increase the likelihood that co‑development efforts yield viable, well‑supported cannabinoid therapeutics rather than stalled projects or regulatory setbacks.