It’s no secret by now, BeLazy’s vision is to enable efficient continuous localization across the supply chain. As we work hard towards this goal, we are constantly interviewing translation buyers to understand their needs and technology solutions, and discussing with their multilingual language vendors (MLVs) the inefficiencies that small and repetitive translation jobs represent to the supply chain mesh. While companies at the top of the chain invest a lot of effort and money to integrate their technology stack, those at the bottom of the chain, the so-called single language vendors (SLVs), struggle badly in trying to keep up with the overhead caused by continuous localization methodologies.

In our attempt to understand the logic behind which language services flow across the industry, last December we launched the BeLazy Early Automators Program (BEAP): a collaboration scheme between BeLazy and language service providers (LSPs) that had already identified the need for automation within their organization and were keen to get on board with new initiatives that bring efficiency and cost savings.

We worked closely with each of the LSPs to analyze their supply chain environment and match their needs to BeLazy’s product roadmap. All in all, we identified six different scenarios that show the different collaboration possibilities throughout the translation supply chain. After having drafted and sketched the respective scenarios, our next goal is to enable full automation workflows within BeLazy for each of them.

To our surprise, our findings are much more complex than you and I probably ever thought. Yet, we are committed to raising awareness of the complex bonds that make up the translation supply chain, that is why we will share insights on each of these scenarios on the course of the following months (we are starting with the first one today!). We will explain the challenges that each scenario presents and show how BeLazy has been able to help integrate these platforms and make continuous localization seamless.


We would very much like to have your feedback on the existing scenario and help us identify new ones. And always feel free to reach out to us when you are ready to introduce automation to your organization 😉

Before getting started, we go over this concise dictionary of continuous localization.

What is Continuous Localization?

We see more and more enterprises integrating the copywriting process into the product development lifecycle. This growing trend has led to a series of changes to the traditional translation workflow, some of which are making things easier while others bring on new challenges.

The main characteristics of continuous localization are:

What does the supply chain look like?


Translation jobs are (almost) always initiated by the end client — the content owner.


The content is processed by a language service provider — in the case of big companies, the LSP is usually a Multilingual Language Vendor. The content then flows across the supply chain to other stakeholders in the process: the single language vendors, translators and other language professionals such as quality checkers or reviewers.


The supply chain is usually long and is made up of many different companies, all of which could benefit from BeLazy’s integrations and connectors in the role of automators.

Vendors | Translators

Each automator has a client, the previous stakeholder in the supply chain, but has also vendors. At the end of the supply chain there are translators who could be in-house or freelancers. The shortest supply chain is that which only includes an end client and translators.

What’s an automation scenario?

An automation scenario basically describes the many systems a piece of content needs to go through in order to be translated and published. The following systems may be involved in the process:

What is an online/offline workflow?

Offline workflow: The content is exported from the client’s systems and arrives to the Automator (language service provider) in different formats such as translation packages, bilingual files, or original files (e.g. Adobe files). The Automator may need to use specific technology to process the file. In this kind of environment, it will be impossible to track if the vendor decides to re-assign the job to other sub-vendors.

Online workflow: The content never leaves the translation management system. The translation job is assigned to the Automator within the system and the vendor uses an application or web browser to work in it — possibly reassigning to sub-vendors if needed. Everything can be tracked within the system.

Scenarios describing the interconnected systems driving continuous localization

BeLazy’s primary goal is to support the workflows built upon standardized processes. The scenarios we present outline some of the most common system setups that an Automator needs to manage when working with its client.

The processes described in these scenarios do not include quoting, price, or deadline negotiation. Do you have projects that meet these characteristics of the continuous localization programs? If yes, sign up to BeLazy now!

If there is a connector missing and this is preventing you from becoming the next Automator, please let us know. Also, do reach out to us if your projects follow a different path: we are very interested to learn about your workflow and see whether it is possible to make your work more efficient.