Launch Starts Before Launch

A launch is rarely won in the final six months. By then, many of the decisions that shape its potential have already been made.

For emerging biotech companies especially, approval can feel like the starting line for commercialization. In reality, the commercial runway begins much earlier—often 12 to 24 months before the expected launch.

That is when an organization is still creating options. Each delayed decision narrows them.

The Signal

Launch planning is often organized around a countdown: strategy at one milestone, infrastructure at another, field deployment closer to approval and execution once the clock reaches zero.

The timeline can create the appearance of progress while masking a more important question: is the organization making the consequential decisions early enough to learn, adapt and align?

Segmentation, evidence, positioning, access, customer experience, field design, data, technology and partner choices are deeply connected. When they are made sequentially or in isolation, downstream teams inherit assumptions they had little role in shaping—and little time to correct.

Why It Matters

Late commercial decisions do more than compress a workplan. They reduce strategic choice.

A weak understanding of the market creates fragile positioning. Unresolved access assumptions distort forecasts and field plans. A customer model built too late turns segmentation into a list rather than a decision system. Technology selected before workflows are clear introduces complexity at the moment teams need focus.

These risks are magnified in emerging organizations, where the same leaders may be building the company, preparing the asset and selecting an ecosystem of external partners at the same time.

The goal is not to predict every detail earlier. It is to identify the decisions that become expensive—or impossible—to revisit later.

The Curbside View

A practical pre-launch model follows four stages: Understand, Decide, Prepare and Activate.

Understand the market. Build a fact base around patient flow, customer behavior, unmet need, access dynamics, competitive alternatives and the decisions that will drive adoption.

Decide what must be true. Make explicit choices about priority customers, positioning, evidence, experience and the capabilities the launch requires. Separate true strategic decisions from assumptions that still need to be tested.

Prepare the organization. Translate the strategy into an operating model: people, partners, processes, data, technology, governance and decision rights. Build around the work rather than around a collection of functions or vendors.

Activate through rehearsal. Test the handoffs, decisions and customer journeys before launch. Readiness is demonstrated when the system works together—not when every function reports that its checklist is complete.

The Move

Create a pre-launch decision map, not just another workstream tracker.

For each consequential decision, name the owner, the evidence required, the assumptions still being tested and the date after which changing course becomes materially harder. Then connect those decisions across functions so leaders can see where one unresolved choice is constraining several others.

Review the map as a leadership team. Focus the conversation on the decisions that preserve optionality, not merely the tasks that demonstrate activity.

The strongest launch organizations do not eliminate uncertainty. They make uncertainty visible early enough to act on it.

One Question to Take With You

That is where launch readiness should begin.