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

How should PostHog describe itself now?

PostHog is a developer focused product platform, best known for product analytics, that helps software teams understand and improve their products. Answer this product management case and get it graded line by line against a weighted rubric.

Positioning
Go to market strategy
Strategic framing
Messaging
Risk management

The situation

The founders have asked you, a senior PM working across the business, to recommend how PostHog should describe itself to the market. The company is widely associated with product analytics, which helped early growth, but the product now appears to cover a broader set of jobs for builders. Some teammates think the current label is too narrow and causes prospects, customers, and even internal teams to underestimate what PostHog can do. Others worry that moving away from a familiar category will make the company harder to understand and weaken a clear entry point that still works. Why now, the website, sales narrative, and product education are starting to diverge, and leadership wants a sharper company level story before the next planning cycle. The hard part is that existing categories may not fit cleanly, while inventing new language could confuse buyers if it is not grounded in real user problems. You need to recommend whether to stay within the analytics frame, broaden it, or define a new one, and how to do that without outrunning what the product can credibly deliver.

What to produce

A 2 page positioning strategy memo.

Your answer must

Explain the core positioning problem in terms of market category, buyer understanding, and product reality.
Evaluate at least 3 positioning options, including staying in analytics and introducing new category language.
Recommend a primary audience, a core value proposition, and a one sentence company description.
Outline a rollout sequence across the website, sales narrative, product surfaces, and documentation.
Identify the main risks, what remains unproven, and how you would validate the new positioning.

Constraints

Do not assume major new product capabilities that are not already in market.
Keep a path for existing users who still come to PostHog mainly for analytics.
Any new term or category must be explained in plain language and tied to a real user problem.
Be explicit about uncertainty rather than presenting the recommendation as fully proven.

Format

Use clear section headings and include a short option comparison table.

How PostHog actually played it

PostHog describes a six week effort to reposition from analytics to the company that makes your product self-driving. It defines what repositioning means, why the old category no longer fit, and how new concepts like a context warehouse are introduced. A candid look at positioning work in progress.

Reposition when the category you are in no longer describes what you build
Define new terms carefully and explain why they are needed
Share where the new positioning is still unproven

Built from Repositioning PostHog by Charles Cook.