Case Studies

Case Study #1

A Simple Live Dashboard

One of our awesome customers needed to monitor the status of equipment located all over the country.They were actively logging into to over 25 devices one by one in order to determine each devices status. They originally contacted the manufacturer of the equipment and were quoted $35,000 to build a full fledged dashboard.

Brief Review & Savings of $34 Thousand Dollars

After a brief discovery meeting we determined that the fundamental need relatively simple. The customer wasn’t interested in all sorts of bells and whistles. After a short discussion we mapped out a simple path forward. Within 24 hours we had built a prototype that was able to accomplish all of their main goals. After the second iterations, the simple dashboard was implemented. Although the product implementation was simple, the code was built using well established standards and architecture which will help reduce future costs when the project inevitably grows into something more.


We were able to build and implement a solution in under 48 hours. By working with and understanding the clients needs, we managed to save over 98% on the $34,000 that was originally estimated for the project.

Case Study #2

Server Client Relationships w/ Changing Needs​

This customer approached us with a need to build a web app that worked with mobile devices. The mobile app needed to synchronize changes to data with the server, even while offline. After the applications were set up, it was also determined that the server needed to interact with a third party authorization server.

Loosely Coupled Software & Concurrent Modifications

We took a hint from version control libraries and designed the system to use the server as the authority on the data. Then we used the client roles to check in software changes and alert users when a concurrent data change was attempted. All in all, we were able to solve the problem while preventing data loss. Then, because the software was built using SOLID principles, we easily added third party authentication to the server.


We successfully built a web server that allowed a mobile client to easily handle offline data transactions. Because of the way it was built, we were able to easily accomodate new requirements.