CRO vs CDMO vs CMO: What Each One Actually Does, and When to Use Them

What's the actual difference between a CRO, a CDMO, and a CMO?

Strip away the jargon and there's one clean dividing line: research versus making the molecule. A CRO generates evidence. A CMO and a CDMO make the drug. Everything else is detail.

A CRO (Contract Research Organization) runs the studies that prove your candidate is safe and effective. Tox, pharmacology, the clinical trials, the data package that goes to a regulator. It does not produce commercial drug product. A CMO (Contract Manufacturing Organization) does the opposite: it manufactures to a process you already defined, and develops nothing. A CDMO (Contract Development and Manufacturing Organization) is the integrator. It develops the process and then manufactures it, which is why most early-stage biotechs gravitate to one.

Where people get tripped up is that the acronyms are used loosely. Plenty of companies that call themselves a CDMO are really a CMO with a thin development team bolted on, and some large CROs have quietly added CMC and clinical-supply work. The label tells you less than the actual scope of work in the statement of work. Read the SOW, not the logo.

• CRO: research and clinical studies. Never manufactures.
• CMO: GMP manufacturing to a defined process. No development.
• CDMO: process development plus manufacturing, one partner across the lifecycle.
• The acronym is marketing. The SOW is the truth.

What is a CRO (Contract Research Organization)?

A CRO is the company you hire to run studies you can't or won't run in-house. It generates and manages the safety and efficacy evidence a regulator needs to let your drug move forward.

On the preclinical side that means in vitro assays, pharmacology, and the IND-enabling toxicology package: 28-day and 90-day GLP repeat-dose tox, genotoxicity batteries (Ames, in vitro micronucleus), safety pharmacology like hERG for cardiac liability, and PK/ADME work. On the clinical side it's protocol design, site selection, patient recruitment, monitoring, biostatistics, data management, medical writing, and pharmacovigilance. Some CROs do the whole span; many specialize in one slice, say a GLP tox lab or a clinical CRO that only runs oncology trials.

What a CRO does not do is make commercial drug product. That's the hard boundary. If your program needs GMP material for a Phase 1, a CRO won't produce it (though it will happily design the trial that material feeds into).

• Preclinical: GLP tox, Ames, micronucleus, hERG, PK/ADME, pharmacology
• Clinical: protocol design, monitoring, biostatistics, data management, pharmacovigilance
• Generates the safety/efficacy package for IND, NDA, and BLA submissions
• Does not manufacture drug substance or drug product

What is a CMO (Contract Manufacturing Organization)?

A CMO makes the drug. You hand it a process, it produces material to spec under GMP, and that's the deal. Drug substance, drug product, fill-finish, packaging, clinical or commercial supply.

