Use case · "I want to expand to another EU country."
Expanding to another EU country: why "close" is not "the same"
For wellness and preventive health startups working in France, Germany, Sweden or any EU country, looking at the neighbour next door. The border is open; the market is not.
The trap of the neighbouring market
Expanding from France to Belgium, from Germany to Austria, from Sweden to Denmark looks like the safe first step: same currency or nearly, same regulation, often the same language. The product goes live with a translated store listing and a local payment method, and six months later usage is a fraction of home. Nothing broke. The product simply did not fit how people there look after their health.
The closer a market looks, the less founders test it, and the more surprised they are. Habits around sleep, food, movement and mental health are shaped locally: by the healthcare system, by who pays, by what is considered normal to talk about. None of that is visible from the capital next door.
What usually goes wrong
- The product travels, the trigger doesn't. The moment someone opens a wellness app (after a doctor's visit, a work programme, a friend's recommendation) differs by country. Same product, missing trigger, no usage.
- The payer changes. Out of pocket in one country, employer-funded in the next, insurer-reimbursed in a third. A pricing page that worked at home can be simply irrelevant across the border.
- Hiring before knowing. A country manager is recruited to "open" the market, and spends the first year discovering what a test would have shown in eight weeks.
- Translating everything. Full localisation before validation is the single most common waste in intra-EU expansion. Test with light localisation first; translate what the test proves worth translating.
What a test looks like for this case
Usually a single-country test: one neighbour, eight weeks, a go / no-go. If you hesitate between two or three neighbours, a comparison on the same calendar costs little more and answers the better question.
Scope (week 1)
A one-page plan: the country, the user profile (the same as at home, or deliberately different), the usage hours, and the threshold for a go. Here the threshold is often "retention at week 6 within X% of home", which gives you a direct read on how much the product travels.
Recruit (weeks 2–3)
At least 20 targeted users in the target country, outside your network, matched to your profile. You get the panel's make-up, never identities.
Run (8 weeks)
Users use your product as it is, or with the minimal localisation you can ship now. Weekly readout; we keep the panel engaged until the contracted hours are delivered.
Decide (final week)
A report: usage over eight weeks compared with your home benchmark, what people said, and a reading: go, adjust (with the list of what to adapt) or stop. Then a call.
What you walk away with
A decision on the neighbour, made before the hire and before the translation budget. If it is a go, you also have the adaptation list and a retention benchmark your future country manager can be measured against. If it is a stop, you have saved a year, and you know which country to test next.
Six questions before you commit. The expansion risk check takes two minutes and shows what you don't know yet about the market next door.
Looking at the country next door?
Book a 30-minute call. Bring the country and your home retention numbers; we'll tell you what a test would need to show for the move to make sense.
Questions founders ask about intra-EU expansion
Do I need to localise the product before the test?
Only lightly: enough that testers can use it. The test tells you what full localisation is worth. Testing a fully localised product first means paying for the translation of features the market may reject.
GDPR applies in both countries. Does anything change for data?
The law is the same; the practice is not always. Health data remains a special category everywhere in the EU, so explicit consent, pseudonymisation and a processing agreement apply to any test, and the tester information is written in the local language.
Can I test two neighbours at the same time?
Yes. Two or three countries on the same scorecard and the same eight weeks is often the better design, because it turns "is Belgium a go" into "Belgium or the Netherlands first", which is the decision you actually face.