Should Segment prioritize adding new integrations or improving existing ones?

Introduction

The trade-off question at hand is whether Segment should prioritize adding new integrations or improving existing ones. This scenario involves balancing the expansion of our product's capabilities against enhancing the quality and performance of our current offerings. I'll approach this analysis by examining the context, evaluating potential impacts, and proposing a data-driven decision framework.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming Segment is facing pressure to expand its integration ecosystem. Could you provide more context on the current market demands and competitive landscape?

Why it matters: Helps understand the urgency of new integrations vs. improving existing ones. Expected answer: Increasing competition in the CDP space with new players offering more integrations. Impact on approach: Would influence the balance between growth and consolidation strategies.

• Business Context: Based on our revenue model, I'm thinking a significant portion comes from enterprise clients. How does our current pricing structure relate to the number and quality of integrations?

Why it matters: Determines if new integrations or improved existing ones have a more direct impact on revenue. Expected answer: Tiered pricing based on number of integrations used, with enterprise plans including premium support. Impact on approach: Would help prioritize between adding new integrations for upselling or improving existing ones for retention.

• User Impact: Considering our user base, I'm assuming we have a mix of technical and non-technical users. Can you share insights on the most common user pain points related to integrations?

Why it matters: Identifies whether users are more frustrated by limited integration options or issues with existing ones. Expected answer: Technical users want more advanced integrations, while non-technical users struggle with existing integration reliability. Impact on approach: Would guide the focus on either expanding the integration catalog or improving user experience and reliability.

• Technical Feasibility: Given our current architecture, I'm thinking about the complexity of adding new integrations versus optimizing existing ones. What's our engineering team's assessment of the technical debt in our integration codebase?

Why it matters: Determines the feasibility and resource requirements for both options. Expected answer: Moderate technical debt, with some legacy integrations requiring significant refactoring. Impact on approach: Would influence the balance between innovation and maintenance efforts.

• Resource Allocation: Considering our team structure, I'm curious about our current capacity for integration development and maintenance. How are our engineering resources currently split between new development and support for existing integrations?

Why it matters: Helps understand the feasibility of pursuing both strategies simultaneously. Expected answer: 70% new development, 30% maintenance and support. Impact on approach: Would inform how we might need to reallocate resources based on our chosen strategy.