PostHog · Strategy · Entry · 45 to 60 minutes

How should data pipelines be billed?

PostHog is a product analytics and data tools platform that helps teams capture, analyze, and route product data. Answer this product management case and get it graded line by line against a weighted rubric.

pricing strategy
customer empathy
structured thinking
tradeoff analysis
communication

The situation

A product leader and a finance partner ask you to review how PostHog charges for its data pipelines product. Today, billing is tied to an input based usage measure that is easy to count and easy to explain internally. But customer feedback suggests the bill does not always match the value users feel they get. In some setups, customers may be charged heavily even when little useful data is ultimately delivered or acted on. In other setups, the product may create clear downstream value without the pricing feeling tightly connected to that value. Leadership wants a recommendation before the next pricing update because PostHog has public pricing principles and does not want pipeline pricing to drift away from them. The tension is that any change could improve fairness for some customers while making pricing less predictable, harder to implement, or worse for short term revenue. Your task is to recommend whether to keep the current meter or move to a different one, and how PostHog should evaluate that choice.

What to produce

Write a 1 to 2 page strategy memo.

Your answer must

State the pricing problem clearly, including why an input based meter can drift away from customer value in data pipelines.
Define 3 pricing principles you will use to judge billing options, including fairness and clarity for customers.
Compare the current input based meter with at least 2 alternative meter types in a simple table, covering pros, cons, and where each option could fail.
Assume a small set of customer usage patterns and explain which kinds of customers would likely pay more, pay less, or see little change under each option.
Make a recommendation and include a validation plan, a customer communication approach, and 2 to 3 success metrics for the first quarter after launch.

Constraints

Base your reasoning only on the summary above, do not assume hidden internal data or new product capabilities.
Your proposal must be explainable to customers in plain language and fit published pricing principles.
Do not optimize only for short term revenue, balance fairness, customer trust, and billing simplicity.

Format

Use short headings, one option comparison table, and one simple customer segment table.

How PostHog actually played it

PostHog changed data pipeline billing from events ingested to rows exported and trigger events, saying 98 percent of customers pay less and most save about 87 percent. The post ties the change to its stated pricing principles. A short example of repricing so the meter matches the value delivered.

Bill on the unit that matches value, not the one that is easiest to count
Publish pricing principles and show each change follows them
Share how many customers win or lose from a billing change

Built from Data pipelines just got cheaper (and fairer) by Abe Basu.