<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/7f34524d-9389-4bb8-b803-8796988dd464/Web_logo_(256__256px)_(2).png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/7f34524d-9389-4bb8-b803-8796988dd464/Web_logo_(256__256px)_(2).png" width="40px" /> What we love about this handbook section
🖤 We are in LOVE with Posthog and their handbook. But this page jumped out to us for their openness around company strategy, both long and short term. This gives employees a clear sense of direction which is transparent, but also gives applicants a sense of comfort that the business has a plan and knows where it’s going. It’s a powerful page to share publicly. Great work Posthog! 👏
****Check out their entire handbook for inspiration here: đź”—Posthog's full handbook
</aside>
Last updated:Â Jul 25, 2023
|
“Help engineers build better products"
PostHog helps engineers be better at product through a suite of tools that we call a “Product OS” (product analytics, session recordings, feature flags, experiments, and a lightweight CDP). We build for and sell to product engineers at early stage to high-growth startups. Our competitors provide point solutions focused on (non-technical) product managers. Focusing on engineers enables us to get in earlier and empower the engineer to own product outcomes - owning the market for product tools.
We now add more companies each week than any closed-source SaaS rival, and we're the open-source standard for all our applications. Financially, we're in a great position - default alive, and profitable within the next 12 months.
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, product managers and in some cases, a data team 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 source of truth for customer and product data.
_(2).png){kind=link}