Future-proofing LSP technology TAUS Annual Conference Takeaways: 1 out of 3
LSPs become services aggregators
At the TAUS Annual conference in Vancouver, Welocalize’s VP of software development, Douglas Knoll, demonstrated a new production platform that can now be used for virtually any task. This opens up a technology discussion among LSPs regarding the ability to add new services quickly.
Bad news for TMS creators inside translation companies. Even if you develop the world’s best translation management system, it won’t be enough to prepare the company for the challenges of the future. Why? Because the future of LSPs is not exclusive to translation.
New lines of business
As the translation market decelerates, language services providers seek growth in new services. Consider the following examples:
From transcription to copywriting, many LSPs have already become professional human service aggregators. And who knows what new offerings will spring up in the next three years. Markets might materialize in areas yet to be explored, and agile companies will try to probe every interesting opportunity. Are their production units and tech teams ready for rapid transitions?
It is clear that each new offering will use new talent and new software, but in a startup economy, LSPs will likely not have the luxury of developing production units over 5 -10 years, as was the case in the past. Once CEOs validate a new line of business, team-leads will need to jump onto the moving train.
In technical terms “jumping onto a moving train” means that companies will need a central system, so that multiple systems for each individual service can be plugged in.
- The central business management system to handle clients, talent, business intelligence, financials, purchase orders and invoices, and orders via a client portal
- Production systems to handle and automate actual work – TMS for translation services, an IMS for interpreting, a media suite with media asset management for audiovisual, a testing suite for functional QA, and so on.
It’s clear that each system will need a strong API and that most of the work will happen automatically in the backend, instead of manual actions inside user interfaces.
As LSPs add more and more services, it becomes less relevant for them to develop language automation features. Instead of creating CAT-tools and basic TMSs, developers should concentrate their effort on the central platform that automates company processes that are common for all lines of business, such as a CRM, invoicing, payment automation, and talent management.
Since their software will have to adapt for a bigger variety as their clients change their nature of business, business management software developers (such as Plunet, XTRF, and FlowFit) should consider investing in a strong API with the ability to plug new services into existing projects, vendor management, and client portals. Developers who overlook this advice might find eventually themselves outpaced by more generic and customizable management software.
Stay up to date as Nimdzi publishes new insights. We will keep you posted as each new report is published so that you are sure not to miss anything.