What was the scope of their involvement?
We started out building two modules in the cloud solution, replicating what we already had in Windows, but focusing on two main functions which would enable us to start migrating US clients. It was all about rating insurance products and administering claims on them. It’s a flexible solution by which clients can tailor their own products with the rating engine behind them, and issue policies in order to receive and administer claims on the same insurance product.
We don’t have any integrations yet, but we will be integrating with financial systems within the new year. When offering invoicing on top of these insurance products, the next step would be for the system owner (the person who buys the system and hooks into it) to hook in with whatever they have in the backend as a financial system, for example, QuickBooks. The aim is for invoices to flow automatically into the system in which they typically get their financial stream of payments so that they can match payments automatically with invoices. Hopefully, the next step of integration will be for payments going back to our solution.
From the start, we specified that we needed ASP.NET development, and Diceus suggested that we use ASP.NET Core so it would be more transparent for me — the platform running the code didn’t need to be Windows. I appreciated this suggestion since I hadn’t known about .NET Core previously.
What is the team dynamic?
Diceus’ team has typically provided full stack development, but I am the type of person who wants to be in control of the bottom layer. This is my fourth time building a system for this trade. I’ve been in the business for 20 years and have specialized in insurance-related software. I know exactly what I want when it comes to functionality and data structures, so the split between me and Diceus is that I provide the data architecture features, and they program up against a black box. If I was not happy with them, I could swap them out with another development company at any time, since I am in full control of what goes on beneath the 2 top layers of the solution. It took a little while for them to get used to that way of working since I might be too specific when it comes to what I want and how it should look, but, after a while, it became better and better.
This is not a huge project; we only have 2 developers. They’ve consistently been the same resources from the start.
We use Skype and email for communication, and I went to their office when we started up to have brainstorming sessions on functionalities. Most of the time, we communicate electronically about specific parameters.
How did you come to work with Diceus?
Being in the trade we are in, we get all sorts of prompts from different providers, many of them from outsourcing companies in India or Eastern Europe. Diceus came across as one of the more serious ones. Diceus reached me at a point when I was starting to warm up to the idea of outsourcing development, so I remembered the contact. The fact that they had experience with solutions for the insurance world made a difference. They had references in Scandinavia and might have been looking for similar prospects.
In spring of 2017, I created a description of our product and my intentions in building a cloud solution. We had a Skype meeting and discussed my criteria, and they came across as a professional option. Diceus connected me with a developer to discuss the issues more specifically. He was proactive in terms of technology and methods, pinpointing issues in my demands. This was the main reason for selecting Diceus. Their CEO, Illia Pinchuk, controlled the initial discussions, quoting, and analysis in a very serious way, which gave me the impression that they were not only skillful developers, but when it came to communication, he would be able to allocate the right people.
How much have you invested with them?
The cost of two developers over the last seven months was $60,000–$70,000. We are invoiced monthly. Compared to our in-house resources, it is a good value for the money.
What is the status of this engagement?
We started working with Diceus in May 2017. We will launch the cloud solution at the beginning of 2018.