When CDMO Capacity Plans Fail: Why Biotech Launches Get Delayed

When Capacity Commitments Disappear

• A biotech company with a promising oncology drug received FDA approval in Q2. They'd been working with three CDMOs one for bulk manufacturing, one for fill-finish, one for secondary packaging.

• During vendor selection nine months earlier, each CDMO had confirmed capacity. Deal signed. Biotech built launch plans around 5M units annually. Six weeks before their planned production start, they discovered: CDMO A was only 15% available (not the 40% promised), CDMO B had other customers with priority contracts, CDMO C had an undisclosed quality hold on their line. Launch was delayed four months. A competitor launched first. They lost an estimated $8M in first-year revenue.

1. The biotech team felt blindsided. The contracts clearly stated capacity commitments. But the capacity commitment was a moment in time nine months ago. What actually existed on launch day was something entirely different.
2. This is not a story about broken contracts. It's a story about how capacity conversations happen once, while operations run continuously. It's about visibility that stops at the contracting event and never asks: what exists right now?

The False Confidence of Capacity Conversations

Capacity conversations follow a predictable pattern in biotech.

Biotech company needs a CDMO. They send an RFQ (Request for Quote): "We need capacity for 5M units annually with 12-week lead times. Do you have it?"

CDMO responds: "Yes, we have capacity."

Biotech verifies with two other CDMOs. Same answer: "Yes, capacity available."

Biotech feels confident. They signed contracts. Each CDMO committed to service levels. They built launch timelines based on these conversations.

What they don't realize: the capacity conversation happened one day. It captured a snapshot. CDMO A had 40% available last September when the RFQ came in. But between RFQ and contract signing (two months), two major customers escalated their volumes. Between contract and launch (nine more months), three smaller projects consumed additional slots. By launch day, available capacity had compressed to 15%.

The CDMO didn't violate the contract. The contract said "capacity available." Technically, they still had it. Allocated differently, but available in some form. The biotech company never asked: "What's your actual available capacity today?" They asked: "Do you have capacity?" and received a yes which was true nine months ago.

How Capacity Becomes Fiction Between Signature and Launch

Capacity operates in layers that don't naturally stay aligned.

Theoretical Capacity: What the equipment can produce under optimal conditions (maximum throughput).

Committed Capacity: What's already promised to existing customers (documented in contracts).

Available Capacity: What's left after commitments are honored (actual runway for new customers).

Companies operate confidently on layer one. They contract based on layer two. But they plan launches against layer three which nobody monitors regularly.

Here's where the gap appears:

A CDMO genuinely has 100% theoretical capacity. They've committed 85% to existing customers contractually. That leaves 15% available. But when they quote to a new customer, they often quote the first number (theoretical), not the third (available). The distinction matters enormously it determines whether launch succeeds or collapses.

Between contract signature and launch, committed capacity shifts:

