For Cribl Stream, should we invest in developing more pre-built functions or improve the customization options for existing functions?

Introduction

The trade-off we're considering for Cribl Stream is whether to invest in developing more pre-built functions or improve the customization options for existing functions. This decision is crucial for the product's evolution and its ability to meet diverse user needs. I'll analyze this trade-off by examining the product context, potential impacts, key metrics, and experimental approaches to guide our decision-making process.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Cribl Stream's current market position. Could you share our market share and primary competitors in the observability data pipeline space?

Why it matters: Helps gauge competitive pressure and market opportunity Expected answer: Growing market share, competing with established players Impact on approach: Would influence whether to focus on differentiation or feature parity

• Business Context: Based on our revenue model, I assume most of our income comes from enterprise licenses. Is this correct, and are there any specific verticals we're targeting for growth?

Why it matters: Aligns product strategy with revenue goals and target markets Expected answer: Primarily enterprise licenses, targeting finance and healthcare Impact on approach: Would prioritize features most valuable to key verticals

• User Impact: I'm curious about our user segments. What's the split between those who primarily use pre-built functions versus those who heavily customize?

Why it matters: Identifies which user group might benefit most from each option Expected answer: 60% pre-built, 40% custom, with enterprise users customizing more Impact on approach: Would help balance resource allocation between options

• Technical: Regarding our current architecture, how modular is our function system? Could we easily add new pre-built functions or enhance customization without major refactoring?

Why it matters: Assesses technical feasibility and potential development costs Expected answer: Modular system, but customization enhancements might require more work Impact on approach: Would influence development timeline and resource allocation

• Resource: Considering our current team structure, do we have specialized teams for pre-built functions and customization features, or is it a shared resource pool?

Why it matters: Determines if we have the right expertise and capacity for each option Expected answer: Shared resource pool with some specialization Impact on approach: Might need to consider team restructuring or hiring