Summary

We build for the highest-performing product teams (engineers, PMs, designers) building the most loved products at fintech companies. We focus specifically on the product-engineers (full-stack engineers skewed towards the frontend) but it should be usable by everyone in the product team.

Example: PostHog anytime from their Series B to IPO

Marketing and customer success should primarily focus on this ICP, but should also develop high-potential customers (customers that are likely to later become high-growth customers e.g. James and Tim during YC). We should be in maintenance mode for hobbyists (engineers building side-projects e.g. Ben White building Mealyo). We want to be the first tool that technical founders add to their product.

Why? We believe that the best tech companies are increasingly engineering-led. By building for the best product-engineers we'll create a positive feedback loop of being the best product for them. This is clearly differentiated from others in the space which are focused on less technical PMs. As more of the leading tech companies adopt being engineering-led and having highly technical PMs PostHog will become the clear product leader.

Proposed ICP

High-growth startup
Description Startups that have product-market fit and are quickly scaling up with new customers, hiring, and adding more revenue.
Suggested Criteria - 15-500 employees- $100k+/month in revenue OR very large number of consumer users- Raised from leading investors- Not yet IPO’ed
Why they matter? - Able to efficiently monetize them- Very quick sales cycle- Act as key opinion leaders for earlier-stage startups/slower moving companies- Strong opinions on what they need - helping us build a better product
Job role We build for the power users of the The Product teamPrimary focus- Product-engineers (full-stack engineer skewing front-end)- PMs (those that are highly technical)Should be usable by:- Designers- Less technical PMs- Marketers
Examples PostHog anytime from their Series B to IPO, Linear, Ramp, Vercel, Retool

Each team will focus more or less on different members of the product team. This is detailed on their team pages.

FAQs

Why double-down on product engineers vs making it more accessible and easy to use?

Situation:

Guiding policy:

Counter argument: