Main idea

"We already have the software translated into Portuguese, so we can go after Brazil." The sentence assumes a market is the same market in another language, and that translation lifts the only obstacle left.

It confuses two layers. Language, currency, taxes and customer support form the visible layer: it is handled by a localization project, with a budget and an end date. Underneath sits an infrastructure of usage — how people pay, whom they trust, which identifiers they present, which platforms are part of their lives, which risks they work around. That layer doesn't translate: it is encountered.

A payroll system, a commerce site, a subscription tool translated into Portuguese land in Brazil in a country where credit is built into the act of buying, where a tax ID number is asked for over a coffee, where the central bank's instant transfer serves the beach vendor and the doctor alike. The words are right and the product stays foreign.

Why it matters

This shifts the question of market entry. "Is it translated?" has a binary, reassuring answer; "which infrastructure of usage does our product plug into here?" forces you to go and look.

And it gives an exposure criterion: a product that touches payment, identity, customer data, delivery, trust or credit is in direct contact with that layer. A product that doesn't touch it can get away with translation — which is what makes the illusion durable, because it has sometimes worked.

Nuances and limits

Translation remains necessary: it isn't a useless step, it is an insufficient one. Nothing in this note says you can skip it.

And the gap isn't the same size everywhere: two neighbouring countries sharing currency, regulation and banking habits leave little room for that layer. It is between distant economic zones that it becomes decisive.

Open questions

• Which signals, observable before investing, indicate that a product touches a country's infrastructure of usage rather than only its surface?