Credence

INTERVIEW - Centrix Pharma: When Should Manufacturability Start Shaping Drug Development?


The pressure to reach the next drug development milestone can often take precedence over longer-term manufacturing considerations. Decisions made during early formulation and process development can have significant implications for scalability and commercial viability. Focusing solely on speed can lead to costly redevelopment and delays further down the line. Instead, pharmaceutical developers should aim to maintain momentum while preserving the flexibility needed for future success. Chris Davison, CEO of Centrix Pharma, recently spoke with Drug Development & Delivery about why manufacturability should be considered from the outset, the risks of overlooking it and how a balanced, forward-thinking approach can support more efficient drug development.

Centrix Pharma Solutions logo

At what point in drug development should manufacturability begin to influence decision-making, and why is it important to consider these requirements before a program approaches commercial scale?

I would argue that manufacturability should influence development decisions from the very beginning, but that doesn’t mean every manufacturing challenge needs to be solved on day one. Early development has a clear job to do: generate the data needed to reach the next milestone and make informed decisions. The mistake is assuming that because commercial manufacture may be years away, manufacturing considerations can be ignored entirely.

The more practical question is whether an early development decision preserves future options or closes them off. If a decision could significantly limit scalability, process robustness, supply chain flexibility or future formulation choices, then it is worth considering its longer-term implications before proceeding. The goal is not to build a commercial process during preclinical or early clinical development. It is to avoid creating unnecessary constraints that become expensive or time-consuming to undo later.

Early development teams are understandably focused on reaching their next clinical milestone. How can they balance the need for rapid progress with decisions that support future manufacturing requirements?

Development is always a balance between speed and optionality. Every program is under pressure to reach the next milestone as efficiently as possible, whether that is first-in-human studies, proof-of-concept or registration. In many cases, the simplest route forward is the right one.

Where teams can get into difficulty is when short-term decisions are made without understanding the implications for later phases. A relatively small investment in understanding formulation behavior, process risks or material attributes early on can reduce the risk of significant redevelopment later.

I don’t believe in doing more work for the sake of it. I believe in doing the right work at the right time. The best development programs generate information that changes decisions and reduces uncertainty. That allows teams to move quickly while maintaining flexibility as the program evolves.

Which decisions made during early formulation and process development tend to have the greatest impact on manufacturability later, and which are particularly difficult or costly to reverse?

Formulation architecture is often one of the most difficult areas to revisit later because so many other aspects of development become linked to it. Choices around dosage form, excipient strategy, API particle size, release characteristics and dose loading can all have consequences that may not become apparent until much later. Equally important are decisions around analytical methods, raw material sourcing and process design, which can become deeply embedded as programs progress.

What makes these decisions challenging isn’t that they’re necessarily wrong at the time they are made. It’s that development rarely follows a perfectly predictable path. Clinical data emerge, doses change, specifications evolve and unexpected technical challenges arise. The strongest programs recognize this uncertainty and deliberately maintain flexibility where it matters most.

What are the most common consequences of overlooking manufacturability during early development?

The most common consequence is not failure. It’s inefficiency. One example involved a programme with multiple tablet strengths that were intentionally designed using a common tablet weight to simplify blinding within clinical studies. The approach worked well in early development and met the immediate needs of the program.

As clinical data emerged, however, the required dose increased beyond the levels originally anticipated. Maintaining the same tablet weight meant API loading became significantly higher, which led to challenges with compressibility and manufacturability.

What could have been done differently was to better understand the manufacturing design space of the highest-strength formulation earlier in development. That may have shown that the original formulation was already approaching the limits of robust manufacturability, with relatively little room to accommodate a subsequent increase in dose. Knowing that wouldn’t necessarily have changed the original decision, but it would have made the constraint visible and allowed the team to consider how best to preserve flexibility.

Ultimately, that is where manufacturability really matters. It isn’t enough to demonstrate that you can manufacture a product. You need a formulation and process that are sufficiently robust and reproducible to manufacture it consistently on a routine basis.

The later that lack of robustness is discovered, the more difficult and costly it becomes to address. Remediating an established, launched product can involve significant formulation or process redevelopment, validation, stability studies and regulatory changes. It is far better to understand and address those limitations during development, when there is still greater freedom to make changes.

For me, considering manufacturability early isn’t necessarily about changing the decisions you make. It’s about understanding the boundaries of those decisions and how much room you have to adapt as the program evolves.

Can you share specific examples of how seemingly minor decisions can lead to redevelopment, delays, additional costs or challenges during technology transfer and scale-up?

One example shows how even the right response to an emerging development issue can have wider manufacturing consequences. During development of an immediate-release oral product, a significant impurity issue was identified. The decision was made to introduce a functional film coat to limit the product’s exposure to the low-pH environment of the stomach. That was the right development decision because it successfully addressed the impurity issue, but it also had consequences elsewhere in the product and manufacturing process.

