Should Vestwell prioritize expanding its recordkeeping capabilities or focus on enhancing its advisor-facing tools to improve user experience?

Introduction

The trade-off we're examining today is whether Vestwell should prioritize expanding its recordkeeping capabilities or focus on enhancing its advisor-facing tools to improve user experience. This decision is crucial for Vestwell's growth strategy and market positioning in the fintech space. I'll analyze this trade-off by considering the business context, user impact, technical feasibility, and resource allocation. Let's dive into the details to determine the best path forward.

Step 1

Clarifying Questions (3 minutes)

• Based on Vestwell's current market position, I'm thinking recordkeeping might be a core differentiator. Could you share how our recordkeeping capabilities compare to our main competitors?

Why it matters: Helps assess the urgency of improving this area Expected answer: We're lagging in some key recordkeeping features Impact on approach: Would prioritize recordkeeping if we're significantly behind

• Considering our revenue model, I assume advisor satisfaction directly impacts our bottom line. What percentage of our revenue is tied to advisor-driven business?

Why it matters: Determines the financial impact of focusing on advisor tools Expected answer: 70-80% of revenue is advisor-driven Impact on approach: High percentage would lean towards prioritizing advisor tools

• Looking at user behavior, I'm curious about advisor engagement with our current tools. What's the adoption rate of our existing advisor-facing features?

Why it matters: Indicates whether low adoption is due to poor UX or lack of features Expected answer: Moderate adoption with room for improvement Impact on approach: Low adoption might suggest prioritizing UX enhancements

• From a technical standpoint, I'm wondering about the complexity of expanding our recordkeeping capabilities. How integrated is our current recordkeeping system with other core functionalities?

Why it matters: Assesses the technical effort required for recordkeeping expansion Expected answer: Moderately integrated, requiring significant development work Impact on approach: High complexity might favor focusing on advisor tools first

• Considering our team structure, I'm thinking about our capacity to handle both initiatives simultaneously. How are our engineering and product teams currently allocated between recordkeeping and advisor tools?

Why it matters: Helps understand if we have the resources to pursue both paths Expected answer: Teams are stretched thin, focusing mainly on maintenance Impact on approach: Limited resources might necessitate choosing one priority