The defining trait is that a pure CMO executes rather than develops. You arrive with a validated or near-validated process and a method package, and the CMO scales it up and runs the batches. Because process development sits outside its scope, sponsors who use a pure-play CMO usually pair it with a separate development group, and they own the tech transfer between the two. That handoff (moving a process from one site's heads and equipment to another) is where a lot of timelines quietly slip.

Worth saying plainly: the standalone CMO label is fading. The economics pushed most contract manufacturers to add development services and rebrand as CDMOs, because development is where the early, stickier revenue lives. You'll still find true CMOs in commodity small-molecule and generics manufacturing, but in novel-modality work the term has largely been absorbed into CDMO.

• GMP manufacturing of drug substance and drug product to a fixed process
• Fill-finish, packaging, clinical and commercial supply
• Engaged after the process is locked; develops nothing itself
• Often paired with a separate development partner, and you own the tech transfer

What is a CDMO (Contract Development and Manufacturing Organization)?

A CDMO does development and manufacturing under one roof. The model grew out of the CMO by adding the development front end, so a single partner can take a candidate from process design and scale-up all the way to GMP commercial supply.

The pitch is fewer handoffs. Because the same organization develops your process and then manufactures it, you avoid a tech transfer between a development house and a separate plant, which is the seam where deviations, comparability headaches, and schedule slips tend to appear. A CDMO can engage early too, often at preclinical or early clinical stage, which is exactly when a small biotech has no manufacturing of its own.

Typical CDMO scope: API and formulation development, process development and scale-up, analytical method development and validation, stability programs, CMC regulatory support for the IND/IMPD and later the NDA/BLA, plus clinical and commercial manufacturing. Some run cell and gene therapy or sterile fill-finish suites; others are classic small-molecule oral solid dose shops. You'll also see the newer term CRDMO (Contract Research, Development and Manufacturing Organization), which extends the one-stop idea further back into discovery research.

• Integrated development plus manufacturing across the lifecycle
• Engages early (preclinical/early clinical), which suits venture-backed biotechs
• Scope: process and formulation development, scale-up, analytical, CMC, GMP supply
• Fewer tech transfers than a CMO-plus-separate-developer setup

Where do CRO, CDMO, and CMO overlap (and why is it confusing)?

The overlap shows up at two seams, and both cause real confusion when you're scoping a program.

First, CMO and CDMO. A CDMO is essentially a CMO that also develops, so a pure CMO is a subset of CDMO capability. When a contract manufacturer adds a formulation team and starts calling itself a CDMO, the line gets blurry fast. The only way to tell them apart is to ask what process development they'll actually own versus what they expect you to hand them.

Second, CRO and CDMO at the clinical stage. A CDMO making your GMP clinical batches sits right next to CMC regulatory work that a clinical CRO might otherwise help coordinate. And the CRDMO model deliberately collapses research, development, and manufacturing into one vendor. In practice most programs run all three partner types at once, the acronyms get applied loosely, and the smart move is to map the specific deliverables (a 28-day GLP tox report, a validated HPLC method, a 50kg GMP batch) rather than argue about which three-letter bucket a vendor belongs in.

When do you engage a CRO vs a CDMO vs a CMO across the lifecycle?

The three map to different phases, though the edges are fluid and good programs overlap them on purpose.

Discovery and preclinical: a CRO runs your assays, pharmacology, and IND-enabling GLP toxicology, while a CDMO handles early process and formulation development and supplies preclinical material. IND-enabling into early clinical: the CRO runs the Phase 1, and a CDMO (or CMO) produces the GMP clinical supply that goes into those patients. Clinical phases: the CRO manages trial operations, monitoring, and data across Phase 2 and pivotal Phase 3, while the CDMO scales the process up to support larger cohorts. Commercial launch: manufacturing sits with a CDMO or CMO, and the CRO often stays on for Phase IV and pharmacovigilance.

You can run separate specialists at every stage to get the best capability per phase, or consolidate with an integrated CDMO (or CRDMO) to cut handoffs. There's no universally right answer. Specialists usually win on depth; integrators usually win on speed and on programs where tech transfer risk is the thing you most want to kill.

• Discovery/preclinical: CRO for research and GLP tox; CDMO for early process and supply
• IND-enabling/early clinical: CRO runs the trial; CDMO/CMO makes GMP clinical material
• Clinical: CRO manages operations and data; CDMO/CMO scales the process
• Commercial and post-market: CDMO/CMO for supply; CRO for Phase IV and pharmacovigilance

How do you choose and contract the right partner?

Start from what you actually need, not the acronym. Research and trials point to a CRO. A defined process that just needs to be made points to a CMO. Development plus manufacturing points to a CDMO. Then evaluate on the things that decide whether a program ships: concrete scope, modality fit (small molecule vs biologic vs cell and gene therapy is a different world of capability), regulatory track record with FDA, EMA, and ICH expectations, GLP and GMP status, and available capacity in your window.

The annoying part isn't picking a category. It's sourcing and qualifying the actual vendors. Enterprise marketplaces like scientist.com and Science Exchange run large supplier networks, and access usually sits behind a sales or demo gate. BioBridgeX (BioBridgeX Ltd, London, UK) takes a more open, neutral route. It's an all-indications CRO and CDMO marketplace covering Discovery, Preclinical, IND-enabling, Clinical, and CMC/Manufacturing, with vendor profiles you can browse directly at biobridgex.com/vendors. It acts as a vendor of record: it coordinates vendor qualification, a single contract, project management, and milestone-based payments between buyer and vendor, and it runs no labs of its own. It's free for buyers, and vendors pay a flat 2% platform fee on a pay-when-paid basis. Buyers get matched at biobridgex.com/register; vendors onboard at biobridgex.com/cro/onboarding.