book
howtheygrow.coNov 18, 2024

How PostHog Grows: The Power of Being Open-Core

by Jaryd Hermann

Read Original
case-studydeveloper-toolsgrowthopen-sourcepricingsaasteam-structure

TL;DR: PostHog's strategy is built on radical transparency. After 6 failed pivots in 9 months (sales tools, CRMs, engineering retention), they found PMF with open-source product analytics. Their first 1,000 users came from Hacker News and GitHub, where they launched and engaged developers directly. Key strategic choices: laser-focused ICP (product engineers at high-growth startups, deliberately NOT marketers), full transparency (public handbook with compensation and strategy), and microservices selling (each feature is its own product with dedicated team of 6 or less). Growth split: 70% recommendations, 30% content. They embrace late-mover advantage, only entering markets with proven $1B+ competitors. Small autonomous teams, no design by default (engineers own UX), and minimal product management keep them moving fast.

Key Insights

  • Open-core everything - be transparent about failures, team structure, customer acquisition, strategy
  • 6 pivots in 9 months taught them to validate demand and pursue ideas with founder conviction
  • First 1000 users from developer communities (HN, GitHub) and treating users as co-creators
  • Laser-focused ICP: product engineers at high-growth startups - deliberately avoid building for non-technical users
  • Public handbook shares everything (compensation, strategy, roadmap) - signals maturity and attracts aligned talent
  • 70% growth from word-of-mouth recommendations, 30% from inbound content marketing
  • Microservices approach: each feature is its own product with roadmap, team, and pricing
  • Small autonomous teams (6 or less) operate as mini-startups
  • Late mover advantage - only build in markets with proven $1B+ demand

Actionable Takeaways

  • Publish a public handbook with compensation, strategy, and roadmap to build trust
  • Define ICP tightly and explicitly say who you are NOT building for
  • Launch on developer communities (HN, GitHub) for technical products
  • Treat users as co-creators - integrate feedback directly into roadmap
  • Use transparent usage-based pricing with self-serve discounts
  • Structure teams as small autonomous units (6 or fewer) with full ownership
  • Enter proven markets with existing $1B+ competitors rather than creating new categories
  • Focus content on education and value, not direct selling

Principles Validated (3)