For Wolt's subscription service, should we focus on increasing the subscriber base or maximizing revenue per subscriber?

Introduction

The trade-off we're examining today is whether Wolt's subscription service should focus on increasing the subscriber base or maximizing revenue per subscriber. This scenario involves balancing growth and monetization strategies for a food delivery platform's subscription offering. I'll analyze this trade-off by considering various factors including user behavior, market dynamics, and long-term business implications.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming Wolt's subscription service is relatively new. Could you confirm how long it's been in the market and its current penetration rate among Wolt users?

Why it matters: Helps gauge market maturity and growth potential Expected answer: 6-12 months, 5-10% penetration Impact on approach: Newer service with low penetration would lean towards subscriber growth

• Business Context: Based on Wolt's current strategy, I'm thinking profitability might be a key focus. How does the subscription service fit into Wolt's overall revenue model and near-term financial goals?

Why it matters: Aligns solution with company priorities Expected answer: Subscription is a growing revenue stream, but not yet primary Impact on approach: Balanced approach needed, considering both growth and revenue per user

• User Impact: I'm curious about user behavior patterns. What's the current usage frequency difference between subscribers and non-subscribers?

Why it matters: Indicates value proposition strength and potential for revenue optimization Expected answer: Subscribers order 2-3x more frequently Impact on approach: High usage difference might suggest focusing on conversion to subscription

• Technical: Considering potential scaling, are there any technical limitations to rapidly expanding the subscriber base or implementing personalized pricing?

Why it matters: Influences feasibility of growth-focused or revenue-optimization strategies Expected answer: No major limitations, but some development work required for personalization Impact on approach: Flexibility to pursue either strategy, with some lead time for advanced features

• Resource: Thinking about execution, what's our current team capacity for developing new subscription features or running complex pricing experiments?

Why it matters: Determines scope and timeline of potential solutions Expected answer: Limited bandwidth, 1-2 dedicated engineers Impact on approach: May need to prioritize simpler, high-impact initiatives initially