For Bilt's credit card, should we emphasize features that drive frequent usage or those that attract new cardholders?

Introduction

The trade-off between emphasizing features that drive frequent usage or those that attract new cardholders for Bilt's credit card is a critical decision that will shape our product strategy and growth trajectory. This scenario involves balancing short-term acquisition goals with long-term engagement and retention objectives. I'll analyze this trade-off by examining the product context, identifying key metrics, designing experiments, and providing a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on the competitive landscape, I'm thinking Bilt might be facing pressure to grow its user base rapidly. Could you share our current market position and growth targets?

Why it matters: Helps prioritize acquisition vs. retention strategies Expected answer: Moderate market share, aggressive growth targets Impact on approach: Would lean towards new cardholder acquisition if growth is the primary goal

• Considering the credit card industry's focus on customer lifetime value, I'm curious about our current user engagement metrics. What's our average transaction frequency and spend per user?

Why it matters: Indicates the potential impact of focusing on frequent usage Expected answer: Below industry average, significant room for improvement Impact on approach: Would emphasize frequent usage features if engagement is low

• Given the unique value proposition of earning points on rent payments, I'm wondering about our user demographics. What percentage of our cardholders are renters vs. homeowners?

Why it matters: Helps tailor features to our core user base Expected answer: Majority renters, but growing homeowner segment Impact on approach: Would influence the balance of rent-related vs. general spending features

• Thinking about our technology stack, I'm curious about our ability to implement and test new features quickly. What's our current release cycle for new card features?

Why it matters: Affects our ability to iterate and experiment Expected answer: Monthly release cycle with some flexibility for faster updates Impact on approach: Would inform the pace and scope of feature rollouts

• Considering the potential resource implications, I'm interested in our current team structure. Do we have dedicated teams for acquisition and engagement, or a single product team?

Why it matters: Influences our ability to execute on both strategies simultaneously Expected answer: Single product team with some specialization Impact on approach: Would need to carefully prioritize resources between acquisition and engagement initiatives