How can TradingView balance offering free access to basic charts and data versus driving subscriptions for premium features?

Introduction

Balancing free access to basic charts and data with driving subscriptions for premium features is a critical trade-off for TradingView. This scenario involves weighing user acquisition and engagement against revenue generation and sustainable growth. I'll analyze this trade-off by examining product understanding, metrics, experimentation, and decision-making frameworks.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking TradingView's current user base might be split between free and paid users. Could you share the current ratio of free to paid users and how it's changed over the past year?

Why it matters: Helps understand the current conversion funnel and potential for growth Expected answer: 80% free, 20% paid, with a slight increase in paid users over the past year Impact on approach: A high free-to-paid ratio might suggest focusing on conversion strategies

• Business Context: Based on industry trends, I assume subscription revenue is a key growth driver. How does subscription revenue compare to other revenue streams, like advertising or data licensing?

Why it matters: Helps prioritize subscription growth against other business objectives Expected answer: Subscriptions account for 60% of revenue, growing faster than other streams Impact on approach: Would justify more aggressive strategies to drive subscriptions

• User Impact: I'm thinking different user segments might have varying needs for premium features. Can you share insights on which user segments are most likely to upgrade to paid subscriptions?

Why it matters: Helps target specific user groups for conversion efforts Expected answer: Active traders and financial professionals are most likely to upgrade Impact on approach: Would focus on enhancing premium features for these high-value segments

• Technical: Considering the importance of real-time data, I'm curious about our infrastructure's ability to handle increased premium feature usage. Are there any technical limitations we should be aware of?

Why it matters: Ensures scalability of premium features Expected answer: Current infrastructure can handle 2x growth in premium users Impact on approach: Might influence the pace of driving subscriptions to align with technical capacity

• Resource: Given the potential impact on multiple teams, I'm wondering about our current resource allocation. How are product and engineering resources currently split between free and premium feature development?

Why it matters: Helps understand potential constraints in executing strategies Expected answer: 60% on free features, 40% on premium features Impact on approach: Might suggest reallocation of resources to support subscription growth