• Product
  • Pricing
  • Docs
  • Using PostHog
  • Community
  • Company
  • Login
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Offsites
    • Security
    • Brand assets
    • Team structure
    • Customer Success
    • Exec
    • Experimentation
    • Growth
    • Infrastructure
    • Marketing
    • People & Ops
    • Pipeline
    • Product Analytics
    • Session Recording
    • Website & Docs
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Side gigs
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • How to interview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Working with product design
      • Releasing a new version
      • Handling incidents
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • How-to access PostHog Cloud infra
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
      • Overview
      • Data storage or what is a MergeTree
      • Data replication
      • Data ingestion
      • Working with JSON
      • Query performance
      • Operations
        • Overview
        • sharded_events
        • app_metrics
        • person_distinct_id
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Paid features
    • Releasing as beta
    • Our philosophy
    • Product design process
    • Designing posthog.com
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Offsites
    • Security
    • Brand assets
    • Team structure
    • Customer Success
    • Exec
    • Experimentation
    • Growth
    • Infrastructure
    • Marketing
    • People & Ops
    • Pipeline
    • Product Analytics
    • Session Recording
    • Website & Docs
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Side gigs
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • How to interview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Working with product design
      • Releasing a new version
      • Handling incidents
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • How-to access PostHog Cloud infra
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
      • Overview
      • Data storage or what is a MergeTree
      • Data replication
      • Data ingestion
      • Working with JSON
      • Query performance
      • Operations
        • Overview
        • sharded_events
        • app_metrics
        • person_distinct_id
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Paid features
    • Releasing as beta
    • Our philosophy
    • Product design process
    • Designing posthog.com
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Handbook
  • Marketing
  • Value propositions

Value propositions

Last updated: Oct 17, 2022

On this page

  • 1. An all-in-one platform
  • 2. Integrate with data warehouses
  • 3. Retain control & ensure compliance

PostHog has 3 value propositions, outlined below in order of importance. Each is structured like a story:

  • The proposition we make (e.g. Have more fun at the arcade)
  • The challenge before PostHog (e.g. Most arcade games are for one player)
  • The experience of this challenge (e.g. It's not fun to play on your own)
  • The solution PostHog offers (e.g. Our arcade game has a two-player mode)
  • The result of the solution (e.g. You'll have twice as much fun)

1. An all-in-one platform

PostHog offers a suite of product analysis tools, including funnels, heat maps, session recording, feature flags, experimentation, and more, all in one easy-to-use platform. This enables data and engineering teams to get information faster, while less technical teams are also able to self-serve and get answers without needing support.

  • Proposition: Get all the analysis you need in one place.
  • Challenge: You have to go between many different tools, often making requests of other teams to get information.
  • Experience: You aren't able to progress quickly and even simple requests can take a lot of time.
  • Solution: PostHog is the only product solution that combines several useful tools into a single, self-serve platform.
  • Result: Now you can get answers faster and focus on improving your product.

2. Integrate with data warehouses

PostHog's app system works seamlessly with tools such as data warehouses, both for importing and exporting data. This means users can analyse data from across their infrastructure with ease and develop a conclusive understanding of user behaviour.

  • Proposition: Connect your analytics platform to the rest of your stack, including your data warehouse.
  • Challenge: You're unable to fully leverage the potential of your data warehouse, or to run analytics on more than one data source at a time.
  • Experience: You never see the big picture, just fragments of user behavior. Your data team becomes a bottleneck for others.
  • Solution: PostHog's open-source product OS can push and pull data to any tool, including data warehouses.
  • Result: Better leverage your data team and get insights from across your entire data infrastructure.

3. Retain control & ensure compliance

PostHog is the only product platform which enables users to self-host on their own infrastructure. This means they have greater control over who has access to their data, and makes regulatory compliance is a breeze because information never leaves existing systems. If a customer chooses to host their data with us, we also offer the choice of hosting in the US or Germany.

  • Proposition: Retain control of your data and simplify regulatory compliance by self-hosting on existing systems.
  • Challenge: You can't understand user behavior while remaining compliant without sharing data with third parties.
  • Experience: You face an increased risk of privacy issues, or else are forced to cope without product analytics.
  • Solution: PostHog's open-source software is entirely transparent and can be deployed to your own infrastructure.
  • Result: Now you can get trustworthy product insights without worrying about privacy issues.

Questions?

Was this page useful?

Next article

Content

Content is the main pillar of our marketing strategy. As our products are quite technical in nature, we believe that frequent and regular content output helps improve acquisition and ongoing product engagement. The blog is where we publish interesting product content, share feature updates, and tell PostHog stories. Content & SEO strategy Content & SEO is a long-term strategy. We are focused on generating a sustained output of high quality content that is genuinely valuable to users. Rather…

Read next article

Authors

  • Charles Cook
    Charles Cook
  • James Hawkins
    James Hawkins
  • leggetter
    leggetter

Share

Jump to:

  • 1. An all-in-one platform
  • 2. Integrate with data warehouses
  • 3. Retain control & ensure compliance
  • Questions?
  • Edit this page
  • Raise an issue
  • Toggle content width
  • Toggle dark mode
  • Product

  • Overview
  • Pricing
  • Product analytics
  • Session recording
  • A/B testing
  • Feature flags
  • Apps
  • Customer stories
  • PostHog vs...
  • Docs

  • Quickstart guide
  • Self-hosting
  • Installing PostHog
  • Building an app
  • API
  • Webhooks
  • How PostHog works
  • Data privacy
  • Using PostHog

  • Product manual
  • Apps manuals
  • Tutorials
  • Community

  • Questions?
  • Product roadmap
  • Contributors
  • Partners
  • Newsletter
  • Merch
  • PostHog FM
  • PostHog on GitHub
  • Handbook

  • Getting started
  • Company
  • Strategy
  • How we work
  • Small teams
  • People & Ops
  • Engineering
  • Product
  • Design
  • Marketing
  • Customer success
  • Company

  • About
  • Team
  • Investors
  • Press
  • Blog
  • FAQ
  • Support
  • Careers
© 2022 PostHog, Inc.
  • Code of conduct
  • Privacy policy
  • Terms