Guides

Outbound in multiple languages: Swedish, Norwegian, Danish and Finnish in one campaign

How to run cold outreach across the Nordics in each prospect's own language without cloning campaigns: how to structure your list, what goes wrong with manual translation, and a campaign example.

Oscar Hill 2 min read
lemonreach title card: Outbound in multiple languages. A dropdown showing the language setting Per prospect, each in their own language, plus English, Swedish, Danish and Norwegian

You don’t need one campaign per country. In lemonreach, the same sequence writes to every prospect in their own language, Swedish, Danish, Norwegian or Finnish, all within a single campaign, and multilingual output is included in all plans.

The hard part is therefore not running the campaign but structuring the list and reviewing the copy. Here is what I would do.

Why write in the recipient’s language?

An email in your own language is easier to read and feels more personal. MarketingSherpa reports an IBM example where reply rates in Poland rose from 4.24 percent in English to 17.43 percent in Polish.

The same source warns that translations not done by well-trained native speakers can hurt replies. That is the important part: writing in the local language only helps if the writing is good.

Across the Nordics, English is also widely accepted in B2B, which is exactly why an email in the prospect’s own language stands out from the others in the inbox. Compare the two on your own list.

How do you structure a Nordic list?

  • Language per person, not per country. A company in Stockholm may have a Danish or Finnish CEO. Set the language on the contact.
  • Segment by target audience first. The same role and the same problem across all countries gives you one sequence. Market differences are a separate question.
  • Start small. 25 to 50 contacts per language is enough to review the copy and see the first replies.
  • Measure per language. Break out replies and meetings by language, otherwise you won’t know whether a particular variant is working.

What goes wrong with manual translation?

  • Every change has to be made four times. If you update the offer in a sequence running in four languages, that’s four changes and four chances for errors.
  • Tone and titles. Formal versus informal address, how you write a job title and which industry terms are used all differ, and a native speaker will notice immediately.
  • Machine-translated copy sounds translated. A word-for-word translation of an English email misses how you actually write a short cold email in Swedish. See how to write a good cold email.

What does a Nordic campaign look like in lemonreach?

You describe your target audience and offer once. The sequence writes every email for the individual, drawing on news about the person and their company, in the language you have set for that contact. See personalized outreach without manual research for how the research is gathered, and sequences for multilingual output.

An example setup:

  1. A list of 150 decision-makers at Nordic e-commerce companies.
  2. Language field: 60 Swedish, 40 Danish, 30 Norwegian, 20 Finnish.
  3. One sequence with an opening email and two follow-ups.
  4. Review the first emails per language, ideally with a native speaker, before the rest go out.
  5. Compare replies per language after two weeks.

The numbers in this example are illustrative, not results.

Frequently asked questions

Yes. In lemonreach, every prospect is written to in their own language, even within a single campaign spanning multiple markets. You build one sequence instead of cloning it per language, and multilingual output is included in all plans.

It often does. A frequently cited IBM example from MarketingSherpa saw reply rates in Poland rise from 4.24 to 17.43 percent with Polish instead of English. The effect varies by market and audience, so split your list by language and compare replies per language.

lemonreach writes in many languages, including Swedish, Danish, Norwegian and Finnish. As with any language, read the first sends before you scale up, ideally with a native speaker.

Add a language field per contact and set it based on the person, not the country. Keep one shared sequence and let the language field drive the copy. Start with a small batch per language and measure replies per language.

It gets expensive and slow when every change has to be made in four versions, and poor tone is immediately obvious. MarketingSherpa warns that translations not done by well-trained native speakers can hurt replies.

Get started

Your AI SDR is ready. Find prospects, send outreach, book meetings.