Should AppFolio prioritize adding new features to its property management software or focus on improving the stability and performance of existing functionality?

Introduction

The trade-off between adding new features to AppFolio's property management software and improving the stability and performance of existing functionality is a critical decision that impacts user satisfaction, market competitiveness, and long-term product success. This scenario requires careful consideration of various factors, including user needs, technical constraints, and business objectives. I'll analyze this trade-off using a structured approach, considering both short-term gains and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about the current market position of AppFolio. Could you share insights on our market share and primary competitors in the property management software space?

Why it matters: Helps assess the urgency of new features vs. stability improvements Expected answer: Moderate market share with 2-3 strong competitors Impact on approach: High competition might lean towards new features, while market leadership could prioritize stability

• Business Context: Based on our revenue model, I assume we operate on a subscription basis. What's the breakdown between new customer acquisition and existing customer retention in terms of revenue growth?

Why it matters: Influences whether to focus on attracting new users or retaining existing ones Expected answer: 60% from existing customers, 40% from new acquisitions Impact on approach: Higher retention importance would favor stability improvements

• User Impact: Considering our user segments, are we seeing any particular pain points or feature requests consistently across different property types or management company sizes?

Why it matters: Helps prioritize specific features or stability issues Expected answer: Small to medium-sized property managers requesting more automation features Impact on approach: Could guide the type of new features to prioritize if that direction is chosen

• Technical: Regarding our current technical debt, what's the assessment of our engineering team on the stability of our core functionality?

Why it matters: Determines the urgency of addressing stability issues Expected answer: Moderate technical debt with occasional performance issues during peak usage Impact on approach: Significant stability concerns would shift focus towards improvement of existing features

• Resource: Can you provide an overview of our current team capacity and any planned hiring in product and engineering roles?

Why it matters: Assesses our ability to tackle both new features and stability improvements simultaneously Expected answer: Fully staffed product team, engineering team at 80% capacity with ongoing hiring Impact on approach: Limited resources might necessitate a more focused strategy on either new features or stability