Insurance Center
Azibo
Azibo is a platform for small landlords to collect rent, manage their properties, and handle their finances all in one place.
Landlords have lots of things to track regarding their properties. One of the more tedious items is making sure their properties are insured (and at a good price).
Our team knew that if we gave users a place to track their current policies, not only would it help them stay organized, it would put us in a position to also help them find and compare quotes from our insurance partners.
Landlords have lots of things to track regarding their properties. One of the more tedious items is making sure their properties are insured (and at a good price).
Our team knew that if we gave users a place to track their current policies, not only would it help them stay organized, it would put us in a position to also help them find and compare quotes from our insurance partners.
Getting Started
Learning on the fly
The first thing I had to do was deep dive into landlord insurance. I worked with our head of insurance sales and other coworkers who were landlords to get an understanding of the various types of policies, how they managed them, etc.
Using that information, as a small team (me, PM, and engineer), we started with brainstorming ways to build the insurance center. We became hyper focused on ways to drive engagement, because the more we were able to encourage users to track and store their policies with us, the better situated we'd be to convert them to using our insurance services.
From there, I jumped into lo-fi wireframes to lay out the structure and figure out what features we wanted to include. Ideas that started forming were a progress bar of how many properties had insurance documents, a super convenient checkmark during policy upload to allow us to "analyze" their quote and find better options, and tips such as recommending an umbrella policy to get better coverage.
Using that information, as a small team (me, PM, and engineer), we started with brainstorming ways to build the insurance center. We became hyper focused on ways to drive engagement, because the more we were able to encourage users to track and store their policies with us, the better situated we'd be to convert them to using our insurance services.
From there, I jumped into lo-fi wireframes to lay out the structure and figure out what features we wanted to include. Ideas that started forming were a progress bar of how many properties had insurance documents, a super convenient checkmark during policy upload to allow us to "analyze" their quote and find better options, and tips such as recommending an umbrella policy to get better coverage.
.png)
syzygy
Aligning the team
Being a newer company at the time, there was a lot of room to improve our processes. Our team (me, a PM, and a lead engineer) worked hard to define a system of communication that worked for us and kept us all aligned.
This design/product/engineering triad was one of the best I've worked in, and our communication and collaboration style was a key factor in the success of launching the feature.
This design/product/engineering triad was one of the best I've worked in, and our communication and collaboration style was a key factor in the success of launching the feature.
Defining the Model
How should the elements be structured?
Option A: Property Centric
While this felt more obvious, it was harder to work with. For properties with multiple policies (e.g. main and umbrella), it would be harder to show both while cleanly presenting quotes and actionable items. Because there was a property tab with linked policies, it was redundant to repeat that in the insurance section.
Option B: Policy Centric
After thinking about the various issues with the property centric model, I landed on the policy structure. This made it easier to show which policies were property insurance vs umbrella policies (and more in future concepts such as auto), and to sort them by when they were expiring so users could easily remember to renew or get a new quote.
meeting the goal
Key word: Engagement
One of the key ways we solved for this was by creating the feeling of wanting to complete the progress bar. By showing how many of their properties they had added or bought policies for, they could be driven to finish the others to “complete” the process.
In multiple places, including in the Properties tab, we implemented the ability to see which properties needed policies and have a prominent CTA to add a policy. It also gave them a second (more commonly visited) place to keep an eye on whether their policies are up to date or not, which of course could drive them towards checking out a quote with us before renewing.
In multiple places, including in the Properties tab, we implemented the ability to see which properties needed policies and have a prominent CTA to add a policy. It also gave them a second (more commonly visited) place to keep an eye on whether their policies are up to date or not, which of course could drive them towards checking out a quote with us before renewing.
The end result
