Should Pantheon prioritize expanding its WordPress hosting capabilities to attract more users, or focus on enhancing Drupal support to retain its core customer base?

Introduction

The trade-off we're examining today is whether Pantheon should prioritize expanding its WordPress hosting capabilities to attract more users or focus on enhancing Drupal support to retain its core customer base. This scenario touches on the classic product dilemma of growth versus retention, set against the backdrop of the competitive web hosting industry. I'll analyze this trade-off through multiple lenses, considering business impact, user needs, technical feasibility, and strategic alignment.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Pantheon's current market position. Could you share our current market share in WordPress versus Drupal hosting, and how that's changed over the past year?

Why it matters: Helps understand the growth trajectory and potential market opportunity Expected answer: Stronger in Drupal, but WordPress market share growing Impact on approach: Would influence resource allocation between the two platforms

• Business Context: Based on our revenue model, I assume we charge differently for WordPress and Drupal hosting. Can you confirm if there's a significant difference in average revenue per user (ARPU) between these two segments?

Why it matters: Affects the financial impact of focusing on one platform over the other Expected answer: Drupal hosting likely has higher ARPU due to enterprise focus Impact on approach: Would influence the revenue projections for each option

• User Impact: I'm curious about user behavior. Do we have data on the churn rates for our WordPress users compared to our Drupal users?

Why it matters: Helps assess the retention risk and potential impact of focusing on one platform Expected answer: Lower churn rate for Drupal users due to more established relationships Impact on approach: Would affect the prioritization of retention versus acquisition strategies

• Technical: Considering the different architectures of WordPress and Drupal, how much overlap is there in our current hosting infrastructure that could be leveraged for expansion?

Why it matters: Affects the technical feasibility and resource requirements for expansion Expected answer: Some overlap, but significant differences requiring separate development Impact on approach: Would influence the timeline and cost estimates for each option

• Resource: Given our current team structure, how are our engineering and support resources currently split between WordPress and Drupal?

Why it matters: Helps understand the current resource allocation and potential for reallocation Expected answer: Majority focused on Drupal, with growing WordPress team Impact on approach: Would impact the feasibility of quickly scaling up efforts in either direction