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

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Ideal Customer Persona
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Sprints
    • 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
      • Roadmap
      • 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
      • YouTube
    • 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
    • Ideal Customer Persona
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Sprints
    • 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
      • Roadmap
      • 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
      • YouTube
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Handbook
  • Small teams
  • Growth

Growth Team

Last updated: Dec 05, 2022

On this page

  • People
  • Mission
  • What the Growth team does
  • Q1 2023 objectives
  • How to work with the Growth team
  • Feature ownership
  • What we're building

People

Team members

  • Emanuele Capparelli

    Growth Engineer

  • Raquel Smith

    Growth Engineer

Mission

Maximize the number of people who get value out of PostHog, and help them realize and leverage all the value we offer.

What the Growth team does

  • Sign up
  • Activation and reducing time to value
  • Billing and pricing changes
  • Product led growth, including messaging, emailing and notifications

Q1 2023 objectives

  • Objective 1: Feel confident in our definitions and metrics for all our areas of responsibility
    • Reasoning: So that we know we are looking at the right things and can prioritize future work
    • KR: 1 dashboard with 1 insight for each area of responsibility
    • KR: 1 dashboard for each area of responsibility, and insights that describe the entire flow
  • Objective 2: Improve conversion to paid
    • Reasoning: This metric directly impacts our company performance, and it encompasses many things downstream (eg. activation, billing conversion, etc).
    • KR: Sign up-> paid anything from 1.6% to 5% (3 month average).
      • Idea: Each sub-product has its own onboarding flow with in-app tutorials/videos
      • Idea: All the docs, tutorials and product material is accessible from within the app
  • Objective 3: We can iterate quickly on pricing
    • Reasoning: Pricing is the most important factor in success for PostHog, and getting a smooth process to make pricing changes will allow us to iterate more.
    • KR: An iteration or experiment on pricing takes 1-2 pull requests, and solves grandfathering smoothly

Current status of the Activation metrics can be checked on the Growth dashboard (internal only)

How to work with the Growth team

In addition to covering specific areas of the product, members of the Growth team can temporarily join other small teams to execute jointly on growth-related tasks. This can be done by requesting help during Sprint planning, or at the beginning of the Quarter during the OKR definition phase.

Feature ownership

You can find out more about the features we own here

What we're building

Check out the company roadmap to see what we're working on next!

Questions?

Was this page useful?

Next article

Infrastructure Team

People Mission Slack channel #team-infrastructure How we work? Guidelines We work as teams on one goal/project - not having a single person alone working on a goal The board should be our source of truth We document what we do to share context internally We finish what we start, or we don't start it at all We continually prioritize We prioritize unblocking others We have an agenda and follow up on actions from our meetings Be frugal Standups We have a Platform wide standup every Monday…

Read next article

Authors

  • Tim Glaser
    Tim Glaser
  • Eli Kinsey
    Eli Kinsey
  • Emanuele Capparelli
    Emanuele Capparelli

Share

Jump to:

  • People
  • Mission
  • What the Growth team does
  • Q1 2023 objectives
  • How to work with the Growth team
  • Feature ownership
  • What we're building
  • Questions?
  • 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
© 2023 PostHog, Inc.
  • Code of conduct
  • Privacy policy
  • Terms