Should Solaris prioritize expanding its Banking-as-a-Service API features or focus on improving the user interface of its white-label banking platform?

Introduction

The trade-off we're examining today is whether Solaris should prioritize expanding its Banking-as-a-Service API features or focus on improving the user interface of its white-label banking platform. This decision is crucial for Solaris' product strategy and market positioning. I'll analyze this trade-off by examining the business context, user impact, technical considerations, and potential outcomes. My approach will involve clarifying the situation, understanding the products, identifying key metrics, designing experiments, and providing a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on recent fintech trends, I'm thinking API expansion might be critical for attracting new partners. Could you share how our current API offering compares to competitors like Stripe or Plaid?

Why it matters: Helps assess market positioning and potential growth areas Expected answer: We're competitive in core banking APIs but lag in specialized features Impact on approach: Would prioritize API expansion if we're significantly behind

• Considering our revenue model, I assume we have a mix of API usage fees and white-label platform subscriptions. What's the current revenue split between these two product lines?

Why it matters: Informs which area might have a larger impact on overall business growth Expected answer: 60% API, 40% white-label platform Impact on approach: Higher API revenue might justify prioritizing that area

• Looking at user behavior, I'm curious about the adoption rates of our white-label platform. What percentage of our clients fully utilize the platform's features?

Why it matters: Indicates whether UI improvements could significantly boost engagement Expected answer: 70% of features used on average Impact on approach: Lower utilization might suggest focusing on UI improvements

• Regarding technical feasibility, how modular is our current architecture? Could we enhance API features without major overhauls to the white-label platform?

Why it matters: Assesses the complexity and potential timeline of API expansions Expected answer: Moderately modular, some dependencies exist Impact on approach: High modularity might favor API expansion due to easier implementation

• Considering our team structure, do we have separate teams for API development and UI/UX, or is it a shared resource pool?

Why it matters: Influences resource allocation and potential parallel development Expected answer: Partially separated teams with some shared resources Impact on approach: Fully separate teams might allow pursuing both options simultaneously