cmo vs cdmo, read as cdmo vs cmo or as cmo cdmo from either direction, decided by what you already have: what a contract manufacturer does when the process is finished and transferred, what the development half adds when it is not, where cdmo and cmo language is used loosely, and why the wrong choice shows up as an engineering batch nobody budgeted

Deciding which you need

1. Be honest about how defined your process is. A finished process has fixed unit operations, defined parameters and ranges, qualified analytical methods and a specification. If any of those is still moving, you have a development project, and giving it to a manufacturer as if it were finished makes the development happen anyway, slower and at a higher rate.
2. Check whether your analytics transfer as well as your process. Methods have to be qualified at the receiving site, and programmes routinely plan the process transfer and discover the analytical transfer afterwards. That is where the months go, and it is a development activity whoever performs it.
3. Match the partner to your scale and your format. A site running your format weekly will spot a problem sooner than one running it for the first time at a better rate. Ask what they run routinely rather than what they can run, and ask for a reference programme of your size.
4. Read the slot as seriously as the price. Capacity in eighteen months is not capacity, and a slot without penalty terms is an intention. Confirm the slot, the campaign length and what happens if your material is late, because those terms describe how real it is.
5. Settle ownership of process knowledge in the contract. Who owns process improvements, whether you can take the process elsewhere and what documentation transfers at the end are terms, not defaults. A development partner that owns your process is a partner you cannot leave.

What to put in the request before either quotes

The process description, the analytical package and its status, the scale, the format, the quantity, the timeline and the regulatory destination. Quotations against an incomplete request are quotations against different assumptions and cannot be compared.

Ask each to state what they assume about your process readiness. The gap between those assumptions and your own is the project risk, made visible before anything is signed.

Managing either relationship

A quality agreement naming who does what, one named decision maker on each side, and an agreed escalation path. Campaigns stall on questions nobody was empowered to answer far more often than on technical problems.

Ask for batch documentation as it is produced rather than at the end. Reviewing a record while the campaign is running is the only way a problem gets fixed rather than investigated.

Common questions

What is the difference between a CMO and a CDMO?

A contract manufacturer makes a process you have defined and transferred. A development and manufacturing organisation develops or finishes the process first and then makes it. The extra capability is development, and it is charged for.

How do I know my process is ready for a CMO?

Unit operations fixed, parameters and ranges defined, analytical methods qualified and a specification agreed. If any of those is open, the development will happen wherever you go, and a manufacturer is not set up to do it well.

Is a CDMO more expensive?

For the same batch, generally yes, because development capability is being paid for. For a programme whose process is not finished, it is usually cheaper overall than paying a manufacturer to discover the process during a campaign.

What is the most common mistake?

Underestimating how much analytical transfer and how many engineering runs are needed, and planning straight into a clinical batch. That plan produces an investigation rather than material, at either kind of partner.

Browse by service class

• Compare Gene synthesis on advertised prices