Company Context
Andreessen Horowitz is evaluating whether one of its portfolio products, Speedrun, has enough user love to justify continued aggressive investment. Speedrun is an early-stage founder platform that helps startup teams access tactical guidance, operator content, and curated workflows during company building.
Problem
Speedrun has grown from 20,000 to 85,000 registered users in 12 months, but growth has come from multiple channels: a16z brand-driven acquisition, founder referrals, and content distribution. Leadership believes users "like" the product, but the open question is whether that love is deep enough to support a venture-scale outcome rather than a niche utility business.
Recent signals are mixed:
- 42% of new users activate in week 1
- 31% of activated users are still active in week 8
- NPS is 54 among active users, but only 18 across all signups
- 14% of weekly active users account for 61% of core actions
- 38% of new users say they would be "very disappointed" if Speedrun disappeared
- Paid conversion on the premium tier is only 3.5%
The investment team wants a product-minded assessment, not just a dashboard readout. They want to know whether user love is real, for whom, and whether it can plausibly compound into a large business.
Deliverables
- Define what "enough user love" should mean for a product like Speedrun and how it connects to venture-scale potential.
- Identify the most important user segments and jobs-to-be-done to evaluate first.
- Propose a framework to determine whether current signals indicate true product-market fit or shallow engagement driven by brand and distribution.
- Recommend what product evidence, qualitative research, and behavioral metrics you would prioritize before making an investment or growth recommendation.
- Explain the key trade-offs in deciding whether to double down, iterate on the product, or narrow the target segment.
Constraints
- You have 6 weeks to form a recommendation for the investment committee.
- The product analytics stack is incomplete; cohort retention and event data are available, but attribution and long-term revenue data are noisy.
- Engineering resources are limited, so your recommendation should not assume a major rebuild before validation.
- You must distinguish durable user love from temporary usage caused by the a16z brand, launch novelty, or one-time founder needs.
