CEO Executive AssistantDigital therapeutics arrived in pharmaceutical boardrooms with enormous promise and, for many organizations, delivered a lesson in organizational misalignment. The companies that treated DTx as a software side project underestimated the regulatory rigor required. The companies that treated it as a pure clinical development program underestimated the software engineering cadence, the patient engagement dynamics, and the reimbursement challenge. Most pharma CEOs pursuing DTx programs are managing the consequences of one of those two errors right now.
If you are building a digital therapeutics capability, your most important task is not picking the right therapeutic area or the right technology platform. It is deciding how to spend your own time, and how to structure your organization, so that the disciplines required for DTx success are genuinely integrated rather than sequentially managed.
This article is a working guide to that challenge.
What Makes DTx Different From Everything Else in Your Portfolio
Before getting into time allocation, it is worth being precise about why digital therapeutics demand different executive behavior than conventional pharmaceutical programs.
A prescription digital therapeutic is software that delivers a clinical intervention. The regulatory framework is FDA’s Software as a Medical Device guidance, and the most common pathways for prescription DTx are De Novo classification and 510(k) clearance, with Breakthrough Device Designation available in some cases. The clinical evidence standard is substantively similar to what FDA expects for a drug: randomized controlled trial data, pre-specified endpoints, and a benefit-risk assessment. The evidence bar is real.
But the development cadence is not pharmaceutical. Software products iterate continuously. The version of your DTx that enters the pivotal trial may not be identical to the version that ships to patients two years later, and FDA’s position on post-authorization modifications is an active area of guidance development. The patient engagement problem is acute: a patient who does not open the app does not receive the therapy, which means adherence is both a clinical outcome and a product design problem simultaneously. And the reimbursement landscape for DTx is still being constructed, with payer coverage decisions that vary dramatically across commercial, Medicare, and Medicaid populations.
None of the functional disciplines in a traditional pharmaceutical company are individually equipped to manage these intersections. Your job is to hold those intersections at the strategic level while enabling functional teams to execute within their lanes.
The Regulatory Decision Set That Requires Your Personal Judgment
FDA’s pathway choices for a DTx program are not purely technical decisions. They are strategic choices that involve competitive timing, resource allocation, and risk tolerance, which means they belong to you.
Choosing the Right Pathway
The De Novo pathway is the appropriate route for novel DTx products without a predicate device. It offers the benefit of establishing a new regulatory classification that can serve as a predicate for future 510(k) submissions, including your own follow-on products or potential competitors. The trade-off is time: De Novo reviews have historically taken 12 to 18 months, with FDA working to improve cycle times but not yet consistently hitting faster targets.
Breakthrough Device Designation accelerates FDA interaction and can significantly compress the review timeline. The criteria require that your DTx provide more effective treatment or diagnosis for a serious condition than available alternatives. For a pharma CEO, the question is not just whether you qualify, it is whether you want to invite the heightened FDA scrutiny and resource investment that comes with active Breakthrough Device engagement before you are ready.
Your regulatory affairs leadership can assess eligibility. The decision about whether to pursue it, given your competitive landscape and your internal bandwidth, is yours.
Defining the Indication and the Software Boundary
The indication statement for a DTx determines whether it is regulated as a device at all, and if so, under which classification. This is not a regulatory technicality. It affects your marketing claims, your reimbursement category, your prescriber targeting strategy, and your competitive differentiation. Getting it wrong early means expensive remediation later.
You should personally review the proposed indication language with your regulatory and commercial teams before any FDA submission. This is a 90-minute meeting, not a delegation. The trade-offs involved, between a narrower indication that is easier to clear and a broader one that creates more commercial opportunity but faces a harder regulatory path, are exactly the kind of trade-off that requires CEO judgment.
Sound regulatory strategy oversight for DTx programs means being in the room when your indication strategy is set, not reviewing it after the pre-submission meeting.
The Reimbursement Challenge Is Not a Post-Approval Problem
The most common mistake pharma CEOs make in DTx programs is treating reimbursement as a launch-phase commercial problem. It is not. The clinical trial design, the endpoint selection, the target population definition, and the health economic model all need to be constructed with payer requirements in mind from the beginning of your pivotal program.
What Payers Actually Need
Commercial payers and PBMs evaluating a DTx are asking fundamentally different questions than they ask about a new drug. They want to know whether the clinical outcomes in your trial population translate to their covered population, which is typically sicker, less adherent, and more comorbid than trial participants. They want to understand the per-patient cost relative to outcomes achieved in real-world use, which means your adherence data matters enormously. And they want a reimbursement code structure that fits their administrative systems, which for DTx still involves navigating an imperfect fit between existing HCPCS and CPT code categories.
The Centers for Medicare and Medicaid Services has been developing coverage frameworks for digital health technologies, and several state Medicaid programs have established DTx coverage policies. Commercial payers are watching each other and watching CMS. Your market access team needs to be engaged with this landscape actively, and you need to understand the strategic implications of the coverage decisions that are being made now.
Building the Health Economic Case
Your health economics team needs to build the value dossier in parallel with your pivotal trial, not after it. The primary outcomes you choose to measure, the quality-of-life instruments you select, the cost offsets you model, all of these need to be defensible to payer medical directors who are increasingly sophisticated about DTx evidence.
This is a resource allocation decision that requires your involvement. Health economics work that runs parallel to a pivotal trial costs real money and requires talent that is in short supply. It competes for budget with the clinical program itself. You need to make the call on how much to invest, and when, based on your read of the payer landscape and your competitive urgency.
Patient Engagement as a Clinical and Product Problem
In a conventional pharmaceutical program, patient adherence is a clinical problem you measure. In a DTx program, it is also a product design problem you actively manage. This creates an organizational challenge that most pharma companies have not fully resolved.
The Software Development Cadence
Your DTx product will require continuous iteration. The user experience needs to be optimized based on engagement data. Clinical content may need to be updated as your evidence base develops. Technical performance needs to be maintained as operating system versions change across the iOS and Android ecosystems. None of this is part of the traditional pharmaceutical development model.
You need a software engineering capability that operates on a release cadence measured in weeks, not the years that characterize pharmaceutical development cycles. That capability is either built in-house, which requires hiring software engineers and product managers who are accustomed to consumer tech standards, or sourced through a technology partner. Either way, the governance model for software releases needs to account for FDA’s expectations about post-market modifications.
The FDA’s Software Predetermined Change Control Plan framework allows for pre-approved categories of software changes that can be implemented without a new submission. Getting that PCCP right at authorization is a significant benefit. Your regulatory and engineering teams need to plan for it together, and you need to understand what flexibility it gives you and what it does not.
Engagement Design Belongs in Your Clinical Strategy
Engagement is not separable from efficacy in a DTx program. A therapy that patients stop using does not work, and your payer conversations will expose this quickly. The engagement design, the behavioral science principles embedded in your product, the notification strategy, the content progression logic, these are clinical strategy decisions as much as product decisions.
Your CMO and your head of product need to be genuinely aligned on engagement strategy, not just coordinating on separate workstreams. That alignment is hard to create through org charts; it requires deliberate joint governance that you sponsor at the executive level.
For context on how digital health engagement translates to real-world outcomes, the New England Journal of Medicine’s coverage of digital therapeutics evidence provides a rigorous foundation for the evidence standards your program should target.
Integrating DTx Into a Traditional Pharma Organization
The organizational integration challenge is where most pharma DTx programs either succeed or fail. Traditional pharma organizations are built around molecules. The incentive structures, the career paths, the project management methodologies, the regulatory muscle memory, all of it is optimized for chemical and biological entities. DTx fits awkwardly into every one of those systems.
The Build-Buy-Partner Decision
You have three structural options for DTx capability: build an internal team, acquire a DTx-native company, or partner with a DTx developer. Each has a distinct risk profile.
Building internally gives you integration and control but takes years and requires hiring talent that is scarce and expensive. Acquiring a DTx company gives you speed and existing capability but creates integration challenges and often results in cultural attrition from the acquired team. Partnering gives you access without the integration risk, but creates IP and commercialization complexity and a dependency on a partner whose incentives may not be fully aligned with yours.
Your choice depends on how central DTx is to your long-term strategy. If you are making a one-program bet to complement a drug franchise, partnership is almost certainly the right answer. If you believe DTx is going to be a meaningful part of your commercial model across multiple therapeutic areas, you need to be building or acquiring.
This is a CEO-level strategic decision that will shape your capital allocation and organizational design for years. Give it the analytical rigor you would give a major M&A transaction.
Protecting the DTx Team From Organizational Antibodies
Traditional pharma organizations reliably generate what some executives call organizational antibodies: institutional responses that slow or neutralize things that do not fit the existing model. DTx teams experience this as resource competition with drug programs, regulatory affairs teams that default to pharmaceutical frameworks when software frameworks are more appropriate, commercial teams that do not know how to position a prescription app, and finance teams that apply drug development NPV models to software products with very different cost and revenue structures.
Your job is to protect the DTx team’s ability to work at a pace and with a methodology appropriate to software-driven development, while ensuring the clinical and regulatory rigor that prescription status requires. That means creating a dedicated governance structure for your DTx program that does not route every decision through the same committees that govern your drug pipeline.
Sound pipeline governance decisions for DTx require separate stage gates calibrated to software development milestones, not just traditional clinical development milestones.
The Joint Venture and Co-Development Model
Several large pharma companies have structured their DTx investments as joint ventures or co-development agreements with technology companies. These structures have the advantage of bringing in software expertise and sometimes consumer-facing distribution capability. They have the disadvantage of creating governance complexity that can slow decisions and create accountability gaps.
If you are in or considering a joint venture structure, your personal involvement in the JV governance body is not optional. The decisions that go to the JV board are exactly the ones where pharma and technology perspectives diverge most sharply: evidence standards, regulatory timelines, product iteration pace, and reimbursement strategy. Without CEO-level engagement on the pharma side, you will consistently lose those debates to partners who are more comfortable with their own framework.
Time Allocation for a DTx Program
A practical framework for a CEO with an active DTx program in pivotal development or early commercial stage:
Monthly: DTx program review covering clinical data, engagement metrics, and regulatory milestones (90 minutes), market access and payer strategy update (60 minutes).
Quarterly: Software release governance review including any FDA-relevant changes (60 minutes), health economics and value dossier progress review (60 minutes), commercial readiness review covering payer coverage updates and prescriber engagement (90 minutes), executive alignment meeting with any technology partner or JV counterpart (60 minutes).
Annually: Full strategic review of your DTx portfolio and organizational capability, including the build-buy-partner question and capital allocation decisions. This should be a dedicated half-day, separate from your broader pipeline review, because the strategic logic is different enough to warrant its own conversation.
The total is roughly 8 to 12 hours per month of structured DTx-specific engagement. That is less than an ADC program demands, but only because the deep technical complexity is lower. The organizational and strategic complexity is, if anything, higher.
The Integration Payoff
The companies that will win in digital therapeutics are not necessarily the ones with the best technology or even the best clinical data. They are the ones that figure out how to integrate software development discipline, pharmaceutical regulatory rigor, payer engagement expertise, and patient behavior science into a coherent operating model. That integration does not happen at the VP level. It happens when the CEO is personally committed to building it.
The DTx opportunity is real. Prescription digital therapeutics that treat serious conditions with evidence comparable to drug standards represent a genuinely new category of medicine. The reimbursement infrastructure is maturing. The regulatory framework, while still evolving, is becoming more predictable. The patient populations that stand to benefit are large and underserved by existing pharmaceutical options alone.
The CEOs who capture that opportunity will be the ones who took the organizational and strategic work seriously from the beginning, who built the right structures, made the right calls at the right moments, and were personally present for the decisions that no one else could make. That is the work. It starts with how you allocate your time.