What's Changing in How You Run Your Programmes

Every Chief Operating Officer or Head of Development Operations at a mid-sized European biotech has had the same Monday morning. Three meetings on the calendar. The first is a CRO steering committee on your Phase IIb programme, and site activation has drifted to week twelve against a plan of week eight. The second is a CDMO quality review on the comparator batch, with an out-of-spec your senior CMC lead is the only person in the company who can fully interpret. The third is a thirty-minute slot Thursday with your senior regulatory affairs director. The subject line says transition.

You have run this function for fifteen years. The pattern used to be simple. Hire the best clinical operations, regulatory, and CMC people you could find. Write the SOPs. Follow them. Keep the cash burn honest for the CFO. Keep the board reporting clean. The business was understandable.

Something changed. Your monthly cash-burn conversations with the CFO are tighter every quarter. Your senior regulatory and CMC leads are the scarcest resource in the firm, and they are spending most of their billable week on coordination and preparation work an infrastructure you have not built could carry. Your milestone cycles have not meaningfully shortened in fifteen years, despite the tooling that exists now. And you can name the three or four senior people whose retirement inside five years will cost you more than any operations-cost programme has ever gained you.

This is not a you problem. It is an industry problem and a development-engine problem, happening at the same time. Most biotech COOs are treating them as two. The ones who see them as one are going to own the next decade of European mid-market biotech operations.

This briefing covers what is happening in your sector, what it means inside your development engine, and the three questions your operations team should answer before the next pipeline review.

Every technology wave your sector absorbed in the last thirty years gave your firm a reason to hire more senior operations people. ICH E6 revisions widened the monitoring and quality workload. EudraCT and CTIS pulled more regulatory operations into every submission. Risk-based monitoring shifted CRO oversight back onto the sponsor. Adaptive trial designs stretched the protocol-amendment cycle. Each new layer gave the senior headcount plan a new reason to grow. Development operations has run on senior specialists plus SOPs for a generation, and it never once broke.

AI does not behave the same way. Your programmes still need the same IND, the same CTA, the same quality agreement, the same CMC dossier. The scope of the work is unchanged. But the coordination, preparation, cross-reference, and documentation layer that used to absorb most of your senior people's week can now be done in a fraction of the time by infrastructure the firm has not deployed. Under a senior-heavy operations model, that shift means the same cash-burn run rate for the same pipeline, while competitors who rebuilt the architecture are hitting milestones four to eight months faster on the same capital. Your sector is starting to call this milestone compression, and for the first time in a generation, the senior operations cost structure is actually moving.

Your partners' and acquirers' due-diligence teams are showing up with explicit questions about programme continuity. By the time your team walks into the data room, the risk premium has already been set.

The competitors in your segment are not waiting. A handful of Nordic and continental biotechs have committed serious budget to development-operations infrastructure in the last eighteen months. The ones moving first are submitting INDs in twelve to fourteen months that used to take eighteen, activating sites in eight to ten weeks that used to take twenty, and closing partnership conversations on programme-continuity terms that competitors cannot credibly offer. The other half of the story sits on the partnership side. Licensors and acquirers who used to pay a heavy key-person-risk premium against mid-market biotech are now paying a materially smaller one to firms whose development history lives in infrastructure. The firm that builds that infrastructure first captures a valuation asymmetry the incumbents will not close quickly.

Your clinical operations. Programme managers are working harder to hold sites, amendments, and data lock on the same timelines. Handoffs between CRO project manager, internal operations, and monitoring carry friction built when the function was organised around a 2008 ICH workflow and never redesigned. The firm activates a site and locks a database the same way it did in 2015. The tooling, the CROs, and the agency expectations have all changed. The operations engine has not.

Your regulatory and quality. First-cycle acceptance has not moved in ten years, and is now at risk. The senior regulatory director who catches the protocol finding a junior would miss, who reads the agency's meeting minutes before others see them, who walks your team through a regulator's unwritten preference, carries that judgment as biography. When one steps back, the firm runs two submissions with a visible quality gap before anyone names the cause. Three before a reviewer questions the precedent cited. Five before an inspection finds something that loses a partnership.

