U.S. launch readiness
FDA Approval Is a Milestone. A U.S. Launch Is a System.
What first-time U.S. launchers often discover too late—and the decisions that should be made before one approval date becomes the only date anyone can see.
For years, one date can carry the emotional weight of an entire company: the expected FDA decision. The board asks about it. Investors ask about it. Families plan around it. People refresh their phones waiting for it.
Then the decision arrives—and the company discovers that one date has been hiding a hundred other decisions. Who owns the patient journey? Which payer assumptions are still assumptions? Is the field team the right size for the actual prescriber universe? What happens when one vendor misses a dependency? Who is allowed to say the launch is not ready?
FDA reported 46 novel drug approvals in 2025. Every one represents an extraordinary scientific and regulatory achievement. Approval, however, does not create payer coverage, patient access, trained managers, a functioning distribution path, or a reliable commercial operating cadence.[1]
First-time launchers are not short on intelligence
They are usually short on institutional memory. Experienced organizations have routines for questions a first-time launcher may not yet know to ask. Those routines live across people, governance, systems, vendor relationships, and the informal pattern recognition that comes from previous launches.
In McKinsey’s analysis of launches from 2014 through 2017, first-time launchers reached a median 63% of prelaunch expectations, compared with 93% for experienced launchers. The study period matters: this is not a 2026 market census. But the operating lesson remains useful. A strong asset does not automatically come with a strong launch institution.[2]
That gap is not solved by producing a longer checklist. A checklist records activities. Leadership needs to see decisions, weak assumptions, cross-functional dependencies, evidence quality, and the consequence of waiting.
Regulatory readiness and commercial readiness touch—but they are not interchangeable
For a manufacturer outside the United States, the distinction is especially important. FDA requirements continue beyond the approval event. Foreign drug establishments offering products for U.S. import must meet registration, listing, application, and import-information requirements. Incomplete or inconsistent information can delay entry or lead to detention. FDA also expanded its use of unannounced inspections at foreign manufacturing facilities in 2025.[3][4]
Those obligations belong in the launch critical path. But they do not replace the separate commercial work: evidence strategy, payer engagement, distribution design, patient services, organization design, hiring, training, data, governance, and field execution.
One workstream can be green while the launch remains exposed. A field team can be hired on schedule and still be mis-sized because the target-account assumptions were weak. A hub can be contracted and still fail patients because escalation ownership is unclear. A distribution agreement can be signed while operational data still cannot reach the people who need to act on it.
Replace “percent complete” with a decision view
A leadership team does not need another meeting where every workstream reports 80% complete. It needs an honest view of what is true and what is not yet known.
For every material launch decision, I would want to see the decision owner, the evidence being used, the confidence in that evidence, the assumptions that could change the answer, the dependent workstreams, the next decision date, and the consequence of delay.
This is also where AI requires discipline. AI can organize evidence, compare inputs, surface gaps, and show contradictions. It should not manufacture confidence or silently convert an uncertain recommendation into a completed decision. Consequential choices still need accountable human approval.
- Run an “approval came 60 days early” exercise and identify the five decisions that break first.
- Run the opposite exercise: if approval moves, which commitments should pause and which should continue?
- Define commercial hard gates before workstream owners begin reporting against them.
- Assign one manufacturer-side owner to every dependency that crosses vendors or functions.
- Record “evidence insufficient” as a legitimate status, with a next action—not as an embarrassment to hide.
The philosophy behind LaunchOS
LaunchOS is grounded in a simple belief: launch leadership should be able to see what decision is required, why it matters now, what evidence supports it, and what happens if the team waits. It supports experienced operators and accountable leaders rather than attempting to replace their judgment or the systems a manufacturer already uses.
The intended role is a manufacturer-side decision layer: configurable methodology, evidence-aware AI, explicit rules, and scoped expert judgment working together. When the system does not know enough, it should say so—and help the team get the right human expertise into the decision.
A launch plan tells you what everyone intends to do. A launch operating system tells leadership what is true, what is uncertain, and which decision cannot wait. If your team is preparing for a first U.S. launch, start with the decisions—not the dashboard.
Research and sources
- 1.Novel Drug Approvals for 2025
U.S. Food and Drug Administration
- 2.First-time launchers in the pharmaceutical industry
McKinsey & Company · Analysis includes launches from 2014–2017.
- 3.Importing Human Drugs
U.S. Food and Drug Administration
- 4.FDA Announces Expanded Use of Unannounced Inspections at Foreign Manufacturing Facilities
U.S. Food and Drug Administration