On-premise vs Remote Software Localisation: which model works best for you?

In order to better communicate with international clients, Software Publishers will look to translate and localise their applications into other languages. During this process, one of the first steps will be to approach a Language Service Provider (LSP) to evaluate project requirements, scope and cost.

Some Software Publishers show concern at outsourcing to an LSP, and will maintain a preference for on-premise localisation, using in-house translators.

The localisation industry has come a long way in terms of their technical capabilities, which allows them to be flexible when dealing with various systems and file formats. Let’s explore the pros and cons of each approach.

On-premise Software Localisation:

It’s not easy to find qualified and native linguists, with experience in localising software, located within a reasonable vicinity of your offices, who are also available purely for a short fixed-term placement.

Remote Software Localisation:

Although this luxury could be viewed as a major distinguisher, you will need twice the budget, twice the time, and ultimately, the linguistic quality will be compromised due to restricted linguist options.

It’s easy to understand why some buyers would initially opt for this first option; perhaps there is nervousness amongst some that a LSP would not grasp the technical content without constant supervision. As long as the LSP has access to screenshots, glossaries and style guides, and you have allowed time for language testing, this should never be a problem.


Sean joins Capita TI from our acquisition of ITR. He has over 25 years' experience in the translation industry and has worked in a variety of roles. He's now our Pre-sales Language Solutions Consultant.

Share this story

Sign up to our newsletter

Sign up