I designed an insurance application workflow to provide property insurance to property investors. The product went through multiple iterations from the 1st generation of the product to what I’m proposing as the 3rd generation here.
TO launch an insurance quoting/application service FOR property investors SO they may receive a property insurance quote in minutes utilizing a vendor API.
https://www.loom.com/share/8a5b65a6c84446d5ac36ec02480921e2?sid=b946c71e-e9ea-4056-bacf-2d91312002fc
The first version (1st generation) we built worked fairly well, however, the requirement on the applicant was they would need to manually enter all the necessary property information to receive a real-time property insurance quote. From the video (above) I’m showing the 3rd version which reduces/removes much of the manual entry of property info. by the property investor.
Flow of the 1st version (above) is more manual requiring the user to know all the information about their property (unlikely) and have to enter it manually.
Flow of the 3rd version of the insurance quoting workflow (above) incorporates data lookup, reduces the number of screens reducing the need to manually enter the information, or know all of the information about the property.
Above is a walkthrough of the first version of the applicaton.
Above is a walkthrough of the first version of the applicaton.