Is expanding cloud services worth the potential cannibalization of MongoDB's on-premises deployments?

Introduction

The trade-off we're examining today is whether expanding MongoDB's cloud services is worth the potential cannibalization of its on-premises deployments. This scenario touches on the core of MongoDB's business model and future growth strategy. I'll analyze the key aspects of this trade-off, including product understanding, potential impacts, metrics, experimentation, and decision-making framework.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming MongoDB is seeing increased demand for cloud services. Could you confirm if this is driven by market trends or specific customer requests?

Why it matters: Helps understand the urgency and potential market size Expected answer: Mix of both, with a trend towards cloud adoption Impact on approach: Would influence the speed and scale of cloud expansion

• Business Context: Based on MongoDB's current revenue split, I'm thinking on-premises deployments still form a significant portion. What's the current revenue breakdown between on-premises and cloud services?

Why it matters: Helps quantify the potential cannibalization risk Expected answer: On-premises still dominant, but cloud growing faster Impact on approach: Would affect the balance of resources allocated to each

• User Impact: I'm assuming different customer segments have varying cloud adoption rates. Can you share insights on which customer segments are driving cloud demand?

Why it matters: Helps tailor the expansion strategy to specific user needs Expected answer: Larger enterprises moving slower, startups and SMBs faster Impact on approach: Would influence targeted marketing and feature development

• Technical: Considering the complexity of database migrations, I'm curious about the current ease of transitioning from on-premises to cloud. What's the current state of MongoDB's migration tools and processes?

Why it matters: Affects the friction in the cannibalization process Expected answer: Tools exist but there's room for improvement Impact on approach: Would highlight areas for technical investment

• Resource: Given the potential scale of this initiative, I'm wondering about our current team structure. How are our engineering and sales teams currently split between on-premises and cloud focuses?

Why it matters: Indicates our readiness for a potential shift Expected answer: Still primarily on-premises focused Impact on approach: Would inform hiring and training needs