In particular, the functional coating significantly reduced bioavailability. To mitigate that effect, the team subsequently had to introduce API particle-size modification and increase the dose to achieve the required exposure. Those changes had important manufacturing implications. Particle-size modification introduced an additional API processing step, while applying the functional coat created a longer and more complex drug product manufacturing process. The coating itself also became critical to product performance, meaning both the coating materials and the process needed to be understood and controlled appropriately. Considerably more development work was therefore required to establish the robustness of these additional manufacturing steps.

For me, the key lesson from this example is not that an earlier decision was wrong. Drug development is inherently a process of learning. New information becomes available, unexpected challenges emerge and programmes adapt accordingly. The value of considering manufacturability early is not that it prevents every future change, but that it helps teams understand the potential implications of those changes and respond more effectively when they arise.

How can development teams identify which manufacturing considerations need to be addressed early and which can reasonably be deferred until later stages? What factors should guide these decisions?

The first question I ask is: where are we ultimately trying to get to? It’s very difficult to decide what matters today unless you have a clear understanding of the intended destination. That starts with the patient and the intended use of the product. Who is the intended patient population? Is the ambition a proof-of-concept study, a niche orphan product, a global commercial launch, a high-volume primary care medicine, or something else entirely? The answer influences which risks deserve attention and which can reasonably wait.

I often describe this as starting with the end in mind. You don’t need to solve every future manufacturing challenge at the beginning of development, but you do need to understand what success ultimately looks like. Once that destination is clear, you can work backwards and identify the decisions that could become difficult to reverse. Some assumptions may have little impact if they prove incorrect. Others may fundamentally influence formulation design, process scalability, supply chain strategy or commercial viability.

The objective is not to eliminate uncertainty. Development will always involve uncertainty. The objective is to understand which unknowns have the potential to alter the route to your destination and generate the information needed to make informed decisions about them.

In my experience, the strongest development programmes are not those that try to answer every question upfront. They are the ones that have a clear vision of where they want to get to and make deliberate decisions about which risks need addressing today, which can wait until later and which options need to be preserved along the way.

What practical steps can developers take to preserve flexibility and future manufacturing options as a program evolves, particularly when clinical outcomes, funding and commercial requirements remain uncertain?

Preserving optionality starts with having a credible development plan that looks beyond the next immediate milestone. That doesn’t mean trying to predict every eventuality. It means understanding the likely development pathway and identifying the pharmaceutical development risks, assumptions and uncertainties that could influence it.

As the program progresses and new information becomes available, those risks should be continually assessed and the development plan adapted accordingly. Some risks will fall away, others will become more important and new ones will emerge. The plan won’t provide all the answers, but it should create transparency around what is known, what remains uncertain and where future decisions may be required.

That visibility is valuable beyond the technical development team. It allows more informed conversations about timelines, investment and funding because everyone has a clearer understanding of where the key uncertainties sit, what may need to be addressed and what the consequences could be.

For me, that’s how you preserve optionality. You don’t try to anticipate and solve every future problem. You create enough visibility of the development pathway and its risks to make informed choices as the program evolves, without unnecessarily closing down your options.

What role should CDMOs and manufacturing specialists play in early development decisions, and how can their expertise help teams anticipate potential challenges without introducing unnecessary complexity or slowing progress?

A good CDMO should contribute far more than execution capacity. The most effective development partnerships involve people who understand the wider objectives of the program and can help identify potential challenges before they become critical. They bring experience from multiple products, technologies and development pathways, allowing them to identify risks that individual project teams may not have encountered previously.

Importantly, they should also challenge assumptions when appropriate. Sometimes the most valuable contribution a development partner can make is not providing an answer, but asking a question the sponsor hadn’t considered. Those conversations can help teams preserve flexibility, avoid unnecessary redevelopment and make more informed decisions about where to focus their resources.

Ultimately, the best CDMOs are not simply service providers. They become problem-solving partners who understand what a sponsor is trying to achieve and help them navigate the most efficient route to that destination.

Looking at the wider industry, what change in mindset would you most like to see in how pharmaceutical developers approach manufacturability, and what is the single most important piece of advice you would give to teams developing new drug candidates?

The mindset shift is to stop viewing manufacturability as something that can simply be left until later in development, while avoiding the other extreme of trying to solve every future manufacturing challenge too early.

My advice is to get the balance right. Generate the right data, understand the key risks and constraints, have the right conversations and use that information to make informed decisions at the appropriate point in development.

You won’t have all the answers, nor do you need them. But considering manufacturability early enough means you are less likely to inadvertently close off options that you may need later.