What improvements could Hagerty make to its online quote tool to streamline the classic car insurance process?

Introduction

To streamline Hagerty's online quote tool for classic car insurance, we need to focus on enhancing user experience, simplifying the data input process, and providing more accurate, personalized quotes. I'll analyze the current system, identify key pain points, and propose targeted improvements to make the quoting process more efficient and user-friendly for classic car enthusiasts.

Step 1

Clarifying Questions (5 mins)

• Looking at the product context, I'm thinking Hagerty might be facing challenges with user drop-off during the quoting process. Could you share some data on the current conversion rate from quote initiation to completion?

Why it matters: Helps identify where users are struggling most in the process Expected answer: 40% completion rate with significant drop-off at vehicle details stage Impact on approach: Would focus on simplifying vehicle information input

• Considering user behavior, I'm curious about the device preferences of our target audience. What's the current split between desktop and mobile users accessing the quote tool?

Why it matters: Determines if we need to prioritize mobile optimization Expected answer: 60% mobile, 40% desktop Impact on approach: Would emphasize mobile-first design and responsive features

• Examining Hagerty's market position, I'm wondering about the competitive landscape. How does our quote completion time compare to other classic car insurers?

Why it matters: Identifies if speed is a key differentiator or pain point Expected answer: Our process takes 2-3 minutes longer than leading competitors Impact on approach: Would focus on streamlining and automating parts of the process

• Considering the product lifecycle, I'm interested in understanding the tool's current stage. How long has the current version been live, and what were the last major updates?

Why it matters: Helps determine if we need an overhaul or incremental improvements Expected answer: Current version is 2 years old with minor UI updates 6 months ago Impact on approach: Would suggest a more comprehensive redesign