HomeCompaniesPostHog

PostHog

Open source product operating system

PostHog helps engineers build better products. We provide everything they need to make sure they are building something that people want. This means - product analytics, session replays, feedback tools, feature flags, experimentation, and a datawarehouse (with SQL) with one click data imports from the places you use. PostHog can be deployed to the cloud, or self-hosted on existing infrastructure, removing the need to send data externally. PostHog was created as an open source project during Y Combinator's W20 cohort and had the most successful B2B software launch on HackerNews since 2012 - with a product that was just 4 weeks old. Since then, more than 40,000 companies have installed the platform, we're doing $MMs in revenue, and have a community of 120K developers - 97% driven by word of mouth. Despite the tech market, we're default alive and doing better than ever! We've been averaging ~10% monthly revenue growth, we are [default alive](http://www.paulgraham.com/aord.html), and we didn't raised a huge / now-overpriced round in 2021. While others are focused on layoffs and struggling to grow into huge valuations, we're focusing on an awesome product for end users, hiring (a handful of) exceptional team members and seeing fantastic increases in revenue as a result. Check out posthog.com/careers if you want to be part of this journey.
PostHog
Founded:2020
Team Size:55
Location:San Francisco
Group Partner:Dalton Caldwell

Active Founders

James Hawkins, Founder

cofounder at PostHog / used to be a bad pro cyclist / knows about brand (sounds fluffy right, my mom says i'm special though)/shipping lots of stuff/marketing to developers
James Hawkins
James Hawkins
PostHog

Tim Glaser, Founder

Tim Glaser
Tim Glaser
PostHog

Hear from the founders

How did you decide to apply to Y Combinator? What was your experience applying, going through the batch, and fundraising at demo day?

We applied simply because it’s the best place in the world to start a startup, particularly as we were both Silicon Valley “outsiders”.Looking back, YC has been the single most important thing we’ve ever done in our careers.

How have you kept in touch with the YC community and continued to use YC resources & programs since the batch ended?

Every single week we spend time with other YC founders or partners.The YC community is a critical source of advice, fundraising, friendship, marketing and sales.

What's the history of your company from getting started until the present day? What were the big inflection points?

We pivoted 5 times, got into YC, pivoted a month into the batch, then shipped PostHog as we got so frustrated re-implementing analytics every single time we pivoted.\It was a wild success on Hacker News and we’ve not looked back.

What is the core problem you are solving? Why is this a big problem? What made you decide to work on it?

We help engineers be better at product.\We do this by providing all the tools they need to do this in one - it means no time spent pulling together insight from all over the place (in the way a traditional PM would) and it means no time lost to data engineering. We want you to engineer your product instead.

What is your long-term vision? If you truly succeed, what will be different about the world?

Our mission is to increase the number of successful products in the world.We do this by helping engineers be better at product. They’re some of the brightest and hardest working employees, and so getting them to focus on building something people want instead of shipping tickets set by someone else is really important.\This is how we’ll do that:Provide every tool needed for evaluating feature success. The best use of an engineer's time is to ship features that have an impact on customers. Currently, this requires a large number of tools and product managers to pull all the insights together. By integrating all these tools we can make this easy - no integration needed, no extra vendors, no extra javascript, and workflows to guide engineers through feature development.Get in first. By already being used by our customers, we’re the default for each additional tool they add. It’s the technical co-founder and early engineers building the MVP and integrating the first product tools, not PMs. By focusing on engineers we can be their preferred choice and get in first. Additionally, we can ladder our tools - for example, session recording is used much earlier in the life cycle of the product than others like the CDPs helping us get in earlier than competing products.Be the pipeline for product and customer data. Traditionally, as companies scale their data warehouse becomes the source of truth and non-warehouse native tools (like product analytics) become less relevant. By being their core pipeline from connecting their data to their warehouses we can remain sticky for the life of our customers. And by providing this infra, we ensure the data we have remains comprehensive.##