How Do You Know If You're Ready to Fix the 90%?

The problem isn't deciding to invest. It's knowing where to start.

By now, the argument is familiar to most commercial leaders. Patients don't fall off therapy at enrollment. They fall off in the 90% of the journey that happens between visits — the long middle where most support budgets don't reach, and where persistence is quietly won or lost.

Accepting that is the easy part. Acting on it is where teams stall.

The leader who believes the 90% matters still has to answer a harder question before spending a dollar: where, specifically, is our infrastructure failing — and which gap, if we closed it, would change the most?

Most teams cannot answer that. Not because they lack effort, but because the honest starting point feels like everywhere at once.

Why "just start somewhere" fails

The instinct, once a team accepts the problem, is to move. Stand up a new program. Add a nurse line. Fund a copay expansion. Buy a vendor solution that promises to close the gap.

The trouble is that action without a baseline is indistinguishable from guessing. You can invest real money into the part of the journey that was already working, while the actual leak — two functions over, in a handoff nobody owns — keeps draining patients. The program looks like progress. The persistence numbers don't move. And because nobody measured the starting point, nobody can say why.

Starting in the wrong place is not a small inefficiency. It burns the budget and the credibility you need to make the case for the next investment.

What "ready" actually means

A team that is ready to fix the 90% has three things, and none of them is enthusiasm.

A baseline. A clear, scored picture of where the infrastructure stands today — before anything is built — so that six months from now you can prove whether it worked. Without a baseline, every future claim of improvement is an assertion, not evidence.

A prioritized map, not a list. Knowing your gaps is not enough. You need them ranked by impact — which failure point is costing the most persistence, and therefore the most revenue. A list of twelve problems paralyzes a team. A ranked map of which three matter most lets it move.

Cross-functional agreement on the starting point. Because persistence leaks in the handoffs between functions, no single function can fix it alone — and no single function can even see the whole picture. Readiness means patient services, market access, field, and marketing are looking at the same map and agree on where to begin. Absent that, each function optimizes its own piece and the handoffs stay broken.

If a team has those three things, it is ready. If it doesn't, the first investment is not a program. It's a diagnostic.

The starting instrument

This is the specific problem the Gap Finder, our patent-pending diagnostic, was built to solve: to give a team its starting line.

It maps the patient journey and scores infrastructure readiness across the full 90% — with the cross-functional team in the room, not in separate interviews. It produces a baseline you can measure against later, a ranked view of where persistence is leaking most, and a single shared picture that every function has agreed to. What a team walks away with is not a report that sits on a shelf. It is the answer to "where do we start" — in evidence, before the first dollar is spent.

The point is not to measure for its own sake. It's that measurement is what turns a belief that the 90% matters into a plan a board will fund.

Back to the question

So: are you ready?

If your team can already name, with evidence, the single highest-impact gap in your patient infrastructure — and every function agrees — then you're ready to build, and you should.

If it can't, that's not a failure. It's the most useful thing to know before the budget cycle. Because the teams that waste the least are not the ones that move first.

They're the ones that know where to start.

Linked Patient Learning helps pharma teams find their starting line — where persistence is leaking, what it's costing, and what to build first.