PostHog as neo-Twilio for engineers
$58M/year hedgehog of product analytics
The important parallel is not analytics, it is distribution. PostHog is winning the same way Twilio did, by giving engineers a tool they can plug in themselves, use for free, and expand through usage rather than a seat based contract. That makes the engineer who adds the SDK or tracks the event the entry point, then lets PostHog sell more products off the same event stream, just as Twilio sold more APIs off the same developer account.
-
At the product level, PostHog is built around the engineer workflow. Teams drop in posthog.js, auto capture events, and quickly turn those events into funnels, charts, session replay, and experiments. In one customer example, engineers own tracking for each feature and use the resulting dashboards themselves to decide what to ship next.
-
That is different from the classic Amplitude and Mixpanel center of gravity. Amplitude positions itself as self serve analytics for product managers, marketers, and broader business teams, while PostHog is optimized for the person instrumenting the app and maintaining the data flow. The buyer may still be a product leader, but the daily operator is much closer to engineering.
-
The neo Twilio part is the business model. Twilio says it acquired the substantial majority of customers through self service and generates most revenue from usage based fees. PostHog follows the same logic with free entry, usage pricing, and expansion into adjacent tools. Statsig shows why this matters, metered feature flags and experiments can turn one technical foothold into large multi product contracts.
This points toward product engineering becoming its own software budget. The vendors that own the event stream, the feature flag, and the feedback loop will keep moving outward into data, testing, monitoring, and AI driven iteration. If PostHog keeps that engineer first wedge, it can look less like a reporting tool and more like operating infrastructure for shipping software.