Most Launch Infrastructure Is Built on Assumptions. Here's the Cost.

The earlier you measure, the more you can influence. By launch, the decisions are already made.

Eighteen months before a launch, a team sits down to design the patient support infrastructure. Hub model. Specialty pharmacy strategy. Patient services. Adherence programs. Field coordination.

And most of what gets decided in that room is a guess.

Not a careless guess. An informed one — built on competitive benchmarks, on what worked for the last launch, on the experience in the room, on the loudest confident voice. But a guess all the same, because nobody has evidence for where this therapy's patients will actually struggle. So the team builds for the problems it assumes, funds the programs it believes matter, and hopes the assumptions hold.

They rarely do. And by the time the gaps show up in the persistence data, the infrastructure is built, the budget is committed, and the window to influence the outcome has closed.

Assumptions don't just risk being wrong — they tell you to measure the wrong things

Here's the part that gets missed. The real cost of building on assumptions isn't only that you might build the wrong programs. It's that assumptions decide what you measure — and measuring the wrong things is how a team stays blind while believing it can see.

If you assume the risk is in initiation, you instrument initiation. You track enrollment, time-to-first-fill, activation. The dashboard fills with those numbers, they look healthy, and everyone relaxes — while persistence quietly erodes in the part of the journey nobody thought to measure, because nobody's assumptions pointed there.

You cannot influence what you do not measure. And you do not measure what your assumptions told you didn't matter. That is the trap: the launch that fails on persistence usually had a green dashboard the whole way down, because it was measuring exactly the things its assumptions predicted, and none of the things that actually determined the outcome.

Evidence does something assumptions can't: it tells you where to look

Replacing assumptions with evidence at the launch-planning stage does two things, and the second is the one that matters most.

It tells you where this therapy's patients are actually likely to fall through — not where the last launch's patients did, not where the benchmark says, but where your journey, your handoffs, your access dynamics create the friction.

And then it tells you what to measure. Because once you know where the persistence risk actually sits, you know which metrics will show you whether you're influencing it. The measurements stop being generic launch KPIs and start being the specific signals that tell you if the infrastructure is doing its job — early enough to change it.

That is the difference between measuring to report and measuring to influence. Assumptions give you the first. Only evidence gives you the second.

Why the timing is everything

There is a reason this has to happen early, and it is not a preference — it is a constraint.

The ability to influence a launch outcome decays with time. Eighteen months out, everything is still movable: the hub design, the vendor selection, the resource allocation, the cross-functional plan. Six months out, most of it is locked. At launch, you are no longer designing — you are watching. Every month closer to launch converts decisions you could have made into realities you have to live with.

So the evidence has to arrive while the decisions are still open. Measuring at launch tells you what went wrong. Measuring eighteen months out tells you what to build. The first is an autopsy. The second is a plan.

This is also why a single assessment isn't enough. Assumptions creep back in as teams build in silos — marketing to its plan, patient services to its own, hub ops to theirs. Evidence has to be renewed across the pre-launch phases to keep the whole team aligned to the same reality, so that when leadership asks "why are we investing here," the answer is a scored diagnostic, not a confident opinion.

The instrument for this

This is precisely what the Gap Finder, our patent-pending diagnostic, was built to do at the launch-planning stage.

It maps the patient journey and scores infrastructure readiness across the full 90% — with the cross-functional team in the room — early enough that the findings can still change the build. It replaces the assumptions in that eighteen-months-out planning room with an evidence baseline: here is where this therapy's persistence risk actually sits, here is what to measure to track it, here is which gap to close first. And because it is re-run across the pre-launch phases, it keeps the team measuring against reality as the build progresses — not drifting back into the assumptions each function brought with it.

The point is not to measure for its own sake. It is that evidence, arriving early, is the only thing that lets a team influence a launch outcome instead of merely reporting on it.

The question worth asking eighteen months out

Before the next launch infrastructure is designed, there is one question worth putting to the team:

The programs we're about to fund — do we have evidence they address where this therapy's patients will actually struggle? Or are we building for the problems we assume, and hoping we assumed right?

If the honest answer is the second, the first investment isn't a program.

It's finding out.

Linked Patient Learning helps pharma teams replace launch assumptions with evidence — where persistence risk actually sits, what to measure, and what to build first.