Execution · 2026-05-12 · 5 min
Outbound in the Buyer's Language
Messaging a prospect in their own language can lift replies, but only when it is done properly. Here is when translation helps, when it backfires, and how we decide which markets get a native-language message.
A client selling into France asked us once why we were not messaging their prospects in French. The honest answer is that it depends on who the prospect is, and getting this decision wrong in either direction costs replies.
Messaging someone in their own language signals effort and respect. It also introduces risk, because a message that reads slightly off in a language the sender does not speak fluently reads worse than the same message in competent English. Bad translation is more damaging than no translation.
When English Is the Right Choice
Most senior B2B buyers across Europe, particularly in tech, operate in English as their working language, especially in software, and especially at companies with any international customer base. A CTO at a German SaaS company reads and writes English daily as part of the job. Messaging them in German here adds no value and can even read as slightly off, because their own professional identity in that context is English-speaking.
English is also the safer default when you cannot guarantee native-quality writing in the target language. A message with awkward phrasing or a slightly wrong idiom reads as careless, which is worse than reading as foreign. If a translation is not going to be genuinely fluent, competent English outperforms it.
When the Local Language Earns Its Place
The calculation changes for buyers whose role is less internationally oriented. A finance director at a mid-sized manufacturing company in Lyon, an operations manager at a regional logistics firm in Bavaria, or a procurement lead at a domestic retailer are all far more likely to work primarily in their own language day to day. For these buyers, a message in French or German is not a nice-to-have. It is the difference between being read as a peer and being read as an outsider cold-calling from abroad.
Government, public sector, and heavily regulated domestic industries also skew towards local language, almost regardless of seniority, because the entire professional context they operate in runs in that language.
The Rule We Actually Use
We look at two things before deciding: the buyer's role and industry, and the maturity of the local-language content we can produce. If the buyer's daily work language is clearly English, we write in English. If it is clearly the local language, we write in that language, but only using a fluent speaker or a properly reviewed translation, never a raw machine translation sent without a native check.
Where it is genuinely unclear, we test both on a small scale within the same segment and let the reply data decide, rather than guessing.
What Goes Wrong With Machine Translation
Running a message through a translation tool and sending it directly is the single most common mistake we see companies make when they decide to "go local." It is detectable within one sentence to a native speaker, because translation tools consistently get formality register wrong, particularly in languages like German and French that carry different levels of formal address. A message that uses the informal form where the formal one is expected reads as either careless or oddly familiar, and either reading damages the message before the actual offer is even considered.
The fix is not to avoid the local language. It is to have a fluent reviewer check tone and formality, not just grammar, before anything goes out. This is a short review step, not a full localisation project, and it is worth the extra day.
A Short Example
A campaign into the Netherlands selling a horizontal SaaS tool sent two versions to comparable segments: one in English, one in professionally reviewed Dutch. Directors at internationally facing scale-ups replied at similar rates to both. Managers at more domestically focused mid-market companies replied noticeably better to the Dutch version. That single split told us more about how to segment the rest of the campaign than any amount of guessing would have.
What This Means for Planning a Campaign
Do not decide language policy at the country level. Decide it at the segment level, based on how internationally oriented the actual buyer persona is, and revisit it once you have real reply data rather than a general assumption. This is one reason we build language testing into new market launches within our campaigns, rather than defaulting to whichever language the client's own team happens to write in.
Next: if you are expanding into a new market, split your first month of outreach into an English test and a properly reviewed local-language test before committing either way.