It is eleven o'clock on a Tuesday morning and somewhere in your organisation someone has just opened a blank document for the third new market this year.
Registration tab, localisation tab, messaging tab, all empty.
They will fill them in from nothing, more or less exactly as they did for the last market, and the one before that. Nobody told them what worked last time. Nobody wrote it down. The person who built the last launch plan left for a competitor eight months ago, and their laptop went back to IT with everything still on it.
Three blank tabs. The fourth market this year that starts the same way. And at some point in the kickoff call, someone will use the word bespoke.
This piece is about that word. What genuinely needs rebuilding when you enter a new healthcare market, and what doesn't. What's actually happening inside a launch team right now that's running two markets at once off a single plan. And what changes when a company finally stops rebuilding the parts that were never the problem.
The blank tab is not proof of difference.
First, the obvious pushback. Healthcare markets really are different from each other. Different regulator, different reimbursement pathway, different buying behaviour, sometimes a different language on every claim you make. Nobody is arguing the German notified-body process and the UK route to market are the same thing. They plainly aren't.
(A colleague once tried to argue otherwise to a room full of regulatory affairs leads. It did not go well.)
But the claim here isn't that markets are identical. It's that most of what a launch team rebuilds from nothing, every single time, was never actually the local part.
The plan everyone builds anyway
Here's what most healthcare companies do when a new market opens up, and it's worth saying clearly that this isn't a stupid response. It's the obvious one.
A new market lead gets appointed, or an existing commercial lead picks up the extra territory. They start from the beginning. Stakeholder map, built from scratch, usually from memory and a few calls to people who've worked in the market before. Message hierarchy, drafted fresh, because the old one lived in a slide deck nobody can find. Proof sequence, rebuilt because the last version was tailored so tightly to the previous market it doesn't obviously transfer. Localisation brief, written new, because it always is.
Every one of those steps takes real time. The registration pathway alone, on a typical launch, runs to around eleven weeks before anything else can start moving properly. And that's before the local claims review, before the messaging gets adapted, before a single piece of content is genuinely ready for the market it's landing in.
Called bespoke, this feels rigorous. It feels like the company is taking the new market seriously, respecting its differences rather than lazily copying a UK plan onto a German market and hoping nobody notices.
Bespoke feels rigorous. It is usually just unbuilt.
It also has a quieter benefit nobody says out loud in the kickoff call. If every launch is bespoke, nobody can be blamed when the plan underperforms, because no plan repeats for long enough to be judged against the last one. Convenient, that.
Multiply this across a portfolio and the cost stops being one team's inefficiency and starts being a structural drag on how fast the whole company can move. A company launching in four markets a year isn't running four launches. It's running the same launch four times, badly, with the learning thrown away at the end of each one.
Why the tidy plan still misses forecast
Here's the uncomfortable number. 73% of healthcare launches miss commercial forecast. Not by a rounding error. By enough that someone, somewhere, is explaining to a board why the numbers don't match the business case that got the launch funded in the first place.
It's not that the people running these launches are bad at their jobs. Most of them are good at their jobs, working long hours, doing everything the plan asks of them. It's that the plan gets rebuilt from nothing, market by market, with no institutional memory of what actually worked last time.
Think about what that means in practice. Every new market, the team relearns which stakeholders matter first, in what order, and why. The proof points that land and the ones that don't get re-derived from scratch, usually by trial and error over the first two quarters. And the messaging architecture is redrafted almost from nothing each time, because the previous version is buried in a folder structure that changed hands twice.
No memory, no system, no repeat performance.
That's the pattern underneath the 73% figure. Not bad products, not bad people, absence of architecture. A launch plan without memory behaves exactly like a new hire on their first day, competent and well intentioned, and starting from zero regardless of how many times the company has done this before.
What's actually different this time
What if the market isn't actually where the differences concentrate? What if most of a launch plan, the parts that take the longest to build and matter most to whether it lands, are the same wherever you launch?
The messaging architecture, the way the value proposition is structured and which proof points support which claims, doesn't change because you crossed a border. The content library, the assets that bring the messaging to life, largely doesn't change either. The proof sequence, the order in which you introduce evidence to a sceptical stakeholder, is shaped by how healthcare decisions get made, not by which country you're standing in.
You start to wonder whether the problem was ever the market at all, or the habit of assuming it must be.
The spine travels. Only the skin is local.
What genuinely is local, and needs to be built fresh every time, is narrower than most launch plans treat it as. The specific regulatory pathway. What a claim needs to look like to clear a particular regulator's bar. The precise wording that satisfies one country's advertising code but would trip up in another's. That's it, really. Everything else is the same spine, wearing different local skin.
This isn't a theory. It's happening this week, on a live account, which is the part of this piece worth remembering after the rest of it fades.
Two countries, one desk
A mid-sized patient marketing client of ours is currently building two country registration packs at the same time. Same product, two new European markets, one UK-style regulator and one German-style regulator, running in parallel on the same desk.
The conventional approach, the one this same client had used on every previous launch, was to run country entries sequentially. Each new market got its own build, starting from a blank stakeholder map and a blank messaging document, with the registration pathway alone typically taking around eleven weeks before anything downstream could properly begin.
The shift this time was structural, not cosmetic. One messaging architecture, a single content library, the same proof sequence, used twice. Two claims trackers running against two different regulators, tracking exactly what's local and nothing more, both moving off the same shared spine.
The measurable result is the plainest one there is. These two markets are moving through registration at the same time, in the same week, rather than one after the other. What would previously have been two sequential eleven-week builds, roughly twenty-two weeks of calendar time end to end, is now running as one build with two local tracks inside it.
"The project plan looks suspiciously tidy for something this complicated."
That was the reaction in the review call. Fair point. I keep checking it for the catch. Haven't found one yet.
What to do before your next market
If your next market entry is sitting on someone's desk as a blank document right now, here's the direction, not a step-by-step manual.
Before anyone rebuilds a stakeholder map from scratch, go and find the last one. It almost certainly exists somewhere, half-finished, in someone's old files. Extract what's genuinely reusable, the sequence of stakeholder types, the proof points that worked, the objections that came up more than once.
Separate the plan into two piles honestly.
- What's local, meaning it genuinely changes with the regulator, the language, or the reimbursement pathway.
- What's structural, meaning it would work the same way in any market you're likely to enter next.
Build the structural pile once, properly, as something reusable rather than something bespoke to this launch. Then let every future market plug its local pile in against that same spine.
Build the architecture once, localise the claim.
None of this happens by accident, to be fair. Someone has to sit down and do the unglamorous work of separating structural from local, once, properly. That's an afternoon nobody enjoys.
(Still working on getting better at doing this early, rather than after the third launch, if I'm honest.)
It saves every afternoon after it.
The stakes underneath the spreadsheet
None of this is really about spreadsheets, or registration trackers, or claims matrices, even though that's the visible layer.
It's about how quickly a genuinely useful healthcare product reaches the people who need it. Every week spent rebuilding a launch plan from nothing is a week a clinician somewhere doesn't know a better option exists, and a patient doesn't get offered it.
Eleven weeks doesn't sound like much on a project plan. It's eleven weeks a patient in that second market waited for something that was already sitting, finished, in the first one.
The market was never the variable. The system was.
Download the Repeatable Launch Checklist, a one-page split you can run with your own launch team tomorrow. No email required.
What next?