CEO Executive AssistantCombination product strategy pharma CEO leadership sits at an unusual intersection: pharmaceutical development expertise, medical device regulatory knowledge, engineering capability, and commercial positioning across both drug and device markets. Companies that develop combination products – drug-device products like prefilled syringes, autoinjectors, drug-eluting stents, or inhaled drug delivery systems – face regulatory complexity that neither pure pharma nor pure device companies encounter in the same form.
CEOs who understand this complexity and who have built organizational capability to navigate it hold a genuine competitive advantage. Combination products can be powerful commercial differentiators: a biologic delivered via a patient-friendly autoinjector versus a competitor’s IV infusion creates meaningful clinical and commercial advantages. But getting there requires managing two regulatory agencies, two quality systems, and two sets of manufacturing standards in a way that most pharma organizations have not historically been equipped to do.
What Combination Products Require That Standard Pharma Does Not
The regulatory complexity of combination products stems from a jurisdictional architecture that divides oversight between FDA’s Center for Drug Evaluation and Research (CDER), Center for Devices and Radiological Health (CDRH), and the Office of Combination Products (OCP), which coordinates the two. For biologics, CBER may also be involved.
The determination of which center has primary jurisdiction shapes your entire regulatory strategy. A prefilled syringe where the primary mode of action is the drug is typically regulated by CDER with CDRH consultation. A drug-eluting stent where the device component may have a separate mode of action may have different primary jurisdiction.
CEOs do not need to master this regulatory architecture. But they need to understand it well enough to ensure their regulatory strategy team has the expertise to navigate it, and that combination product regulatory complexity is reflected in timeline and resource planning.
The specific implications for CEO oversight:
Two quality systems: Pharmaceutical current Good Manufacturing Practice (cGMP) and device Quality System Regulation (QSR) have different requirements. Your manufacturing operations for a combination product must comply with both. This is an organizational capability question that requires CEO-level attention when entering combination product development.
Device design controls: Medical device development requires design controls that are not standard in pharmaceutical development: user research, risk analysis (ISO 14971), design verification and validation, and human factors testing. These are not optional – they are FDA requirements. Building this capability or partnering to access it is a CEO-level decision.
Human factors engineering: FDA requires human factors testing for combination products – studies demonstrating that patients and healthcare providers can use the product safely and effectively. This is particularly important for self-injection devices where administration errors could cause harm. Human factors testing should be planned early and integrated into your development timeline, not added as a post-development requirement.
CEO Decision Points in Combination Product Development
The Device Platform Decision
When your drug development program requires a combination product (because the drug requires a specific delivery mechanism for clinical performance), the first major CEO decision is the device platform: develop a proprietary delivery system, partner with a device company, or license an existing platform.
Each option has distinct implications for cost, timeline, IP, and commercial positioning. A proprietary device platform is a competitive asset but requires device development expertise and capital. A partnership with a device company creates shared economics and execution risk. A licensed platform is faster but potentially less differentiated.
This is a strategic decision with multi-year financial implications. Present it formally with scenario analysis before committing to a development path.
Combination Product vs. Drug-Only Development Path
In some therapeutic areas, you have a choice: develop the drug alone (for healthcare provider administration) or develop a combination product that enables self-administration. The combination product path takes longer, costs more, and adds regulatory complexity – but if the self-administration use case is clinically important, it may create a substantially superior commercial product.
This trade-off belongs in your development strategy review. Engage your Chief Medical Officer, Chief Commercial Officer, and Chief Regulatory Officer in a structured analysis before committing to either path. The CEO’s role is to ensure this choice is made explicitly with full commercial and regulatory analysis, not defaulted into because the drug development path is simpler.
Supplier and CDMO Selection for the Device Component
The device component of a combination product requires specialized manufacturing – typically a device CDMO or a partnership with a device manufacturer. The selection of this partner is a major supply chain decision with quality, regulatory, and commercial implications.
Ensure your combination product device supplier meets the same standards you apply to your drug CDMO: quality system rigor, regulatory compliance history, capacity planning, and CEO-to-CEO relationship for Tier 1 partners.
Regulatory Strategy for Combination Products
The most important regulatory strategy decision for a combination product is whether to pursue a single IND/NDA/BLA submission covering both components or separate applications. For most combination products where the drug is primary, a single application with the appropriate device information incorporated is the standard approach.
But the regulatory content is substantially more complex: you must address both drug safety and efficacy data and device safety and usability data, including human factors study results. Your regulatory team needs experience with both CDER and CDRH submissions. If they do not have direct combination product experience, build in time for a Request for Designation from OCP early – before you are deep in development – to understand your specific regulatory pathway.
Seek a meeting with FDA’s OCP early in development, particularly if your product raises complex jurisdictional questions. These early interactions prevent the regulatory surprises that create timeline delays close to submission.
Your regulatory timeline management process needs to account for the longer development and review timelines typical of combination products, and for the possibility of additional review cycles if human factors or device design issues emerge during review.
Commercial Differentiation Through Combination Products
The commercial case for combination product investment is typically patient experience and adherence. A self-injection device that patients can use accurately and comfortably at home, without requiring a healthcare provider visit, is a meaningful quality-of-life improvement. In competitive therapeutic areas, this can drive formulary preference and patient loyalty.
To realize this commercial return, the device component must genuinely perform well: intuitive design, minimal injection-site pain, reliable dose delivery, robust failure mode prevention. This requires substantive investment in human factors and device design – not a minimum viable device added as an afterthought.
Your Chief Commercial Officer should be involved in device platform decisions from the early stages. If the device does not deliver a meaningful patient experience improvement over alternatives, the commercial case for the additional development investment is weak.
The pharma commercial launch process for a combination product must address device-specific commercial requirements: training programs for patients and healthcare providers, device support infrastructure, and any post-market surveillance commitments for the device component.
Building Organizational Capability for Combination Products
Many pharma organizations entering combination product development do so without adequate device development expertise. The specific capabilities you need internally or through partners:
- Device design engineering
- Human factors research and testing
- Quality system integration across pharmaceutical and device requirements
- Regulatory affairs expertise covering both CDER and CDRH
The CEO’s role is to assess whether these capabilities exist in your organization and to make the investment or partnership decisions needed to close the gaps. Do not underestimate the time required to build genuine device development capability in a pharmaceutical organization – it is a multi-year organizational development effort.
Conclusion
Combination product strategy pharma CEO leadership requires a broader regulatory and technical awareness than pure drug development, and a willingness to make specific organizational capability investments that most pharma companies have not historically needed. The CEOs who navigate this well treat the device component as a first-class citizen in their development strategy – with appropriate resource, expertise, and timeline planning – rather than a downstream add-on to a drug program. The commercial reward for excellent combination product development is real. So is the regulatory risk of approaching it without adequate preparation.
Related Reading
For further context, explore Pharma CEO Time Management for Autoimmune Disease Strategy and Biomarker-Driven Trial Management: What Pharma CEOs Must Decide and When.