Learn more about how our team of experts has created solutions for clients facing a wide range of issues and challenges.
When a person files a vehicle insurance claim, providers turn to a company for scheduling a damage assessment. That company— a K-Optional Software client— specializes in getting every vehicle appraised so that the insurance provider can cut a check for the repair. Working with insurance providers means adopting long-lived industry conventions; our client receives claims to a dedicated email server in a pseudo-consistent format. Before working with K-Optional Software, our client had written a script in-house for reading this inbox, attempting to interpret the data, and exporting it into a CSV file. This approach proved brittle; slight variations in claim emails confused the script causing entire CSVs to drop. Worse yet, the evolution of email authentication— actually a welcome improvement for IT security— broke the script entirely.
You have been incredible for us from the beginning but the level of effort and dedication you have put into helping us get across the line before tomorrow is above and beyond. Thank you so much for the hard work. We are really excited about the state of the platform.
Flowty approached K-Optional Software prior to their public release. They had been contracting with an off-shore team for about a year, and at this point were urgently trying to bring their product to market because without a positive cash flow, they were dead in the water. Flowty’s CTO recommended K-Optional to assess the frontend codebase. Subsequently, Flowty hired K-Optional as an embedded team working under the Flowty logo. Our first assignment was the stable release of the product.
We have gone over the software and are very pleased with it. Looks wonderful, magnitudes better than before. Downloading the app went very smoothly. And the data export process is perfectly straightfoward.
The University of Texas (UT) Nursing Department requested a technical solution for administering a sophisticated survey. The results would become the basis for a major statewide study. UT hired a development firm, but the subjects (pharmacists) had a hard time with the interface. This created user errors and data output that were impossible to interpret, which made it difficult to derive any meaningful insights.