Should EdgeVerve prioritize expanding Finacle's cloud-native capabilities or focus on enhancing its on-premises features to cater to traditional banking clients?

Introduction

The trade-off we're examining today is whether EdgeVerve should prioritize expanding Finacle's cloud-native capabilities or focus on enhancing its on-premises features to cater to traditional banking clients. This decision is crucial for Finacle's future positioning in the rapidly evolving banking software market. I'll analyze this trade-off by considering market trends, client needs, technical feasibility, and business impact.

Step 1

Clarifying Questions (3 minutes)

• Based on market trends, I'm thinking cloud adoption in banking is accelerating. Could you share insights on the current cloud vs. on-premises split in Finacle's client base?

Why it matters: Helps gauge the urgency of cloud migration and potential market size. Expected answer: 30% cloud, 70% on-premises Impact on approach: Higher on-premises percentage might favor enhancing those features first.

• 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 long-term value?

Why it matters: Influences the financial implications of our strategy. Expected answer: Cloud offerings have higher margins and recurring revenue. Impact on approach: Strong cloud profitability would support prioritizing cloud capabilities.

• Looking at user impact, I'm curious about the pain points our traditional banking clients face with the current on-premises solution. What are the top 3 feature requests or issues they've reported?

Why it matters: Identifies immediate opportunities for on-premises improvements. Expected answer: Security enhancements, integration capabilities, and performance optimization. Impact on approach: Critical on-premises needs might necessitate balancing both strategies.

• From a technical perspective, I'm wondering about the complexity of migrating existing on-premises features to a cloud-native architecture. What's our current estimate for this process?

Why it matters: Assesses feasibility and resource requirements for cloud expansion. Expected answer: 12-18 months for core features, with ongoing optimization. Impact on approach: Longer migration time might favor a phased approach or parallel development.

• Regarding our development resources, how is our team currently structured between cloud and on-premises expertise? Are we equipped to pursue both strategies simultaneously?

Why it matters: Determines our capacity to execute on different strategies. Expected answer: 60% cloud-focused, 40% on-premises specialists. Impact on approach: Team composition might influence which strategy we can effectively pursue.