How can Ualá balance offering competitive interest rates on savings accounts with maintaining profitability in its lending operations?

Introduction

Balancing competitive interest rates on savings accounts with maintaining profitability in lending operations is a critical challenge for Ualá. This trade-off involves managing the cost of funds against the revenue generated from loans, while ensuring customer satisfaction and market competitiveness. I'll analyze this problem by examining the product ecosystem, identifying key metrics, designing experiments, and providing a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Business Context: I'm thinking Ualá's revenue model relies heavily on the spread between savings and lending rates. Could you share how significant this spread is to our overall profitability?

Why it matters: Helps quantify the impact of rate changes on the bottom line Expected answer: Spread accounts for 60-70% of revenue Impact on approach: Would focus on optimizing this spread while exploring alternative revenue streams

• User Impact: Based on our user base, I'm assuming we have distinct segments of savers and borrowers. Can you provide insights into the overlap between these groups and their price sensitivity?

Why it matters: Informs how rate changes might affect user behavior and retention Expected answer: 30% overlap, with savers more price-sensitive than borrowers Impact on approach: Would consider segmented strategies and personalized offerings

• Technical Feasibility: Considering our current tech stack, I'm curious about our ability to implement dynamic pricing. How flexible is our system for adjusting rates based on user behavior or market conditions?

Why it matters: Determines the granularity and speed of potential solutions Expected answer: Moderate flexibility, with weekly rate adjustments possible Impact on approach: Would explore gradual implementation of more dynamic pricing models

• Resource Allocation: Given the importance of this issue, I'm wondering about our capacity to dedicate resources to this problem. What's our current bandwidth for product and engineering teams to work on this?

Why it matters: Helps scope the scale and timeline of potential solutions Expected answer: Limited bandwidth, with 1-2 sprints available in the next quarter Impact on approach: Would prioritize high-impact, low-effort solutions initially

• Timeline and Urgency: Considering market dynamics, I'm thinking this might be a pressing issue. How urgent is addressing this trade-off, and are there any upcoming milestones or competitor moves we need to consider?

Why it matters: Helps prioritize this issue against other product initiatives Expected answer: High urgency due to increasing competition and Q4 targets Impact on approach: Would focus on quick wins while developing a longer-term strategy