COMPANY SIZE: 5–200 employees, Seed–Series B, $500K–$20M ARR IDEAL ROLE: Product Manager, Data Engineer, or CTO at developer-led SaaS companies that care about data privacy and product-led growth INDUSTRY: Developer tools, B2B SaaS, privacy-conscious verticals (healthtech, fintech, legaltech) TRIGGER SIGNALS: GDPR/SOC 2 requirements making Mixpanel/Amplitude a liability, self-hosting requirement, engineering-led product culture, open-source-friendly company
POSITIONING ANGLE The angle isn't "better analytics" — it's "analytics you actually control." For engineering-led and privacy-sensitive teams, the real pain is that Mixpanel and Amplitude are black boxes where customer event data lives on someone else's servers. PostHog's self-host option is the moat; lead with data residency, not dashboards. SUBJECT LINE Your analytics tool probably fails your GDPR audit OPENING (first 2 sentences) Noticed you're pursuing SOC 2 certification — which means your analytics vendor's data processing agreements just moved from "check the box" to "potential audit finding." Teams at your stage typically hit this when they realize Amplitude or Mixpanel can't provide the data residency guarantees their legal team is now requiring.
1. LINKEDIN: Announced SOC 2 or ISO 27001 certification → triggers vendor review of all data processors 2. JOB BOARDS: "Data Privacy" or "Compliance Engineer" hire → formalizing compliance function, vendor audits follow 3. TWITTER/X: CTO or PM tweets GDPR frustration with SaaS analytics vendors → active evaluation window, likely PostHog shortlisted 4. GITHUB: Self-hosted infrastructure repos, Kubernetes configs, or Terraform modules → engineering culture that prefers control 5. COMPANY BLOG: Engineering post about "why we self-host X" → explicit values signal, PostHog self-host perfectly aligned