Is it better for Segment to focus on enterprise features or expand our self-serve offering?

Introduction

The trade-off between focusing on enterprise features or expanding our self-serve offering at Segment is a critical decision that will shape our product strategy and market positioning. This scenario involves balancing the needs of high-value enterprise clients with the potential for broader market penetration through self-service options. I'll analyze this trade-off by examining our product understanding, potential impacts, key metrics, and experimental approach to arrive at a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about our current market position. Could you share our current revenue split between enterprise and self-serve customers?

Why it matters: Helps understand the potential impact on our revenue streams Expected answer: 70% enterprise, 30% self-serve Impact on approach: A higher enterprise percentage might justify focusing on those features

• Business Context: Based on our growth targets, I'm curious about our acquisition costs. How do customer acquisition costs (CAC) compare between enterprise and self-serve segments?

Why it matters: Informs the efficiency of our growth strategies Expected answer: Enterprise CAC is significantly higher Impact on approach: Lower self-serve CAC could make expansion more attractive

• User Impact: Considering user behavior, what's the typical conversion rate from self-serve to enterprise?

Why it matters: Indicates the potential for self-serve as a pipeline for enterprise customers Expected answer: 10-15% of self-serve users upgrade to enterprise within 12 months Impact on approach: A high conversion rate could justify expanding self-serve as an enterprise onboarding strategy

• Technical: Thinking about our architecture, how much of our current codebase is shared between enterprise and self-serve offerings?

Why it matters: Affects the feasibility and efficiency of developing for both segments Expected answer: 60% shared codebase Impact on approach: A higher shared percentage could make dual development more efficient

• Resource: Given our current team structure, what's the split of engineering resources dedicated to enterprise vs. self-serve features?

Why it matters: Indicates our current focus and capacity for shifts Expected answer: 70% enterprise, 30% self-serve Impact on approach: A significant imbalance might require careful resource reallocation