PostHog · Go-to-market · Mid · 45 to 60 minutes

How should PostHog design its cloud free tier?

PostHog is an open core product analytics platform that teams can use in the cloud or self host. Answer this product management case and get it graded line by line against a weighted rubric.

Pricing and packaging
Go to market strategy
Growth thinking
Trade off analysis
Metric design

The situation

The CEO has asked you, the PM for cloud growth, to recommend whether PostHog should change its cloud free tier. Today, the hosted product has a small free allowance and some friction at sign up, while self hosted use is attractive to developers who want to try the product with fewer limits. The team believes the free experience strongly affects adoption, community growth, and how many users later become paying customers, but there is disagreement on where to draw the line. Sales and support are hearing that some prospects see the cloud free tier as too restrictive to evaluate properly. Finance and engineering worry that a much more generous offer could attract abuse, increase infrastructure cost, and create a large population of free users who never convert. There is also concern that if users start on one edition and later need another, the path could feel confusing or like a trap. Assume the current cloud free tier includes 10,000 events per month, and leadership wants a recommendation this week on positioning, packaging, guardrails, and migration between editions.

What to produce

Write a 1 to 2 page product strategy memo for the leadership team.

Your answer must

State a clear recommendation for the cloud free tier, including whether to change the usage allowance and whether to require a credit card at sign up.
Identify the primary target user segments for the proposed free tier and explain why they matter to PostHog's growth model.
Lay out the main trade offs across acquisition, abuse risk, infrastructure cost, conversion, and user trust.
Propose how users should move between cloud free, paid cloud, and self hosted options so the experience is understandable and not a dead end.
Define 3 to 5 success metrics and leading indicators you would track in the first 90 days after launch.

Constraints

Work only from the context given here, do not assume proprietary market data or internal benchmarks.
You may not propose major new product capabilities, only changes to packaging, sign up policy, guardrails, messaging, and edition transitions.
Your plan must acknowledge both cloud and self hosted deployment options and how they interact.

Format

Use short sections with headings: recommendation, target users, rationale and trade offs, edition and upgrade flows, metrics and rollout risks.

How PostHog actually played it

PostHog raised its free cloud allowance from 10k to 1 million events a month and explains the open core logic behind it. It covers who the change targets, why a card is still required, and how users move between editions. A clear look at free tier design as a growth lever.

A generous free tier feeds an open core flywheel of community and product value
Require a card on a free plan if you need to limit abuse and ease upgrades
Explain migration paths between editions so the free tier is not a trap

Built from Why we're giving away 100 times more cloud usage, free by James Hawkins.