PostHog · Strategy · Mid · 45 to 60 minutes
Fix PostHog's ad hoc pricing decisions
PostHog is a developer focused product analytics company that also offers related tools for building and understanding products. Answer this product management case and get it graded line by line against a weighted rubric.
- Strategic thinking
- Problem framing
- Experiment design
- Cross functional leadership
- Decision making
The situation
PostHog's leadership asks you, a PM, to review how the company makes pricing changes. Today, pricing decisions are mostly reactive. A launch happens, a customer asks for a discount, usage patterns shift, or a competitor changes packaging, and different people jump in to make a call. Some changes may help, but the company lacks a clear way to tell which ones worked, for whom, and at what cost. That is starting to matter more as PostHog grows and offers more products and plans. You are not being asked to set new prices today. Instead, leadership wants a strategy for improving how pricing decisions get made over the next two quarters. The challenge is that pricing touches revenue, product positioning, customer trust, and engineering effort at the same time. Moving too slowly could leave money and learning on the table. Moving too quickly could confuse customers or create internal churn. Your job is to recommend how PostHog should move from ad hoc pricing calls to a more reliable decision process.
What to produce
A 1 to 2 page strategy memo.
Your answer must
- Diagnose the main problems with the current ad hoc approach and explain why they are becoming more serious now.
- Recommend an operating model for pricing decisions, including who should own which decisions and how product, data, finance, and go to market partners should be involved.
- Identify the most important customer and business questions PostHog should answer before making larger pricing changes, and explain how you would gather that evidence.
- Define how PostHog should evaluate pricing changes, including leading indicators, outcome metrics, and how to tell whether a test or rollout is worth expanding.
- Propose a phased plan for the next two quarters, including the first steps, major risks, and how you would reduce customer confusion or internal churn.
Constraints
- Do not propose a full company reorg or a complete pricing reset as the first step.
- Assume limited engineering and analytics support in the next quarter.
- Your approach must minimize surprise or disruption for existing customers.
Format
Use clear headings such as problem, options, recommendation, evidence plan, metrics, and rollout.
How PostHog actually played it
PostHog describes giving pricing an owner, understanding customer needs, building tooling and running experiments on repeat. It shows how pricing as a product works inside the company. Helpful for PMs who want a repeatable process for pricing changes.
- Assign a team to own pricing like any other product
- Build experimentation tooling for pricing
- Repeat the cycle of research, build and test
Built from How (and why) we treat pricing like a product by Raquel M Smith.
Related case studies
- Get the first 1,000 users for a new analytics toolPostHog · Go-to-market · Senior
- What should happen to the Sessions page?PostHog · Product sense · Entry
- Should PostHog keep its AI chat assistant?PostHog · AI product · Mid
- Should PostHog reprice anonymous events?PostHog · Strategy · Senior
- Should PostHog reprice session replay?PostHog · Strategy · Mid
- How should PostHog design its cloud free tier?PostHog · Go-to-market · Mid