Your CMC and supply. Your senior CMC lead carries tech-transfer history, batch-record pattern reading, yield-trend judgment, and CDMO relationship memory for the two or three CDMOs you depend on most. Most of that knowledge has never left the monthly review call. The reasoning behind the specification choices your CDMOs now take as given sits in one person's head. The next time you add a CDMO, or a project manager rotates, that knowledge is the asset that either transfers or does not.

Your programme and partnership team. Your programme managers run dashboards, pipeline reviews, data rooms, and investor briefings on substrate the firm has accumulated over a decade. Most of that substrate lives in a hundred thousand emails, a hundred PowerPoints, and a programme history nobody has written down. When a partner asks why the Phase II design branched the way it did in 2023, the person who knows the answer schedules a call and reconstructs it from memory. That call is the valuation exposure.

Your senior experts. Your three to six most senior development-operations people cost the firm between €220 and €380 thousand fully loaded. On a standard week they deliver twelve to sixteen hours of the judgment only they can provide. The remaining twenty-four hours go into agency correspondence, CDMO coordination, CRO oversight, precedent cross-reference, and documentation assembly. The scarcest resource in the firm is spending most of its week on the work it is least suited for.

Your sector is compressing from above because AI compresses discovery, sending more programmes into the clinical bridge and loading more work onto your development operations. Your engine is compressing from below because your senior regulatory and CMC leads are spending most of their week on coordination work the firm has not built infrastructure to hold. Same force, two altitudes. But there is a third thing happening that most biotech COOs have not named yet, and it is the one that matters most.

You do not have three problems. You have one. The senior judgment that makes your programmes credible, to agencies, to CDMOs, to partners, to acquirers, has never been separated from the senior who carries it. Every milestone slip, every quality finding, every protocol amendment cycle, every stuck negotiation is a symptom of that single unsolved thing. Pay a senior regulatory director to prepare a pre-IND briefing book from scratch, and velocity drifts. Let a senior CMC lead step back with their CDMO judgment still in their head, and your next tech transfer costs you two quarters. Keep the development engine designed around a bottleneck that cannot be unblocked, and the milestone cycle cannot shorten.

Look at the firms pulling ahead. Clinical operations, regulatory, CMC, and partnership history are not four separate programmes. They are one piece of infrastructure. Every submission enriches the infrastructure. The senior who retires adds to it on the way out. The mid-level programme manager learns by using it. The partnership conversation holds because the answers live in it. The same infrastructure that protects first-cycle acceptance protects tech-transfer continuity and shortens the milestone cycle.

You have eighteen to twenty-four months. The AI adoption debate is over. Your question now is whether you build the infrastructure your firm will run on for the next decade, or wait until the CFO brings in a vendor who will build one that belongs to someone else.

Every biotech COO has had the AI conversation. Most are making the same four decisions. A smaller group is making different ones. The difference is architecture, not tooling.

Three questions every biotech COO is tracking. None of them used to be the same question. They are now.

Four concrete moves any biotech COO can start this quarter. Each touches one part of the development engine. Pulled together, they become one architecture the firm runs on.

The biotech COO has four places to go for help. None of them can do what we do.

The big consulting firms' life-sciences practices sell €500K to €2M operating-model diagnostics delivered by partners and analysts billing hours. They produce decks. They cannot put working infrastructure into a regulatory director's workflow in three months. Their own revenue model is part of your problem.

The biotech-specialist CROs and advisory firms sell seconded regulatory or CMC specialists on retainer. They carry domain expertise. They do not deliver infrastructure that outlives the engagement. Senior judgment stays biographical, rented instead of owned.

The biotech-operations software vendors sell a platform and leave you to fill it. They cannot tell you which precedent is worth extracting or how to structure it. Every biotech has watched this purchase underdeliver once.

Your internal IT and the process-mining platforms will build a chatbot on your document system. IT optimises for standardisation. It does not sit close enough to how your seniors reason about agency precedent to codify it.

The market offers four things you have already said no to. GRAIL is the fifth option.

We start with your leadership team because the change cannot outrun their personal understanding of what is possible. Three workshops. Each delivers standalone value.

The questions where your operations team cannot agree on an answer are the ones worth an hour on the agenda. Ask these honestly.