Should Qumulo prioritize expanding its cloud-native file system features or focus on enhancing on-premises storage solutions to meet diverse customer needs?

Introduction

The trade-off question at hand is whether Qumulo should prioritize expanding its cloud-native file system features or focus on enhancing on-premises storage solutions to meet diverse customer needs. This scenario involves balancing the company's resources and strategic direction between two critical areas of its product offering. My response will analyze this trade-off, considering various factors such as market trends, customer needs, and technical feasibility.

Step 1

Clarifying Questions (3 minutes)

• Based on market trends, I'm thinking cloud adoption is accelerating. Could you share insights on the current split between Qumulo's cloud and on-premises customers?

Why it matters: Helps gauge market demand and potential growth areas Expected answer: 60% on-premises, 40% cloud, with cloud growing faster Impact on approach: Higher cloud percentage would favor cloud-native feature development

• Considering our revenue model, I assume we have different pricing structures for cloud and on-premises solutions. How do these compare in terms of profitability and customer lifetime value?

Why it matters: Informs resource allocation based on financial impact Expected answer: Cloud solutions have higher margins but shorter contracts Impact on approach: Higher cloud profitability might justify more investment in cloud features

• Regarding user impact, are there specific customer segments or industries that are more reliant on on-premises solutions due to regulatory or security concerns?

Why it matters: Identifies potential risks of neglecting on-premises development Expected answer: Healthcare and finance sectors have stricter on-premises requirements Impact on approach: Strong on-premises demand in key sectors would necessitate balanced development

• From a technical perspective, how much of our codebase is shared between cloud and on-premises solutions?

Why it matters: Assesses the efficiency of development efforts across both areas Expected answer: 70% shared codebase with 30% platform-specific code Impact on approach: High shared codebase would suggest potential for simultaneous improvements

• Considering our current team structure, do we have separate teams for cloud and on-premises development, or is it a unified team?

Why it matters: Influences the feasibility of parallel development efforts Expected answer: Unified team with some specialists for each platform Impact on approach: Unified team might favor a balanced development strategy