Context and edwin's dumb analogy

PostHog is kind of like a buffet. A user visits PostHog and sees an impressive, overwhelming spread of products and features. But what they might need instead is a more opinionated and curated experience, something that helps them understand which products to start with and how they all fit together in a sequence.

So let's create content in multiple formats that define and highlight flagship use cases. These will help users identify their needs, understand how multiple PostHog features work together, and see how real companies succeed with PostHog.

Attendees: @cleo-pleurodon @SaraMiteva @gewenyu99 @dphawkins1617 @edwinyjlim

Existing content

• Getting HogPilled: Winning with PostHog
• Customer case studies
• Tutorials

Notes

• @SaraMiteva suggested creating developer-focused situations that combine multiple features into a specific POV or narrative
  • For example, “I use PostHog product analytics and data pipelines to send real-time notifications to Slack to alert my manager when feature usage spikes and crosses a threshold.”
  • Each use case guide should include:
    • Criteria for when/why to use it
    • Multiple PostHog features working together
    • Diagrams showing the data flow and integrations
    • A perspective of someone who is doing a job
• Build narrative-driven recipes for problems customers already have and solved with PostHog
• Use real case studies from onboarding and sales could inform these guides. Show “real” customer workflows instead of generic examples.
  • @consultingsultan we talked about this in nyc
• Build narrative-driven recipes for problems customers already have and solved with PostHog
• @cleo-pleurodon suggested defining an ideal tech stack + PostHog especially for startups and Y Combinator companies
  • also suggested we explore the cross-pollination with competitors. For example, how many users overlap between PostHog and Amplitude? Let's investigate why.
  • Should we should highlight partnering technologies or companies where relevant?
  • Is there an ideal tech stack for PostHog + X other technologies? E.g. Supabase + PostHog + Railway
• Proposed content around replacing or consolidating multiple tools with PostHog: “If you’re using all these platforms, here’s how to simplify.” Sort of like migration guides.
  • @gewenyu99 no platform fully replaces another’s exact feature set. Teams mix tools freely. Our goal should be to show how PostHog fits into real, diverse stacks.
• Updating our case study format o include diagrams showing how different PostHog products connect. Visualize the “technical plumbing.”
• Suggested a company logo wall and social proof, so users can see themselves reflected. "Our peers or competitors use PostHog, so it must be for us"
• @cleo-pleurodon Mentioned personalized homepages (Cory’s idea) and signup field enrichment to enable this personalization.
• “What if I asked Max, ‘How do I build a company like X?’”
• Should we also promote hobby projects and indie dev projects in PostHog to highlight community?
  • PostHog is developer-friendly, so these promoting indie devs and hackers fit our brand
  • Kits for indie hackers, a long-term awareness play.
• The “Winning with PostHog” concept should exist across multiple formats — docs, blog, YouTube, onboarding, etc.
• We should reuse diagrams and visual assets across these channels to build a consistent story.
• Think multi-format from the start — one narrative, many outputs.

Core qualities

Flagship use cases should:

• Be scenario-based or describe a job-to-be-done
• Show the full stack of key technologies involved (includes non-PostHog products)
• Be tailored to company profile (e.g., YC startups vs. series A/B, team size, requirements)
• Specific to industry or vertical

Rough ideas

• Build a roadmap or a personalized setup based on personal filters (e.g., I’m a B2B SaaS company, team of 5–10, with web and mobile apps)
  • Max AI could generate a personalized setup pathway for your company
  • Here's an example: https://roadmap.sh/ai-engineer
• Lots of visuals and diagrams
• Screenshots or mockups of customer websites that are annotated with PostHog features that power them @a-lider 🙌
• Builder kits (github repos?)
• Docs pages
• Blog posts