In Looker's embedded analytics offerings, should we emphasize seamless integration with existing platforms or expand standalone capabilities to attract new customers?

Introduction

The trade-off we're examining today is whether Looker's embedded analytics offerings should prioritize seamless integration with existing platforms or expand standalone capabilities to attract new customers. This decision is crucial for Looker'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)

• Based on our current market position, I'm thinking this decision might significantly impact our competitive advantage. Could you share more about our market share and main competitors in the embedded analytics space?

Why it matters: Helps assess the urgency and potential impact of our decision Expected answer: We're a top player but facing increasing competition Impact on approach: Would influence whether we prioritize differentiation or market expansion

• Considering our revenue model, I assume embedded analytics is a key offering. What percentage of our revenue currently comes from embedded analytics versus standalone products?

Why it matters: Informs the potential business impact of our decision Expected answer: Embedded analytics contributes significantly, perhaps 60-70% of revenue Impact on approach: Would help balance the focus between improving existing offerings and expanding capabilities

• Looking at user behavior, I'm curious about the adoption rates of our current embedded offerings. What percentage of our customers are actively using the embedded features, and how does this compare to standalone usage?

Why it matters: Indicates the current value proposition and potential for growth Expected answer: High adoption rate for embedded features, perhaps 80%+ Impact on approach: Would influence whether to double down on integration or diversify

• From a technical perspective, I'm wondering about the complexity of enhancing our standalone capabilities. How much of our current codebase is shared between embedded and standalone offerings?

Why it matters: Assesses the feasibility and resource requirements for expansion Expected answer: Significant shared codebase, perhaps 70-80% Impact on approach: Would affect the timeline and resource allocation for potential expansion

• Considering our product roadmap, how does this decision align with our long-term strategy? Are there any major platform or architecture changes planned in the next 12-18 months?

Why it matters: Ensures alignment with broader company goals and technical direction Expected answer: Some platform upgrades planned, but flexible on timing Impact on approach: Would influence the timing and scope of our decision implementation