White Paper · 01

When Platform Processes Break: CMC Realities of Manufacturing Novel Engineered AAV Capsids

A Practical Perspective from the Developer Side of the Table.

Michael J. DiBiasio-White, PhD Founder & Principal, ViroSpark BioConsulting ~10 min read

AI-designed and rationally engineered AAV capsids are delivering tissue tropism, immune evasion, and potency profiles that natural serotypes cannot match. For early-stage gene therapy developers, access to these capsids represents a genuine competitive advantage. But novel engineered capsids don't behave like AAV9 or AAV5 on a manufacturing floor — and for resource-constrained teams, that mismatch compounds into costly rework, missed milestones, and weakened CMC packages.

Why platform assumptions break

"Platform" is one of the most useful words in viral vector CMC. It captures the idea that a fixed set of processes, methods, and supplier relationships — built around a familiar serotype like AAV9 or AAV5 — can be re-applied across programs to save time, money, and risk. For natural-serotype work, this assumption holds remarkably well. For engineered capsids, it does not.

Engineered capsids challenge platform assumptions across four interlocking domains:

Where the cracks first show up

The earliest warning signs are easy to miss because they look like ordinary "process variability." Common patterns:

Yields that don't reproduce at scale

Small-scale transient transfection results that look promising in 24-well format don't translate cleanly to 50 L or 200 L bioreactors. The capsid biology — assembly kinetics, packaging efficiency, stability of the assembled particle — interacts with the platform conditions in ways the platform was never tuned for.

Capture chemistry that drops off

Affinity resins designed for natural-serotype AAVs can bind engineered capsids with very different efficiency, selectivity, or elution behavior. A program can run an entire pilot campaign before the team realizes the capture step is the wrong tool for this capsid.

Analytics that test the wrong thing

Identity assays, potency assays, and full/empty methods are usually built against a specific tropism or epitope. For an engineered capsid, those methods may pass the candidate while measuring something that no longer correlates with clinical performance.

Comparability that won't hold

Process changes are inevitable. For engineered-capsid programs, they are more frequent than for platform programs — and the comparability framework most teams default to is built around the assumption that the capsid is the constant, not a variable.

Engineered capsids reward developers who treat manufacturability as a discovery-stage variable — and punish those who treat it as a downstream problem.

What to do about it

The expensive version of this problem is the one where each crack is discovered separately, sequentially, after the team has already committed to the platform assumption. The cheaper, faster version is to plan for capsid-specific behavior from candidate selection forward.

1. Manufacturability scoring before candidate lock

Score capsid candidates on a small set of manufacturability indicators alongside biology: small-scale transient yield, capsid stability across pH and ionic conditions, behavior under the platform's capture chemistry, and full/empty profile by your standard analytic. None of this requires a finished process; all of it is cheap relative to discovering problems later.

2. Producer system commitment with a real exit ramp

Transient transfection or stable producer cell line? The right answer depends on capsid behavior, expected scale, and clinical timeline. Commit to one route for IND-enabling work — but design the comparability strategy you will need if you switch, before you have to.

3. Analytical strategy that anticipates the engineered capsid

Identity, potency, and full/empty methods built for AAV9 may not transfer cleanly. Build the analytical gap assessment into the discovery hand-off, not into IND preparation. Method development time you cannot recover later.

4. Comparability designed up-front

For engineered-capsid programs, comparability is not a single event near the end of development; it is a continuous discipline. Write the framework before tox material is made. The difference between a clean amendment and a clinical-hold question is often whether comparability was an afterthought or a plan.

5. CDMO selection that matches the capsid, not the platform

The "right" CDMO for an AAV9 program may be the wrong CDMO for your engineered capsid. Capacity, capsid experience, analytical depth, and tech transfer maturity all matter. The diligence done at selection is the cheapest CMC investment a program will ever make.

Key takeaways

  • Platform processes were built around the assumption that the capsid is constant. For engineered capsids, that assumption fails — usually quietly, and usually late.
  • Failure modes cluster in four areas: process development, purification, analytics, and GMP readiness / comparability.
  • The cheapest fix is preventative: manufacturability scoring at candidate selection, analytical gap assessment at hand-off, and a CDMO chosen for the capsid rather than the platform.
  • Comparability is a discipline, not an event. For engineered-capsid programs, it has to be designed in before tox.
  • Resource-constrained teams cannot afford the expensive version of this problem. Sponsor-side judgment, applied early, is the difference between a program that holds its IND timeline and one that quietly loses a quarter.

Closing

Engineered capsids deepen the existing valley between RUO and Phase 1. The good news is that the decisions that determine outcomes are knowable, sequenceable, and — for lean teams — surprisingly affordable when made on time. The expensive version is the one where they get made by default.

If you are building an engineered-capsid program and want a sponsor-side perspective on where you are and what's next, ViroSpark BioConsulting was built for that conversation.

About the author

Michael J. DiBiasio-White, PhD is the Founder & Principal of ViroSpark BioConsulting. He is a PhD molecular virologist and CMC/TechOps operator with 10+ years building viral vector and complex biologics programs from research through IND and first GMP supply, including CMC & TechOps roles at Affinia Therapeutics and Ring Therapeutics (Flagship Pioneering). More about Michael →