BeLazy is the localization operations infrastructure that enterprises and translation companies require to stay competitive in the age of fragmented systems, AI processing and vibe coding.
The localization industry is experiencing a major disruption and the old methods of manually synchronizing data between systems are not sufficient any longer. The most widely used systems in the industry, namely translation management systems and business management systems have been created to support manual work. Instead of forcing you to completely changing systems, BeLazy adds the capability to carry out fully automated, hands-off projects in the systems you currently use, by connecting the systems and adding the metadata-based automation layer on top. BeLazy does not make project management unnecessary, but shifts the focus from manually entering data in the systems to defining rules of how it must be done, and handling exceptions as they arise.
BeLazy is based on the concept of harmonization. Translation management systems all work differently, handle workflows differently, but in the end, files are imported via filters, pre-translation and analysis is done, AI automations and linguists are assigned, jobs are delivered, and files are exported in each of them. Business management systems all have different structure and pricing concepts, but in the end, they are always the systems that hold the most information about vendors, and that serve as the general ledger for every operation. Companies that do not have a sophisticated business management system such as Plunet, XTRF or Protemos still perform some project tracking, mostly in the form of a spreadsheet. Content sources, whether it's a CMS system or PIM system, a JIRA ticket, a customer portal, an email, another TMS, or a vendor portal always carry translatable content, which needs to be converted into a scoped localization project with a deadline, and the translated content needs to be delivered, sometimes only once, sometimes after each and every workflow step. AI systems can be machine translation systems, LLMs with single prompts, LLMs with agentic workflows, can be used for various steps like translation, quality estimation, post-editing, QA, LQA. Increasingly, more and more localization programs and translation companies are exposed to working in multiple systems, and with the possibility of everyone vibe coding their own systems, this is just going to get more complicated.
BeLazy shifts the horizon of localization teams from one old-fashioned translation management system or business management system to the best-of-breed of all possible systems. Connect your systems to BeLazy and allow every aspect to be replaceable. Your TMS does not support the AI your colleagues were working on? You know the rules how you'd automate vendor assignments but you are still doing it manually? You want to change TMSes but you feel locked in because of your content management integrations? No problem. With BeLazy you can increase the number of systems without increasing the complexity of the operation.
Harmonization also means that every project, coming from every different customer, different system, processed through different methods can be described in a single way, with standard metadata and an arbitrary number of added metadata called extra data. This information is reflected on the APIs and can also be exported directly into Google Sheets, which can be directly connected to any business intelligence system. This allows outcome-based reporting - mixing localization-related data with data coming from the markets. Through this approach, even localization vendors can offer real-time visibility into the projects to their customers, which shifts the traditional quarterly business review approach.
Traditional API-based integrations are point-to-point. They are complex, prone to break with updates, and you may not have the necessary resources available to update them when it's needed. BeLazy goes beyond this: depending on the system, BeLazy decides for and implements the best integration capability - which may or may not be the use of the public API -, researches the way to abstract away all the capabilities of a given system, and separates the different use cases. BeLazy offers a web of integrations that keep on expanding, and an open, simple API to integrate systems not supported - for example, your internal content sources. BeLazy is the backbone of any localization operation: a secure infrastructure, a set of integrations, extensibility, and simple, Javascript-based orchestration/choreography. It's similar to the systems the largest localization teams in the world have developed in-house to take automation to the maximum, but it's available to any size of a team.
BeLazy consists of several functional hubs that separate the different concerns:
- the Content and Project Hub consists of connections and an API to integrate any content or project source, including content coming already prepared from TMSes and vendor portals,
- the TMS Processing Hub allows you to choose the TMS you would like to analyse and process the source content that comes in a traditional file format,
- the Business Management Hub defines the workflow that goes beyond the TMS, and takes care of the financials and holds all the information about the vendors,
- the AI Hub allows using different AI integrations to perform certain workflow steps with the use of linguistic automation. AI in BeLazy is optional, not mandatory.
- the Orchestration Hub allows you to finish the configuration that does not come from the structure of projects in the source system and walk the extra mile in automation,
- and the Sales Management Hub integrates commercial BMS systems such as XTRF and Plunet with CRM systems to separate project and sales related work.
BeLazy also offers several helper tools:
- the Google Sheet-based project management tool (part of the Business Management Hub) allows companies that do not have a Business Management System to track all projects for finances and completion automatically, and initiate complex automations from Google Apps Scripts. It also helps those that do have such a system to agilize and further automate project management in the world of microtransactions.
- the Email Assistant (part of the Content and Project Hub) allows project managers to create projects directly from emails in BeLazy, and then push them through automation.
- the BeLazy Portal (part of the Content and Project Hub) allows enterprises and LSPs to set up portals for their customers where they can place orders specifying only the metadata necessary and specific to the customers to carry out projects with the highest degree of automation. The portal is freely customizable using vibe coding, implements single sign-in with any OpenID Connect provider, and can be installed on premise for any customer.
Extensibility is also related to the different hubs:
- The Project Ingestion API (part of the Content and Project Hub) offers feature parity with BeLazy's own integrations, and allows integrators to implement any content integration without having to learn and understand how a TMS or a BMS works. Every integration built through this API will survive a TMS or BMS change. Users also use this API to connect their own TMS not supported by BeLazy out of the box, and companies like iLangL push their CMS integration projects to BeLazy via the same API. Both the BeLazy Portal and the Email Assistant are connected to BeLazy via this API.
- The Update Opportunity API (part of the Content and Project Hub) allows the enrichment of information coming from BeLazy's own integrations. The enriched metadata description allows more sophisticated project routing.
- The BMS Integration API (part of the Business Management Hub) allows users who built their own business management system to take advantage of all the capabilities of BeLazy even if they do not use Plunet, XTRF or Protemos. BMS provider Quahill built their integration through this API, and LSPs with own systems are also using this.
- The BMS Extension API (part of the Business Management Hub) allows users to achieve further configuration in systems already integrated in BeLazy, like Plunet, XTRF and Protemos. This API gives direct access to the entities stored in those systems via a simple, unified API to achieve things like vendor assignment, deadline change, or finance change. It allows users to go the extra mile.
- The AI workflow APIs (part of the AI Hub) allow 3rd party AI-based bilingual document processing for each and every workflow step in any TMS integration BeLazy supports.