Build to Operate or Build to Exit? Choosing the Right Licensed Entity Model
Every pharma or biotech business that sets up a licensed entity, a UK MIA, a WDA, an EU manufacturing authorisation, is making a decision that goes well beyond compliance. They are deciding what that entity is for.
Is it being built to run the business for the next decade? Or is it being built to be sold, merged, or absorbed into a larger organisation within the next few years?
Most businesses do not ask that question explicitly before they start. They default to whichever model their consultant or first hire happens to know, and only discover the mismatch later, usually when a buyer's due diligence team starts asking questions the QMS was never designed to answer.
The two models are different enough that the distinction is worth making deliberately, from the first SOP onward.
Two different builds, two different endpoints
Built for You is an entity designed to operate. The licence, the QMS, the staffing model, and the systems are built for the business you are actually running, scaled to your real volume and your real risk profile, with the flexibility to grow as the business grows.
Built to Buy is different. It is an investment-ready commercial package, a QMS and licensed infrastructure built specifically to withstand the scrutiny of a buyer, an investor, or a partner conducting due diligence. The end goal is not day-to-day operation. It is a clean, defensible asset that holds up when someone else's technical and quality team goes through it line by line.
Both are legitimate, well-established paths. The problem is not choosing one. The problem is not choosing at all, and ending up with a build that quietly compromises on both.
Signs of which model you actually need
• Built for You: you plan to hold and operate this entity long-term, growth will be organic, and the priority is operational efficiency
• Built for You: you need a licence that flexes as your product portfolio and headcount change year on year
• Built to Buy: you are building toward a trade sale, acquisition, or investment round within a defined timeframe
• Built to Buy: a buyer's technical due diligence team will eventually review every SOP, deviation, and CAPA you have ever raised
• Built to Buy: the value of the business depends partly on the quality infrastructure being demonstrably clean and complete, not just compliant
Why the distinction matters from day one
The mistake most businesses make is treating this as a decision for later, something to sort out once the entity is established and running. In practice, the choice shapes decisions that are expensive and disruptive to unwind.
A QMS built purely for operational efficiency will often carry pragmatic shortcuts. Streamlined change control, a lean deviation process, documentation calibrated to what a working team needs day to day rather than what an external reviewer needs to be convinced of. None of that is wrong for a business built to operate. It becomes a liability the moment a buyer's due diligence team starts asking why records are thin, why certain decisions were never formally documented, or why the audit trail has gaps that made sense internally but read as risk externally.
The reverse is also true. A QMS built to satisfy due diligence, with every process heavily documented and every decision exhaustively evidenced, can be genuinely inefficient to run day to day if the business's real intention was always to operate it long-term. That level of overhead, sustained indefinitely, becomes a drag on the operation it was never designed to carry.
TDP builds both models. End-to-end licensed entity builds for businesses that intend to operate long-term, and investment-ready commercial packages for those building toward a sale or investment round.
What actually changes depending on which model you choose
1. QMS depth and documentation standard. A Built for You QMS is scaled to operational need. A Built to Buy QMS is scaled to what a due diligence reviewer, often more conservative than a regulator, will expect to see fully evidenced.
2. Staffing and RP/QP model. An operating entity can grow its RP, QP, and quality resource in step with real workload. A sale-track entity often needs that resource in place earlier and more visibly, because a thin quality function at the point of due diligence reads as a gap the buyer has to price in.
3. Change control and traceability. Buyers want to see a clean, complete trail from every significant decision to its rationale and its closure. Operating businesses can sometimes carry informal decision-making that never gets fully written up. That gap rarely causes a problem operationally. It becomes a red flag in due diligence.
4. Timeline and sequencing. A Built to Buy entity is usually built against a deal timeline, which means licensing, QMS build, and audit readiness need to converge by a specific date, not develop organically. A Built for You entity can afford to mature at the pace the business actually needs it to.
5. What 'good enough' means. For an operating entity, good enough is a system that keeps the business compliant and running smoothly. For a sale-track entity, good enough is a system that survives a hostile, detailed technical review by someone actively looking for reasons to reduce the price.
The cost of retrofitting
Businesses that build without deciding often find out which model they actually needed at the worst possible moment, when a term sheet is on the table and due diligence has already started.
Retrofitting a QMS built for operational efficiency into something that will survive due diligence, under deal timeline pressure, is far more expensive and disruptive than building it correctly from the start. Gaps have to be closed retroactively, documentation has to be reconstructed for decisions made months or years earlier, and the buyer's confidence in the whole system takes a hit the moment they see how much scrambling was needed to get it presentable.
The reverse mistake is quieter but still costly. A business that over-builds for due diligence it never actually needed carries unnecessary process weight for years, slowing decisions and adding cost to an operation that was never going to be sold. Layers of documentation and sign-off that exist purely to satisfy a hypothetical buyer become friction on every routine change control, every supplier qualification, every batch disposition, for a business that simply needed to operate well.
Both failure modes trace back to the same root cause: nobody made the call early enough for it to shape the build itself.
Questions worth answering before you build
• Is there a realistic prospect of a sale, acquisition, or investment round within the next three to five years?
• Who is the intended long-term owner and operator of this entity?
• What would a buyer's technical due diligence team look for, and could your current plan survive it?
• Is your QMS being designed for the business you have, or the business you hope someone else will want to buy?
• Does your current build timeline match your actual commercial timeline, or is it drifting?
TDP's Built to Buy service delivers investment-ready QMS and licensed infrastructure designed to withstand real due diligence, not just pass a routine inspection.
What good looks like on each path
A well-executed Built for You entity tends to look unremarkable from the outside, and that is the point. The QMS matches the actual scale and risk of the operation. Documentation is thorough where it needs to be and lean where it does not. RP and QP cover grows in step with headcount and product complexity, rather than sitting oversized against current volume. The system is built to be lived in, not admired.
A well-executed Built to Buy entity looks different. Every process has a clear owner and a documented rationale. Deviations and CAPAs close on time and read cleanly, without gaps that require explanation months later. The audit trail assumes an unfamiliar, sceptical reader will go through it, not a team that already knows the context. Licensing and quality infrastructure are timed to be fully mature well before a deal process begins, not still being finished when the data room opens.
Neither version is more rigorous than the other in absolute terms. They are calibrated to different audiences: a working team on one side, and an external reviewer actively looking for reasons to discount value on the other.
Deciding before you build, not after
There is no universally right answer between Built for You and Built to Buy. The right model depends entirely on what the business is actually for, and where the owners genuinely intend to take it.
What matters is making that decision consciously, early, and honestly, rather than defaulting into a build that was never designed for the outcome you are actually working toward. The businesses that get this right are the ones who ask the question before the first SOP is written, not the ones who discover the answer when a buyer's due diligence team asks it for them.
Talk to us about which model fits your plans