Technology Transfer Series

The Scale-Up Surprise: When Optimism Meets Reality

A person handing a tube to another person

Often, the reason for a tech transfer is to scale up output in anticipation of a significant program milestone. The optimism that sponsors begin with can shift to surprise once the realities of the required process steps come to light. Moving from bench scale to commercial scale is rarely as simple as ‘bigger tanks and more product.’ Real success depends on aligning teams, investing early in development, and recognizing the true complexity of scaling up during tech transfer. Let’s dig into a few ways to avoid a scale-up surprise.

Clinical & Commercial Alignment

One of the most impactful predictors of a smooth transfer is early collaboration between a sponsor’s clinical and commercial teams. Typically, clinical teams prioritize speed and trial continuity, while commercial teams focus on long-term efficiency and cost of goods. Unfortunately, these goals can be at odds when it comes to process development and scale up.

Scientist with pipette in pilot lab

"It is not uncommon for us to receive a process in tech transfer that, while functional at a clinical scale, will not perform well for commercial. And, since the Phase 3 process often becomes the commercial process, it needs to be optimized at or before Phase 3. Once a process is locked in and regulatory filings are complete, changes become costly and difficult."

For example, we worked with a sponsor whose clinical team had included a specific brand and model of equipment in their regulatory submission. When they reached commercial stage, that specific model was not appropriate for the scaled-up batch size. What they should have done is include details on functionality instead of calling out specific makes and models. That allows the later-stage team to, if needed, move to different equipment that is appropriate for the batch size but maintains the same functionality.

Timelines Rarely Behave as Expected

Sponsors often underestimate the scope of work required to scale. Early-phase programs move quickly, but later phases introduce layers of qualification, validation, equipment integration, and troubleshooting. Often, these steps are linear and a delay in one area affects others. Even with best-case planning, aggressive timelines leave little room for learning, iteration, or remediation. Programs move faster and more reliably when they include a bit of breathing room. 

Budget Blind Spots and Material Constraints

Early programs frequently arrive with limited budgets and minimal material, along with the hope that fewer pilot runs will be sufficient. But robust development requires multiple batches to explore the design space, understand variability, and stress-test processes. Without sufficient resources and enough development work, including challenging the process repeatedly, you may end up with an inefficient process that gets locked-down ahead of moving to commercial stage.

The Equipment Factor: Why Bigger Means Different

Scaling equipment isn’t just a matter of volume. At small scale, processes might rely on flexible human interventions and straightforward tools like autoclaves, but at commercial scale, each step may introduce relatively complex automation such as sterilization-in-place (SIP) technologies.

Larger systems introduce new variables: automation programming, cleaning and sterilization requirements, integration with existing controls, and more complex validation. These aren’t technical footnotes they’re major contributors to timeline risk.

Managing Risk Through Preparation and Flexibility

Effective risk mitigation combines strong up-front assessments with hands-on testing. Development batches and trial runs reveal issues that aren’t visible on paper. Trends in data, deviations, CAPAs, and investigation reports often highlight parameters more critical than initially assumed.

For programs with aggressive timelines, we sometimes run GMP batches before all prerequisites are complete. It’s not ideal, but with the right contingency planning, this approach can prevent larger schedule disruptions. Flexibility grounded in data, not hope is key.

Final Thoughts

Scaling up is more than repeating what worked before at a larger size it requires new thinking, realistic timelines, and strong collaboration. Optimism is valuable, but preparation is what allows teams to adapt when surprises arise. Those who align early, invest in development, and stay flexible will be the teams that scale successfully.