Skip to content

Multilingual Translation Services

Many languages, managed as one project


When one document has to go into twenty languages, the languages are not twenty separate jobs. They share the same source, the same terminology, the same questions and the same deadline. Managed as one project, that becomes an advantage: preparation is done once, a question about the source is answered once for every language, and problems are solved by a team rather than by twenty suppliers working alone.


We have run multilingual projects since 2002, with Turkish at the centre and 40 languages in our project records. One coordinator, one terminology base, one quote, one delivery plan.

 

 

The numbers behind our work

Continuous translation work since 2002, with every project recorded in our own system since 2009. The figures below come from those records, not from estimates.

  • 72 language pairs delivered, 40 languages with documented project history
  • 6,135 projects for 587 clients since 2009, recorded in ]Project Open[ (April 2026)
  • 38 clients have worked with us for 10 years or more
  • 484 translators and reviewers paid across 9,606 purchase orders, 54 of them on 50 or more orders
  • ]Project Open[ open-source project management system, hosted in the EU, in use since 2009

 

▮Twenty vendors or one project?

Sending each language to its own vendor has a real advantage: every vendor answers directly for one language, and you know exactly whom to call. The price of that clarity is that nobody manages the project as a whole. You become the coordinator.

  Separate vendors One project
Accountability Direct, one vendor per language One contact answers for every language
Price Each vendor prices alone: file preparation, minimum fees and project management paid per language One quote: file preparation, terminology and DTP set-up done once and shared across languages
Source questions The same question asked by several vendors, answered several times, not always the same way Collected once, answered once, the answer applied to every language
Terminology Each language builds its own; terms drift between languages One approved glossary, applied to every language
Problems Found by one vendor, unknown to the others Found once, fixed for every language, handled by the team
Your workload You coordinate files, queries, deadlines and invoices We coordinate; you approve

 

Separate vendors can still make sense: when you already have a strong in-country partner for one market, or a local reviewer whose sign-off is required. We can work alongside them, sharing the translation memory and glossary so that their language stays consistent with the rest. Which model fits which programme.

▮How we run a multilingual project

  • One coordinator. One person who knows the whole project answers for every language, from the quote to the last delivery. urgent translation
  • Preparation done once. Files are analysed and prepared once, the translation memory and glossary are set up once, and the layout is prepared once for every language, including right-to-left and non-Latin scripts.
  • Shared terminology. Key terms are approved in the source and pivot languages first, then applied to every target language. A term decided in German does not come back differently in Dutch.
  • One query sheet. Questions from every language go into one list. The answer is sent to every team, not only to the translator who asked.
  • A team, not a list of suppliers. When a problem appears in one language, such as a source error, a broken file or a terminology conflict, it is checked in all the others and solved together.
  • Consistency checked across languages. QA covers numbers, terms, tags and layout across all language versions, not only within each one.


Tell us about your project 
Send the file, the language pair, and your deadline. We will come back with a price, a delivery date, and which workflow we recommend for that content. You can start with a single document and expand from there. We reply within 1 working hour
→ Request a quote

 

Translation tools and AI workflow
Tools and AI, under our control

We work in Trados and memoQ, or in the client's own translation system, with client-specific translation memories and glossaries maintained across every project. AI drafts are produced with the whole document in view, not sentence by sentence through a machine translation API, so terminology, cross-references and tone hold from the first page to the last. We are not tied to one model: we test models on your own sample files. A named specialist reviews and approves every output.

→ How we manage projects
→ The technology behind our workflows