PostHog · Strategy · Mid · 45 to 60 minutes

No one will pay for the early product

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

Strategic thinking
Customer insight
Monetization
Prioritization
Hypothesis design

The situation

A founder asks you, the PM working on the early product, for a recommendation before the team commits its next phase of work. Several friendly companies have taken meetings, reacted positively, and said the product seems useful. Some have even offered ideas and encouragement. But when the discussion turns to buying, the pattern changes. Prospects do not move forward, do not commit budget, or say it is not important enough to pay for right now. The team now has a hard strategy question. Is this mainly a pricing, packaging, positioning, or customer segment problem that can be fixed with sharper execution? Or is the stronger signal that the current product does not solve a painful enough problem to support a business? The founders do not want to overreact to one bad call, but they also do not want to confuse politeness with demand and spend months building the wrong thing. You need to advise what to do next, what evidence matters most, and how the team should decide whether to keep pushing this product or rethink the problem it is solving.

What to produce

Write a 1 to 2 page strategy memo.

Your answer must

Explain what the current evidence does and does not prove, separating product usefulness from willingness to pay.
Lay out at least three plausible paths forward, such as refining pricing or positioning, narrowing the target customer, or reconsidering the problem area, with trade-offs for each.
Make a recommendation and justify it with the strongest signals available in the scenario.
Propose a short validation plan with concrete conversations or tests to run next and the exact signals that would support or weaken your recommendation.
Define decision criteria for when the team should continue with the current direction versus change course.

Constraints

Use only the information in the prompt and do not assume hidden product, market, or revenue data.
Assume the team can spend only the next 4 to 6 weeks on validation before committing to a direction.
Do not recommend a long build-first approach that requires major new product development before testing demand.

Format

Use short sections with headers for diagnosis, options, recommendation, validation plan, and decision criteria.

How PostHog actually played it

A founder diary of the pivot that led to PostHog. After friendly companies liked the earlier product but would not pay, the team had to face that it did not solve a paid problem. The entry shows how the signal came from money conversations rather than praise.

Friendly feedback without willingness to pay is a warning sign
Talk about price early to test real demand
A pivot can come from a pattern across several conversations, not one

Built from Pivot to PostHog by James Hawkins.