Should Enfusion prioritize adding new asset classes to its multi-asset class portfolio management platform or focus on deepening functionality for existing asset types?

Introduction

The trade-off question at hand is whether Enfusion should prioritize adding new asset classes to its multi-asset class portfolio management platform or focus on deepening functionality for existing asset types. This scenario involves balancing the expansion of product capabilities against the refinement of current offerings. I'll approach this analysis by examining the context, evaluating potential impacts, designing experiments, and providing a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on Enfusion's market position, I'm thinking this decision could significantly impact our competitive advantage. Could you provide more context on our current market share and main competitors in the multi-asset class portfolio management space?

Why it matters: Helps assess the urgency of expansion vs. deepening functionality Expected answer: Moderate market share with increasing competition Impact on approach: Would influence whether to focus on differentiation or market expansion

• Considering our revenue model, I assume we charge based on assets under management (AUM) or number of portfolios. Is this correct, and how does pricing vary across different asset classes?

Why it matters: Informs the potential revenue impact of adding new asset classes Expected answer: Tiered pricing based on AUM with some variation by asset class complexity Impact on approach: Would affect the financial analysis of expanding into new asset classes

• Regarding user impact, I'm curious about the distribution of our client base across different asset classes. What percentage of our clients are currently using multiple asset classes on our platform?

Why it matters: Helps understand the demand for new asset classes vs. deeper functionality Expected answer: Majority of clients use 2-3 asset classes, with some using more Impact on approach: Would influence whether to prioritize breadth or depth of offerings

• From a technical perspective, I'm wondering about the modularity of our current platform architecture. How easily can we add new asset classes without disrupting existing functionality?

Why it matters: Assesses the feasibility and potential risks of platform expansion Expected answer: Moderately modular, but some integration challenges exist Impact on approach: Would impact the timeline and resource allocation for adding new asset classes

• Considering resource constraints, what's our current capacity for taking on new development projects? Are we fully utilized or do we have flexibility?

Why it matters: Determines the feasibility of pursuing both options simultaneously Expected answer: Near full capacity with some flexibility for high-priority projects Impact on approach: Would influence whether to choose one direction or attempt a balanced approach