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

How should PostHog find its first users?

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

Segmentation
Go-to-market strategy
Prioritization
Experiment design
Metric design

The situation

You are the PM working with PostHog's founder just before the product's first public push. The team has a working early product, but almost no brand awareness, no established sales motion, and limited time to learn what will make adoption stick. The founder wants a go-to-market recommendation for getting the first meaningful set of users, not just a burst of signups that quickly disappears. Several choices are on the table and the team cannot optimize for all of them at once. Should the product be positioned first for developers, product teams, or a broader audience? Should the team lean into self-hosting, a managed cloud offer, or keep both equally visible? Should open source be a core part of distribution and trust, or a distraction at this stage? And should the company try to monetize immediately, or treat early usage as a learning phase? Your job is to recommend a focused plan for the next few months that maximizes learning and creates a path to durable adoption, while being realistic about what a very early company can actually execute.

What to produce

Write a 1 to 2 page go-to-market strategy memo.

Your answer must

State the single primary user segment you would target first and explain why that segment is the best fit for an early product.
Recommend a clear product and packaging posture across self-hosted, managed cloud, and open source, including what you would emphasize in messaging.
Propose 3 acquisition or launch tactics for the first few months, with the logic for why each should help reach early users efficiently.
Define success with 3 to 5 metrics, including at least one metric that captures repeat usage or retained adoption rather than raw signup volume.
Lay out a short experiment plan for the first 6 to 8 weeks, including what you would test, what would count as a positive signal, and how results would change your next step.
Make a recommendation on monetization timing and explain the tradeoff between short term revenue and fast learning.

Constraints

Assume the team is small, with no large marketing budget and no established sales team.
You cannot rely on enterprise procurement, major partnerships, or long implementation projects to drive early adoption.
The product is still early, so the plan should favor speed of learning and self-serve adoption over broad feature promises.
Use only the information in this prompt and reasonable early-stage assumptions, do not invent existing traction or market data as facts.

Format

Use sections with headings: target user, positioning, launch plan, metrics, experiments, risks.

How PostHog actually played it

PostHog's founder recounts reaching 100 users in four weeks and 1,000 in three months, with key decisions like building for developers, focusing on self-hosting, being open source and not monetizing at launch. It covers the public launch, first sales and the cloud product. A solid early-stage go-to-market example.

Plan how to find first users before building
Optimize for learning, not revenue, at the start
Repeat users matter more than volume

Built from How we got our first 1,000 users by James Hawkins.