Should Curve prioritize adding more supported banks and cards to its app or focus on improving the stability and performance of existing integrations?

Introduction

The trade-off we're examining today is whether Curve should prioritize adding more supported banks and cards to its app or focus on improving the stability and performance of existing integrations. This decision is crucial for Curve's growth strategy and user satisfaction. I'll analyze this trade-off by considering user needs, business objectives, and technical implications.

Step 1

Clarifying Questions (3 minutes)

• Business Context: I'm thinking Curve's revenue model might be based on transaction fees or premium subscriptions. Could you clarify how Curve generates revenue and how this decision might impact our financial goals?

Why it matters: Helps align the solution with revenue streams Expected answer: Revenue from transaction fees and premium features Impact on approach: Would influence whether to focus on volume (more banks) or retention (better performance)

• User Impact: Based on user behavior, I'm assuming our active users frequently switch between cards. Can you share data on how often users change cards and which user segments are most affected by integration issues?

Why it matters: Identifies key user pain points and priorities Expected answer: Power users switch cards frequently and face most integration issues Impact on approach: Would help prioritize stability for power users vs. expansion for new users

• Technical Feasibility: Considering our current architecture, I'm thinking scaling to more banks might be challenging. What are the main technical hurdles for adding new integrations vs. improving existing ones?

Why it matters: Assesses technical complexity and resource requirements Expected answer: Adding banks requires significant API work, while improving stability involves optimizing existing systems Impact on approach: Would influence resource allocation and timeline estimates

• Resource Allocation: Given our team structure, I'm assuming we have separate teams for integrations and performance. How are our engineering resources currently distributed between these areas?

Why it matters: Determines our capacity to execute on either option Expected answer: Limited resources, with more focus on new integrations Impact on approach: Might suggest a phased approach or reallocation of resources

• Timeline and Urgency: Considering market dynamics, I'm thinking there might be pressure to expand quickly. What's our timeline for achieving significant growth, and how urgent is the need to improve existing integrations?

Why it matters: Balances short-term gains with long-term stability Expected answer: Aggressive growth targets for the next year, but increasing user complaints about stability Impact on approach: Would help prioritize immediate expansion vs. building a stable foundation for future growth