Should Enghouse Interactive prioritize expanding VidyoCloud's video collaboration features or improving its integration with existing contact center systems?

Introduction

The trade-off we're examining today is whether Enghouse Interactive should prioritize expanding VidyoCloud's video collaboration features or improving its integration with existing contact center systems. This decision is crucial for the company's product strategy and market positioning. I'll analyze this trade-off by considering user needs, technical feasibility, business impact, and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking VidyoCloud is a relatively new offering in Enghouse's portfolio. Could you provide some background on its current market position and adoption rate?

Why it matters: Helps gauge the product's maturity and existing user base Expected answer: Moderate adoption, growing steadily Impact on approach: Would influence whether to focus on core features or integrations

• Business Context: Based on industry trends, I assume video collaboration is a key growth area. How does VidyoCloud's performance align with Enghouse's overall revenue targets?

Why it matters: Determines the urgency and resources we might allocate Expected answer: Significant contributor to future growth projections Impact on approach: High alignment would justify more aggressive feature expansion

• User Impact: I'm curious about our user segments. Are we primarily serving enterprise clients with existing contact center solutions, or are we targeting new markets?

Why it matters: Influences whether to prioritize integration or standalone features Expected answer: Mix of existing enterprise clients and new market segments Impact on approach: Balanced approach might be necessary to serve both groups

• Technical: Regarding our current integration capabilities, what's the level of complexity in connecting VidyoCloud with various contact center systems?

Why it matters: Assesses the technical effort required for integration improvements Expected answer: Moderate complexity due to diverse legacy systems Impact on approach: High complexity might favor focusing on our own feature set first

• Resource: Can you give me an idea of our current team structure? Are we better staffed for feature development or integration work?

Why it matters: Helps understand our execution capabilities Expected answer: Stronger in feature development, integration team being built Impact on approach: Might lean towards feature expansion in the short term