In what ways can Finastra optimize its Fusion Treasury solution to better address the needs of corporate treasurers?

Introduction

To optimize Finastra's Fusion Treasury solution for corporate treasurers, we need to thoroughly analyze the current product, understand user needs, and develop strategic improvements. I'll approach this by examining key stakeholders, identifying pain points, generating solutions, and proposing metrics for success.

Step 1

Clarifying Questions (5 mins)

• Looking at the product context, I'm thinking Fusion Treasury might be targeting mid to large-sized corporations. Could you clarify the primary user base and their typical company sizes?

Why it matters: Determines the complexity and scale of features needed Expected answer: Primarily large multinational corporations Impact on approach: Would focus on advanced features for complex treasury operations

• Considering the evolving financial landscape, I'm curious about the current integration capabilities. How well does Fusion Treasury currently integrate with other financial systems and what are the most requested integrations?

Why it matters: Identifies potential areas for improvement in connectivity Expected answer: Basic integration with ERP systems, but lacking in real-time data exchange Impact on approach: Would prioritize enhancing API capabilities and real-time data processing

• Given the increasing importance of risk management, I'm wondering about the current risk analytics features. What types of risk analysis does Fusion Treasury currently offer, and what are users asking for?

Why it matters: Helps identify gaps in risk management capabilities Expected answer: Basic interest rate and FX risk analysis, but lacking in advanced scenario modeling Impact on approach: Would focus on developing more sophisticated risk modeling and predictive analytics

• Considering the shift towards cloud-based solutions, I'm interested in understanding the current deployment model. Is Fusion Treasury primarily on-premise, cloud-based, or a hybrid solution?

Why it matters: Influences the approach to scalability and feature updates Expected answer: Primarily on-premise with a growing cloud-based offering Impact on approach: Would prioritize cloud migration and developing cloud-native features