How can ThoughtSpot balance the need for customization in ThoughtSpot Everywhere with maintaining a consistent user experience across embedded analytics implementations?

Introduction

Balancing customization in ThoughtSpot Everywhere with maintaining a consistent user experience across embedded analytics implementations is a critical challenge. This scenario involves weighing the benefits of flexibility against the need for coherence in our product offering. I'll address this trade-off by analyzing key factors, proposing metrics, and outlining an experimental approach to guide our decision-making process.

Step 1

Clarifying Questions (3 minutes)

• Based on our current market position, I'm thinking this customization vs. consistency issue might be driven by competitive pressures. Could you share insights on how our main competitors are handling embedded analytics customization?

Why it matters: Helps understand market dynamics and customer expectations Expected answer: Competitors offer varying degrees of customization Impact on approach: Would influence how aggressively we pursue customization

• Considering our revenue model, I assume ThoughtSpot Everywhere is a key growth driver. Can you confirm its contribution to our overall revenue and growth targets?

Why it matters: Aligns solution with business priorities Expected answer: Significant revenue contributor with high growth expectations Impact on approach: Would justify more resources for a balanced solution

• Regarding user impact, I'm thinking about the diversity of our client base. Can you provide an overview of the main industry verticals and use cases for ThoughtSpot Everywhere?

Why it matters: Helps tailor solution to specific user needs Expected answer: Wide range of industries with varying customization needs Impact on approach: Would inform the degree of flexibility needed in our solution

• On the technical side, I'm curious about our current architecture. How modular is our codebase, and what's our capacity for supporting varied customizations without compromising core functionality?

Why it matters: Determines feasibility and scalability of customization options Expected answer: Moderately modular with some limitations Impact on approach: Would influence the extent of customization we can offer

• Regarding timeline, is there a specific market event or customer commitment driving urgency for this decision?

Why it matters: Helps prioritize and scope the solution Expected answer: Upcoming major release or strategic partnership Impact on approach: Would impact the aggressiveness of our implementation strategy