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

Get the first 1,000 users for a new analytics tool

PostHog is a product analytics platform that helps product engineers understand and improve how people use software. Answer this product management case and get it graded line by line against a weighted rubric.

ICP definition
Go-to-market strategy
Product positioning
Pricing and packaging
PMF learning

The situation

James Hawkins and Tim Glaser ask you, the first senior PM, to propose a go-to-market plan for a new developer-focused product analytics tool. In the last nine months the company has tried several products for sales and engineering teams, and the main lessons have been painful: broad audiences do not convert well, crowded categories punish weak differentiation, and insight-only tools can attract curiosity without becoming urgent. This new idea comes from a problem the founders feel themselves. Existing analytics products are powerful, but they send user data to third parties, limit raw data access, and give developers little control over deployment and pricing. The market already has many analytics vendors, so a me-too launch will likely fail. You need to recommend who to target first, how the product should be distributed and positioned, how to reach the first 1,000 users without a large marketing budget, and how to learn fast enough to know whether this is real pull or another false start. The hard part is balancing trust, adoption, product focus, and a path to monetization.

What to produce

A 2 page go-to-market strategy memo.

Your answer must

Recommend a primary ICP for the first year and name at least two user groups PostHog should not target yet.
Propose a clear positioning statement and differentiation strategy against existing analytics tools, tied to data control, data access, and developer workflow needs.
Outline a sequenced plan to acquire the first 1,000 users, including channels, launch tactics, and the role of community, self-serve adoption, and any sales motion.
Choose a distribution and monetization approach, such as hosted, self-hosted, open-source, open-core, or another model, and explain the tradeoffs.
Define success metrics and a 90 day learning plan, including what signals would make you double down, narrow the ICP, or pivot again.

Constraints

There is no large paid acquisition budget and no established sales team.
The product is still lean, so you cannot rely on a broad suite of features to win deals.
Any plan must address developer trust concerns around user data and control.
The company has already spent time on multiple pivots, so speed to learning matters more than polished packaging.

Format

State your recommendation first, then cover ICP, positioning, distribution and monetization, first 1,000 user plan, metrics, and risks.

How PostHog actually played it

Covers PostHog's six early pivots before landing on product analytics, how it got its first 1,000 users, and how an open-core model shapes growth.

Pivot based on evidence of pull
Open-core can drive trust and adoption
The first thousand users shape the product

Built from How PostHog Grows: The Power of Being Open-Core by Jaryd Hermann (How They Grow).