Should BMC Software prioritize expanding the feature set of Control-M for cloud environments or focus on improving its on-premises functionality?

Introduction

The trade-off we're examining today is whether BMC Software should prioritize expanding Control-M's feature set for cloud environments or focus on improving its on-premises functionality. This decision is crucial for BMC's product strategy and market positioning in the evolving IT operations management landscape. I'll analyze this trade-off by considering market trends, user needs, technical feasibility, and business impact.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking Control-M is a critical product for BMC. Could you share its current market share and growth rate in both on-premises and cloud segments?

Why it matters: Helps understand the product's current position and growth trajectory Expected answer: Strong on-premises presence, growing cloud adoption Impact on approach: Would influence resource allocation between cloud and on-premises development

• Business Context: Based on industry trends, I assume cloud adoption is a strategic priority. How does cloud revenue compare to on-premises for Control-M currently?

Why it matters: Indicates the urgency of cloud expansion vs. on-premises improvement Expected answer: Cloud revenue growing faster but smaller overall Impact on approach: Would affect the balance of short-term vs. long-term focus

• User Impact: I'm guessing many enterprise customers are in hybrid environments. What percentage of our users are purely on-premises, purely cloud, or hybrid?

Why it matters: Helps prioritize features based on user segment needs Expected answer: Majority in hybrid, significant on-premises, growing cloud-only Impact on approach: Would guide feature prioritization and development focus

• Technical: Considering the complexity of Control-M, how much of the current codebase is shared between on-premises and cloud versions?

Why it matters: Affects the efficiency of developing for both environments simultaneously Expected answer: Significant shared codebase with some environment-specific components Impact on approach: Would influence the feasibility of parallel development strategies

• Resource: Given our current team structure, what's the split of engineering resources dedicated to cloud vs. on-premises development?

Why it matters: Indicates current resource allocation and potential for reallocation Expected answer: More resources on on-premises, growing investment in cloud Impact on approach: Would inform staffing and budget decisions for each focus area