Mecon Insurance

Strategy, research, design, delivery and ongoing operation

Challenge

Mecon Insurance develops and provides specialised insurance products through insurance brokers to deliver tailored solutions for a wide range of clients and industries. They provide insurance for risks throughout Australia and New Zealand, as well as overseas operations for locally-based clients.

In 2018, Mecon chose to develop a new portfolio of insurance products and, at the same time, revitalise the tools that their broker’s used to do business with them, however Mecon used an existing industry solution to design their products and manage their back-office operations.

Mecon engaged Thinking.Studio to help them reimagine their broker experience while integrating seamlessly with their existing back office technology.

Solution

Thinking.Studio team worked with the client and back-office software vendor to design a solution that would surpass any other broker platform for performance, efficiency and simplicity - and Thinking.Studio developed a solution based on a completely open-source implementation stack of Angular and Act.Framework (Java).

As part of the Thinking.Studio delivery process, a series of agile design sprints were undertaken and a detailed user interface prototype was developed and tested with different broker groups. Once the design was approved, the portal was then developed over several Agile sprints using the Thinking.Studio Scrum methodology.

As the development was undertaken, an environment on Amazon Web Services was configured with SSL and a production NGINX web-server that proxies to the Act.Framework application and MongoDB database. This server side code would act as middle-ware between the legacy back-office application and the modern broker portal - providing high performance caching and modern web-application security, while keeping the back-office systems isolated.

The code was added to the Thinking.Studio Jenkin’s continuous deployment pipeline. As code is tagged in GIT for acceptance testing or release, it was then built, tested, and deployed into the appropriate AWS environments.