How Squeak! got started

When PostHog took off, our engineers quickly got flooded with questions in our Slack community.

These questions would disappear, and weren’t indexed by Google. All that work would disappear into nothing. Like a sand mandala. But in a bad way.

If a user doesn't ask a question directly, the path to finding an answer to a product question often leads users to third-party developer forums. This usually happens when a user can’t find a solution within a product’s own docs or knowledge base.

The in-house community model

Companies like Shopify, Webflow, and Figma created successful, in-house communities by offering resources around their core product. Meaning, they heavily invested into the entire customer experience – and outranked even developer forums because of their usefulness.

But these communities were duct taped together by integrating third-party solutions. These services require extensive customization, send data to third parties, and can be expensive.

So why Squeak!?

PostHog started Squeak! as a productized version of the tools we use internally to build our own community. We outgrew using Slack as a community platform and wanted that content to be accessible to everyone.

Because we built these tools to align with our brand values, it’s led to a better customer experience, developed a more loyal community, and grown our brand stickiness.

We’ll continue to build these tools to solve our own customers needs, and we invite you to use them to solve yours.

What's next?

The roadmap lives on GitHub. We welcome your feedback.

Browse the roadmap on GitHub