Fleet insurance quotation
Project goal:
Development of the car fleet quotation system for Sulamérica Seguros, focusing on moving the system to the web.
Design Thinkig
UI Design
Prototype
User research
Understanding the problem
​To start the project for Sulamérica's car fleet quoter, we carried out extensive field research in which we visited dealerships and insurance companies. During these visits, we observed how employees quoted car fleets for large companies. We did a competitor analysis and interviewed stakeholders and insurance brokers to understand the main pains and challenges of quoting more than one car at a time.
After the interviews, we wrote down the main findings on insight cards and grouped them by affinity to identify business opportunities and improvements in the existing car quotation system. At the same time, we also mapped all the interfaces that the dealership employee had to go through in order to get a quote for a fleet of cars. The existing system only addressed the individual quote, and there was no easy way to include more than one car. In this way, the brokers had to carry out the insurance analysis one by one, which was a lot of work and consumed the employee's day.
Presenting for stakeholders
To present the main findings, we took the map of the screens with the opportunity cards revealing where the main problems of the quoter, which was in vogue at the time, were. Together with the project's stakeholders, we chose the main pain points that should be prioritized to resolve.
​
Building the solution
Within MJV, we then built the ideal scenario for the car fleet quoter, considering the main pain points that we had mapped. Every week we went to the client to present the evolutions and the next steps, and the entire process of creating and gathering requirements was done together.
The client was an insurance company, so we had some trouble with the validation of prototypes. We tried to use employees from the insurance company to validate the solutions we were making.
Helping developers
After the end of the project, we were also responsible for passing front end specifications to the engineers who would be responsible for executing the project. We made a "design system" (we called it style guide) to facilitate the implementation on their side.
