How can Thryv enhance its CRM functionality to better support multi-location businesses?

Introduction

Enhancing Thryv's CRM functionality to better support multi-location businesses is a critical challenge that requires a deep understanding of user needs and market dynamics. I'll approach this by first clarifying our objectives, then analyzing user segments and pain points, before proposing and evaluating solutions. Let's dive in.

Step 1

Clarifying Questions

• Looking at the product context, I'm thinking Thryv might be targeting small to medium-sized businesses with multiple locations. Could you confirm the primary user base and their typical business size?

Why it matters: This helps us tailor solutions to the specific needs of our target users. Expected answer: Small to medium businesses with 2-10 locations. Impact on approach: Would focus on scalable solutions that work across different location sizes.

• Considering user behavior, I'm curious about how these multi-location businesses currently use Thryv's CRM. What are the most common cross-location CRM activities?

Why it matters: Identifies key areas for improvement and potential feature expansions. Expected answer: Customer data sharing, appointment scheduling across locations, centralized reporting. Impact on approach: Would prioritize features that enhance these core activities.

• Regarding pain points and market position, how does Thryv currently compare to competitors in serving multi-location businesses?

Why it matters: Helps identify gaps in the market and areas where we can differentiate. Expected answer: Strong in single-location features, but lacking in multi-location coordination. Impact on approach: Would focus on developing unique multi-location capabilities.

• Considering the product lifecycle, where is Thryv in its growth trajectory, and what key metrics are driving this improvement initiative?

Why it matters: Determines if we optimize for scale, feature expansion, or user retention. Expected answer: Steady growth phase with increasing customer acquisition costs. Impact on approach: Would balance new feature development with optimizing existing functionality.