What was the scope of their involvement?
We had a discovery phase so that Slingshot could identify the most critical functions they could work on; we didn’t prescribe any solutions or areas of work. They outlined small projects we could build, test, and launch iteratively to consistently get value from our partnership.
They’re working on a web-based app that we use internally and externally. It provides quotes, issues policies, and performs all aspects of customer service, including payment processing, reporting claims, and renewing memberships. It’s our primary tool used by both employees and customers.
The app was written in .NET, and Slingshot kept some features and changed others. For example, they rewrote our payment processing platform, transitioning to a new payment processor and updating how our software engages with it. For the next phase, they revised our renewal process, making it smoother and more accessible for the customer to understand.
The final project was our claims processing feature, which we ultimately decided to pull out of the primary app and put into a new tool that’s built in Angular. The first two projects were redevelopment, and the last one was dev from scratch.
What is the team composition?
We worked with three developers and a strategy planner.
How did you come to work with Slingshot?
We’d been connected with Slingshot for several years but weren’t ready to financially commit to an investment in our infrastructure. They maintained the relationship and, when we decided it was time for this project, we hired them.
How much have you invested with them?
We spent between $250,000–$500,000.
What is the status of this engagement?
We partnered in November 2016, and the work is ongoing. We’re starting a new engagement soon.