This website was developed using the latest technology available, and therefore requires a newer, safer browser than the one you are currently running. Use the links below to download the most up to date version of your browser and try again!
Realizing that the methodology for developing both compliant and accurate mileage reports was antiquated and largely inaccurate, LogFirst founder Jeff Mason sought the help of KDG to create something new.
The app was ready to deploy on both Android and iOS platforms from day one without having to maintain two applications.
Built for a distributed load, the application is capable of handling hundreds of millions of transactions and rise to load demands.
KDG helped procure a GPS dongle and wrote software to power it in order to be used in a vehicle.
KDG wrote the algorithm to recognize frequent trips and automatically categorize them.
The simple and intuitive UI allows users to get up to speed quickly, pun intended.
Emailable reports allow for expense management in minutes.
KDG developed a multi-platform system that allows business travelers to track mileage using a passive mobile phone app or a proprietary GPS dongle that is permanently left in the car.
KDG developed a proprietary and patent-pending trip detection algorithm that recognizes trips, trip patterns, as well as frequently omitted routes in order to allow the software to “learn” the users’ behavior. The firm also helped LogFirst to design, develop, and source GPS devices from Asian manufacturers to reduce cost.
The app tracks mileage and reports it directly to the software. The GPS dongle does the same thing, but is plugged into a car’s lighter or USB port.
Successfully launching LogFirst involved several moving parts. Working with LogFirst, KDG simultaneously launched a mobile app for Android and iOS devices, rolled out GPS dongle device drivers for both Mac and Windows platforms, and launched a web-based app with an accompanying marketing website that incorporated marketing automation so that new prospects are always engaged without the need for actual hands-on attention from LogFirst. Not only did each of these components launch at the same time. They launched without incident.
