PostHog Handbook Library / Brand

1,561 words. Estimated reading time: 7 min.

Overview

Auto TL;DR

At a Glance

This long page covers these main areas. The list is generated from the article headings, so it updates with every handbook rebuild.

  1. Taste
  2. Brand personality
  3. Who we're talking to
  4. The Hacker News test
  5. How we describe PostHog
  6. The standard description
  7. What we want people to know
  8. Why people pick PostHog

PostHog's brand is the total sum of how people experience us – from a first visit to posthog.com to an onboarding email, from how quickly we ship a bug fix someone complained about on X, to billboards, merch, event collateral, ads, and more.

This matters for two reasons:

  1. Brand is a growth driver. It's one of the main reasons PostHog gets recommended. People who trust a brand talk about it. Developers who find us authentic fight for us in comment sections.
  1. Trust is slow to build and fast to lose. A generic headline, a forced joke, a bad sticker, a robotic support reply – each of these chips away at the trust we've earned.

Taste

Taste is the most important principle PostHog has. "Polish" is surface-level – smooth gradients, perfect shadows, trendy layouts – the visual equivalent of buzzwords. "Taste" is deeper: making decisions that reflect a real point of view, caring about whether something is right and not just done, going the extra mile even if only one person notices.

Something made with taste looks like someone made this on purpose, especially in a world where more people are shipping AI slop.

What taste looks like in practice:

Brand personality

PostHog should feel:

| Feel like this | Not like this | | -------------- | ----------------------------------------- | | Opinionated | Diplomatic to the point of saying nothing | | Human | Corporate robot | | Slightly weird | Trying to be funny in a try-hard way | | Thoughtful | Random | | Direct | Fluffy | | Honest | Corporate fluff | | Playful | Childish or unprofessional | | Approachable | Arrogant |

Who we're talking to

Our primary audience is AI-pilled software teams. Many of them are technical founders or assume the role. It's incredibly important that we don't alienate them, as they're a driver of word-of-mouth growth.

We should assume our audience either has to do technical work or wants to, regardless of whether they can code. Most of them are engineers, and for the rest, we're the bridge, giving everyone direct access to data and the power to ship.

This shapes everything. Engineers...

For the full picture, see who we build for.

The Hacker News test

Before you ship anything – copy, design, a campaign, a policy – ask: how would this be received on Hacker News?

Hacker News is intensely logical and skeptical. They'll call out corporate spin, vague claims, and try-hard humor in seconds. If you think your thing would get roasted, change it. If it would hold up to scrutiny, ship it.

How we describe PostHog

PostHog is the context layer for your product. PostHog ingests and stores your analytics, errors, replays, and business data so you and your agents can query it and make changes.

This is the frame everyone at PostHog should use, everywhere.

Our products help customers do one of four things, which build on each other:

  1. Get data in. PostHog ingests and stores your data, which can come directly from our own products or 3rd party sources.
  2. Query the data with your agent. Ask PostHog AI or use the PostHog MCP to run queries.
  3. Give the data to your agent to act on. We make the same data available via PostHog MCP so our users' agents can find issues and propose or take action.
  4. Let PostHog self-drive. Use PostHog to ship changes, measure their effect, and repeat.

Start with the step that matches the customer's needs. Self-driving is an aspirational state, but the component parts are composable. If a customer wants to take Reports and pass them to their own agents to act on, that is totally fine. Our job is to give engineers a suite of tools they can pick and choose from.

The standard description

Use this whenever you need a longer standard description of PostHog, e.g. for a newsletter or press. We also embed this in all our blog posts.

Product Analytics, Session Replay, Logs etc. are products. The surfaces that you interact with PostHog, like Web, Slack, MCP are apps.

Developer marketers can find the granular vocabulary rules and the per-product playbooks in Positioning and selling.

What we want people to know

Beyond literally communicating what PostHog is and what it does, we want to equip developers to build successful products. We do this by communicating the following:

Why people pick PostHog

See Why buy PostHog and How we make users happy.

What we are not

PostHog could be a lot of things, and we have a lot of terms for the same things. This creates cognitive load and confusion, and we'd rather our audience use their energy elsewhere.

A few things to avoid when describing PostHog:

Canonical URL: https://posthog.com/handbook/brand/foundations

GitHub source: contents/handbook/brand/foundations.md

Content hash: 7b215f4b2cf632ff

Static reader notes
  • MDX_COMPONENT_STATIC_ADAPTER: Adapted interactive MDX components for static reading: AboutPostHog.