7 Languages, 4 Continents, 18 Products: Lessons from Building Globally

I speak French, Arabic, Italian, Spanish, English, Portuguese, and some Dutch. I've lived in Belgium, Italy, Mexico, and the United States. I've built products used in 120+ countries.

None of that makes me special. What it makes me is someone who's been wrong about cultural assumptions enough times to learn the lesson.

This article is about what building globally actually means, not the inspirational version, but the practical one. The payment systems that don't work. The product decisions that make sense in one country and fail in another. The communication patterns that change everything.

Language Is Not Localization

The first mistake every product builder makes when "going global" is translating the UI.

You take your English strings, send them to a translation service, and ship a "French version" or a "Spanish version." Done. Global product.

Except it's not. Translation changes the words. Localization changes the product.

When I built Aviation Infinity for EASA markets (Europe), the product wasn't a translated version of the FAA product. The exam structure is different. The subject weighting is different. The terminology is different. A question about "VFR minima" uses different altitude references in EASA versus FAA airspace. Translating the question from English to Italian wouldn't help. The content itself had to change.

When I built Babonbo for the Italian market, the booking flow needed to account for the fact that Italian parents communicate differently than American parents. Italians prefer WhatsApp messages to in-app chat. They expect more personal interaction before a booking. The "instant book" pattern that works in the US felt impersonal in Italy.

When I built Comensalaqui in Tijuana, the entire payment infrastructure had to change. Many users didn't have credit cards. Cash on delivery wasn't just an option. It was the primary payment method. The "enter your card number" checkout flow that every US product takes for granted was a dead end.

Localization means understanding how people in a specific market actually behave, not just what language they speak.

What Speaking 7 Languages Actually Teaches You

People assume multilingualism is about communication, being able to talk to more people. That's true but superficial.

What multilingualism actually teaches you is that different languages encode different assumptions about the world.

In Arabic, the default greeting is about peace: "as-salamu alaykum." In Italian, it's about how you're doing: "come stai?" In French, it's formal by default. "Bonjour" maintains a distance that "hey" in English doesn't. These aren't just words. They reflect different social contracts about formality, respect, and the relationship between strangers.

When you build products, these assumptions surface everywhere:

Form design. In the US, "First Name, Last Name" is standard. In many Arabic-speaking countries, people have multiple names that don't fit the Western first/last model. In Spain, people use two surnames. A name field that assumes Western naming conventions breaks for a large portion of the world.

Date and time. Americans use MM/DD/YYYY. Most of Europe uses DD/MM/YYYY. Some Asian countries use YYYY/MM/DD. This isn't a display preference. It's a cognitive pattern. Showing a date in the wrong format doesn't just look wrong; it causes errors.

Tone in UI copy. English UI copy tends to be casual and direct: "Got it!", "Let's go!", "Awesome!" This tone translates poorly into languages where formality signals professionalism. In Italian, overly casual product copy feels cheap. In Arabic, it can feel disrespectful.

Reading direction. Arabic and Hebrew read right-to-left. This doesn't just flip the text. It flips the entire UI layout. Navigation, progress indicators, image placement, form flows, everything mirrors. If your product doesn't support RTL, you've excluded 400+ million Arabic speakers and 10+ million Hebrew speakers.

You can learn these things from a localization guide. But you internalize them only by thinking in multiple languages, by experiencing how each language shapes perception, expectation, and behavior.

The Four Markets I Know Best

Italy: Relationships Before Transactions

Italian users want to know who they're dealing with before they spend money. Reviews matter, but personal connection matters more. Babonbo's best-performing renters in Italy were the ones who sent a personal message with every booking: "Ciao! I'm Maria, I have two kids, here's the stroller I'll deliver."

Product implication: the onboarding flow for Italian supply-side users emphasized personal profiles, photos, and bio sections. The same onboarding for UK users emphasized response time and availability.

Mexico: Flexibility Over Efficiency

In Tijuana, building Comensalaqui taught me that the US obsession with efficiency doesn't translate. Mexican users valued flexibility: the ability to customize orders, negotiate prices, communicate directly with sellers. A streamlined, "optimized" checkout that removed human interaction felt sterile.

Product implication: we built direct messaging into the core flow, not as an add-on. Users talked to chefs before ordering. This made the platform less efficient but dramatically more sticky.

United States: Speed and Scale

American users expect instant everything. Instant booking confirmation. Instant customer support. Instant onboarding. The tolerance for friction is near zero. If your loading spinner lasts more than two seconds, you've lost them.

Product implication: every US-facing product I've built optimizes for speed above all else. Edge caching, optimistic UI updates, background data loading. The perception of speed matters as much as actual speed.

Global (Aviation): Universal Precision

Aviation Infinity serves 120+ countries, and aviation culture overrides local culture. Pilots worldwide share a common language (English is the international aviation language), common procedures (ICAO standards), and a common obsession with precision. A pilot in India and a pilot in Brazil have more in common with each other than either has with non-pilots in their own country.

Product implication: Aviation Infinity is one of the few products I've built where a single product experience works globally. The localization is in the content (which authority's syllabus), not in the UX.

Payment Systems Are the Real Barrier

If you want to understand how hard global products are, look at payments.

In the US, everyone has a credit card. In Italy, many people prefer bank transfers or prepaid cards. In Mexico, cash and OXXO payments (convenience store payment networks) dominate. In India, UPI is the standard. In Brazil, PIX and Boleto are essential.

Each payment method has different settlement times, different fee structures, different dispute processes, and different user expectations. A product that only accepts Visa and Mastercard has excluded most of the developing world.

For Babonbo, we integrated with Stripe for card payments but had to add local payment methods for each market we entered. For Comensalaqui, we built cash-on-delivery into the core flow. For Aviation Infinity, we use Stripe's global payment methods to support 135+ currencies.

Payments are the most unsexy and most important part of going global. Get them wrong and nothing else matters. You can build the best product in the world, but if people can't pay for it, it doesn't exist.

What I'd Tell Founders Going Global

Don't localize your product. Build a local product. The gap between translation and localization is the gap between failure and success. If you wouldn't use the product yourself in the target market, neither will your users.

Hire locally or don't bother. You cannot understand a market from your home country. You need people on the ground, not just for language, but for cultural judgment. My best decisions in the Italian market came from Italian teammates. My best decisions in Mexico came from living there.

Start with one market and go deep. The temptation is to launch in ten countries simultaneously. Don't. Launch in one. Understand every edge case. Build trust with that community. Then expand. Aviation Infinity started in Italy. Babonbo started in Milan. Comensalaqui started in Tijuana.

Respect the existing infrastructure. Every market has existing tools, habits, and preferences. You're not replacing them. You're integrating with them. If Italian parents use WhatsApp, integrate with WhatsApp. If Mexican customers prefer cash, accept cash. Fighting local infrastructure is a losing battle.

Multilingualism is a superpower, but empathy is the real skill. Speaking the language gets you in the door. Understanding how people think (what they expect, what they fear, what they value) is what lets you build something they'll use.

I've built products that work in one country. I've built products that work in 120 countries. The difference isn't technology. It's the willingness to be wrong about your assumptions, repeatedly, and adjust until the product fits.