Use case
Launching in a new European market
The product travels. The website, the checkout, the consent banner and the email programme generally do not.
The situation
A business that works in one European market decides to enter another. The instinct is to translate the site, add a currency and start advertising. The instinct is wrong often enough to be expensive, and the reasons are rarely obvious from the outside.
Europe is not a single market operationally. Consent rules, payment habits, invoicing obligations, accessibility deadlines and search behaviour all differ by country, and several of them differ in ways that break a system rather than merely reducing its performance.
The failures follow a pattern. Conversion is weak and gets blamed on brand awareness when the cause is a missing payment method. An email programme that was compliant at home creates real exposure. An invoice cannot be issued because the country requires a national e-invoicing platform nobody scoped for.
How it shows up
- Conversion in the new market is far below the home market with no obvious cause.
- You are mailing contacts under the home market’s consent assumptions.
- The checkout offers cards and nothing else.
- Local-language content is translated from English and ranks for nothing.
- Invoices to local businesses are being rejected or queried.
- The language switcher produces 404s on untranslated pages.
Symptom, cause and change
The most expensive mistake in this situation is treating a symptom as a diagnosis. These are the three columns kept apart.
Why it happens
- Payment habit divergence
- iDEAL, Bancontact, BLIK, MobilePay, Swish, Multibanco and others dominate their markets. A card-only checkout underperforms in each and the cause is invisible from a funnel report.
- Consent regime divergence
- Germany requires prior consent for B2B email; the Netherlands permits opt-out to legal entities. One list under one assumption is exposure.
- Mandatory e-invoicing
- Italy, Romania, Hungary, France and others operate national platforms or reporting obligations. A PDF invoice does not satisfy them.
- Translated rather than native content
- Keyword research does not survive translation, particularly in inflected and compound-forming languages. Translated pages rank for terms nobody searches.
- Hreflang implemented carelessly
- A switcher that prefixes a locale to the current path 404s on every untranslated page, and crawlers follow those links.
How we approach it
Establish what actually differs
Before anything is built: the consent regime, the payment methods, the invoicing obligations, the accessibility position and the language requirement for that specific country. This is a short piece of work that prevents most of the expensive surprises.
Fix the checkout for the market
Local payment methods, correct VAT handling and local address formats. This is frequently the single largest conversion factor and the one most often diagnosed last.
Build the locale properly
A genuinely separate locale with correct hreflang, self-references and reciprocation — and a language switcher that renders disabled rather than linking to a page that does not exist.
Commission native content
Keyword research conducted in the target language and content written natively. Translated commercial copy underperforms consistently and is identifiable to native readers.
Rebuild the consent and email position
Consent provenance recorded per contact for the new jurisdiction, with suppression enforced. A list cannot simply be extended across a border.
Handle invoicing before the first sale
Where the market mandates structured e-invoicing or transaction reporting, the integration has to exist before you transact, not after the first invoice is rejected.
What changes
- Checkout that converts locally
- The payment methods that market actually uses, which frequently resolves a conversion gap attributed to brand.
- A locale that ranks
- Native content built on native keyword research rather than translation.
- Hreflang that does not 404
- Alternates declared only for pages that exist, with a switcher that behaves accordingly.
- A defensible email position
- Consent recorded per contact per jurisdiction rather than inherited from the home market.
- Invoices that are accepted
- National e-invoicing or reporting obligations handled before the first transaction.
- A realistic view of the opportunity
- Including, occasionally, that the market is not worth entering yet.
Where it goes wrong
The most expensive pattern is diagnosing a payment problem as a marketing problem. Conversion is weak, so the response is more spend and new creative, and months pass before anyone notices the checkout offers only cards in a market where most people pay another way.
The second is extending the email list across the border. A programme that is entirely lawful in the Netherlands can be non-compliant in Germany, and a list built under United States assumptions is generally unlawful to mail into the EU at all.
The third is machine translation. It is identifiable to native readers, it damages credibility more than it saves in fees, and it produces content targeting keywords that do not correspond to how anyone searches in that language.
A fourth is discovering e-invoicing obligations after launch. Italy, Romania and Hungary in particular operate systems where a conventional invoice simply cannot be issued, and retrofitting the integration under commercial pressure is far more expensive than scoping it.
A fifth is the hreflang and switcher combination. Declaring alternates for pages that do not exist, or building a switcher that blindly prefixes a locale, produces 404s that crawlers follow and index.
Finally, entering too many markets at once. Each one carries its own consent, payment, language and invoicing work, and doing three simultaneously usually means doing none of them properly.
A further failure is treating the first market entry as a template for the next. Each country differs enough on consent, payment, invoicing and language that the reusable part is the process rather than the artefacts, and clients who expect the second entry to be trivial are consistently disappointed.
Finally, support and fulfilment are frequently forgotten. Selling into a market creates customers in it, with expectations about response times, language and returns that a home-market operation is not set up to meet.
What else you could do instead
Full localisation is not the only option, and for some businesses one of these is the better commercial answer.
- Sell cross-border without localising
- Viable in English-tolerant markets — the Netherlands, the Nordics, Ireland — for B2B specifically. It caps the opportunity and it costs almost nothing to try first.
- Localise the checkout only
- Local payment methods and correct VAT without a full content locale. Frequently captures most of the available conversion gain for a fraction of the cost.
- Use a marketplace or partner
- Entering through an established local marketplace or distributor avoids the compliance and language work entirely, at the cost of margin and customer relationship.
- Pick a different market
- If the obligations in one country are disproportionate to the opportunity, a neighbouring market may deliver the same growth with far less work. We will say so when that is the case.
How we would know it worked
The baseline that matters is the home market’s conversion rate by device and traffic source, captured before entry, because the honest question is how far the new market falls short of it and why. Without that comparison, a weak number in a new market is uninterpretable.
After launch we track conversion rate, payment method mix and cost per qualified opportunity in the new market separately, never blended with the home market. Blended reporting hides exactly the divergence the exercise is meant to detect.
Search performance is read from Search Console filtered to the country, and we would rather report at ninety days that a locale is not gaining traction than at thirty days that impressions are rising. Impressions in a new locale rise for reasons that have nothing to do with commercial progress.
How long it takes and what it costs
A checkout-only localisation is typically three to five weeks. A full locale with native content, consent rebuild and e-invoicing integration is more commonly ten to sixteen weeks, with content production and translation scheduling driving most of the variance.
Search results in a new locale are slow. Six to twelve months to a meaningful position is realistic in most competitive European markets, and considerably faster in smaller markets where competition for local-language terms is low.
Cost is quoted per market and per phase after a scoping call, because the obligations differ enough between countries that a single figure across Europe would be meaningless.
Estimates are labelled as estimates. Timelines here are planning ranges from comparable work, not commitments, and not measured client outcomes. We quote against a defined scope after a discovery call.
Services involved
Website Design & Development
Sites built to convert and to survive — fast, accessible, integrated with your CRM, and maintainable by someone other than us.
Read more →Search Engine Optimisation
Getting found for the things people actually search — technical foundations first, then structure, then content that deserves the position.
Read more →Systems Integration
Making the systems you already pay for talk to each other, reliably, without a person in the middle re-typing things.
Read more →Email, SMS & WhatsApp Marketing
The channels you own outright — where the list is yours, delivery is not rented from an algorithm, and automation does the follow-up nobody has time for.
Read more →Digital Marketing
The layer above the channels: what the funnel is, which campaigns run, what each is meant to produce, and whether it did.
Read more →Content Creation & Creative Production
The production line behind everything else — the graphics, video, photography and copy that campaigns, channels and sales teams all consume.
Read more →Questions
Can we just translate our site?
You can, and it usually underperforms. Keyword research does not survive translation, native readers identify translated commercial copy, and translation does nothing about payment methods, consent or invoicing obligations — which are frequently the larger problems.
Which market should we enter first?
Usually the one with the lowest operational friction relative to the opportunity. English-tolerant markets with straightforward obligations are cheaper first steps than large markets with heavy language and invoicing requirements.
Do we need local payment methods?
In most European markets, yes, and it is the single most commonly missed factor. Card-only checkouts underperform materially in the Netherlands, Belgium, Poland, Denmark, Sweden and Portugal among others.
Can we use our existing email list in the new market?
Not without checking the consent position for that jurisdiction. Rules differ substantially — Germany requires prior consent for B2B email where the Netherlands permits opt-out to legal entities — and extending a list across a border is a common exposure.
What is the risk with hreflang?
Declaring alternates for pages that do not exist, and language switchers that prefix a locale to the current path and 404 on untranslated pages. Crawlers follow those links, and it is entirely avoidable.
How many markets can we enter at once?
One properly, usually. Each carries its own consent, payment, language and invoicing work, and three simultaneously generally means three done badly.
What does it cost?
Quoted per market and per phase after a scoping call. A single European figure would be meaningless because the obligations differ so much between countries.
How long before it produces revenue?
Paid channels can produce enquiries within weeks of a working localised checkout. Organic search in a new locale is six to twelve months in competitive markets and faster in smaller ones.
Will you tell us not to enter a market?
Yes, when the obligations are disproportionate to the opportunity or a neighbouring market would deliver the same growth for less work. It has happened and it is a legitimate outcome of the scoping phase.
What if this is not the right piece of work for us?
Then we say so, and it is a common enough outcome that it is worth stating plainly rather than treating as an awkward exception. The most useful thing a first conversation produces is frequently a recommendation to do something smaller, something different, or nothing at all.
Other situations
- Replacing spreadsheets with a real system
- Cutting cost per qualified lead
- Making company knowledge searchable
- Automating quote to invoice
- Recovering from a failed migration
- Inheriting undocumented software
- Passing a customer security review
- Merging systems after an acquisition
- Opening a second location
Recognise this?
Tell us what it looks like in your business. We will tell you what we would do about it, and whether it is worth doing.
Get in touch