Expanding self-serve PLG to a new country
Say a self-serve SaaS company with a freemium tier decides Europe is next. The instinct is almost always the same: translate the site, maybe the product too, then start running ads in the new language. Nine times out of ten, that's the wrong first move. Not because translation doesn't matter, but because it answers a question nobody asked yet: does this market actually want what's being sold.
Start with a question translation can't answer
Deciding to expand a sales-led motion into a new market usually starts from zero: market sizing, competitive research, outbound lists built from nothing, because there's no user yet to look at. A self-serve product doesn't have that problem in the same way. If it's been live and findable for a while, there's often already a trickle of signups or downloads from that country. People found it and started using it before anyone targeted that market on purpose. That's a demand signal a sales-led motion doesn't get for free.
The sign that a market is worth translating for isn't excitement in a strategy meeting. It's existing demand: traffic already coming from that country, a sign-up rate that holds up without any local push, support tickets or competitor searches that show someone already looked. Translate ahead of that signal and a company ends up with five language versions of a page nobody reads in any of them.
It's the same blind spot as judging a whole funnel by one number instead of its segments, covered in marketing and sales funnel misalignment. Country is just another segment. Funnelsight filters an existing funnel view by country the same way it already filters by channel or persona, using the activation event already defined for the rest of the product. No new setup for a new market, just a different filter. A few hundred signups, even pulled from a spreadsheet export, is enough to see whether activation and conversion hold up against the existing baseline.
What actually blocks the product, not the page
Assume the demand is real. The next question isn't about copy, it's about data and law. GDPR applies the moment a company touches EU user data, regardless of where that company is incorporated. Germany goes further: a strong expectation, and in regulated sectors a legal requirement, that data stays within its borders. A product without multi-region infrastructure can't promise that and sort it out later.
The UK breaks the "Europe is one market" assumption too. Post-Brexit, UK VAT runs on its own registration threshold, separate from the EU's. Solving VAT for the EU doesn't solve it for the UK. None of this is about language. It's about whether the product can legally and technically operate there at all, and that has to be settled before a single page gets translated.
A self-serve product can often reach a market like that at close to no marginal cost: nothing new to build, nothing new to translate. It just needs two things already in place: data protection rules close enough to the ones the product already meets, and an audience where English converts, even when it isn't the first language. The moment a market doesn't share those conditions, self-serve runs into the same questions a sales-led motion already has answers for, built market by market with a team on the ground from the start.
Payment decides conversion before language does
A self-serve product lives or dies on how easy it is to pay for. Translate the page while checkout still runs on one currency and a short list of payment methods, and the part fixed is the one a buyer reads last, not the one that decides whether they finish. Stripe has reported meaningfully higher conversion in markets where local payment methods were switched on. For a self-serve motion specifically, that matters more than it would with a sales team: there's no one in the loop to paper over a clunky checkout.
Currency is the deeper choice. Bill in local currency where conversion is price-sensitive, hold a single currency where it barely moves the decision. Either way, it should be a deliberate call, not whatever happened to be configured when the first customer in that currency signed up.
Buying habits don't translate either
Even with infrastructure and payments sorted, how a market buys can still break a motion built for English-speaking, credit-card-first customers. German public-sector and enterprise buyers, in particular, often require contracting through a locally registered entity before anything gets signed, no matter how good the self-serve trial was. A local reseller relationship can still be the fastest way into a market like that, even for a product the company would rather sell directly.
See your funnel broken down by country, channel and segment, without waiting on a data team.
Start free trialDoes this mean translation never matters?
No. It means translation earns its place after demand, infrastructure and payment are already sorted, not before. Once those hold up, translating the product is often the fast, almost boring part, especially for a site and product that weren't built with language hardcoded into them anywhere. Skipping straight to translation is the mistake, not translation itself.
Should I expect the same conversion rate in every market?
No, and that's not a red flag by itself. Payment habits, buying culture and plain regulatory friction move the number up or down without the product being at fault. Compare a new market to its own numbers over time. Forcing it to match an unrelated baseline on day one just produces a bad decision dressed up as data.