Everything from

PostHog

4 resources from PostHog we point founders to, and the questions each answers.

📄 Article
✓ Link checked Free Beginner

Written by PostHog's operations lead, this is the sharpest piece on hiring for judgment over resume. Its core claim, attributes far outweigh technical expertise, maps exactly to our answer: your first ops person will hold admin access to your banking, passwords, and infra, so trust, unflappability, and extreme optimism matter more than a shiny CV. It even hands you interview questions and antipatterns for each trait.

Making your first startup ops hire: what founders should look for

From PostHog by Charles Cook 10 min read

  • Ops is a purely defensive role early on: up to roughly 50 people you are putting out fires, not building systems for hyperscale, so hire someone who stays calm when blamed.
  • This hire gets top-level access to banking, passwords, and infrastructure, so if you would not trust them with that, keep looking.
  • Screen for optimism and dependability with real questions, not for pedigree; a great generalist beats a specialist who cannot roll up their sleeves.
Open posthog.com →
🛠️ Tool
✓ Link checked Freemium Beginner

An all in one, generously free product analytics tool that early teams can set up in minutes, with events, funnels, session replay, and surveys in one place. It is one of the two tools our short answer points to, and the free tier easily covers an MVP. A good default when you want signal without stitching tools together.

PostHog Product Analytics

From PostHog

  • Free tier covers early stage event volumes
  • Combines analytics, replay, and surveys in one place
  • Autocapture lets you start before you know every event
Open posthog.com →
📄 Article
✓ Link checked Free Intermediate

This is the open-source-as-growth playbook told by a founder who lived it, aimed at products where developers are the users. Hawkins explains why they chose an open, self-hostable, transparent product to win trust as unknown founders in a crowded space, and how roughly 70 percent of early growth came from recommendations. Read it if open-sourcing is genuinely on the table, because it shows the payoff and the work involved.

How we got our first 1,000 users

From PostHog by James Hawkins ~15 min read

  • Open source and transparency built trust that let unknown founders break into a crowded market
  • Have a plan to reach your first users before you build, not after
  • Optimize early for learning and repeat usage, not raw signups or revenue
Open posthog.com →
📄 Article
✓ Link checked Free Intermediate

This is a founder team telling on themselves: they grew for years without a defined ICP and it caused real damage to their roadmap and go-to-market. It is a useful antidote if you think ICP work is a nice-to-have exercise rather than something that changes what you build and who you call. Concrete, no fluff, written by people who actually shipped a product.

Defining our ICP is the most important thing we ever did

From PostHog

  • Product-market fit and a defined ICP are linked, you struggle to get one without the other.
  • Not having an ICP doesn't just hurt marketing, it makes the whole roadmap unfocused.
  • Define your ICP earlier than feels comfortable, waiting has a real cost.
Open newsletter.posthog.com →
eChai Partner Brands The partnership →