{"id":2520,"date":"2021-03-22T09:54:45","date_gmt":"2021-03-22T09:54:45","guid":{"rendered":"https:\/\/www.softera.lt\/klientu-istorijos\/vakaru-laivu-gamykla-microsoft-dynamics-365-sales\/"},"modified":"2026-04-14T16:15:52","modified_gmt":"2026-04-14T15:15:52","slug":"vakaru-laivu-gamykla-microsoft-dynamics-365-sales","status":"publish","type":"klientu-istorijos","link":"https:\/\/www.softera.lt\/en\/client-success-stories\/vakaru-laivu-gamykla-microsoft-dynamics-365-sales\/","title":{"rendered":"Vakar\u0173 laiv\u0173 gamykla – Microsoft Dynamics 365 Sales"},"content":{"rendered":"\r\n
\r\n
\r\n
\r\n \r\n \r\n \r\n \r\n \r\n \r\n
\r\n About the Company <\/h5>\r\n \r\n\r\n \"corner\"\r\n\r\n \"corner\"\r\n\r\n <\/div>\r\n
\r\n

Business activity: <\/strong>Manufacturing and services<\/p>\n

Company size:<\/strong> ~1,800 employees<\/p>\n

Revenue: <\/strong>\u20ac100,000,000 \u2013 \u20ac150,000,000<\/p>\n <\/div>\r\n <\/div>\r\n<\/div>\r\n\r\n\r\n\r\n\r\n\r\n

\r\n
\r\n
\r\n

Vakar\u0173 laiv\u0173 gamykla has been one of the largest marine engineering industry groups in Lithuania for more than five decades. The group currently brings together 21 companies with different specializations and provides a full range of services across the entire ship lifecycle. <\/p>\n

It is also the largest employer in Western Lithuania, creating more than 3,000 jobs.<\/p>\n

We spoke with Laurynas Prikockis, IT Director.<\/p>\n

How did the need for a CRM system arise?<\/strong><\/h4>\n

The need to implement a CRM solution emerged in 2012, as the volume of information increased rapidly. It became impossible to manage this flow manually or keep track of all contacts. The need for analytics, timely decision-making, and employee turnover became key drivers for implementing a CRM system as soon as possible.<\/p>\n

Why did you choose Microsoft Dynamics 365?<\/strong><\/h4>\n

Back in 2012, we evaluated various CRM solutions, including Microsoft Dynamics 365 Sales<\/a><\/strong>, but at that time the available on-premise version did not meet our needs. As the solution evolved and a cloud-based version became available, we adopted it in 2016. The decision was based on several factors: <\/p>\n