• One customer escalates volumes (original contract said "up to 5M"; now they're taking 6M)
• Another customer activates priority language in their SLA (their orders queue before new customers)
• A product line gets regulatory approval ahead of schedule (demand jumps, they need more manufacturing slots)
• Quality issues on one line compress available equipment

None of this violates contracts. It's operational reality. But it's not communicated to the new customer who signed up for "40% available capacity."

The Multi-CDMO Coordination Gap

The problem compounds when a biotech uses multiple CDMOs which most do.

Company needs:

• Bulk manufacturing (CDMO A)

• Fill-finish operations (CDMO B)

• Secondary packaging (CDMO C)

Each CDMO has capacity. But they don't coordinate sequencing. There's no joint planning to ensure one CDMO's production timing aligns with the next manufacturer's intake capacity.

Here's what happens:

CDMO A completes bulk manufacturing in week 12. Ships to CDMO B. But CDMO B's fill-finish line doesn't have intake capacity until week 16. Bulk sits in inventory for four weeks. Then CDMO B's hold time is 18 weeks instead of 14. CDMO C can't start packaging until week 34 instead of week 30. The four-week gap propagates, extending total timeline by 4+ weeks.

Nobody planned this. Each CDMO operates independently No governance forum brings all three together to sequence the manufacturing pipeline.

The biotech company assumes: CDMO A (12 weeks) + CDMO B (14 weeks) + CDMO C (8 weeks) = 34 weeks total. Reality: gaps between handoffs add 4-6 weeks. Actual timeline: 40 weeks.

Launch planned for week 38 now targets week 42. That's a month slip. First production batch isn't ready. Shelves stay empty. Retailer de-lists. Competitor's product sits on the shelf instead.

Why Real Capacity Never Surfaces

Three structural reasons organizations don't see actual available capacity until it's too late:

1. Capacity conversations are contracting conversations, not operational ones

Finance and sourcing teams negotiate contracts. They have scope, pricing, SLAs. They don't have real-time capacity calendars. Once signed, the contract lives with the CDMO operations team who actually knows capacity. But they don't have ongoing dialogue with the biotech customer's operations team. The two organizations talk through contracts, not through operations.

2. Capacity data is treated as static, not dynamic

Biotech builds launch timelines assuming capacity they confirmed nine months ago still exists. They don't ask: "What's your available capacity today?" They assume: "You confirmed it then, so it must still be there." Capacity actually changes weekly as customer volumes fluctuate. But nobody monitors it in real-time. There's no weekly or monthly capacity review. The conversation happens once, at contract.

3. Multi-CDMO networks have zero integration points

Each CDMO relationship is bilateral. Biotech to CDMO A. Biotech to CDMO B. Biotech to CDMO C. There's no trilateral planning to sequence production across the network. Each CDMO optimizes their own throughput, not the collective timeline. The biotech company never asks: "Given CDMO A's output timeline, when can CDMO B actually intake material? And given that, when can CDMO C start?" Integration points don't exist.

When It Breaks: The Launch Date Reckoning

• The gap becomes visible six to eight weeks before launch too late to adjust.

• Biotech reaches out to CDMO A: "We're ready to schedule the production run."

• CDMO A: "Our intake schedule shows we can fit you in week 28."

• Biotech: "We need it in week 18. That's 10 weeks later than planned."

• CDMO A: "That's the earliest available. Your contract has SLA for 12-week lead times from order, but we can't front-queue you ahead of committed customers."

• Biotech calls CDMO B: "We need fill-finish to start in week 30."

• CDMO B: "If intake starts week 28, we won't be ready until week 45. We have two other projects in our schedule."

• The timeline is now completely broken. Biotech has no inventory to ship. Retailer deadlines expire. Shelf space goes to competitors. Revenue timeline slips by months.

• The conversation that should have happened in month 1 (capacity planning across the network) now happens in month 9 (crisis management). Too late to fix.

The Real Signal: What Visibility Actually Requires

The gap isn't hidden. It simply isn't asked.

Capacity visibility requires three things biotech companies typically don't implement:

Real-Time Capacity Data:

Each CDMO submits available capacity slots monthly, not once. What's actually available now (not promised theoretically). This requires CDMO transparency, which requires trusting relationships, which requires asking.

Multi-CDMO Sequencing:

Joint planning meetings across all three CDMOs. Not sourcing conversations. Operations conversations. Where CDMO A confirms output timing. CDMO B confirms intake and output timing. CDMO C confirms intake availability. Mismatches are identified and resolved in a planning forum, not discovered in a crisis.

Binding Commitments:

Capacity reserved, not assumed. Once the biotech company commits to a production timeline, the CDMO holds those slots. It's reflected in the capacity calendar. Other customers can't bump them. This is a governance choice, not a contracting choice.

Most biotech companies skip these steps. They sign contracts and assume capacity is secured. It's not. The capacity is committed to whoever moves fastest operationally.

What Actually Works

Companies that launch successfully don't have better contracts. They have better operational governance.

They implement:

1. Quarterly capacity planning (binding, not theoretical)

2. Monthly capacity reviews (real-time adjustments, not annual assumptions)

3. Multi-CDMO coordination forum (sequencing across the network)

4. Escalation path (when assumptions change, decision authority is clear)

One biotech client applied this model. Their next two launches hit target dates. CDMO delays that used to derail timelines now triggered contingency plans. Available capacity was known 12 months in advance, not discovered 6 weeks before launch.

The insight: Capacity visibility is a governance choice, not a system choice. It requires asking different questions in different forums with different frequency. The companies that win launches are the ones that treat capacity as dynamic and coordinate across the network, not as static and siloed by vendor relationship.

When capacity is invisible, launch surprises are guaranteed. When capacity is managed operationally, launches become predictable.