What new features could Smarsh add to its Voice Capture service to better support financial services compliance?

Introduction

To improve Smarsh's Voice Capture service for financial services compliance, we need to identify new features that enhance its functionality, user experience, and overall value proposition. I'll analyze the current product, user needs, and market trends to propose strategic improvements that align with compliance requirements and user expectations.

Step 1

Clarifying Questions (5 mins)

• Looking at the financial services industry, I'm thinking compliance requirements are constantly evolving. Could you share insights on recent regulatory changes affecting voice capture requirements?

Why it matters: Determines if we need to focus on new compliance features or optimize existing ones. Expected answer: Recent regulations require more granular metadata and longer retention periods. Impact on approach: Would prioritize features enhancing metadata capture and storage capabilities.

• Considering the user base, I'm curious about the primary pain points reported by financial institutions using Voice Capture. What are the top 3 issues customers frequently mention?

Why it matters: Helps identify areas for immediate improvement and long-term strategic focus. Expected answer: Integration complexity, search functionality limitations, and scalability issues. Impact on approach: Would focus on simplifying integration, enhancing search, and improving infrastructure.

• Examining the competitive landscape, I'm wondering about Smarsh's current market position. How does our Voice Capture service compare to key competitors in terms of market share and feature set?

Why it matters: Informs whether we should focus on differentiation or catching up to industry standards. Expected answer: Strong market share but lagging in AI-powered analytics compared to newer entrants. Impact on approach: Would prioritize AI and machine learning capabilities to maintain competitive edge.

• Considering product maturity, I'm interested in understanding the current adoption rate and user engagement metrics. What percentage of Smarsh's customer base actively uses Voice Capture, and how frequently?

Why it matters: Helps determine if we should focus on acquisition or retention/engagement features. Expected answer: 60% adoption rate with daily usage among active users. Impact on approach: Would balance between features to drive adoption and those enhancing daily workflows.