Global Logistics Company Benefits from Industry-Leading, Customer-Facing Application

challenge

Inconsistent Customer Experience

Our client, a global logistics company, needed a partner to introduce their first Azure-based customer-facing application. They wanted to create a central portal where customers could view their scheduled trailer requests and submit ad hoc requests in the event of volume spikes. Previously, requests were managed via phone and fax using processes defined by each dispatch location. This created an inconsistent customer experience across the brand and had significant administrative overhead. Additionally, speed-to-market was essential on this engagement as none of their competitors had a similar application, so they wanted to be the first to market with it.

solution

A First for the Industry

Our Scrum-as-a-Service® team built an industry-first, customer-facing application built in .NET and Angular and deployed in Azure that allowed customers to submit, update, view and filter trailer requests. During the course of the project the team was able to pivot to other application areas in order to remove blockers and high priority backlog items in order to maintain momentum on the trailer reservation project. Because our client had no established method of communicating between internal and external facing applications, data exchange between our application and the client’s internal application was essential for our application to function.

results

An Edge Over the Competition

Our client was the first to market with an application of this type, giving them an edge over their competitors as well as a unified and corporate branded customer experience. Our team was able to deploy a customer facing enterprise application in seven months using a multidisciplinary approach of front-end, back-end, quality assurance and DevOps engineers. Because the team was capacity based rather than project based, it was able to shift work to the items of highest priority in order to clear development bottlenecks for dependencies in other application areas adjacent to the application being developed. Our team was able to use knowledge gained through the development of the initial MVP release to continue into a second year of feature development.