From IND to NDA/BLA: What Changes, What Scales, and What Breaks

For many small and startup pharma and biotech companies, the transition from IND-stage development to NDA or BLA preparation feels less like a clean handoff—and more like a stress test.

Processes that worked perfectly well during early development suddenly feel strained. Documents multiply. Timelines compress. Questions from regulators get more detailed, more cross-functional, and less forgiving of gaps.

This isn’t a sign that your team did anything wrong. It’s a sign that your program is maturing.

In this third post of our year-long NDA/BLA series, we’ll break down what actually changes as companies move from IND to NDA/BLA, what can realistically scale with you, and what often breaks if it isn’t rethought in time.

IND vs. NDA/BLA: A Shift in Expectations

IND-stage development is fundamentally exploratory. FDA expects programs to evolve, data to mature, and strategies to adjust as new information emerges.

NDA and BLA submissions, by contrast, are defensive by design. They ask you to demonstrate not only that your product is safe and effective—but that your entire development story is coherent, controlled, and reproducible.

That shift affects everything:

• The level of documentation required

• How decisions are justified

• How consistently information must align across functions

• How confidently teams must answer “why” and “how,” not just “what”

What Changes: The Nature of the Questions

One of the first things teams notice as they approach NDA/BLA preparation is that FDA’s questions change.

During IND-stage interactions, questions often focus on:

• Is the study design reasonable?

• Are risks being appropriately managed?

• Is the program safe to continue?

As NDA/BLA approaches, questions shift toward:

• Is the totality of evidence internally consistent?

• Are conclusions fully supported by the data?

• Can variability be explained and justified?

• Are decisions traceable and defensible?

This is where teams sometimes feel caught off guard. Answers that were “good enough” earlier may no longer be sufficient when viewed across an entire submission.

What Scales: Smart Foundations Built Early

Not everything needs to be rebuilt for NDA/BLA—and teams that planned intentionally often find that some elements scale surprisingly well.

Examples include:

• Clear decision documentation, even if informal early on

• Cross-functional communication habits between clinical, CMC, regulatory, and quality

• Centralized document and data management, even if lightweight

• Program-level thinking rather than document-by-document problem solving

• Submission Cloning from IND to NDA/BLA saves tons of effort at the publishing stage, so the more you can submit even what may feel like "extra" documentation to the IND, the easier it makes it to simply clone that to your marketing application.

These foundations don’t require big-company infrastructure. They require consistency, ownership, and foresight.

Teams that invested modest effort in these areas early often experience a smoother transition as volume and scrutiny increase.

What Breaks: Common Stress Points for First-Time Sponsors

As programs scale, certain cracks tend to appear—especially for first-time NDA and BLA sponsors.

Common breaking points include:

• Regulatory operations processes that worked for INDs but can’t handle NDA/BLA complexity

• Data traceability gaps between source data, analyses, and submission narratives

• Inconsistent terminology or positioning across documents authored over many years

• Limited visibility across functions, leading to misalignment late in development

These issues rarely stem from lack of effort. More often, they result from systems and processes being asked to do something they were never designed to handle.

Why the IND to NDA/BLA Transition Feels So Hard

The jump from IND to NDA/BLA is not incremental—it’s exponential.

• More documents

• More contributors

• More dependencies

• More regulatory risk

At the same time, timelines tighten and tolerance for rework shrinks. Teams are expected to move faster and be more precise.

This is why Phase 2–3 is such a critical window. It’s the moment to assess what will scale, what needs reinforcement, and what should be redesigned before it fails under pressure.

Making the IND to NDA/BLA Shift Without Overbuilding

Preparing for NDA/BLA doesn’t mean abandoning agility. It means evolving intentionally.

For many sponsors, that looks like:

• Strengthening regulatory operations before submission crunch time

• Clarifying ownership of cross-functional deliverables

• Improving traceability and version control

• Introducing just enough program management to keep teams aligned

The goal isn’t perfection—it’s resilience.

Looking Ahead in the Series

This post continues the core theme of our series: NDA and BLA success is built long before submission.

In the next post, we’ll explore what it really means to be “NDA/BLA-ready” as a Phase 2–3 company—and how to assess readiness honestly, without panic or overengineering.

At The Sugar Water Operations Team, we help first-time sponsors navigate this transition thoughtfully—keeping what works, fixing what doesn’t, and building only what’s truly needed for a successful NDA or BLA.