BeLazy's costing is based on tokens.
In the Content and Project Hub, BeLazy takes a certain number of projects. In one connection, for example an XTM connection where you are project manager, you get a single project with multiple files and languages as a BeLazy project. In another XTM connection where you are a linguist, even if all the files and languages are assigned to you, they are still individual BeLazy projects. While it's true that there is more work in registering the projects in the latter scenario, we do not charge for the origin projects coming from the Content and Project Hub: we charge for the Business Management System projects that you create. The functionality of bundling means merging several origin projects into one BMS project. Even in the XTM linguist scenario BeLazy allows you to bundle all the files and languages and workflow steps back into the same representation that you would have if you were a project manager. Therefore, the cost between the two scenarios does not differ.
A token is measured against the Business Management System projects you create and manage via BeLazy. Every BMS project BeLazy creates has one source language and one or more target languages. We charge by the target languages in each project.
Single target language projects cost 1 token.
2-10 target language projects cost 2 tokens.
11-20 target language projects cost 3 tokens.
21+ target language projects cost 4 tokens.
If you're already receiving and managing the work manually in a business management system, check the projects there, and see how many target languages each and every project has. Categorize the projects into 1-4 token projects, and calculate the number of tokens you will use. Do this per each different content source (connector type) you want to use.
Your total cost is the cost of your package (which includes certain functionalities, as advertised on the pricing page), plus the token cost of your projects minus the tokens included in the package. If you receive or create many projects in one TMS, you can maximize the cost and no matter how many projects you will receive, you always pay this fixed cost. The capped token cost is only available for translation management systems as of today, it does not apply to vendor portals, emails and other integrations.
Translation companies that receive many small projects, where the cost per project is under 10 euros, can also buy bulk packages of 500 such projects at a much discounted per-project fee. If there are more projects coming in with a revenue of under 10 euros than the ones included in the purchased packages, those are charged at normal token fees. If there are less projects under 10 euros, the extra projects in the package are lost.
When calculating ROI, bear in mind that you are achieving two objectives at the same time:
- end-to-end automated projects, with project managers only supervising them, rather than managing them,
- reduced error rate that comes from automated data entry.
End-to-end automation is optional: some of our customers only automate acceptance and creation of the projects in the relevant systems. However, we already envision a near future where fully qualified projects can flow through resilient, well-defined pipelines across the entire supply chain.