Opportunity & Project lifecycle

From opportunity to project

BeLazy calls the translation work offered to you (offers, projects, etc.) opportunities, and once you accept them, they become projects. Whether you are implementing the BMS Integration or the Project Ingestion use case, you will need to work with opportunities, projects, or both. The opportunity and the project are not just central entities in BeLazy, but they also have their own lifecycle - just as your translation jobs have their lifecycle. In order to interact with the BeLazy REST API, we advise that you understand the journey of opportunities into projects.

The lifecycle of the translation work starts as an opportunity when it is downloaded from a source system. All translation jobs start here, whether they are downloaded by BeLazy from a supported system, or they are created through BeLazy's Project Ingestion API for proprietary systems. Such opportunities appear in the BeLazy web application dashboard, waiting for acceptance.

An opportunity can either be accepted or dismissed. An accepted opportunity turns into a project and begins its journey, while a dismissed opportunity is no longer available for any action. The decision can be made in the BeLazy web application dashboard, using auto-approve rules, or the Opportunities API also allows performing these actions using the REST API.

Project lifecycle

An accepted opportunity turns into a project and it is ready to be created in the BMS. There are two scenarios depending on the type of the BMS. If BeLazy supports your BMS, the project is automatically created in your Business Management System, hence a project is in the accepted state for a short time only. However, if you have a proprietary Business Management System and integrate with BeLazy using the BMS API, accepted projects are waiting to be fetched by your integration. Once created in this proprietary BMS, project creation needs to be acknowledged in BeLazy.

Projects transferred to the BMS system are managed there. BeLazy does not interfere with your way of managing the localization workflow. Using the connection configuration and possibly API calls, you can instruct BeLazy to perform changes in the source system, for example vendor reassignment or file upload.

Once a project is delivered in the BMS, BeLazy can retrieve the deliverables. Once again, depending on your type of BMS, this can be an automated process managed by BeLazy, or your integration can deliver the project using the BMS Integration API. BeLazy takes care of uploading these deliverables to the Vendor Portal or the Translation Management System.

And finally, after all the deliverables have been transferred to the source system by BeLazy, the project is closed - both in BeLazy and in the source system. When using a proprietary system deliverables download and project closing is managed through the Project Ingestion API.

Lifecycle of projects and opportunities: The image depicts the stages that translation work goes through in BeLazy.